Possible to have loopback + "real" network interface?
sebastian.huber at embedded-brains.de
Mon Aug 26 08:55:24 UTC 2013
On 2013-08-26 10:47, Nick Withers wrote:
> On Mon, 2013-08-26 at 09:24 +0200, Sebastian Huber wrote:
>> On 2013-08-26 09:04, Nick Withers wrote:
>>> The "loopback" sample (testsuites/samples/loopback), if I'm reading it
>>> right, seems to do it by providing a NULL for the struct
>>> rtems_bsdnet_ifconfig pointer in struct rtems_bsdnet_config, which I
>>> don't think is an option with multiple interfaces desired...?
>>> P.S., To be honest, I don't *really* want a loopback interface, I'd
>>> prefer socketpair() / select() on pipes and / or pselect(), but oh
>>> well! :-P
>> What you want is kqueue(2).
> Yeah, that'd do it too (although in the ideal world I'd prefer to use
> something more portable). kqueue's not available in RTEMS, right?
Its not yet supported, but we may have it after the network stack update.
Sebastian Huber, embedded brains GmbH
Address : Dornierstr. 4, D-82178 Puchheim, Germany
Phone : +49 89 189 47 41-16
Fax : +49 89 189 47 41-09
E-Mail : sebastian.huber at embedded-brains.de
PGP : Public key available on request.
Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.
More information about the users