From: Michel Pastor <K@codefx.org>
To: Stephen Hemminger <shemminger@osdl.org>
Cc: bridge@lists.osdl.org
Subject: Re: [Bridge] single briged network internet access problems
Date: Tue, 25 Oct 2005 01:56:07 +0200 [thread overview]
Message-ID: <20051025015607.2cd2c189.K@codefx.org> (raw)
In-Reply-To: <20051024163055.5b3d4f2f@dxpl.pdx.osdl.net>
Forget the part about tcpdump, I rebooted the machine and the default route was reset to host2.
It seems I was right. As you can see packets is output through eth2 with an internal ip even with the MASQUERADE rule...
# tcpdump -i eth2 icmp
listening on eth2, link-type EN10MB (Ethernet), capture size 96 bytes
01:25:50.114069 IP 10.22.2.4 > mutu.nuxit.net: ICMP echo request, id 247, seq 0, length 64
01:25:51.113813 IP 10.22.2.4 > mutu.nuxit.net: ICMP echo request, id 247, seq 1, length 64
but with host2 as default route it'ok :
# tcpdump -i eth2 icmp
listening on eth2, link-type EN10MB (Ethernet), capture size 96 bytes
01:54:12.666919 IP 8X.242.21.225 > janus-2-20.x-echo.com: ICMP echo request, id 250, seq 0, length 64
01:54:12.719119 IP janus-2-20.x-echo.com > 8X.242.21.225: ICMP echo reply, id 250, seq 0, length 64
01:54:13.666751 IP 8X.242.21.225 > janus-2-20.x-echo.com: ICMP echo request, id 250, seq 1, length 64
01:54:13.706618 IP janus-2-20.x-echo.com > 8X.242.21.225: ICMP echo reply, id 250, seq 1, length 64
This confirm that the packets didn't get through the NAT-POSTROUTING chain.
So, why ?
Thanks
- Michel
prev parent reply other threads:[~2005-10-24 23:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-24 23:02 [Bridge] single briged network internet access problems Michel Pastor
2005-10-24 23:30 ` Stephen Hemminger
2005-10-24 23:56 ` Michel Pastor [this message]
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=20051025015607.2cd2c189.K@codefx.org \
--to=k@codefx.org \
--cc=bridge@lists.osdl.org \
--cc=shemminger@osdl.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.