From: Pascal Hambourg <pascal.mail@plouf.fr.eu.org>
To: netfilter@buglecreek.com
Cc: netfilter@vger.kernel.org
Subject: Re: FORWARD chain and Interfaces
Date: Sat, 21 May 2011 22:51:55 +0200 [thread overview]
Message-ID: <4DD825EB.2080300@plouf.fr.eu.org> (raw)
In-Reply-To: <1306007342.28169.1454496985@webmail.messagingengine.com>
netfilter@buglecreek.com a écrit :
>
> As far as the virtual machines. All three test systems are virtual.
> They run RH5 using Mac with parallels. The routing tables are below.
[Nothing unexpected in the routing tables]
How are the virtual machine network interfaces connected together ?
Did you create two separate virtual links ?
One explanation could be that all interfaces are connected to the same
virtual link, so traffic coming to the router could arrive at any of its
two interfaces.
next prev parent reply other threads:[~2011-05-21 20:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-21 6:10 FORWARD chain and Interfaces netfilter
2011-05-21 7:37 ` Andrew Beverley
2011-05-21 11:23 ` Pascal Hambourg
2011-05-21 19:49 ` netfilter
2011-05-21 20:51 ` Pascal Hambourg [this message]
2011-05-21 21:40 ` netfilter
2011-05-21 22:05 ` Pascal Hambourg
2011-05-21 22:31 ` netfilter
2011-05-22 8:48 ` Pascal Hambourg
2011-05-22 19:06 ` netfilter
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=4DD825EB.2080300@plouf.fr.eu.org \
--to=pascal.mail@plouf.fr.eu.org \
--cc=netfilter@buglecreek.com \
--cc=netfilter@vger.kernel.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