From Issue #156April 2007
ther eis probably a mistake in the file:
/sbin/iptables -A FORWARD -m state --state \
I will try to get my head around this and code my own little thing soon i think. Johnston @ webwurzel.de
The method of setting up this firewall would probably work fine, but for a beginner's guide to setting up a firewall I think that this glossed over too many details and outright left some unanswered.
It looks like the author set up this firewall in this manner because he didn't have access to the router. Why else would you setup proxy arp instead of just routing the protected network to the firewall? He also refers to the untrusted segment of his network as public network, and then mentions that for some that would be the Internet. He used non-routable IP space behind his firewall but then didn't mention that if you also did this you would need to do NAT.
I like the article because it explained how to set up a Linux box to be a firewall with needing to install a GUI for it, but I think that it used a poor example for what a typical network layout would be.
Yes, I did forget to mention the connection to the outside world properly. It can be either through a server with a global address running a squid, or even some technique using NAT - Sorry that I missed these points.
I was majorly referring to a large campus-kind-of network where one would like to protect his/her smaller LAN.
Divakaran this is a very good write up on iptables,Good and very practical example for a small setup.
Is it possible to expand this article and to add transparent proxy server using squid , as in a small setup its very common to have a linux Router/Gateway with proxy server.
I should have added those details here; I will try to come up with another one, as and when time permits.