From: Joel Newkirk <netfilter@newkirk.us>
To: cees-bart <ceesb@cs.kun.nl>, netfilter@lists.netfilter.org
Subject: Re: "iptables: Invalid argument" with kernel 2.4.20
Date: Mon, 16 Dec 2002 14:35:06 -0500 [thread overview]
Message-ID: <200212161435.06101.netfilter@newkirk.us> (raw)
In-Reply-To: <Pine.LNX.4.44.0212161717490.11632-100000@flex.cs.kun.nl>
On Monday 16 December 2002 11:25 am, cees-bart wrote:
> hi all,
> -A OUTPUT -d MYMACHINE -p udp -m udp --dport 27960 -j DNAT \
> --to-destination OTHERMACHINE:30000
> this setup works fine on kernel 2.4.19 with iptables 1.2.6a.
>
> BUT, the last rule (OUTPUT) fails with message "iptables: Invalid
> argument" when running under 2.4.20.
>
> i tried iptables 1.2.7a as well, but the result is the same.
>
> am i doing something wrong?
Have you tried manually creating the rule, or are you restoring from a
save made with the earlier version? Since you list it in a save format,
(dated November 12) and said it won't load, this strikes me as likely.
I don't know, but it's possible this won't work. Just try a:
/sbin/iptables -t nat -A OUTPUT -d MYMACHING -p udp --dport 27960 \
-j DNAT --to OTHERMACHINE:30000
and see if it accepts it. If so, then there must have been some change
in the save file structure or handling (possibly fixing a flaw) that
prevents newer netfilter form restoring from the older save.
If you require the ability to use the same save under both versions, it's
possible that saving from the new will be restorable in the old, even if
the reverse turns out to be broken.
j
next prev parent reply other threads:[~2002-12-16 19:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-16 16:25 "iptables: Invalid argument" with kernel 2.4.20 cees-bart
2002-12-16 17:42 ` Rob Sterenborg
2002-12-17 2:19 ` Anders Fugmann
2002-12-16 19:35 ` Joel Newkirk [this message]
2002-12-17 9:55 ` cees-bart
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200212161435.06101.netfilter@newkirk.us \
--to=netfilter@newkirk.us \
--cc=ceesb@cs.kun.nl \
--cc=netfilter@lists.netfilter.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.