Following on from the announcement of a renewed commitment to Linux by Linksys-Cisco and the release of the Linux-compatible WRT54GL Wireless-G series broadband router (discussed here), this post details how to run Iptables on a Linksys-Cisco WRT54GL router via firmware from DD-WRT. A fully functional example Iptables script is provided to get you started.
(more…)
March 24, 2006
Iptables On A Linksys-Cisco WRT54GL Broadband Router HOWTO
February 9, 2006
Confusing Rules In The Default Iptables Configuration Under Fedora And RedHat Enterprise Linux
I have seen posts in a number of online forums to the effect that a couple of rules in the default Iptables firewall configuration under Fedora and Redhat Enterprise Linux are causing confusion.
(more…)
January 25, 2006
January 24, 2006
January 20, 2006
An Affordable Iptables Firewall – The Linksys-Cisco WRT54GL Or WRT54GS Series Router
If you are interested in an affordable way to get working with iptables please read on …
(more…)
January 18, 2006
Running Iptables With NFS
I’ve been asked a number of times how to allow NFS traffic with iptables.
(more…)
January 12, 2006
Iptables – Example Firewall Rulesets
Two example iptables firewall rulesets are provided. Both are designed for a single-homed host and utilize the stateful inspection feature of iptables for all connections.
(more…)
Iptables Connection Tracking – FTP
Firstly, you need to load the ip_conntrack_ftp module.Assuming you have a single-homed box, a simple ruleset to allow an ftp connection would be:
(more…)
Iptables Connection Tracking – ICMP
This post deals with connection tracking and the ICMP protocol.
(more…)
Iptables Connection Tracking – UDP
Because it lacks sequence numbers, UDP is known as a “stateless” protocol. However, this does not mean we can’t track UDP connections. There is still other useful information we can utilize. Here is an example state table entry for a newly formed udp connection:
(more…)
Iptables Connection Tracking – TCP
A tcp connection is initiated via a three-way handshake involving a synchronization request from the client, a synchronization and an acknowledgement from the server, and finally an acknowledgement from the client. Subsequent traffic flowing between server and client is acknowledged in all cases. The sequence looks like:
(more…)