Apparently, _Darryl Luff_, on 22/12/04 18:17,typed:
I found that after running an update last night, my laptop network
interfaces changed this morning. eth0 used to be the firewire
interface, and eth1 was the network. This morning, they are the opposite.
Yup, happened with me too couple of days ago. Probably the new version
of discover did that. That caused me a bit of a problem since I have an
iptables file doing masquarding. The solution was just to change the
interface I use as my LAN interface and all was well again. However,
dhcp was giving the problems. And since manual starting of dhcp caused
no problems, I knew that my iptables script was not the problem anymore.
So basically, if I start dhcp from it's /etc/init.d/dhcp script, it
doesn't work. But if I start dhcpd from command line, it does.
The file /etc/default/dhcp has a list of interfaces in it that DHCP
should run on. This file is used by /etc/init.d/dhcp. When you start
dhcpd manually, it doesn't use this file, so starts and runs on all
interfaces by default. When you use /etc/init.d/dhcp, it DOES use
/etc/default/dhcp, so only starts on the interfaces listed there.
Because the interface ordering has changed, this is probably pointing
to the wrong interface. So edit /etc/default/dhcp and make sure it's
pointing at the right interface.
Yes, you are right. I just noticed that my default dhcp file had eth1 in
it which should now be eth0!
Thanks. I have made the change and will report back in a few hours about
what happened.
->HS