Home > Articles > Operating Systems, Server > Linux/UNIX/Open Source

  • Print
  • + Share This


How Netfilter Works

As I mentioned earlier, for Netfilter to work, you'll need the user space program called iptables. Get the latest version (currently iptables-1.1.1), and build and install it. In the future, the author promises tools to accompany iptables, similar to the ipchains-save and ipchains-restore utilities. But for now, you'll just have to ensure that all your rules are in a script ready to go at boot time.

Netfilter is about rules. Rules work on packets. Each rule is written to do something, and that something is called a target. The rules belong to chains, which are used to group the rules. As you'll also see, the chains that are traversed depend on the packet. Each chain belongs to a table. The table used depends on your requirements. In the next few paragraphs, you'll take a look at targets, chains, and tables, in that order.

Rule Targets

Rules work on packets. If a rule matches a packet, then the target is executed on that packet. The built-in targets are ACCEPT, REJECT, and DROP. This corresponds in ipchains to ACCEPT, REJECT, and DENY. You can do more, such as LOG, QUEUE, and RETURN. Of the six mentioned targets, only four—ACCEPT, DROP, QUEUE, and RETURN—are built in. If you want to use REJECT or LOG, you'll need to insert the appropriate module. But don't panic. You'll handle the modules later.

The Five Built-in Chains

Think of your system as a black box. Outside this black box is a processor that lies just beyond your incoming interface (whatever that may be, Ethernet card, modem, wireless antenna, and so on). This processor will grab all packets destined for your system before they enter the interface. This area is called prerouting. While it's true that packets won't—nay, can't—be acted upon by the system before they've entered the system, it's easier to think of them as being acted on here so that when they hit the interface, they've already been changed and are ready for routing. So, our PREROUTING chain rules are applied before the system (actually, the routing table) is consulted about the packet's destination.

Inside the system are three more chains. These chains are the INPUT, FORWARD, and OUTPUT chains. Arriving packets will go to either one of the INPUT or FORWARD chains. Packets that are only transiting the system will go only to the FORWARD chain, and packets destined only for the local system will go only to the INPUT chain. This is a change from the 2.2.x ipchains software that had every transiting packet going to the INPUT chain first. Packets leaving the system from the local system will travel the OUTPUT chain only.

When packets leave the box (yes, this actually happens before they leave), they can hit one last chain, the POSTROUTING chain. Again, if you think of the change happening as the packet hits the wire, it's a little easier to imagine the flow.

The Three Netfilter Tables

The Netfilter framework is divided into three separate tables: filter, nat, and mangle. Each table affects only certain parts of the overall Netfilter scheme. The default table is the filter table. This is the table you'll use most often and coincides most closely to ipchains.

The other two tables you'll want to know about are the mangle table and the nat table. To do anything with either of these tables, they must be explicitly mentioned. Let me reiterate that: To do anything with any table other than the default filter table, you must declare the table. You don't need to specifically declare the filter table, but you might want to do that just to reinforce which table you're using.

So, to list the nat table, you need to declare it first. To create a user-defined chain for the mangle table, you need to declare the table. Before we get into actually building rules, let's take a look at what I'm talking about. This short exercise will show you two things: that table declaration is most certainly required for other than the filter table, and definitively which built-in chains belong to which table.

On your system (assuming that you're using a 2.4.0 kernel and have iptables installed and the Netfilter modules inserted), try these commands (must be root):

iptables -L -n
iptables -t filter -L -n
iptables -t mangle -L -n
iptables -t nat -L -n

As you run these, note the differences. The first two commands return exactly the same thing:

Chain INPUT (policy ACCEPT)
target     prot opt source               destination         
Chain FORWARD (policy ACCEPT)
target     prot opt source               destination         
Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination         

Because you've not yet defined any rules, none but the default policy exists. So, you can see the chains in their pristine state.

The first two commands work on the filter table to return a list of all rules in all the chains that pertain to the filter table. The -n is for numeric so that you're not trying to resolve DNS, which slows down the table listings. If you had any user-defined filter table chains, they would be listed here.

Now you know that the filter table consists initially of the INPUT, FORWARD, and OUTPUT chains. Again, remember, only one of these chains will be used for any given packet. Packets destined for the FORWARD chain will not traverse the INPUT chain.

The third command, given previously, will return the following:

target     prot opt source               destination         
Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination         

So, the mangle table works initially only with the two built-in chains PREROUTING and OUTPUT. If you try to write a rule using -t mangle (the mangle table) and write that rule to any of the other three built-in tables or any user-defined chain not declared as a mangle table chain, the rule will fail.

The final list command given previously will return this:

target     prot opt source               destination      
target     prot opt source               destination         
Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination         

So, your network address translation (nat) table, one that will be of great interest to many of you, works initially only with the PREROUTING, POSTROUTING, and OUTPUT built-in chains.

Notice that the OUTPUT chain can accept rules for any of the tables. The PREROUTING chain can accept rules for any of the mangle or nat tables. These two chains are exceptions. No other chain can belong to more than one table at a time. So, user-defined chains will be created as part of one table and will not accept rules for any other table. We'll revisit this with a few rule examples in the last article.

Next, we'll start writing rules and see how this all works.

  • + Share This
  • 🔖 Save To Your Account

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.


Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.


If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.


This site is not directed to children under the age of 13.


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020