| View previous topic :: View next topic |
| Author |
Message |
phong
Bodhisattva
Joined: 16 Jul 2002
Posts: 778
Location: Michigan - 15 & Ryan
|
 Posted: Mon Aug 19, 2002 7:56 pm Post subject: iptables-save incorrect output? |
 |
|
I'm having a strange problem with iptables-save... One of my rules is the following:
| Code: | | -A INPUT -i eth0 -p tcp --dport 4200 -j DROP |
BUT, when iptables-save runs (typically when the computer in question shuts down), it saves it as:
| Code: | | -A INPUT -i eth0 -p tcp -m tcp --dport 4200 -j DROP |
iptables-restore chokes when it sees that (says 4200 is an invalid argument). Why is it adding the "-m tcp" part? Is my understanding of iptables flawed? Right now, as a quick hack, I've modified /etc/init.d/iptables to filter out the offending bits when saving the rules, but that's just a hack and I'd like to find a real fix.
_________________
"An empty head is not really empty; it is stuffed with rubbish. Hence the difficulty of forcing anything into an empty head."
-- Eric Hoffer |
|
| Back to top |
|
 |
sschlueter
Guru
Joined: 26 Jul 2002
Posts: 578
Location: Dortmund, Germany
|
| Posted: Mon Aug 19, 2002 11:52 pm Post subject: Re: iptables-save incorrect output? |
|
|
| phong wrote: |
iptables-restore chokes when it sees that (says 4200 is an invalid argument). Why is it adding the "-m tcp" part?
|
Seems to be a bug. Same problem here using Gentoo+iptables 1.2.7 and Mandrake+iptables 1.2.5. |
|
| Back to top |
|
|
bert
n00b
Joined: 20 Jun 2002
Posts: 11
Location: Amsterdam
|
| Posted: Fri Aug 23, 2002 12:26 am Post subject: |
|
|
| I'm pretty sure this is an iptables-1.2.7 problem. Just emerge iptables-1.2.6a, that doesn't have this problem. Might be nice if iptables-1.2.7 could be masked... |
|
| Back to top |
|
|
Abandon
n00b
Joined: 18 May 2002
Posts: 33
Location: Madison, WI
|
| Posted: Sat Aug 24, 2002 4:08 am Post subject: |
|
|
| I encountered the same problem the first time I rebooted after installing iptables 1.2.7. I unmerged 1.2.7 and emerged 1.2.6a-r1 and all is now well. |
|
| Back to top |
|
|
|
Networking & Security
