<?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</title>
    <link>http://blog.crox.net/</link>
    <description></description>
    <dc:language>en</dc:language>
    <generator>Serendipity 1.6 - http://www.s9y.org/</generator>
    <pubDate>Fri, 20 Apr 2012 20:04:29 GMT</pubDate>

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

<item>
    <title>now with IPv6</title>
    <link>http://blog.crox.net/archives/77-now-with-IPv6.html</link>
    
    <comments>http://blog.crox.net/archives/77-now-with-IPv6.html#comments</comments>
    <wfw:comment>http://blog.crox.net/wfwcomment.php?cid=77</wfw:comment>

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

    <author>nospam@example.com (crox)</author>
    <content:encoded>
    In anticipation of &lt;a href=&quot;http://www.worldipv6day.org/&quot; title=&quot;World IPv6 Launch Day&quot;&gt;World IPv6 Launch Day&lt;/a&gt; (6 June 2012), this website is now fully reachable over IPv6. 
    </content:encoded>

    <pubDate>Mon, 30 Jan 2012 20:23:26 +0100</pubDate>
    <guid isPermaLink="false">http://blog.crox.net/archives/77-guid.html</guid>
    <category>ipv6</category>
<category>network</category>

</item>
<item>
    <title>IPv6 test websites</title>
    <link>http://blog.crox.net/archives/76-IPv6-test-websites.html</link>
    
    <comments>http://blog.crox.net/archives/76-IPv6-test-websites.html#comments</comments>
    <wfw:comment>http://blog.crox.net/wfwcomment.php?cid=76</wfw:comment>

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

    <author>nospam@example.com (crox)</author>
    <content:encoded>
    &lt;ul&gt;&lt;br /&gt;
&lt;li&gt;&lt;a href=&quot;http://ipv6-test.com/&quot;&gt;http://ipv6-test.com/&lt;/a&gt; (also has a speed test, &lt;a href=&quot;http://blog.crox.net/archives/75-Enabling-IPv6-Privacy-Extensions-on-all-interfaces-Ubuntu-Linux,-may-work-for-other-distros-too.html&quot;&gt;shows your MAC address when available&lt;/a&gt;)&lt;/li&gt;&lt;br /&gt;
&lt;li&gt;&lt;a href=&quot;http://test-ipv6.com/&quot;&gt;http://test-ipv6.com/&lt;/a&gt; (provides detailed technical info and &quot;readiness score&quot;)&lt;/li&gt;&lt;br /&gt;
&lt;li&gt;&lt;a href=&quot;http://whatismyv6.com/&quot;&gt;http://whatismyv6.com/&lt;/a&gt; (&lt;a href=&quot;http://ipv4.whatismyv6.com/&quot; &gt;IPv4 only&lt;/a&gt;, &lt;a href=&quot;http://ipv6.whatismyv6.com/&quot; &gt;IPv6 only&lt;/a&gt;)&lt;/li&gt;&lt;br /&gt;
&lt;li&gt;&lt;a href=&quot;http://www.whatismyipv6.net/&quot;&gt;http://www.whatismyipv6.net/&lt;/a&gt; (provides traceroute and ping, also suports IPv4)&lt;/li&gt;&lt;br /&gt;
&lt;/ul&gt; 
    </content:encoded>

    <pubDate>Mon, 23 Jan 2012 00:33:00 +0100</pubDate>
    <guid isPermaLink="false">http://blog.crox.net/archives/76-guid.html</guid>
    <category>ipv6</category>
<category>network</category>

</item>
<item>
    <title>Enabling IPv6 Privacy Extensions on all interfaces (Ubuntu Linux, may work for other distros too)</title>
    <link>http://blog.crox.net/archives/75-Enabling-IPv6-Privacy-Extensions-on-all-interfaces-Ubuntu-Linux,-may-work-for-other-distros-too.html</link>
    
    <comments>http://blog.crox.net/archives/75-Enabling-IPv6-Privacy-Extensions-on-all-interfaces-Ubuntu-Linux,-may-work-for-other-distros-too.html#comments</comments>
    <wfw:comment>http://blog.crox.net/wfwcomment.php?cid=75</wfw:comment>

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

    <author>nospam@example.com (crox)</author>
    <content:encoded>
    According to the &lt;a href=&quot;http://en.wikipedia.org/wiki/IPv6&quot;  title=&quot;IPv6&quot;&gt;Wikipedia IPv6 article&lt;/a&gt;, &lt;i&gt;Privacy extensions are, except for the Windows platform and Mac OS X since 10.7 as well as iOS since version 4.3, not enabled by default&lt;/i&gt;.&lt;br /&gt;
&lt;br /&gt;
In theory, one can enable the IPv6 Privacy Extensions on all interfaces at once using sysctl like this:&lt;pre&gt;sudo sysctl net.ipv6.conf.all.use_tempaddr=2&lt;/pre&gt;&lt;br /&gt;
However, this currently doesn&#039;t work as expected, so I&#039;m using this one-liner in /etc/rc.local:&lt;pre&gt;for IF in `/bin/ls /proc/sys/net/ipv6/conf/*/use_tempaddr` ; do echo 2 &gt; $IF ; done&lt;/pre&gt;&lt;br /&gt;
This also sets &quot;use_tempaddr&quot; for &quot;default&quot;, which means it should also apply to interfaces added to the system afterwards.&lt;br /&gt;
&lt;br /&gt;
A simple check to verify that the new configuration is working: &lt;a href=&quot;http://ipv6-test.com/&quot;  title=&quot;ipv6-test.com&quot;&gt;ipv6-test.com&lt;/a&gt; will print your MAC address when available...&lt;br /&gt;
&lt;br /&gt;
See also: &lt;a href=&quot;https://bugzilla.kernel.org/show_bug.cgi?id=11655&quot; &gt;Linux Kernel Bug 11655&lt;/a&gt;&lt;br /&gt;
&lt;br/&gt; 
    </content:encoded>

    <pubDate>Mon, 23 Jan 2012 00:22:01 +0100</pubDate>
    <guid isPermaLink="false">http://blog.crox.net/archives/75-guid.html</guid>
    <category>ipv6</category>
<category>kernel</category>
<category>linux</category>
<category>network</category>
<category>ubuntu</category>

</item>
<item>
    <title>VaudTax 2010 avec Ubuntu linux 64-bit</title>
    <link>http://blog.crox.net/archives/74-VaudTax-2010-avec-Ubuntu-linux-64-bit.html</link>
    
    <comments>http://blog.crox.net/archives/74-VaudTax-2010-avec-Ubuntu-linux-64-bit.html#comments</comments>
    <wfw:comment>http://blog.crox.net/wfwcomment.php?cid=74</wfw:comment>

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

    <author>nospam@example.com (crox)</author>
    <content:encoded>
    &lt;a href=&quot;http://www.vd.ch/fileadmin/user_upload/organisation/dfin/aci/fichiers_pdf/Tutoriel-Linux-Mozilla_2010.pdf&quot; &gt;Les instructions pour Linux fournies sur le site officiel&lt;/a&gt; ne fonctionnent pas pour moi (Maverick / Ubuntu 10.10 desktop amd64).&lt;br /&gt;
&lt;br /&gt;
Il semble qu&#039;il ne soit toujours pas possible d&#039;importer des fichiers sauvegardés dans une version 32 bit de VaudTax avec la version 64 bits, et vice-versa (crash de VaudTax avec une erreur cryptique [1]). Deux options, soit recommencer sa déclaration sans importer les données de l&#039;année précédente, soit faire tourner VaudTax avec une JVM 32-bits ([2]). Pour l&#039;instant j&#039;ai toujours opté pour la deuxième variante. Jusqu&#039;à l&#039;année passée (VaudTax2009), on pouvait télécharger une version incluant une JVM (32-bits), cette option n&#039;est plus disponible mais il est toujours possible d&#039;arriver au même résultat :&lt;br /&gt;
&lt;br /&gt;
1ère étape, avant de commencer le processus d&#039;installation :&lt;pre&gt;$ sudo update-alternatives --config java&lt;br /&gt;There are 3 choices for the alternative java (providing /usr/bin/java).&lt;br /&gt;&lt;br /&gt;  Selection    Path                                       Priority   Status&lt;br /&gt;------------------------------------------------------------&lt;br /&gt;* 0            /usr/lib/jvm/java-6-openjdk/jre/bin/java    1061      auto mode&lt;br /&gt;  1            /usr/lib/jvm/ia32-java-6-sun/jre/bin/java   63        manual mode&lt;br /&gt;  2            /usr/lib/jvm/java-6-openjdk/jre/bin/java    1061      manual mode&lt;br /&gt;  3            /usr/lib/jvm/java-6-sun/jre/bin/java        63        manual mode&lt;br /&gt;&lt;br /&gt;Press enter to keep the current choice[*], or type selection number: 1&lt;br /&gt;update-alternatives: using /usr/lib/jvm/ia32-java-6-sun/jre/bin/java to provide /usr/bin/java (java) in manual mode.&lt;/pre&gt;&lt;br /&gt;
(si l&#039;option JVM 32-bits n&#039;apparaît pas, il faut d&#039;abord installer le paquet ia32-sun-java6-bin)&lt;br /&gt;
&lt;br /&gt;
Une fois VaudTax installé, il faut télécharger et décompacter xulrunner :&lt;pre&gt;$ cd $HOME/VaudTax2010&lt;br /&gt;$ wget http://releases.mozilla.org/pub/mozilla.org/xulrunner/releases/1.9.2.16/runtimes/xulrunner-1.9.2.16.en-US.linux-i686.tar.bz2&lt;br /&gt;$ tar -xpf xulrunner-*&lt;/pre&gt;&lt;br /&gt;
Finalement, il faut encore modifier le fichier VaudTax2010 en ajoutant ces deux lignes juste après `VM_SEARCH_PATH=&quot;$PATH&quot;&#039; :&lt;pre&gt;export MOZILLA_FIVE_HOME=$HOME/VaudTax2010/xulrunner&lt;br /&gt;export LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:${MOZILLA_FIVE_HOME}&lt;/pre&gt;&lt;br /&gt;
&lt;br /&gt;
Note : une fois VaudTax2010 installé, on peut exécuter à nouveau &quot;sudo update-alternatives --config java&quot; pour rétablir la configuration initiale - les paramètres sont en effet enregistrés dans le fichier VaudTax2010.lax&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[1] &lt;pre&gt;The program &#039;SWT&#039; received an X Window System error.&lt;br /&gt;This probably reflects a bug in the program.&lt;br /&gt;The error was &#039;RenderBadPicture (invalid Picture parameter)&#039;.&lt;br /&gt;  (Details: serial 5455 error_code 161 request_code 149 minor_code 7)&lt;br /&gt;  (Note to programmers: normally, X errors are reported asynchronously;&lt;br /&gt;   that is, you will receive the error a while after causing it.&lt;br /&gt;   To debug your program, run it with the --sync command line&lt;br /&gt;   option to change this behavior. You can then get a meaningful&lt;br /&gt;   backtrace from your debugger if you break on the gdk_x_error() function.)&lt;/pre&gt;&lt;br /&gt;
[2] la troisième variante serait d&#039;étudier le format de fichier produit par chacune des versions pour créer un outil de conversion 
    </content:encoded>

    <pubDate>Mon, 18 Apr 2011 17:07:21 +0200</pubDate>
    <guid isPermaLink="false">http://blog.crox.net/archives/74-guid.html</guid>
    <category>linux</category>
<category>ubuntu</category>
<category>vaudtax</category>

</item>
<item>
    <title>bash: how to send output to the console and through a pipe at the same time with tee</title>
    <link>http://blog.crox.net/archives/73-bash-how-to-send-output-to-the-console-and-through-a-pipe-at-the-same-time-with-tee.html</link>
    
    <comments>http://blog.crox.net/archives/73-bash-how-to-send-output-to-the-console-and-through-a-pipe-at-the-same-time-with-tee.html#comments</comments>
    <wfw:comment>http://blog.crox.net/wfwcomment.php?cid=73</wfw:comment>

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

    <author>nospam@example.com (crox)</author>
    <content:encoded>
    Let&#039;s say you want some output to be echoed to the console but also to be passed to a pipe. Specifically, in my case I wanted a message to be displayed to the user and also to be sent to syslog. You could of course just print it twice, but in some cases it&#039;s not possible, or it makes it more complicated than it should be.&lt;br /&gt;
&lt;br /&gt;
There is a simple solution with tee: &lt;pre&gt;echo &quot;a test&quot; | tee &gt;(logger)&lt;/pre&gt;&lt;br /&gt;
 
    </content:encoded>

    <pubDate>Fri, 01 Apr 2011 16:51:51 +0200</pubDate>
    <guid isPermaLink="false">http://blog.crox.net/archives/73-guid.html</guid>
    <category>linux</category>
<category>shell</category>

</item>
<item>
    <title>gulp - tcpdump alternative for lossless capture on Linux</title>
    <link>http://blog.crox.net/archives/72-gulp-tcpdump-alternative-for-lossless-capture-on-Linux.html</link>
    
    <comments>http://blog.crox.net/archives/72-gulp-tcpdump-alternative-for-lossless-capture-on-Linux.html#comments</comments>
    <wfw:comment>http://blog.crox.net/wfwcomment.php?cid=72</wfw:comment>

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

    <author>nospam@example.com (crox)</author>
    <content:encoded>
    &lt;a href=&quot;http://www.tcpdump.org/&quot; &gt;tcpdump&lt;/a&gt; and &lt;a href=&quot;http://www.wireshark.org/&quot; &gt;wireshark&lt;/a&gt; are the tools that usually come to mind when you have to capture network traffic. But in some situations where you have to record a large amount of data and you want to avoid losing packets, tcpdump has some limitations. When I was hit myself by the tcpdump packet loss problem, I quickly found out that I was not alone and that a number of people had already researched the topic and/or provided alternatives.&amp;#42;&lt;br /&gt;
&lt;br /&gt;
In particular, I found two different tools to perform the task: Corey Satten&#039;s gulp (&lt;a href=&quot;http://corey.elsewhere.org/gulp/&quot; &gt;http://corey.elsewhere.org/gulp/&lt;/a&gt;) and lindump from HP Labs (&lt;a href=&quot;http://tesla.hpl.hp.com/opensource/&quot; &gt;http://tesla.hpl.hp.com/opensource/&lt;/a&gt;)&lt;br /&gt;
&lt;br /&gt;
I also found two interesting papers about capturing high volumes of traffic: &lt;a href=&quot;http://www.usenix.org/events/fast09/tech/full_papers/anderson/anderson_html/&quot; &gt;http://www.usenix.org/events/fast09/tech/full_papers/anderson/anderson_html/&lt;/a&gt; and &lt;a href=&quot;http://docs.di.fc.ul.pt/jspui/bitstream/10455/3299/1/thesis-nhenriqu.pdf&quot; &gt;http://docs.di.fc.ul.pt/jspui/bitstream/10455/3299/1/thesis-nhenriqu.pdf&lt;/a&gt; (the second quotes the first one among others, and also contains useful info to optimally spread the load among different cores)&lt;br /&gt;
&lt;br /&gt;
After some tests I quickly became a happy gulp user, and thanks to the software being open source I was able to add features to it that I missed from the latest tcpdump versions:&lt;br /&gt;
&lt;br /&gt;
-n - allows to change the default filename template&lt;br /&gt;
-t - allows to add a timestamp to the filename&lt;br /&gt;
-G - rotate pcap file every n seconds&lt;br /&gt;
-F - allows to skip the check for an ethernet interface&lt;br /&gt;
&lt;br /&gt;
I&#039;ve sent a patch to Corey Satten, who intends to setup a repository to hold the various contributions he gets for gulp. In the meanwhile, you can find my changes in the attached file (&lt;a href=&quot;http://blog.crox.net/uploads/02-gulp-ntGF.patch.gz&quot; title=&quot;02-gulp-ntGF.patch.gz&quot; target=&quot;_blank&quot;&gt;02-gulp-ntGF.patch.gz&lt;/a&gt;). For your convenience and for completeness, I also provide here &lt;a href=&quot;http://blog.crox.net/uploads/01-gulp-amd64.patch.gz&quot; title=&quot;01-gulp-amd64.patch.gz&quot; target=&quot;_blank&quot;&gt;the patch from Guy Harris that fixes issues on 64 bit systems&lt;/a&gt; (see &lt;a href=&quot;http://seclists.org/wireshark/2009/Oct/105&quot; &gt;http://seclists.org/wireshark/2009/Oct/105&lt;/a&gt;, apply that one first).&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;#42; other people have reported a performance drop with libpcap version 1.0 compared to previous builds, see &lt;a href=&quot;http://thread.gmane.org/gmane.network.tcpdump.devel/4629&quot; &gt;http://thread.gmane.org/gmane.network.tcpdump.devel/4629&lt;/a&gt; or &lt;a href=&quot;http://seclists.org/tcpdump/2010/q3/index.html#11&quot; &gt;http://seclists.org/tcpdump/2010/q3/index.html#11&lt;/a&gt;&lt;br /&gt;
 
    </content:encoded>

    <pubDate>Mon, 28 Feb 2011 00:37:54 +0100</pubDate>
    <guid isPermaLink="false">http://blog.crox.net/archives/72-guid.html</guid>
    <category>linux</category>
<category>network</category>

</item>
<item>
    <title>Linux: enable encrypted swap (Ubuntu / Debian)</title>
    <link>http://blog.crox.net/archives/71-Linux-enable-encrypted-swap-Ubuntu-Debian.html</link>
    
    <comments>http://blog.crox.net/archives/71-Linux-enable-encrypted-swap-Ubuntu-Debian.html#comments</comments>
    <wfw:comment>http://blog.crox.net/wfwcomment.php?cid=71</wfw:comment>

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

    <author>nospam@example.com (crox)</author>
    <content:encoded>
    1. create and enable a &quot;regular&quot; swap partition (fdisk / mkswap / swapon)&lt;br /&gt;
&lt;br /&gt;
2. install ecryptfs-utils and run ecryptfs-setup-swap&lt;br /&gt;
&lt;pre&gt;sudo apt-get install ecryptfs-utils&lt;br /&gt;sudo ecryptfs-setup-swap&lt;/br&gt;&lt;br /&gt;
 
    </content:encoded>

    <pubDate>Mon, 15 Nov 2010 22:40:37 +0100</pubDate>
    <guid isPermaLink="false">http://blog.crox.net/archives/71-guid.html</guid>
    <category>encryption</category>
<category>linux</category>
<category>ubuntu</category>

</item>
<item>
    <title>Thunderbird - change default message forward mode from &quot;inline&quot; to &quot;attached&quot;</title>
    <link>http://blog.crox.net/archives/70-Thunderbird-change-default-message-forward-mode-from-inline-to-attached.html</link>
    
    <comments>http://blog.crox.net/archives/70-Thunderbird-change-default-message-forward-mode-from-inline-to-attached.html#comments</comments>
    <wfw:comment>http://blog.crox.net/wfwcomment.php?cid=70</wfw:comment>

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

    <author>nospam@example.com (crox)</author>
    <content:encoded>
    For years the default behaviour in Thunderbird had been to forward e-mails as attachments, but at some point it was changed to &quot;inline&quot;. You can still manually choose how you&#039;d like to transfer a message by going to &quot;Message&quot; -&gt; &quot;Forward as&quot;, but I couldn&#039;t find a way to set the default in the preferences.&lt;br /&gt;
&lt;br /&gt;
There is, however, a way to change it without messing with manual edit of config files. Go to &quot;Preferences&quot; -&gt; &quot;Advanced&quot; -&gt; &quot;Config Editor...&quot;, and look for &quot;mail.forward_message_mode&quot;. 0 is for &quot;attached&quot;, 2 is for &quot;inline&quot;.&lt;br /&gt;
 
    </content:encoded>

    <pubDate>Sun, 10 Oct 2010 20:48:42 +0200</pubDate>
    <guid isPermaLink="false">http://blog.crox.net/archives/70-guid.html</guid>
    <category>mail</category>
<category>thunderbird</category>

</item>
<item>
    <title>hping - [send_icmp] Unsupported icmp type</title>
    <link>http://blog.crox.net/archives/69-hping-send_icmp-Unsupported-icmp-type.html</link>
    
    <comments>http://blog.crox.net/archives/69-hping-send_icmp-Unsupported-icmp-type.html#comments</comments>
    <wfw:comment>http://blog.crox.net/wfwcomment.php?cid=69</wfw:comment>

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

    <author>nospam@example.com (crox)</author>
    <content:encoded>
    When performing tests you may sometimes want to send specially crafted &lt;a href=&quot;http://en.wikipedia.org/wiki/Internet_Control_Message_Protocol&quot;  title=&quot;ICMP&quot;&gt;icmp&lt;/a&gt; packets. &lt;a href=&quot;http://www.hping.org/&quot;  title=&quot;hping&quot;&gt;hping&lt;/a&gt; is a handy tool for that.&lt;br /&gt;
&lt;br /&gt;
However, the default behavior is to refuse to send &quot;unsupported&quot; Type/Code combinations. eg&lt;pre&gt;hping3 -c 1 --icmp -C 33 -K 0 192.168.70.1&lt;br /&gt;HPING 192.168.70.1 (wlan0 192.168.70.10): icmp mode set, 28 headers + 0 data bytes&lt;br /&gt;[send_icmp] Unsupported icmp type!&lt;/pre&gt;&lt;br /&gt;
Fortunately, there is an (undocumented) --force-icmp option that you can add to bypass the check:&lt;pre&gt;hping3 -c 1 --icmp --force-icmp -C 33 -K 0 192.168.70.1&lt;br /&gt;HPING 192.168.70.1 (wlan0 192.168.70.10): icmp mode set, 28 headers + 0 data bytes&lt;br /&gt;&lt;br /&gt;--- 192.168.70.1 hping statistic ---&lt;br /&gt;1 packets transmitted, 0 packets received, 100% packet loss&lt;br /&gt;round-trip min/avg/max = 0.0/0.0/0.0 ms&lt;/pre&gt;&lt;br /&gt;
 
    </content:encoded>

    <pubDate>Fri, 17 Sep 2010 22:47:01 +0200</pubDate>
    <guid isPermaLink="false">http://blog.crox.net/archives/69-guid.html</guid>
    <category>linux</category>
<category>network</category>

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

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://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 23:14:52 +0200</pubDate>
    <guid isPermaLink="false">http://blog.crox.net/archives/68-guid.html</guid>
    <category>adsl</category>
<category>network</category>
<category>pfsense</category>

</item>
<item>
    <title>Numéro pour vérifier la présélection téléphonique (opérateurs en Suisse)</title>
    <link>http://blog.crox.net/archives/66-Numero-pour-verifier-la-preselection-telephonique-operateurs-en-Suisse.html</link>
    
    <comments>http://blog.crox.net/archives/66-Numero-pour-verifier-la-preselection-telephonique-operateurs-en-Suisse.html#comments</comments>
    <wfw:comment>http://blog.crox.net/wfwcomment.php?cid=66</wfw:comment>

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

    <author>nospam@example.com (crox)</author>
    <content:encoded>
    Composer le 0868 868 868.&lt;br /&gt;
 
    </content:encoded>

    <pubDate>Wed, 16 Jun 2010 00:53:20 +0200</pubDate>
    <guid isPermaLink="false">http://blog.crox.net/archives/66-guid.html</guid>
    <category>isdn</category>
<category>phone</category>

</item>
<item>
    <title>Scanner permissions in Ubuntu Karmic (udev libusb saned problem with udev-acl)</title>
    <link>http://blog.crox.net/archives/64-Scanner-permissions-in-Ubuntu-Karmic-udev-libusb-saned-problem-with-udev-acl.html</link>
    
    <comments>http://blog.crox.net/archives/64-Scanner-permissions-in-Ubuntu-Karmic-udev-libusb-saned-problem-with-udev-acl.html#comments</comments>
    <wfw:comment>http://blog.crox.net/wfwcomment.php?cid=64</wfw:comment>

    <slash:comments>3</slash:comments>
    <wfw:commentRss>http://blog.crox.net/rss.php?version=2.0&amp;type=comments&amp;cid=64</wfw:commentRss>
    

    <author>nospam@example.com (crox)</author>
    <content:encoded>
    In Ubuntu Karmic (and possibly Jaunty ?), when you install libsane, it adds a file /lib/udev/rules.d/40-libsane.rules which contains rules that match on supported scanners and set the environment variable &quot;libsane_matched&quot; to &quot;yes&quot;.&lt;br /&gt;
&lt;br /&gt;
This in turn triggers the following in /lib/udev/rules.d/70-acl.rules:&lt;br /&gt;
&lt;pre&gt;# USB scanners&lt;br /&gt;ENV{libsane_matched}==&quot;yes&quot;, ENV{ACL_MANAGE}=&quot;1&quot;&lt;br /&gt;
&amp;lt;snip&amp;gt;&lt;br /&gt;
# apply ACL for all locally logged in users&lt;br /&gt;LABEL=&quot;acl_apply&quot;, ENV{ACL_MANAGE}==&quot;?*&quot;, TEST==&quot;/var/run/ConsoleKit/database&quot;, \&lt;br /&gt;  RUN+=&quot;udev-acl --action=$env{ACTION} --device=$env{DEVNAME}&quot;&lt;/pre&gt;&lt;br /&gt;
In the end, the result is that an ACL is created for the device, which allows locally logged in users to use it (read/write permission). eg for my scanner:&lt;br /&gt;
&lt;pre&gt;~# lsusb&lt;br /&gt;Bus 001 Device 005: ID 04b8:011c Seiko Epson Corp. Perfection 3200&lt;br /&gt;~# ls -l /dev/bus/usb/001/005&lt;br /&gt;crw-rw-r--+ 1 root root 189, 4 2009-12-28 00:11 /dev/bus/usb/001/005&lt;br /&gt;~# getfacl /dev/bus/usb/001/005&lt;br /&gt;getfacl: Removing leading &#039;/&#039; from absolute path names&lt;br /&gt;# file: dev/bus/usb/001/005&lt;br /&gt;# owner: root&lt;br /&gt;# group: root&lt;br /&gt;user::rw-&lt;br /&gt;user:crox:rw-&lt;br /&gt;group::rw-&lt;br /&gt;mask::rw-&lt;br /&gt;other::r--&lt;br /&gt;~#&lt;/pre&gt;&lt;br /&gt;
However, I also wanted to allow access to the scanner from other workstations through saned. In older Ubuntu versions, you could just add saned (or whatever user the service runs as) to the scanner group. This no longer works since the device belongs to root:root, and ACLs are added for specific users. The solution that works for me is to create a file /etc/udev/rules.d/99-sane-group.rules with the following contents:&lt;br /&gt;
&lt;pre&gt;# change group to scanner for sane devices&lt;br /&gt;ENV{libsane_matched}==&quot;yes&quot;, GROUP=&quot;scanner&quot;&lt;/pre&gt;&lt;br /&gt;
Then you just need to run &lt;pre&gt;sudo udevadm trigger&lt;/pre&gt; and the group of the device magically changes to scanner.&lt;br /&gt;
&lt;br /&gt;
Of course you could also add a similar rule specifically for a certain device instead, in my case this would work too:&lt;br /&gt;
&lt;pre&gt;ATTRS{idVendor}==&quot;1d6b&quot;, ATTRS{idProduct}==&quot;0002&quot;, GROUP=&quot;scanner&quot;&lt;/pre&gt;&lt;br /&gt;
&lt;br /&gt;
To check that it worked, run the following: &lt;pre&gt;sudo su -s /bin/bash -c &#039;scanimage -L&#039; saned&lt;/pre&gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
 
    </content:encoded>

    <pubDate>Mon, 28 Dec 2009 00:13:00 +0100</pubDate>
    <guid isPermaLink="false">http://blog.crox.net/archives/64-guid.html</guid>
    <category>linux</category>
<category>scanner</category>
<category>ubuntu</category>

</item>
<item>
    <title>Making a Dell computer running Linux silent (Dell Precision noise problem)</title>
    <link>http://blog.crox.net/archives/60-Making-a-Dell-computer-running-Linux-silent-Dell-Precision-noise-problem.html</link>
    
    <comments>http://blog.crox.net/archives/60-Making-a-Dell-computer-running-Linux-silent-Dell-Precision-noise-problem.html#comments</comments>
    <wfw:comment>http://blog.crox.net/wfwcomment.php?cid=60</wfw:comment>

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

    <author>nospam@example.com (crox)</author>
    <content:encoded>
    Faced with a noisy Dell Precision 490 computer running Ubuntu Karmic, I found an easy way to reduce the noise level to an acceptable threshold. (fancontrol did not help since it seems not to be compatible with the chipset used by Dell at least on this computer.)&lt;br /&gt;
&lt;br /&gt;
Step 1, install i8kutils:&lt;pre&gt;sudo apt-get install i8kutils&lt;/pre&gt;&lt;br /&gt;
Step 2, add i8k to /etc/modules: &lt;pre&gt;sudo sh -c &#039;echo i8k &gt;&gt; /etc/modules&#039;&lt;/pre&gt;&lt;br /&gt;
Step 3, edit /etc/default/i8kmon so that it looks like this:&lt;br /&gt;
&lt;pre&gt;# /etc/default/i8kmon&lt;br /&gt;
&lt;br /&gt;
# Change to one enable i8kmon&lt;br /&gt;
ENABLED=1&lt;br /&gt;
I8KMON_ARGS=&quot;--daemon --nouserconfig --auto&quot;&lt;br /&gt;
&lt;/pre&gt;&lt;br /&gt;
Step 4, reboot and enjoy!&lt;br /&gt;
&lt;br /&gt;
 
    </content:encoded>

    <pubDate>Thu, 10 Dec 2009 21:05:09 +0100</pubDate>
    <guid isPermaLink="false">http://blog.crox.net/archives/60-guid.html</guid>
    <category>dell</category>
<category>linux</category>
<category>ubuntu</category>

</item>
<item>
    <title>SIP support in Nokia phones (S60 VoIP / S40 VoIP)</title>
    <link>http://blog.crox.net/archives/59-SIP-support-in-Nokia-phones-S60-VoIP-S40-VoIP.html</link>
    
    <comments>http://blog.crox.net/archives/59-SIP-support-in-Nokia-phones-S60-VoIP-S40-VoIP.html#comments</comments>
    <wfw:comment>http://blog.crox.net/wfwcomment.php?cid=59</wfw:comment>

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

    <author>nospam@example.com (crox)</author>
    <content:encoded>
    Thanks to &lt;a href=&quot;http://luca.lovalvo.net/&quot;  title=&quot;Luca Lo Valvo&quot;&gt;Luca&lt;/a&gt; who provided me with a link to this table detailing &lt;a href=&quot;http://www.forum.nokia.com/Technology_Topics/Mobile_Technologies/VoIP/Nokia_VoIP_Framework/VoIP_support_in_Nokia_devices.xhtml&quot;  title=&quot;VoIP support in Nokia devices&quot;&gt;VoIP (SIP) support in Nokia devices&lt;/a&gt;. 
    </content:encoded>

    <pubDate>Wed, 02 Dec 2009 22:31:46 +0100</pubDate>
    <guid isPermaLink="false">http://blog.crox.net/archives/59-guid.html</guid>
    <category>n80</category>
<category>nokia</category>
<category>phone</category>
<category>voip</category>

</item>
<item>
    <title>Patch for mISDN-1_1_9_2 to support the Eicon DIVA USB ISDN adapter (071d:1005 mISDN)</title>
    <link>http://blog.crox.net/archives/58-Patch-for-mISDN-1_1_9_2-to-support-the-Eicon-DIVA-USB-ISDN-adapter-071d1005-mISDN.html</link>
    
    <comments>http://blog.crox.net/archives/58-Patch-for-mISDN-1_1_9_2-to-support-the-Eicon-DIVA-USB-ISDN-adapter-071d1005-mISDN.html#comments</comments>
    <wfw:comment>http://blog.crox.net/wfwcomment.php?cid=58</wfw:comment>

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

    <author>nospam@example.com (crox)</author>
    <content:encoded>
    This is a copy of a post I made to the &lt;a href=&quot;https://www.isdn4linux.de/mailman/listinfo/isdn4linux&quot; title=&quot;isdn4linux mailing-list&quot;&gt;isdn4linux mailing-list&lt;/a&gt;.&lt;br /&gt;
&lt;br /&gt;
The attached patch adds support to mISDN-1_1_9_2 for the Eicon DIVA USB ISDN adapter (071d:1005).&lt;br /&gt;
&lt;br /&gt;
The bits I&#039;ve added to hfcs_usb.c are from kernel 2.6.31. So far the adapter works fine for me (tested with 1 and 2 concurrent calls to asterisk 1.4.26.1 with chan_misdn).&lt;br /&gt;
&lt;br /&gt;
You can get the patch here: &lt;a href=&quot;http://blog.crox.net/uploads/misdn-1.1.9.2-Eicon-Diva-USB.patch&quot; title=&quot;misdn-1.1.9.2-Eicon-Diva-USB.patch&quot; target=&quot;_blank&quot;&gt;misdn-1.1.9.2-Eicon-Diva-USB.patch&lt;/a&gt;.&lt;br /&gt;
&lt;br /&gt;
Comments are set to &quot;moderated&quot; for this entry, please consider whether you should rather post to the &lt;a href=&quot;https://www.isdn4linux.de/mailman/listinfo/isdn4linux&quot; title=&quot;isdn4linux mailing-list&quot;&gt;list&lt;/a&gt;.&lt;br /&gt;
 
    </content:encoded>

    <pubDate>Tue, 22 Sep 2009 23:25:33 +0200</pubDate>
    <guid isPermaLink="false">http://blog.crox.net/archives/58-guid.html</guid>
    <category>isdn</category>
<category>kernel</category>
<category>linux</category>

</item>

</channel>
</rss>
