Linux Netfilter discussions
 help / color / mirror / Atom feed
From: John Haxby <john.haxby@oracle.com>
To: Jonathan Tripathy <jonnyt@abpni.co.uk>
Cc: netfilter@vger.kernel.org
Subject: Re: VLANs
Date: Tue, 11 Jan 2011 17:21:33 +0000	[thread overview]
Message-ID: <4D2C919D.5040402@oracle.com> (raw)
In-Reply-To: <4D2C9046.9070408@abpni.co.uk>

On 11/01/11 17:15, Jonathan Tripathy wrote:
> Just one last question. Are there any measures I would need to take to 
> make sure that traffic cannot escape from a Linux bridge? My bridges 
> don't have IP assigned to them and the VM hosts don't do IP routing. 

The only way to get from one bridge to another is by routing so if there 
is no route then there's no way to get packets (or frames) to leap from 
one bridge to another.  (And if you're using separate vlans then you'd 
need a machine on both that is prepared to route the packets.)

Of course, testing is paramount.  No amount of hypothesising is going to 
help if you haven't tested.

jch

  reply	other threads:[~2011-01-11 17:21 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-10 17:42 VLANs Jonathan Tripathy
2011-01-10 21:33 ` VLANs John Haxby
2011-01-10 22:15   ` VLANs Jonathan Tripathy
2011-01-11  8:19     ` VLANs Thomas Berg
2011-01-11 10:26       ` VLANs Jonathan Tripathy
2011-01-11 10:42     ` VLANs John Haxby
2011-01-11 10:57       ` VLANs Jonathan Tripathy
     [not found]         ` <4D2C47DB.10702@oracle.com>
2011-01-11 12:24           ` VLANs Jonathan Tripathy
2011-01-11 12:48             ` VLANs John Haxby
2011-01-11 12:52               ` VLANs Jonathan Tripathy
2011-01-11 17:12                 ` VLANs John Haxby
2011-01-11 17:15                   ` VLANs Jonathan Tripathy
2011-01-11 17:21                     ` John Haxby [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-01-05 12:12 VLANs Jonathan Tripathy
2011-01-06  7:32 ` VLANs John Haxby

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=4D2C919D.5040402@oracle.com \
    --to=john.haxby@oracle.com \
    --cc=jonnyt@abpni.co.uk \
    --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