All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dirk Gouders <gouders@et.bocholt.fh-gelsenkirchen.de>
To: Simon Barber <simon@superduper.net>
Cc: bridge@lists.linux-foundation.org
Subject: Re: [Bridge] IP address on bridged interface
Date: Fri, 06 Mar 2009 12:45:05 +0100	[thread overview]
Message-ID: <giy6vi98ou.fsf@karga.hank.lab> (raw)
In-Reply-To: <49B00385.1010401@superduper.net> (Simon Barber's message of "Thu\, 05 Mar 2009 08\:53\:25 -0800")


> Normally it does not make sense to put any L3 protocol address on port 
> interfaces - because incoming packets are diverted to the bridge 
> interface before the L3 protocol is examined. This means the L3 protocol 
> running on the port interface will never see any incoming packets.

Meanwhile, I played with a one-port setup that works with an IP address
(out of 192.168.106.0/24) only on the port interface:

brctl addbr br0
ip link set br0 up
# delete the network-route via the eth0 interface
ip route del 192.168.106.0/24
ip route add default dev br0
brctl addif br0 eth0

After I put the one and only interface eth0 into this experimental
"bridge", network connections are possible as if eth0 was used directly.
As br0 does not have an L3 protocol address, isn't it the port interface
eth0 that sees the L3 packets in this case?

Dirk

      reply	other threads:[~2009-03-06 11:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-05 14:20 [Bridge] IP address on bridged interface Dirk Gouders
2009-03-05 16:53 ` Simon Barber
2009-03-06 11:45   ` Dirk Gouders [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=giy6vi98ou.fsf@karga.hank.lab \
    --to=gouders@et.bocholt.fh-gelsenkirchen.de \
    --cc=bridge@lists.linux-foundation.org \
    --cc=simon@superduper.net \
    /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.