[U-Boot] [RFC PATCH v3 14/14] dm: eth: Add a bridge to a real network for sandbox

[Simon Glass]

Hi Joe,

On 19 February 2015 at 16:44, Joe Hershberger <joe.hershberger at gmail.com> wrote:
> Hi Simon,
>
> On Tue, Feb 17, 2015 at 11:02 PM, Simon Glass <sjg at chromium.org> wrote:
>>
>> Hi Joe,
>>
>> On 16 February 2015 at 22:16, Joe Hershberger <joe.hershberger at gmail.com>
>> wrote:
>> > Hi Simon,
>> >
>> > On Sun, Feb 15, 2015 at 9:50 AM, Simon Glass <sjg at chromium.org> wrote:
>> >>
>> >> Hi Joe,
>> >>
>> >> On 10 February 2015 at 18:30, Joe Hershberger <joe.hershberger at ni.com>
>> >> wrote:
>> >> > Implement a bridge between u-boot's network stack and Linux's raw
>> >> > packet
>> >> > API allowing the sandbox to send and receive packets using the host
>> >> > machine's network interface.
>> >> >
>> >> > This raw Ethernet API requires elevated privileges.  You can either
>> >> > run
>> >> > as root, or you can add the capability needed like so:
>> >> >
>> >> > sudo /sbin/setcap "CAP_NET_RAW+ep" u-boot
>> >>
>> >> Can you add a note about thsi in README.sandbox? This seems like a
>> >> major new feature. It was talked about a few years ago when sandbox
>> >> was first created.
>> >
>> > OK.  Can you maybe point me to that conversation so I can understand
>> > what
>> > was anticipated potentially covering more of what was expected.
>>
>> All I could find was this:
>>
>> http://permalink.gmane.org/gmane.comp.boot-loaders.u-boot/108687
>
> I dug around and found this too:
>
> http://comments.gmane.org/gmane.comp.boot-loaders.u-boot/118685
>
> It seems it was more complicated to setup, but may have other benefits (such
> as being more likely to be able to change MAC address settings eventually).

Ah yes that is it.

I think your method is simpler and useful, and therefore generally
better as a starting point. The TAP idea if we have it should be a
separate feature. I really like that to, but it requires setup as you
say.

Regards,
Simon