From: Mohamed Eldesoky <eldesoky.lists@gmail.com>
To: Sietse van Zanen <sietse@wizdom.nu>,
netfilter <netfilter@lists.netfilter.org>
Subject: Re: NAT doesn't work (only a fraction of the forwarded packets reach the postrouting chain)
Date: Sun, 13 Mar 2005 15:20:33 +0200 [thread overview]
Message-ID: <1403218a05031305206cb5a0d8@mail.gmail.com> (raw)
In-Reply-To: <02BB8A4AC86C564C89C7F14CF98CE0C49B73@knowledge.wizdom.nu>
On Sun, 13 Mar 2005 13:14:31 +0100, Sietse van Zanen <sietse@wizdom.nu> wrote:
> What do you see, when you tcpdump on your external interface? (tcpdump -I eth0). Can you see natted packets exiting that interface?
>
> The reason, that you only see 4 packets in the iptables -t nat -L is that if you fire off 10 pings, iptables will see the latter 9 as belonging to the same connection and therefor only logs 1.
How come ???
>
> It might be as simple, that the host you are trying to ping is just unpingable.
>
> Specify some more info, like what you are trying to ping, traceroute -I output.
>
> -----Original Message-----
> From: netfilter-bounces@lists.netfilter.org [mailto:netfilter-bounces@lists.netfilter.org] On Behalf Of Mårten Segerkvist
> Sent: Sunday, March 13, 2005 1:01 PM
> To: netfilter@lists.netfilter.org
> Subject: RE: NAT doesn't work (only a fraction of the forwarded packets reach the postrouting chain)
>
> On Sun, 13 Mar 2005, Sietse van Zanen wrote:
>
> > From man iptables:
> > MASQUERADE
> > This target is only valid in the nat table, in the POSTROUTING chain.
> > It should only be used with dynamically assigned IP (dialup)
> > connections: if you have a static IP address, you should use the
> > SNAT target.
> >
> > Try using regular SNAT rule:
> >
> > Iptables --table nat --append POSTROUTING --out-interface eth0 -j SNAT
> > --to-source:your.pub.ip.addr
> >
>
> Now using:
>
> echo 1 > /proc/sys/net/ipv4/ip_forward
> modprobe ipt_MASQUERADE
> modprobe iptable_filter
> iptables --table nat --append POSTROUTING --out-interface eth0 -j SNAT \
> --to-source 81.172.241.145
> iptables --append FORWARD --in-interface eth1 -j ACCEPT
>
> This gives me the same result as previosly. What confuses me further is
> that no packets seems to be accepted from the wlan-interface.
>
> > iptables -L -v
>
> Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
> pkts bytes target prot opt in out source
> destination
> 125 5000 ACCEPT all -- wlan0 any anywhere
> anywhere
>
> > iptables -t nat -L -v
>
> Chain POSTROUTING (policy ACCEPT 0 packets, 0 bytes)
> pkts bytes target prot opt in out source
> destination
> 4 295 SNAT all -- any eth0 anywhere
> anywhere to:<IP>
>
> As before, I'd be most grateful for any suggestions!
>
> /Mårten Segerkvist
>
>
--
Mohamed Eldesoky
www.eldesoky.net
RHCE
next prev parent reply other threads:[~2005-03-13 13:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-13 12:14 NAT doesn't work (only a fraction of the forwarded packets reach the postrouting chain) Sietse van Zanen
2005-03-13 13:20 ` Mohamed Eldesoky [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-03-13 13:34 Sietse van Zanen
2005-03-13 15:01 ` Mohamed Eldesoky
2005-03-13 15:27 ` Jose Maria Lopez Hernandez
2005-03-13 10:41 Sietse van Zanen
2005-03-13 12:01 ` Mårten Segerkvist
2005-03-13 10:11 Mårten Segerkvist
2005-03-13 20:16 ` Jason Opperisano
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=1403218a05031305206cb5a0d8@mail.gmail.com \
--to=eldesoky.lists@gmail.com \
--cc=netfilter@lists.netfilter.org \
--cc=sietse@wizdom.nu \
/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