From: Chinh Nguyen <cnguyen@certicom.com>
To: Daniel Nogradi <nogradi@gmail.com>
Cc: netfilter@lists.netfilter.org
Subject: Re: updated iptables doesn't work with old rules
Date: Thu, 23 Feb 2006 09:42:52 -0500 [thread overview]
Message-ID: <43FDC9EC.1050704@certicom.com> (raw)
In-Reply-To: <5f56302b0602221513i22ff868et991067e3314998da@mail.gmail.com>
Daniel Nogradi wrote:
> Hi Chinh, on machine B DNS resolution doesn't work at all because the
> name servers are on the internet which it can not access. So I'm not
> pinging google.com but the IP addresses.
>
> I've turned on logging and when I try to ssh, ping, etc, from B to A
> then I get these messages on both B and in the logs of A:
>
> kernel: nat: IN=eth1 OUT= MAC=(mac address of eth1) SRC=(IP of machine
> B) DEST=213.191.74.18 LEN=54 TOS=0x00 PREC=0x00 TTL=64 ............
> kernel: out: IN=eth1 OUT=ppp0 SRC=(IP of machine B) DEST=213.191.74.18
> ...........
>
> What does this supposed to mean? :)
>
It mean your packet traversed the prerouting nat eth1, and so on.
I would put 3 log messages, at "prerouting nat eth1", "forward", and
"postrouting nat". If your packet is seen at postrouting then it should be
successfully forwarded.
I noticed that your packet's outbound interface is ppp0. However, I recall your
MASQUERADE rule had "--out-interface eth0". Perhaps this is the cause and your
packet is not masqueraded? Try a simple "iptables -A POSTROUTING -t nat -j
MASQUERADE" without qualifiers.
Other things to try. Use ethereal to sniff eth1, and eth0/ppp0. Is there traffic?
Chinh
next prev parent reply other threads:[~2006-02-23 14:42 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-22 9:58 updated iptables doesn't work with old rules Daniel Nogradi
2006-02-22 11:01 ` Rob Sterenborg
2006-02-22 11:25 ` Daniel Nogradi
2006-02-22 12:35 ` Rob Sterenborg
2006-02-22 13:39 ` Daniel Nogradi
2006-02-22 20:53 ` Daniel Nogradi
2006-02-22 20:54 ` Chinh Nguyen
2006-02-22 21:57 ` Daniel Nogradi
2006-02-22 22:18 ` Chinh Nguyen
2006-02-22 23:13 ` Daniel Nogradi
2006-02-22 23:25 ` Daniel Nogradi
2006-02-23 14:42 ` Chinh Nguyen [this message]
2006-02-23 15:49 ` Daniel Nogradi
2006-02-24 0:41 ` Daniel Nogradi
2006-02-24 6:26 ` Rob Sterenborg
2006-02-24 10:14 ` Daniel Nogradi
2006-02-24 12:22 ` Rob Sterenborg
2006-02-24 14:48 ` Chinh Nguyen
2006-02-24 23:17 ` Daniel Nogradi
2006-02-25 19:20 ` Rob Sterenborg
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=43FDC9EC.1050704@certicom.com \
--to=cnguyen@certicom.com \
--cc=netfilter@lists.netfilter.org \
--cc=nogradi@gmail.com \
/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