From: "Eric Poulin" <epoulin@onepost.net>
To: Frederic Gobin <frederic.gobin@earthtvnet.com>
Cc: netfilter@lists.netfilter.org
Subject: Re: PREROUTING
Date: Tue, 29 Apr 2003 09:28:28 -0400 [thread overview]
Message-ID: <039e01c30e7b$9e6fd000$c565a8c0@lvl.digidyne.ca> (raw)
In-Reply-To: E6CED068-7A23-11D7-8B95-0003938423EC@earthtvnet.com
You are absolutly right. Actually, the command is correct, and also working
fine in my environement, so I suspect also that some options by be missing in
the kernel.
Eric
> This is not really true ...
>
> According to the iptables man page, DNAT is valid only in the OUTPUT
> and PREROUTING chain of the nat table. SNAT is only valid in the
> POSTROUTING chain of the nat table.
>
> It could be a missing kernel option ...
>
> Frederic Gobin
>
> Am Dienstag, 29.04.03 um 09:49 Uhr schrieb SaVaGE:
>
> > Op dinsdag 29 april 2003 09:23, schreef netfilter_user:
> >> Hello everyone,
> >>
> >> this is my problem:
> >> My LAN is connected to Internet via Linux machine with 2 interface (
> >> ppp0 - for internet and eth1 for local net). I need to connect from
> >> local host, service that is running on port 23073 and 23083 UDP in
> >> internet. For this i wrote afew rules with PREROUTING but when I start
> >> script with rules below i receive:
> >>
> >> Bad argument `PREROUTING'
> >> Try `iptables -h' or 'iptables --help' for more information.
> >> Bad argument `PREROUTING'
> >> Try `iptables -h' or 'iptables --help' for more information.
> >>
> >>
> >> iptables -t nat -A PREROUTING -p udp -d 80.50.60.185 --dport 23073 -j
> >> DNAT
> >> --to-destination 192.168.1.2 iptables -t nat -A PREROUTING -p udp -d
> >> 80.50.60.185 --dport 23083 -j DNAT --to-destination 192.168.1.2
> >>
> >> iptables -A FORWARD -p udp -d 192.168.1.2 --dport 23073 -j ACCEPT
> >> iptables -A FORWARD -p udp -d 192.168.1.2 --dport 23083 -j ACCEPT
> >>
> >> What maybe a reason of this msg?
> >> Im using slackware 8.1 with iptables 1.2.6a
> >
> > This behaviour is correct NATting is done on the POSTROUTING table !!!!
> >
> >
> > Pascal (PC-Secure Dutch security service)
> >
>
>
>
>
next prev parent reply other threads:[~2003-04-29 13:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-29 7:23 PREROUTING netfilter_user
2003-04-29 7:49 ` PREROUTING SaVaGE
2003-04-29 9:21 ` PREROUTING Frederic Gobin
2003-04-29 13:28 ` Eric Poulin [this message]
2003-04-29 12:53 ` Re[2]: PREROUTING netfilter_user
2003-04-29 13:33 ` SaVaGE
2003-04-29 14:49 ` Alistair Tonner
2003-04-29 15:59 ` Re[4]: PREROUTING netfilter_user
-- strict thread matches above, loose matches on Subject: below --
2003-09-19 15:48 PREROUTING Mickael DILY
2003-09-19 16:48 ` PREROUTING Jim Carter
[not found] <CAGwLQT0SRyga4go7uk2ujyPiBaD_K4jvd_XHCXG7YGi1hUxVbw@mail.gmail.com>
2011-10-05 11:49 ` PREROUTING Chris Percol
2011-10-05 22:05 ` PREROUTING Andrew Beverley
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='039e01c30e7b$9e6fd000$c565a8c0@lvl.digidyne.ca' \
--to=epoulin@onepost.net \
--cc=frederic.gobin@earthtvnet.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox