1 |
Hi Iain,. |
2 |
|
3 |
On Sat, 2007-10-27 at 21:58 +0930, Iain Buchanan wrote: |
4 |
> On Sat, 2007-10-27 at 13:48 +0200, Jules Colding wrote: |
5 |
> > Hi, |
6 |
> > |
7 |
> > My "/etc/conf.d/net" says: |
8 |
> > |
9 |
> > config_eth0=( "dhcp" ) |
10 |
> > fallback_eth0=( "192.168.3.3/24" ) |
11 |
> > fallback_route_eth0=( "default via 192.168.3.1" ) |
12 |
> > |
13 |
> > |
14 |
> > But dhcpcd is ignoring this. Instead it is using |
15 |
> > "/var/lib/dhcpcd/dhcpcd-eth0.info" to set eth0. This looks like the '-E' |
16 |
> > option is used, but where? How can I make my fallback configuration |
17 |
> > effective? |
18 |
> |
19 |
> is it by any chance assigning you a 169... address? |
20 |
|
21 |
Yes, indeed it is. |
22 |
|
23 |
|
24 |
> Did you recently |
25 |
> upgrade dhcpcd to ... around ... 3.1.6 I think? |
26 |
|
27 |
3.1.5-r1 actually. |
28 |
|
29 |
|
30 |
> Anyway, it now tries |
31 |
> "zeroconf" or whatever it's called, to give you an address when there's |
32 |
> no server around. Personally I don't like it, but you can decide :) |
33 |
> |
34 |
> If you read your elog messages you would have seen: |
35 |
> |
36 |
> "You have installed dhcpcd with zeroconf support. |
37 |
> This means that it will always obtain an IP address even if no |
38 |
> DHCP server can be contacted, which will break any existing |
39 |
> failover support you may have configured in your net configuration. |
40 |
> This behaviour can be controlled with the -L flag. |
41 |
> See the dhcpcd man page for more details." |
42 |
> |
43 |
> get rid of the zeroconf use flag or use -L. |
44 |
|
45 |
|
46 |
Thanks a lot, will do. I didn't catch that message. |
47 |
|
48 |
Thanks, |
49 |
jules |
50 |
|
51 |
|
52 |
|
53 |
-- |
54 |
gentoo-user@g.o mailing list |