[openbeosnetteam] Re: DHCP Status + Help Needed
- From: "Emmanuel Jacobs" <emmanuel.jacobs@xxxxxxxxxxxx>
- To: <openbeosnetteam@xxxxxxxxxxxxx>
- Date: Mon, 18 Oct 2004 14:34:18 +0200
Hi,
Just my 0.02 Eur:
The problem here is a double one:
1) we need to support the broadcast option (see code provided by Ingo)
2) an IP packet for DHCP protocol should be able to leave the NIC with
no IP address configured for it (source IP==0.0.0.0).
May be configuring the nic to have an ip of 0.0.0.0 (via ifconfig)
could work but doing so we must be prudent not to allow "any" traffic to go
in/out (ARP should be disabled, at least for 0.0.0.0 IP's, only DHCP/BOOTP
should be enabled).
Regards,
Emmanuel
-----Message d'origine-----
De : openbeosnetteam-bounce@xxxxxxxxxxxxx
[mailto:openbeosnetteam-bounce@xxxxxxxxxxxxx] De la part de Ingo Weinhold
Envoyé : mercredi 13 octobre 2004 0:16
À : openbeosnetteam@xxxxxxxxxxxxx
Objet : [openbeosnetteam] Re: DHCP Status + Help Needed
On 2004-10-12 at 23:56:04 [+0200], David Enderson wrote:
> Networking Team,
>
> I'm into my second week of unpaid vacation and have spent part of the
> time working on the Haiku DHCP implementation as promised. I've got a
> nearly complete understanding of the RFC and I've enough of the client
> together for some test messages with a DHCP server.
>
> (This is where the "Help Needed" part comes in)
>
> What I'm lacking is the ability to broadcast a UDP packet. I have
> googled for numerous examples and have been thoroughly frustrated. I
> think I can send a UDP packet, but I can't get broadcast to work. I
> implemented a working sockets implementation for an open source game a
> while back, so I think I can do this, I just need the...rosetta
> stone...if you will for UDP.
>
> Can anyone point me towards excellent, simple, and COMPILEABLE examples?
I just very recently learned how to do broadcasting myself. Attached is my
test app. It's definitely simple and compiles and runs under R5. About the
`excellent' part I don't know.
Note that POSIX defines the socket option SO_BROADCAST, that -- if I
understand it correctly -- has to be set (via setsockopt()) for both the
socket of the sender and the receiver. Since R5 doesn't know this option, I
can't set it. Don't know, if it is required for BONE/our stack.
CU, Ingo
Other related posts:
