[openbeos] Re: OBOS Networking
- From: Clay Vincent Schentrup <cvs@xxxxxxxxxxxxx>
- To: openbeos@xxxxxxxxxxxxx
- Date: Sun, 04 Aug 2002 00:11:53 -0500
>As I said, all the DHCP client will do is request an IP, get an answer
>and assign it to an interface. just check the ifconfig code and you
>will see how that works. For actually getting the IP you will have to
>read the RFC that explains DHCP (I don't have the number handy right
>now).
I hate to sound utterly dense here, but my question is still, how does it
interface with the net stack? I can easily read the exact protocol for talking
to the DHCP server and getting an IP. My question is what to "do" with it,
where to pass it off...what reads it..something like that.
Further, if we are changing networking to be more technically
sophisticated, I don't know that it even makes sense to have a binary called
"dhcp_client". Maybe the code for doing this work ought to be in some other
program, so that whatever parts of networking that are 'talking' to
"dhcp_client" can do it within the same app. I think it would be helpful for
me, and many of us, to have a clearly laid out structure for OBOS networking.
I still don't feel like that's been decided or discussed...and when you talk
about reading ifconfig code..are you saying that OBOS is going to use ifconfig?
eth0? Unix-style networking standards? Hmmmm....
Clay
Other related posts:
