> > Binding to interfaces has an API already (see the IP space)
> > SO_BINDTODEVICE
>
> Can you point me to an example how that works from the application point
> of view? How does setting this option interact with bind(), for example?
> The good news: it looks as if the comment in front of ax25_bind() is correct
> and we do not need any API change to support it.
SO_BINDTODEVICE sets the device nanme bind() sets the sending/listening
address. In the IP case they don't reall have to match up and what happens if
they dont is sort of 'undefined'
> What I'm really missing is documentation about the various socket
> options available. Books rarely cover them at all and those that do
> often explain only the most basic ones...
I've not met one, and in many cases even the standards are either fuzzy or
omit the option
