<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Network on To Linux and beyond !</title>
    <link>https://home.regit.org/tags/network/</link>
    <description>Recent content in Network on To Linux and beyond !</description>
    <generator>Hugo</generator>
    <language>fr</language>
    <lastBuildDate>Thu, 17 Apr 2014 14:11:58 +0000</lastBuildDate>
    <atom:link href="https://home.regit.org/feed/tags/network/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Speeding up scapy packets sending</title>
      <link>https://home.regit.org/2014/04/speeding-up-scapy-packets-sending/</link>
      <pubDate>Thu, 17 Apr 2014 14:11:58 +0000</pubDate>
      <guid>https://home.regit.org/2014/04/speeding-up-scapy-packets-sending/</guid>
      <description>&lt;h4 id=&#34;sending-packets-with-scapy&#34;&gt;Sending packets with scapy&lt;/h4&gt;
&lt;p&gt;I’m currently doing some code based on &lt;a href=&#34;http://www.secdev.org/projects/scapy/&#34;&gt;scapy&lt;/a&gt;. This code reads data from a possibly huge file and send a packet for each line in the file using the contained information.&lt;br&gt;
So the code contains a simple loop and uses sendp because the frame must be sent at layer 2.&lt;/p&gt;
&lt;pre&gt;def run(self):
         filedesc = open(self.filename, &#39;r&#39;)
         # loop on read line
         for line in filedesc:
             # Build and send packet
             sendp(pkt, iface = self.iface, verbose = verbose)
             # Inter packet treatment
&lt;/pre&gt;
&lt;p&gt;Doing that the performance are a bit deceptive. For 18 packets, we’ve got:&lt;/p&gt;</description>
    </item>
    <item>
      <title>A bit of fun with IPv6 setup</title>
      <link>https://home.regit.org/2013/09/a-bit-of-fun-with-ipv6-setup/</link>
      <pubDate>Thu, 26 Sep 2013 09:28:38 +0000</pubDate>
      <guid>https://home.regit.org/2013/09/a-bit-of-fun-with-ipv6-setup/</guid>
      <description>&lt;p&gt;When doing some tests on &lt;a href=&#34;http://suricata-ids.org/&#34;&gt;Suricata&lt;/a&gt;, I needed to setup a small IPv6 network. The setup is simple with one laptop which is Ethernet connected to a desktop. And the desktop host a Virtualbox system.&lt;br&gt;
This way, the desktop can act as a router with laptop on eth0 and Vbox on vboxnet0.&lt;/p&gt;
&lt;p&gt;To setup the desktop/router, I’ve used:&lt;/p&gt;
&lt;pre&gt;ip a a 4::1/64 dev eth0
ip a a 2::1/64 dev vboxnet0
echo &#34;1&#34;&gt;/proc/sys/net/ipv6/conf/all/forwarding
&lt;/pre&gt;
&lt;p&gt;To setup the laptop who already has a IPv6 public address on eth0, I’ve done:&lt;/p&gt;</description>
    </item>
    <item>
      <title>Talk about nftables at Kernel Recipes 2013</title>
      <link>https://home.regit.org/2013/09/talk-about-nftables-at-kernel-recipes-2013/</link>
      <pubDate>Tue, 24 Sep 2013 13:48:19 +0000</pubDate>
      <guid>https://home.regit.org/2013/09/talk-about-nftables-at-kernel-recipes-2013/</guid>
      <description>&lt;p&gt;I’ve just gave a talk about nftables, the iptables successor, at &lt;a href=&#34;https://kernel-recipes.org/fr/2013/&#34;&gt;Kernel Recipes 2013&lt;/a&gt;. You can find the slides here:&lt;br&gt;
&lt;a href=&#34;https://home.regit.org/uploads/2013/09/2013_kernel_recipes_nftables.pdf&#34;&gt;2013_kernel_recipes_nftables&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;A description of the talk as well as slides and video are available on &lt;a href=&#34;https://kernel-recipes.org/en/2013/nftables-what-motivations-and-what-solutions/&#34;&gt;Kernel Recipes website&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Here’s the video of my talk:&lt;/p&gt;
&lt;p&gt;I’ve presented a video of nftables source code evolution:&lt;/p&gt;
&lt;p&gt;The video has been generated with &lt;a href=&#34;https://code.google.com/p/gource/&#34;&gt;gource&lt;/a&gt;. Git history of various components have been merged and the file path has been prefixed with project name.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Using tc with IPv6 and IPv4</title>
      <link>https://home.regit.org/2013/09/using-tc-with-ipv6-and-ipv4/</link>
      <pubDate>Wed, 18 Sep 2013 12:57:21 +0000</pubDate>
      <guid>https://home.regit.org/2013/09/using-tc-with-ipv6-and-ipv4/</guid>
      <description>&lt;p&gt;The first news is that &lt;a href=&#34;http://comments.gmane.org/gmane.linux.network/233164&#34;&gt;it works&lt;/a&gt;! It is possible to use tc to setup QoS on IPv6 but the filter have to be updated.&lt;/p&gt;
&lt;p&gt;When working on adding IPv6 support to &lt;a href=&#34;https://github.com/regit/lagfactory&#34;&gt;lagfactory&lt;/a&gt;, I found out by reading tc sources and specifically &lt;a href=&#34;https://github.com/SVMP/android_external_busybox/blob/master/networking/libiproute/ll_proto.c&#34;&gt;ll_proto.c&lt;/a&gt; that the keyword to use for IPv6 was &lt;em&gt;ipv6&lt;/em&gt;. Please read that file if you need to find the keyword for an other protocol.&lt;br&gt;
So to send packet with Netfilter mark 5000 to a specific queue, one can use:&lt;/p&gt;</description>
    </item>
    <item>
      <title>Netfilter and the NAT of ICMP error messages</title>
      <link>https://home.regit.org/2013/04/netfilter-and-icmp-error-messages/</link>
      <pubDate>Wed, 24 Apr 2013 22:30:00 +0000</pubDate>
      <guid>https://home.regit.org/2013/04/netfilter-and-icmp-error-messages/</guid>
      <description>&lt;h4 id=&#34;the-problem&#34;&gt;The problem&lt;/h4&gt;
&lt;p&gt;I’ve been recently working for a customer which needed consultancy because of some unexplained &lt;a href=&#34;http://www.netfilter.org&#34;&gt;Netfilter&lt;/a&gt; behaviors related to ICMP error messages. He authorizes me to share the result of my study and I thank him for making this blog entry possible.&lt;br&gt;
His problem was that one of his firewalls is using a private interconnexion with their border router and the customer did not manage to NAT all outgoing ICMP error messages.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Tomasz Bursztyka, connMan usage of Netfilter</title>
      <link>https://home.regit.org/2013/03/tomasz-bursztyka-connman-usage-of-netfilter/</link>
      <pubDate>Tue, 12 Mar 2013 12:52:16 +0000</pubDate>
      <guid>https://home.regit.org/2013/03/tomasz-bursztyka-connman-usage-of-netfilter/</guid>
      <description>&lt;h4 id=&#34;introduction&#34;&gt;Introduction&lt;/h4&gt;
&lt;p&gt;&lt;a href=&#34;http://connman.net/&#34;&gt;connMan&lt;/a&gt; is a network manager which has support for a lot of different layers from ethernet and WiFi to NFC and link sharing.&lt;/p&gt;
&lt;p&gt;It features automatic link switch and allow you to select your preferred type of support. The communication with UI is event based so it is easy to do as only a few windows type are needed.&lt;/p&gt;
&lt;h4 id=&#34;discussion&#34;&gt;Discussion&lt;/h4&gt;
&lt;p&gt;David Miller pointed out the fact that DHCP client is really often putting the interface in promiscuous mode and this is not a good idea as it is like having a tcpdump started on every laptop. As connMann does ahave its own implementation, they could maybe take this into account and improved the situation. This is in fact already the case as the DHCP client is using an alternate method.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Simon Horman, MPLS Enlightened Open vSwitch</title>
      <link>https://home.regit.org/2013/03/simon-horman-mpls-enlightened-open-vswitch/</link>
      <pubDate>Mon, 11 Mar 2013 15:58:36 +0000</pubDate>
      <guid>https://home.regit.org/2013/03/simon-horman-mpls-enlightened-open-vswitch/</guid>
      <description>&lt;p&gt;&lt;a href=&#34;http://openvswitch.org/&#34;&gt;Open vSwitch&lt;/a&gt; is a multi-layer switch. It is designed to enable network automation through programmatic extension, while still supporting standard management interfaces and protocols.&lt;/p&gt;
&lt;p&gt;Openflow is a management protocol that is supported by Open vSwitch. Openflow is has a basic support for MPLS. It features a minimum operation set to enable to configure MPLS correclty.&lt;br&gt;
Openflow MPLS support is partially implemented in Open vSwitch but there is some difficulties.&lt;/p&gt;
&lt;p&gt;SOme of the operations feature update of L3+ parameter like TTL. They must be updated in same manner in the MPLS header and in the packet header. And this is quite complicated as it supposed to decode the packet below MPLS. But MPLS header does not include the encapsulated ethernet type so it is almost impossible to access correctly to the packet structure.&lt;/p&gt;</description>
    </item>
    <item>
      <title>David Miller: routing cache is dead, now what ?</title>
      <link>https://home.regit.org/2013/03/david-miller-routing-cache-is-dead-now-what/</link>
      <pubDate>Mon, 11 Mar 2013 10:17:21 +0000</pubDate>
      <guid>https://home.regit.org/2013/03/david-miller-routing-cache-is-dead-now-what/</guid>
      <description>&lt;p&gt;The routing cache was maintaining a list of routing decisions. This was an hash table which was highly dynamic and was changing due to traffic. One of the major problem was the garbage collector. An other severe issue was the possibility of DoS using the increase&lt;/p&gt;
&lt;p&gt;The routing cache has been suppressed in Linux 3.6 after a 2 years effort by David and the other Linux kernel developers. The global cache has been suppressed and some stored information have been moved to more separate resources like socket.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Fabio Massimo Di Nitto: Kronosnet.org</title>
      <link>https://home.regit.org/2013/03/fabio-massimo-di-nitto-kronosnet-org/</link>
      <pubDate>Mon, 11 Mar 2013 09:03:03 +0000</pubDate>
      <guid>https://home.regit.org/2013/03/fabio-massimo-di-nitto-kronosnet-org/</guid>
      <description>&lt;p&gt;&lt;a href=&#34;http://kronosnet.org/&#34;&gt;Kronosnet&lt;/a&gt; is a “I conceived it when drunk but it works well” VPN implementation. It is using an Ether TAP for the VPN to provide a lyaer 2 vpn. To avoid reinventing the wheel, it is delegating most of the work to the kernel. It supports multilink and redundancy of servers. On multilink side, 8 links can be done per-host to help redundancy.&lt;/p&gt;
&lt;p&gt;One of the use of this project is the creation of private network in the cloud as it can be easily setup to provide redundancy and connection for a lot of clients (64k simultaneous clients). And because a layer 2 VPN is really useful for this type of usage.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Daniel Borkmann: Packets Sockets, BPF and Netsniff-NG</title>
      <link>https://home.regit.org/2013/03/daniel-borkmann-packets-sockets-bpf-and-netsniff-ng/</link>
      <pubDate>Sun, 10 Mar 2013 16:11:29 +0000</pubDate>
      <guid>https://home.regit.org/2013/03/daniel-borkmann-packets-sockets-bpf-and-netsniff-ng/</guid>
      <description>&lt;h4 id=&#34;pf_packet-introduction&#34;&gt;PF_PACKET introduction&lt;/h4&gt;
&lt;p&gt;This is access to raw packet inside Linux. It is used by libpcap and by other projects like Suricata.&lt;br&gt;
PF_PACKET performance can be improved via dedicated features:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Zero-copy RX/TX&lt;/li&gt;
&lt;li&gt;Socket clustering&lt;/li&gt;
&lt;li&gt;Linux socket filtering (BPF)&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;BPF architecture looks like a small virtual machine with register and memory stores. It has different instructions and the kernel has its own kernel extensions to access to cpu number, vlan tag.&lt;/p&gt;
&lt;h4 id=&#34;netsniff-ng&#34;&gt;Netsniff-NG&lt;/h4&gt;
&lt;p&gt;&lt;a href=&#34;http://netsniff-ng.org/&#34;&gt;Netsniff-ng&lt;/a&gt; is a set of minimal tools:&lt;/p&gt;</description>
    </item>
    <item>
      <title>Ulogd 2.0.2, my first release as maintainer</title>
      <link>https://home.regit.org/2013/03/ulogd-2-0-2-my-first-release-as-maintainer/</link>
      <pubDate>Mon, 04 Mar 2013 00:13:13 +0000</pubDate>
      <guid>https://home.regit.org/2013/03/ulogd-2-0-2-my-first-release-as-maintainer/</guid>
      <description>&lt;h4 id=&#34;objectives-of-this-release&#34;&gt;Objectives of this release&lt;/h4&gt;
&lt;p&gt;So it is my first ulogd2 release as maintainer. I’ve been in charge of the project since 2012 October 30th and this was an opportunity for me to increase my developments on the project. Roadmap was almost empty so I’ve decided to work on issues that were bothering me as a user of the project. I’ve also included two features which are connection tracking event filtering and a Graphite output module. Ulogd is available on &lt;a href=&#34;http://netfilter.org/projects/ulogd/downloads.html&#34;&gt;Netfilter web site&lt;/a&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>Visualize Netfilter accounting in Graphite</title>
      <link>https://home.regit.org/2012/12/visualize-netfilter-accounting-in-graphite/</link>
      <pubDate>Sat, 22 Dec 2012 11:27:09 +0000</pubDate>
      <guid>https://home.regit.org/2012/12/visualize-netfilter-accounting-in-graphite/</guid>
      <description>&lt;h4 id=&#34;ulogd-graphite-output-plugin&#34;&gt;Ulogd Graphite output plugin&lt;/h4&gt;
&lt;p&gt;I’m committed a &lt;a href=&#34;http://git.netfilter.org/cgi-bin/gitweb.cgi?p=ulogd2.git;a=commit;h=8cbeaed5c9b78c8c63f4fb98866722135f46ab86&#34;&gt;new output plugin&lt;/a&gt; for &lt;a href=&#34;http://www.netfilter.org/projects/ulogd/&#34;&gt;ulogd&lt;/a&gt;. The idea is to send &lt;a href=&#34;https://home.regit.org/2012/07/flow-accounting-with-netfilter-and-ulogd2/&#34;&gt;NFACCT accounting data&lt;/a&gt; to a &lt;a href=&#34;http://graphite.wikidot.com/&#34;&gt;graphite server&lt;/a&gt; to be able to display the received data. Graphite is a web application which provide real-time visualization and storage of numeric time-series data.&lt;/p&gt;
&lt;p&gt;Once data are sent to the graphite server, it is possible to use the web interface to setup different dashboard and graphs (including combination and mathematical operation):&lt;br&gt;
&lt;a href=&#34;https://home.regit.org/uploads/2012/12/graphite.png&#34;&gt;&lt;img loading=&#34;lazy&#34; decoding=&#34;async&#34; src=&#34;https://home.regit.org/uploads/2012/12/graphite-1024x372.png&#34; alt=&#34;&#34; title=&#34;Example Dashboard&#34; width=&#34;695&#34; height=&#34;252&#34; class=&#34;aligncenter size-large wp-image-1388&#34; srcset=&#34;https://home.regit.org/uploads/2012/12/graphite-1024x372.png 1024w, https://home.regit.org/uploads/2012/12/graphite-300x109.png 300w, https://home.regit.org/uploads/2012/12/graphite.png 1920w&#34; sizes=&#34;auto, (max-width: 709px) 85vw, (max-width: 909px) 67vw, (max-width: 984px) 61vw, (max-width: 1362px) 45vw, 600px&#34; /&gt;&lt;/a&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>Flow reconstruction and normalization in Suricata</title>
      <link>https://home.regit.org/2012/11/suricata-flow-reconstruction/</link>
      <pubDate>Thu, 15 Nov 2012 17:36:06 +0000</pubDate>
      <guid>https://home.regit.org/2012/11/suricata-flow-reconstruction/</guid>
      <description>&lt;p&gt;The naive approach would consider that an IDS is just taking packet and doing a lot of matching on it. In fact, this is not at all what is happening. An IDS/IPS like Suricata is in fact rebuilding the data stream and in case of known protocols it is even normalizing the data stream and providing keyword which can be used to match on specific field of a protocol.&lt;/p&gt;
&lt;p&gt;Let’s say, we a rule to match on a HTTP request where method is GET and the URL is “/download.php”.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Suricata, to 10Gbps and beyond</title>
      <link>https://home.regit.org/2012/07/suricata-to-10gbps-and-beyond/</link>
      <pubDate>Mon, 30 Jul 2012 21:03:19 +0000</pubDate>
      <guid>https://home.regit.org/2012/07/suricata-to-10gbps-and-beyond/</guid>
      <description>&lt;h4 id=&#34;introduction&#34;&gt;Introduction&lt;/h4&gt;
&lt;p&gt;Since the beginning of July 2012, OISF team is able to access to a server where one interface is receiving&lt;br&gt;
some mirrored real European traffic. When reading &amp;ldquo;some&amp;rdquo;, think between 5Gbps and 9.5Gbps&lt;br&gt;
constant traffic. With that traffic, this is around 1Mpps to 1.5M packet per seconds we have to study.&lt;/p&gt;
&lt;p&gt;The box itself is a standard server with the following characteristics:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;CPU: One Intel(R) Xeon(R) CPU E5-2680 0 @ 2.70GHz (16 cores counting Hyperthreading)&lt;/li&gt;
&lt;li&gt;Memory: 32Go&lt;/li&gt;
&lt;li&gt;capture NIC: Intel 82599EB 10-Gigabit SFI/SFP+&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The objective is simple: be able to run Suricata on this box and treat the whole&lt;br&gt;
traffic with a decent number of rules. With the constraint not to use any non&lt;br&gt;
official system code (plain system and kernel if we omit a driver).&lt;/p&gt;</description>
    </item>
    <item>
      <title>Flow accounting with Netfilter and ulogd2</title>
      <link>https://home.regit.org/2012/07/flow-accounting-with-netfilter-and-ulogd2/</link>
      <pubDate>Sat, 14 Jul 2012 21:11:44 +0000</pubDate>
      <guid>https://home.regit.org/2012/07/flow-accounting-with-netfilter-and-ulogd2/</guid>
      <description>&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;
&lt;p&gt;Starting with Linux kernel 3.3, there’s a new module called &lt;em&gt;nfnetlink_acct&lt;/em&gt;.&lt;br&gt;
This new feature added by Pablo Neira brings interesting accountig capabilities to Netfilter.&lt;br&gt;
Pablo has made an extensive &lt;a href=&#34;http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=commit;h=9413902796f56f6209e19dd54e840ed46950612c&#34;&gt;description of the feature in the commit&lt;/a&gt;.&lt;/p&gt;
&lt;h2 id=&#34;system-setup&#34;&gt;System setup&lt;/h2&gt;
&lt;p&gt;We need to build a set of tools to get all that’s necessary:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;libmnl&lt;/li&gt;
&lt;li&gt;libnetfilter_acct&lt;/li&gt;
&lt;li&gt;nfacct&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The build is the same for all projects:&lt;/p&gt;
&lt;pre&gt;git clone git://git.netfilter.org/PROJECT
cd PROJECT
autoreconf -i
./configure
make
sudo make install
&lt;/pre&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>Opensvp, a new tool to analyse the security of firewalls using ALGs</title>
      <link>https://home.regit.org/2012/06/opensvp-a-new-tool-to-analyse-the-security-of-firewalls-using-algs/</link>
      <pubDate>Fri, 08 Jun 2012 13:34:07 +0000</pubDate>
      <guid>https://home.regit.org/2012/06/opensvp-a-new-tool-to-analyse-the-security-of-firewalls-using-algs/</guid>
      <description>&lt;p&gt;Following my talk at &lt;a href=&#34;http://www.sstic.org&#34;&gt;SSTIC&lt;/a&gt;, I’ve released a new tool called &lt;a href=&#34;https://home.regit.org/software/opensvp/&#34;&gt;opensvp&lt;/a&gt;. Its aim is to cover the attacks described in this talk. It has been published to be able to determine if the firewall policy related to &lt;a href=&#34;http://en.wikipedia.org/wiki/Application-level_gateway&#34;&gt;Application Layer Gateways&lt;/a&gt; is correctly implemented.&lt;/p&gt;
&lt;p&gt;Opensvp implements two type of attacks:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Abusive usage of protocol commands: an protocol message can be forged to open pinhole into firewall. Opensvp currently implements message sending for IRC and FTP ALGs.&lt;/li&gt;
&lt;li&gt;Spoofing attack: if anti-spooofing is not correctly setup, an attacker can send command which result in arbitrary pinhole being opened to a server.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;It has been developed in &lt;a href=&#34;http://www.python.org/&#34;&gt;Python&lt;/a&gt; and uses &lt;a href=&#34;http://www.secdev.org/projects/scapy/&#34;&gt;scapy&lt;/a&gt; to implement the spoofing attack on ALGs.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Transparents de ma prÃ©sentation au SSTIC</title>
      <link>https://home.regit.org/2012/06/transparents-de-ma-presentation-au-sstic/</link>
      <pubDate>Fri, 08 Jun 2012 10:26:13 +0000</pubDate>
      <guid>https://home.regit.org/2012/06/transparents-de-ma-presentation-au-sstic/</guid>
      <description>&lt;p&gt;Les transparents de ma prÃ©sentation du SSTIC sont disponibles : &lt;a href=&#34;https://home.regit.org/uploads/2012/06/conntrack-attack.pdf&#34;&gt;Utilisation malveillante des suivis de connexions&lt;/a&gt;. Merci aux organisateurs du SSTIC d’avoir acceptÃ© mon papier!&lt;/p&gt;
&lt;p&gt;Des vidÃ©os de dÃ©monstration sont disponibles sur ce post: &lt;a href=&#34;https://home.regit.org/2012/03/playing-with-network-layers-to-bypass-firewalls-filtering-policy/&#34;&gt;Playing with Network Layers to Bypass Firewalls’ Filtering Policy&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;L’outil de test &lt;a href=&#34;https://home.regit.org/software/opensvp/&#34;&gt;openvsp&lt;/a&gt; est disponible sur &lt;a href=&#34;https://home.regit.org/software/opensvp/&#34;&gt;cette page&lt;/a&gt;.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Using Scapy lfilter</title>
      <link>https://home.regit.org/2012/06/using-scapy-lfilter/</link>
      <pubDate>Thu, 07 Jun 2012 13:13:45 +0000</pubDate>
      <guid>https://home.regit.org/2012/06/using-scapy-lfilter/</guid>
      <description>&lt;p&gt;Scapy BPF filtering is not working when some exotic interface are used. This includes Virtualbox interface such as vboxnet.&lt;/p&gt;
&lt;p&gt;For example, the following code will not work if the interface is a virtualbox interface:&lt;/p&gt;
&lt;pre&gt;build_filter = &#34;src host %s and src port 21&#34;
sniff(iface=iface, prn=callback, filter=build_filter)
&lt;/pre&gt;
&lt;p&gt;To fix this, you can use the &lt;em&gt;lfilter&lt;/em&gt; option. The filtering is now done inside Scapy. This is powerful but less efficient.&lt;/p&gt;
&lt;p&gt;The code can be modified like this:&lt;/p&gt;</description>
    </item>
    <item>
      <title>IPv6 privacy extensions on Linux</title>
      <link>https://home.regit.org/2011/04/ipv6-privacy/</link>
      <pubDate>Fri, 29 Apr 2011 17:41:24 +0000</pubDate>
      <guid>https://home.regit.org/2011/04/ipv6-privacy/</guid>
      <description>&lt;h2 id=&#34;ipv6-global-address&#34;&gt;IPv6 global address&lt;/h2&gt;
&lt;p&gt;The global address is used in IPv6 to communicate with the outside world. This is thus the one that is used as source for any communication and thus in a way identify you on Internet.&lt;/p&gt;
&lt;p&gt;Below is a dump of an interface configuration:&lt;/p&gt;
&lt;blockquote&gt;
&lt;pre&gt;eth0: &amp;lt;BROADCAST,MULTICAST,UP,LOWER_UP&amp;gt; mtu 1500 qdisc pfifo_fast state UP qlen 1000
&lt;/blockquote&gt;
&lt;pre&gt;&lt;code&gt;link/ether 00:22:15:64:42:bd brd ff:ff:ff:ff:ff:ff
inet6 2a01:f123:1234:5bd0:222:15ff:fe64:42bd/64 scope global dynamic 
   valid_lft 86314sec preferred_lft 86314sec
inet6 fe80::222:15ff:fe64:42bd/64 scope link 
   valid_lft forever preferred_lft forever&amp;lt;/pre&amp;gt;
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;The global address is here &lt;em&gt;2a01:f123:1234:5bd0:222:15ff:fe64:42bd/64&lt;/em&gt;. It is build by using the prefix and adding an identifier build with the hardware address. For example, here the hardware address is 00:22:15:64:42:bd and the global IPv6 address is ending with 22:15_ff:fe_64:42bd.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
