From: "Nicolas de Pesloüan" <nicolas.2p.debian@free.fr>
To: Sinbad <sinbad.sinbad@gmail.com>
Cc: bridge@osdl.org
Subject: Re: [Bridge] vlan interface egress port
Date: Wed, 02 Feb 2011 19:54:54 +0100 [thread overview]
Message-ID: <4D49A87E.4090109@free.fr> (raw)
In-Reply-To: <AANLkTikgstLrscC3JKR7EesgP-hC5G2+CMdEjiwsYCfG@mail.gmail.com>
Le 02/02/2011 15:46, richardvoigt@gmail.com a écrit :
> On Wed, Feb 2, 2011 at 8:42 AM, richardvoigt@gmail.com
> <richardvoigt@gmail.com> wrote:
>> It depends on the destination MAC field in the L2 header of the
>> outgoing packet (which got filled in from the kernel routing table)
>
> Actually I should say it gets filled in during the routing process.
> The MAC address actually comes from the ARP table, but which ARP entry
> is used is determined by routing.
1/ Routing will decide which IP is the next hop.
2/ ARP table will convert this IP into a MAC address.
3/ The bridge code will decide which port to use, based on whether it learned this MAC address on
any port or not. This is the normal behavior of any bridge/switch.
- If the bridge learned this MAC address, it will forward the packet to this port only.
- If the bridge didn't learned this MAC address, it forward the packet to all ports.
To display the currently learned MAC address and associated port, use brctl showmacs <bridge_name>
Nicolas.
>
>>
>> On Wed, Feb 2, 2011 at 6:04 AM, Sinbad<sinbad.sinbad@gmail.com> wrote:
>>> hi,
>>>
>>> suppose my config is as below.
>>>
>>> # brctl addbr mybridge
>>> # brctl addif mybridge eth0
>>> # brctl addif mybridge eth1
>>> # ifconfig mybridge up
>>> # ifconfig mybridge 192.168.100.5 netmask 255.255.255.0
>>>
>>> now if the an l3 packet has to egress from mybridge
>>> which port will be chosen ?
>>>
>>> thanks
>>>
>>>
>>> On Wed, Feb 2, 2011 at 1:53 PM, Nicolas de Pesloüan
>>> <nicolas.2p.debian@free.fr> wrote:
>>>>
>>>> Le 02/02/2011 09:02, Sinbad a écrit :
>>>>>
>>>>> hi,
>>>>>
>>>>> suppose a vlan has 3 member ports and vlan is configured as an l3
>>>>> interface
>>>>> and if data is suppose to go out using that vlan interface, which
>>>>> physical port
>>>>> will be chosen among the 3 member ports ?
>>>>
>>>> Can you describe your configuration a little bit more (possibly using the
>>>> commands used to setup that configuration)?
>>>>
>>>> Nicolas.
>>>
>>>
>>> _______________________________________________
>>> Bridge mailing list
>>> Bridge@lists.linux-foundation.org
>>> https://lists.linux-foundation.org/mailman/listinfo/bridge
>>>
>>
>
prev parent reply other threads:[~2011-02-02 18:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-02 8:02 [Bridge] vlan interface egress port Sinbad
2011-02-02 8:23 ` Nicolas de Pesloüan
2011-02-02 12:04 ` Sinbad
2011-02-02 14:42 ` richardvoigt
2011-02-02 14:46 ` richardvoigt
2011-02-02 18:54 ` Nicolas de Pesloüan [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=4D49A87E.4090109@free.fr \
--to=nicolas.2p.debian@free.fr \
--cc=bridge@osdl.org \
--cc=sinbad.sinbad@gmail.com \
/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.