Just checked man dhcpd3 (now in gutsy: 3.0.5):
dhcpd [ -p port ] [ -f ] [ -d ] [ -q ] [ -t | -T ] [ -cf config-file ] [ -lf
lease-file ] [ -pf pid-file ] [
-tf trace-output-file ] [ -play trace-playback-file ] [ if0 [ ...ifN ] ]
...
So IMHO your line is wrong, too. It looks just like the one that does
*not* work in my environment.
I'm not (yet) familiar with virtualization but I guess *if* it works in your
environment it is because of not having two physically separated interfaces.
In my example with two NICs eth0 and eth1 only clients connected to eth0 got
leases. I guess because of dhcpd ignoring the interfaces spec at all and
guessing itself for the ones serving for (in my env. only eth0 then).
At least in feisty and gutsy is seems not to fixed. And I'm quite sure
it is also not in hardy as there only the micro revision changed (3.0.6)
and I do not expect the parameter layout having changed with such micro
updated number ... ?
** Changed in: dhcp3 (Ubuntu)
Status: Fix Released => New
--
/etc/init.d/dhcp3-server starts dhcpd3 with parameters in wrong order
($INTERFACES)
https://bugs.launchpad.net/bugs/187434
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
