Talk:Iptables

inappropriate
The content on this page does not seem appropriate for Wikipedia (it is more of a user's manual or tutorial than an encyclopedic article). I suggest merging with, or redirecting to, the Netfilter article. -- Dmeranda 07:41, 21 Sep 2004 (UTC)

I agree. How?
There is precedent for highly technical articles targeted at an individual program (see Bash), so I think there is value in showing command syntax, etc. But I also think that this article should be merged with Netfilter. I'm new to Wikipedia -- how does one go about merging two closely-related articles such as these? Is some kind of consensus required? &mdash; franl (talk) 03:51, 27 Nov 2004 (UTC)

this what i need
the netfiler do not contain the info i found here. The merge for me is not ok. puting everything in one big article is IMo against wiki idea. But some pple like to have a big articles :) (megalomania) —Preceding unsigned comment added by 24.15.124.119 (talk) 16:57, 10 April 2008 (UTC)

Output from telnet is wrong
The example which tries to connect to port 80 using telnet is wrong. 'Connection refused' implies only that no service is running on port 80. If it were firewalled, telnet would return with 'No route to host'.

Unless someone can counter that some version of telnet behaves in the way specified, I'll change this soon. —Preceding unsigned comment added by 91.125.35.205 (talk) 13:19, 20 September 2008 (UTC)

will cause a "Connection refused". j.engelh (talk) 12:18, 17 November 2008 (UTC)

Section “Frontends / Alternatives” superfluous
This is a translation from de:Diskussion:Netfilter/iptables for reference. FWIW, I agree to it. —j.eng (talk) 22:48, 28 June 2009 (UTC)

Frontends are neither complete nor important. And furthermore, user-friendly firewall distributions are arbitrarily mixed with real frontends.

Alternatives of other operating systems are irrelevant, since this concerns a Linux firewall. A long list of alternatives can surely be found in Category:Firewall. And Linux alternatives are rar, not existent, or already mentioned in the history part of iptables.

iptables and Netfilter
Netfilter -- the tables, chains and other bits that make up the firewall and are contained in the kernel. iptables -- the command-line, user-space tool used to interact, examine and configure the Netfilter firewall.

Even the introductory paragraph gets this part wrong. — Preceding unsigned comment added by 199.190.170.30 (talk) 21:40, 26 August 2013 (UTC)

External links modified
Hello fellow Wikipedians,

I have just modified one external link on Iptables. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:
 * Added archive https://web.archive.org/web/20170129062919/http://www.netfilter.org/projects/iptables/index.html to https://www.netfilter.org/projects/iptables/index.html

When you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.

Cheers.— InternetArchiveBot  (Report bug) 06:09, 16 November 2017 (UTC)

Wrong initial release year?
The article says iptables was first released in the year 1998. According to Netfilters' archive the first release (v1.0.0-alpha) was from the year 2000. Zciurus (talk) 17:11, 11 August 2022 (UTC)

flowchart nat:INPUT is wrong?
I saw a discussion on Serverfault that the flowchart is incorrect with regards to the nat tables. The discussion is that nat:INPUT must be after filter:INPUT, and that routing decision happens after nat:OUTPUT but before filter:OUTPUT. A link to https://stuffphilwrites.com/wp-content/uploads/2014/09/FW-IDS-iptables-Flowchart-v2019-04-30-1.png was provided for this claim. Which is correct? 139.122.191.225 (talk) 08:07, 29 June 2023 (UTC)