Hi Jana,
I am afraid that you overestimate the completeness of the network stack in
HelenOS slightly. We have a stub setsockopt() function, but it does not do
anything (only returns ENOTSUP).
I am not familiar with any existing DHCP implementation, so pardon my
ignorance. What exactly do we need SO_REUSEADDR for?
The bad news is that IP broadcasting is not implemented at all. In other
words, if you try to send to an address such as 192.168.255.255, it will try
to discover that literal address via ARP. If you try to send to 255.255.
255.255, inet will most likely decide that no direct route to such address
exists and will send the datagram to the default router only. Improvements
to ethip and inet will be necessary.
Also, I believe DHCP needs special provisions in order to be able to send
and receive UDP datagrams on an interface that has no address configured
(bind to an interface as opposed to a subnet). Modifications to inet and udp
will probably be necessary.
Cheers,
Jiri
---------- Původní zpráva ----------
Od: Jana Rapava <[email protected]>
Datum: 30. 4. 2013
Předmět: [HelenOS-devel] question regarding setsockopt()
"
Hi,
I found a function setsockopt() in HelenOS socket API and would like
to set options SO_BROADCAST and SO_REUSEADDR for the socket.
But it seems I can't find any header file which would define these values.
Is there any, or are these options not supported?
Thanks
Jana Rapava
"
_______________________________________________
HelenOS-devel mailing list
[email protected]
http://lists.modry.cz/cgi-bin/listinfo/helenos-devel
