On Sat, 2007-10-27 at 13:48 +0200, Jules Colding wrote: > Hi, > > My "/etc/conf.d/net" says: > > config_eth0=( "dhcp" ) > fallback_eth0=( "192.168.3.3/24" ) > fallback_route_eth0=( "default via 192.168.3.1" ) > > > But dhcpcd is ignoring this. Instead it is using > "/var/lib/dhcpcd/dhcpcd-eth0.info" to set eth0. This looks like the '-E' > option is used, but where? How can I make my fallback configuration > effective?
is it by any chance assigning you a 169... address? Did you recently upgrade dhcpcd to ... around ... 3.1.6 I think? Anyway, it now tries "zeroconf" or whatever it's called, to give you an address when there's no server around. Personally I don't like it, but you can decide :) If you read your elog messages you would have seen: "You have installed dhcpcd with zeroconf support. This means that it will always obtain an IP address even if no DHCP server can be contacted, which will break any existing failover support you may have configured in your net configuration. This behaviour can be controlled with the -L flag. See the dhcpcd man page for more details." get rid of the zeroconf use flag or use -L. HTH, -- Iain Buchanan <iaindb at netspace dot net dot au> In ancient China there is a legend that one day a child will be born from a dragon, grow to be a man, and vanquish evil from the land. That man is not Chuck Norris, because Chuck Norris killed that man. -- [EMAIL PROTECTED] mailing list
