Carlos,
As a debugging aid, I've attached a stand-alone program that uses the same loop as the patch for dhcpd: running it on the CC right after a run-instances should result in output like this:
root@eucahost-4-243:~# gcc getifaddrs.c; ./a.out INTERFACE=lo SCRUBBEDINTERFACE=lo ADDR=127.0.0.1 INTERFACE=eth4 SCRUBBEDINTERFACE=eth4 ADDR=169.254.169.254 INTERFACE=eth4 SCRUBBEDINTERFACE=eth4 ADDR=192.168.6.148 INTERFACE=eth4:priv SCRUBBEDINTERFACE=eth4 ADDR=172.19.1.1 INTERFACE=eth4:pub SCRUBBEDINTERFACE=eth4 ADDR=192.168.16.40 INTERFACE=virbr0 SCRUBBEDINTERFACE=virbr0 ADDR=192.168.122.1
It will help, I think, to see the output of this program on a failing system, if that is possible!
Regards, -Dan
Carlos,
As a debugging aid, I've attached a stand-alone program that uses the same loop as the patch for dhcpd: running it on the CC right after a run-instances should result in output like this:
root@eucahost- 4-243:~ # gcc getifaddrs.c; ./a.out CE=lo ADDR=127.0.0.1 CE=eth4 ADDR=169. 254.169. 254 CE=eth4 ADDR=192.168.6.148 CE=eth4 ADDR=172.19.1.1 CE=eth4 ADDR=192.168.16.40 CE=virbr0 ADDR=192.168.122.1
INTERFACE=lo SCRUBBEDINTERFA
INTERFACE=eth4 SCRUBBEDINTERFA
INTERFACE=eth4 SCRUBBEDINTERFA
INTERFACE=eth4:priv SCRUBBEDINTERFA
INTERFACE=eth4:pub SCRUBBEDINTERFA
INTERFACE=virbr0 SCRUBBEDINTERFA
It will help, I think, to see the output of this program on a failing system, if that is possible!
Regards,
-Dan