DHCP doesn't appear to work, seems to be trying to get IPv6 address

jiewmeng · 2012-03-30 00:20:00

I noticed that this 2 days, my internet is down. I think the problem is that DHCP for IPv4 has stopped working.

$ sudo ip addr

    2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
    link/ether f4:6d:04:cd:36:34 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::f66d:4ff:fecd:3634/64 scope link 
       valid_lft forever preferred_lft forever

$ sudo dhcpcd                   
dhcpcd[1782]: version 5.5.4 starting
dhcpcd[1782]: eth0: sending IPv6 Router Solicitation
dhcpcd[1782]: eth0: broadcasting for a lease
dhcpcd[1782]: eth0: sending IPv6 Router Solicitation
dhcpcd[1782]: eth0: sending IPv6 Router Solicitation
dhcpcd[1782]: eth0: sending IPv6 Router Solicitation
dhcpcd[1782]: eth0: no IPv6 Routers available
dhcpcd[1782]: timed out
dhcpcd[1782]: forked to background, child pid 1798

Notice its just "sending IPv6 Router Solicitation", not IPv4?

I solved it by setting a static IP like:

dhcpcd -S ip_address=192.168.1.122/24 -S routers=192.168.0.1 -S domain_name_servers=8.8.8.8 eth0

But I'd like to know whats wrong? Am I right to say, `dhcpcd` is only trying to get IPv6 address? And how can I fix this?

Last edited by jiewmeng (2012-03-30 00:20:41)

/dev/zero · 2012-03-30 00:24:06

I'm also getting this. I'm not sure what's wrong - I have disabled IPv6. Thanks for that idea of the workaround .

Trilby · 2012-03-30 00:24:08

Perhaps not a complete explanation - but another solution with more information is in the wiki

EDIT: given /dev/zero's above comment this may not be useful, but I'll leave it just in case.

Last edited by Trilby (2012-03-30 00:24:43)

Gcool · 2012-03-30 05:31:18

The "sending IPv6 Router Solicitation" messages just mean that dhcpcd is trying to discover ipv6 routers on the link. It doesn't mean that it's only trying to query for ipv6 responses. If I set it up on a test machine here (which also has ipv6 disabled), I also get those "IPv6 Router Solicitation" messages, but it gets an ipv4 address assigned afterwards without any issues.

I know this is not an explanation of why your dhcp is not working (and why it keeps doing this even with ipv6 disabled), but just thought I'd mention it.

kmacleod · 2012-03-30 17:29:40

I'm having the same issue. Not getting an IPv4 address on startup.

But then running '/etc/rc.d/network stop && /etc/rc.d/network start' gets me a valid IPv4. Weird.

Downgrading dhcpcd from 5.5.5-1 to 5.5.4-1 fixed it.

dunek · 2012-03-30 20:38:09

rc.d network doesn't work for me too, i'll just use dhclient in the time being.

thinkdoom · 2013-10-12 09:51:26

i have meet the same problem. how to get the ipv4 addr.

[root@myarch ~]# ifconfig -a
ens160: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet6 fe80::20c:29ff:fee5:2f0e prefixlen 64 scopeid 0x20<link>
ether 00:0c:29:e5:2f:0e txqueuelen 1000 (Ethernet)
RX packets 9 bytes 2280 (2.2 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 55 bytes 14030 (13.7 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

[root@myarch ~]# systemctl status dhcpcd@ens160
dhcpcd@ens160.service - dhcpcd on ens160
Loaded: loaded (/usr/lib/systemd/system/dhcpcd@.service; enabled)
Active: failed (Result: exit-code) since Sat 2013-10-12 09:23:56 UTC; 23min ago
Process: 366 ExecStart=/usr/sbin/dhcpcd -q -w %I (code=exited, status=1/FAILURE)

Oct 12 09:23:26 myarch dhcpcd[366]: ens160: sending IPv6 Router Solicitation
Oct 12 09:23:26 myarch dhcpcd[366]: ens160: broadcasting for a lease
Oct 12 09:23:30 myarch dhcpcd[366]: ens160: sending IPv6 Router Solicitation
Oct 12 09:23:34 myarch dhcpcd[366]: ens160: sending IPv6 Router Solicitation
Oct 12 09:23:38 myarch dhcpcd[366]: ens160: sending IPv6 Router Solicitation
Oct 12 09:23:38 myarch dhcpcd[366]: ens160: no IPv6 Routers available
Oct 12 09:23:56 myarch dhcpcd[366]: timed out
Oct 12 09:23:56 myarch systemd[1]: dhcpcd@ens160.service: control process exited, code=exited status=1
Oct 12 09:23:56 myarch systemd[1]: Failed to start dhcpcd on ens160.
Oct 12 09:23:56 myarch systemd[1]: Unit dhcpcd@ens160.service entered failed state.

[root@myarch ~]# journalctl -xn
-- Logs begin at Tue 2013-03-26 10:53:15 UTC, end at Sat 2013-10-12 09:48:04 UTC. --
Oct 12 09:47:34 myarch vmsvc[160]: [ warning] [guestinfo] Failed to get OS info.
Oct 12 09:47:34 myarch vmsvc[160]: [ warning] [vmsvc] HostinfoReadDistroFile: Cannot work with empty file.
Oct 12 09:47:34 myarch vmsvc[160]: [ warning] [vmsvc] HostinfoOSData: Error: no distro file found
Oct 12 09:47:34 myarch vmsvc[160]: [ warning] [guestinfo] Failed to get OS info.
Oct 12 09:48:04 myarch vmsvc[160]: [ warning] [vmsvc] HostinfoReadDistroFile: Cannot work with empty file.
Oct 12 09:48:04 myarch vmsvc[160]: [ warning] [vmsvc] HostinfoOSData: Error: no distro file found
Oct 12 09:48:04 myarch vmsvc[160]: [ warning] [guestinfo] Failed to get OS info.
Oct 12 09:48:04 myarch vmsvc[160]: [ warning] [vmsvc] HostinfoReadDistroFile: Cannot work with empty file.
Oct 12 09:48:04 myarch vmsvc[160]: [ warning] [vmsvc] HostinfoOSData: Error: no distro file found
Oct 12 09:48:04 myarch vmsvc[160]: [ warning] [guestinfo] Failed to get OS info.

hydn · 2014-09-16 17:54:08

any fix?

2ManyDogs · 2014-09-16 18:02:03

hydn, rather than bumping multiple old threads by OPs who have not posted for many months, may I suggest that you start a new thread with your specific problem, and link back to these old threads if you think they apply?

jasonwryan · 2014-09-16 18:03:20

Closing...

Arch Linux

#1 2012-03-30 00:20:00

DHCP doesn't appear to work, seems to be trying to get IPv6 address

#2 2012-03-30 00:24:06

Re: DHCP doesn't appear to work, seems to be trying to get IPv6 address

#3 2012-03-30 00:24:08

Re: DHCP doesn't appear to work, seems to be trying to get IPv6 address

#4 2012-03-30 05:31:18

Re: DHCP doesn't appear to work, seems to be trying to get IPv6 address

#5 2012-03-30 17:29:40

Re: DHCP doesn't appear to work, seems to be trying to get IPv6 address

#6 2012-03-30 20:38:09

Re: DHCP doesn't appear to work, seems to be trying to get IPv6 address

#7 2013-10-12 09:51:26

Re: DHCP doesn't appear to work, seems to be trying to get IPv6 address

#8 2014-09-16 17:54:08

Re: DHCP doesn't appear to work, seems to be trying to get IPv6 address

#9 2014-09-16 18:02:03

Re: DHCP doesn't appear to work, seems to be trying to get IPv6 address

#10 2014-09-16 18:03:20

Re: DHCP doesn't appear to work, seems to be trying to get IPv6 address

Board footer