Linux Firewall: IPTABLES and Loopback
:cry:
I can't get my iptables set up correctly. It seems to work perfectly except that the loopback is being denied. I have tried the two following configurations to no avail: -------------------Configuration 1-------------------------- ## Loop Back ## /sbin/iptables -A INPUT -p tcp --syn -s 127.0.0.1 -j ACCEPT ######## Deny Everything else ######## /sbin/iptables -A INPUT -j DROP -------------------Configuration 2---------------------------- ## Loop Back ## /sbin/iptables -A INPUT -i lo -j ACCEPT ######## Deny Everything else ######## /sbin/iptables -A INPUT -j DROP Could someone please shed some light on this for me? TIA |
Well, I got the loopback working (sortof) I can ping myself now but no one else can. Unfortunately, that still hasn't fixed my mail server problems.
Ah, if only Linux were a microsoft product.:evilaugh: |
If linux were a microsoft product, you would have shelled out $200 for it, and it would be buggy, uncustomizable, and evil.
|
if you start off by setting the default policy to DENY on the
IN OUT and FORWARD then you have to set specific rules to allow wanted traffic through the firewall to the corresponding interface. If you wanted to allow the LOOP back you simply do something like this (not sure if it is correct) iptables -A INPUT -i lo -j ACCEPT iptables -A OUTPUT -i lo -j ACCEPT as for the others it may take some more thought as to who and what you want to access the interfaces |
All times are GMT -5. The time now is 06:53 PM. |
Powered by vBulletin® Version 3.7.4
Copyright ©2000 - 2025, Jelsoft Enterprises Ltd.
(C) 2005 ProCooling.com If we in some way offend you, insult you or your people, screw your mom, beat up your dad, or poop on your porch... we're sorry... we were probably really drunk... Oh and dont steal our content bitches! Don't give us a reason to pee in your open car window this summer...