<?xml version="1.0" encoding="utf-8" ?>

<rss version="2.0" 
   xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
   xmlns:admin="http://webns.net/mvcb/"
   xmlns:dc="http://purl.org/dc/elements/1.1/"
   xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
   xmlns:wfw="http://wellformedweb.org/CommentAPI/"
   xmlns:content="http://purl.org/rss/1.0/modules/content/"
   >
<channel>
    
    <title>blog.crox.net (Entries tagged as adsl)</title>
    <link>https://blog.crox.net/</link>
    <description></description>
    <dc:language>en</dc:language>
    <generator>Serendipity 2.5.0 - http://www.s9y.org/</generator>
    <pubDate>Thu, 16 Sep 2010 21:28:12 GMT</pubDate>

    <image>
    <url>https://blog.crox.net/templates/2k11/img/s9y_banner_small.png</url>
    <title>RSS: blog.crox.net - </title>
    <link>https://blog.crox.net/</link>
    <width>100</width>
    <height>21</height>
</image>

<item>
    <title>pfSense dropping packets from specific hosts (outdated bogons lists)</title>
    <link>https://blog.crox.net/archives/68-pfSense-dropping-packets-from-specific-hosts-outdated-bogons-lists.html</link>
    
    <comments>https://blog.crox.net/archives/68-pfSense-dropping-packets-from-specific-hosts-outdated-bogons-lists.html#comments</comments>
    <wfw:comment>https://blog.crox.net/wfwcomment.php?cid=68</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>https://blog.crox.net/rss.php?version=2.0&amp;type=comments&amp;cid=68</wfw:commentRss>
    

    <author>nospam@example.com (crox)</author>
    <content:encoded>
    After a fresh &lt;a href=&quot;http://www.pfsense.org/&quot;  title=&quot;pfSense&quot;&gt;pfSense&lt;/a&gt; install, I found out that traffic from specific hosts was being dropped when it should have been allowed based on the firewall rules I defined.&lt;br /&gt;
&lt;br /&gt;
It turned out that the option &quot;block bogon networks&quot; was activated on the WAN interface, and that fresh pfSense images come with a slightly outdated &lt;a href=&quot;http://en.wikipedia.org/wiki/Bogon_filtering&quot;  title=&quot;bogon&quot;&gt;bogon&lt;/a&gt; list.&lt;br /&gt;
&lt;br /&gt;
If you are facing this problem, you have three options:&lt;br /&gt;
&lt;br /&gt;
1. disable the &quot;Block bogon networks&quot; option at the bottom of the WAN interface page&lt;br /&gt;
&lt;br /&gt;
2. after at most one week, the list will be updated automatically as long as the box is online (there is a cron entry, grep your config file for bogon)&lt;br /&gt;
&lt;br /&gt;
3. if you don&#039;t want 1. and can&#039;t wait for 2, you can trigger the update process manually by running:&lt;pre&gt;/etc/rc.update_bogons.sh 0&lt;/pre&gt;Check the output from the Status -&gt; System Logs -&gt; System page (I ran it from a serial console, but it should work fine by ssh or from the exec.php page too)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
 
    </content:encoded>

    <pubDate>Thu, 16 Sep 2010 21:14:52 +0000</pubDate>
    <guid isPermaLink="false">https://blog.crox.net/archives/68-guid.html</guid>
    <category>adsl</category>
<category>network</category>
<category>pfsense</category>

</item>
<item>
    <title>Linksys WAG200G-EU stops routing UDP after a while (scripted reboot how-to)</title>
    <link>https://blog.crox.net/archives/31-Linksys-WAG200G-EU-stops-routing-UDP-after-a-while-scripted-reboot-how-to.html</link>
    
    <comments>https://blog.crox.net/archives/31-Linksys-WAG200G-EU-stops-routing-UDP-after-a-while-scripted-reboot-how-to.html#comments</comments>
    <wfw:comment>https://blog.crox.net/wfwcomment.php?cid=31</wfw:comment>

    <slash:comments>1</slash:comments>
    <wfw:commentRss>https://blog.crox.net/rss.php?version=2.0&amp;type=comments&amp;cid=31</wfw:commentRss>
    

    <author>nospam@example.com (crox)</author>
    <content:encoded>
    It seems that after having been up for a couple of days, the WAG200G starts having issues routing UDP packets properly. This particularly affects VoIP traffic (here IAX2 on port 4569). The symptoms are that &quot;regular surfing&quot; works flawlessly, but the registration with the asterisk server fails. &lt;a href=&quot;http://en.wikipedia.org/wiki/Tcpdump&quot;  title=&quot;tcpdump&quot;&gt;tcpdump&lt;/a&gt; shows no traffic on the server side. Restarting the WAG200G immediately solves the problem.&lt;br /&gt;
&lt;br /&gt;
Here is how I restarted the router from the command line:&lt;br /&gt;
&lt;pre&gt;wget --http-user=admin --http-password=pa55w0rd \&lt;br /&gt;     --post-data=&#039;reboot=1&amp;save=Enregistrer+les+param%E8tres&amp;todo=reboot&amp;h_reboot=1&amp;this_file=Reboot.htm&amp;next_file=index.htm&amp;message=&#039; \&lt;br /&gt;     http://192.168.0.1/setup.cgi&lt;/pre&gt;&lt;br /&gt;
(replace password and IP address as appropriate)&lt;br /&gt;
 
    </content:encoded>

    <pubDate>Fri, 07 Mar 2008 10:04:25 +0000</pubDate>
    <guid isPermaLink="false">https://blog.crox.net/archives/31-guid.html</guid>
    <category>adsl</category>
<category>linksys</category>
<category>network</category>
<category>wlan</category>

</item>

</channel>
</rss>
