<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Network Coding on Henry Du Blog</title>
    <link>https://www.henrydu.com/categories/network-coding/</link>
    <description>Recent content in Network Coding on Henry Du Blog</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 13 Jan 2024 00:00:00 +0000</lastBuildDate>
    
	<atom:link href="https://www.henrydu.com/categories/network-coding/index.xml" rel="self" type="application/rss+xml" />
    
    
    <item>
      <title>Reading Notes: Netfilter and iptables (1)</title>
      <link>https://www.henrydu.com/2024/01/13/netfilter-iptables-1/</link>
      <pubDate>Sat, 13 Jan 2024 00:00:00 +0000</pubDate>
      
      <guid>https://www.henrydu.com/2024/01/13/netfilter-iptables-1/</guid>
      <description>Reading Notes: Netfilter and iptables Netfilter is firewalling subsystem in the Linux kernel as a modular[1]. For example, some fields are included in the sk_buf data structure only if the kernel is compiled with support for Netfilter feature.
struct sk_buff is defined in linux/include/skbuff.h. There is a well defined document on the top of the file. It include the netfilter common header file
#if IS_ENABLED(CONFIG_NF_CONNTRACK) #include &amp;lt;linux/netfilter/nf_conntrack_common.h&amp;gt;#endif Firewalling, essentially, hooks into certain places in the network stack code that packets always pass through when the packets or the kernel meet certain conditions.</description>
    </item>
    
  </channel>
</rss>