All of lore.kernel.org
 help / color / mirror / Atom feed
From: Grant Taylor <gtaylor@riverviewtech.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] What I learned about Linux bridging
Date: Thu, 07 Jun 2007 14:21:31 +0000	[thread overview]
Message-ID: <4668146B.1060403@riverviewtech.net> (raw)
In-Reply-To: <925A849792280C4E80C5461017A4B8A210B83E@mail733.InfraSupportEtc.com>

On 06/07/07 01:55, Greg Scott wrote:
> I might see if I can do this with one set of rules in the PREROUTING
>  chain.

That is exactly why I put the rules in a new chain and jumped to the 
chain.  One place to maintain them.  With the ability to jump to the 
chain and then return to the chain that you jumped from, things act more 
like a sub-routine in programming.

  - Create new chains with a default policy of RETURN.
  - DROP on failures with in the new chain.
  - Default policy of RETURN will return packet flow to the calling chain.
  - Jump to the new chain from INPUT and return from it if everything is ok.
  - Jump to the new chain from FORWARD and return from it if everything 
is ok.

In fact, you could use the new chain as a (sub)chain from any chain with 
in the filter table.

> Yup - I noticed similar behavior.  So this is how I'll handle it. 
> eth0 gets an IP Address of 1.2.3.6 during normal bootup.  And then 
> when I do the brctl stuff, br0 gets 1.2.3.2.  That way there's never 
> a conflict between the physical and logical.  All the physical 
> interfaces have unique addresses so I can route based on the address 
> when it makes sense, or bridge based on the interface when that makes 
> sense.  I'm feeling lots better about all this.  Hopefully this 
> discussion can help others out there.

This is one way to do it.  Just be careful of race conditions while you 
are bringing things up.



Grant. . . .
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

      parent reply	other threads:[~2007-06-07 14:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-06 23:51 [LARTC] What I learned about Linux bridging Greg Scott
2007-06-07  2:06 ` Grant Taylor
2007-06-07  5:12 ` Greg Scott
2007-06-07  5:50 ` Grant Taylor
2007-06-07  6:55 ` Greg Scott
2007-06-07 14:21 ` Grant Taylor [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=4668146B.1060403@riverviewtech.net \
    --to=gtaylor@riverviewtech.net \
    --cc=lartc@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 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.