David Enderson wrote:
I guess we can consider DHCP being a protocol and making a network protocol kernel module make sense to me. However, currently your (C++) code can't be refactoring into a kernel module like this, before move from socket API to internal API to send and receive UDP packets, iterate and setup interfaces.
I agree. What you said makes perfect sense that the DHCP client should be a protocol module.
I knew whatever I wrote would have to be switched all around and maybe be converted from C++ to C code. I just tried to organize it well and write something since I knew I wouldn't be able to guess the correct format the first time. When I get the DHCP conversation completely working, it looks like my next task will be to make a kernel protocol module.
Which existing kernel protocol module would you suggest I use as an example to make mine from?
BTW, maybe it's a good occasion to write a kernel module exporting the basic (without DNS resolver support at start) sockets API to kernelland. That would help network-related drivers (netblock devices?) and kernel add-ons (network filesystems) but also porting your DHCP_client code...
Since I don't know the exact status of everything, I'll take your word on the fact that its needed. Are you saying this is needed before I can get my DHCP protocol module to work?
Bye, Waldemar