dhcpcd-discuss

Re: dhcpcd changed behavior after upgrading to kernel 3.18

Giorgio

Fri Jan 23 08:42:05 2015

Il 22.01.2015 21:15 Roy Marples ha scritto:

Hi Giorgio

On Thursday 22 Jan 2015 09:55:39 iw3gtf@xxxxxxxxxx [1]wrote:

Hi all, I use dhcpcd 6.6.x in some network configuration scripts also
to configure static addresses, with the cmdline option '-S
ip_address=.../...'. I also found it very handy to use different labels
for the network device to be able to configure/unconfigure different
addresses on the same device as in the following example: # dhcpcd -S
ip_address=192.168.0.10/24 eth0:static # dhcpcd -S
ip_address=10.1.2.3/8 eth0:factory ...

Well, that *is* an interesting use of dhcpcd :)
In would recommend using the -4 flag will all of them bar one, otherwise
you
will get IPv6 autoconf running on each of them which would be .....
interesting. I really don't know how that would work out - it might work,
it
might go tits up.

...

Fixed here:

http://roy.marples.name/projects/dhcpcd/info/6f030781cf1d89f5962f84392adf48f4a1093bc2
[2]

Thanks

Roy

Hi Roy,

thanks for the fix, I've just verified things works now as expected.

My workaround was to build dhcpcd without ipv6 (--disable-ipv6),
I've also tested calling the daemon with '-4' to force ipv4 only
but it has the drawback that it adds a '-4' to the pid file and
to kill it back you have to issue a:

# dhcpcd -k eth0:whatever-4

that's an inconvenient asymmetry is the calls...

I'm not an expert on dhcp or even ipv6; could you please explain, shortly and without too many technical details, what kind of problems could arise when
'IPV6 autoconf' is 'running on each of them'.
Here is an example of what I get when adding two 'static' addresses to my
eth0:

# dhcpcd -S ip_address=192.168.0.10/24 eth0:giorgio_1
# dhcpcd -S ip_address=11.0.0.1/8 eth0:giorgio_2
# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether xx:xx:xx:xx:xx:xx brd ff:ff:ff:ff:ff:ff
    inet 10.0.0.54/8 brd 10.255.255.255 scope global eth0
       valid_lft forever preferred_lft forever
    inet 192.168.0.10/24 brd 192.168.0.255 scope global eth0:giorgio_1
       valid_lft forever preferred_lft forever
    inet 11.0.0.1/8 brd 11.255.255.255 scope global eth0:giorgio_2
       valid_lft forever preferred_lft forever
    inet6 fe80::203:c5ff:fe07:a5/64 scope link
       valid_lft forever preferred_lft forever


giorgio

--
Giorgio, iw3gtf@xxxxxxxxxx



Connetti gratis il mondo con la nuova indoona: hai la chat, le chiamate, le video chiamate e persino le chiamate di gruppo.
E chiami gratis anche i numeri fissi e mobili nel mondo!
Scarica subito l’app Vai su https://www.indoona.com/



Follow-Ups:
Re: dhcpcd changed behavior after upgrading to kernel 3.18Roy Marples
References:
dhcpcd changed behavior after upgrading to kernel 3.18iw3gtf
Re: dhcpcd changed behavior after upgrading to kernel 3.18Roy Marples
Archive administrator: postmaster@marples.name