There is a simple workaround to this bug but it has limitations.
DHCP is working for Linux iff the <ip>tag</ip> in
/var/dfcfg/dfdhcp.xml is set to 0.0.0.0.
This means only one server can be configured which will
listen on all interfaces.
Since each server was only designed to work on one interface
you can only have one pool.
On multi-interfaced systems, this can cause a problem since
a request from another interface will get assigned an IP
which was intended for another interface.
This work around should work flawlessly on single interface
systems.
Tech info:
When the config is set correctly, it seems as though Linux
is listening on the correct interface as it should, BUT is
NOT sending an async signal to the DHCP application.
This code all works 100% on Windows using winsock (which is
basically the same as Linux networking API), and like I
said, I can see it listening on the correct
interface but I don't get a signal...another kernel bug?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=773384
There is a simple workaround to this bug but it has limitations.
DHCP is working for Linux iff the <ip>tag</ip> in
/var/dfcfg/dfdhcp.xml is set to 0.0.0.0.
This means only one server can be configured which will
listen on all interfaces.
Since each server was only designed to work on one interface
you can only have one pool.
On multi-interfaced systems, this can cause a problem since
a request from another interface will get assigned an IP
which was intended for another interface.
This work around should work flawlessly on single interface
systems.
Tech info:
When the config is set correctly, it seems as though Linux
is listening on the correct interface as it should, BUT is
NOT sending an async signal to the DHCP application.
This code all works 100% on Windows using winsock (which is
basically the same as Linux networking API), and like I
said, I can see it listening on the correct
interface but I don't get a signal...another kernel bug?