[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [lwip-devel] Bridge Implementation
From: |
Joel Cunningham |
Subject: |
Re: [lwip-devel] Bridge Implementation |
Date: |
Fri, 10 Feb 2017 10:48:20 -0600 |
> On Feb 10, 2017, at 9:15 AM, Sylvain Rochet <address@hidden> wrote:
>
> Hi Joel,
>
> On Fri, Feb 10, 2017 at 09:02:05AM -0600, Joel Cunningham wrote:
>>
>> Agree that the bulk of the bridge implementation would probably be
>> some kind of virtual netif, but the one piece that I need to
>> think/learn more about is how ARPing for the bridge’s IP address works
>> because there is a different hardware address for each interface
>
> They are not really used. An Ethernet switch (a bridge) doesn't have a
> mac address per se, or only one for its administrative interface over a
> virtual IP interface. Some bridge implementation use either a randomly
> generated one or the one of the first added interface.
>
I like the approach of a virtual port with it’s own MAC, that makes things
simpler!
> It means we need a layer 2 router implementation (an Ethernet switch)
> below everything else with virtual Ethernet interface support if we want
> more than just a bridge.
>
Joel
- [lwip-devel] Bridge Implementation, Joel Cunningham, 2017/02/09
- Re: [lwip-devel] Bridge Implementation, address@hidden, 2017/02/09
- Re: [lwip-devel] Bridge Implementation, Joel Cunningham, 2017/02/09
- Re: [lwip-devel] Bridge Implementation, Simon Goldschmidt, 2017/02/10
- Re: [lwip-devel] Bridge Implementation, Joel Cunningham, 2017/02/10
- Re: [lwip-devel] Bridge Implementation, Sylvain Rochet, 2017/02/10
- Re: [lwip-devel] Bridge Implementation,
Joel Cunningham <=
- Re: [lwip-devel] Bridge Implementation, address@hidden, 2017/02/10
- Re: [lwip-devel] Bridge Implementation, address@hidden, 2017/02/10