You are not logged in.
Hello!
Since a couple of days I am not able to get an IPv4 address from my Route r(Fritzbox 7270) on my computer. My Notebook also running Arch is fine.
IPv6 connections on the computer are working. The IPv6 address gets autoconfigured.
I use NetworkManager and here is a portion of the log file: http://pastebin.com/xaEkCyFh
So the computer sends a DHCPREQUEST, gets a DHCPOFFER from the routers IP (192.168.178.1) but this gets repeated a couple of times until the log says that the request timed out.
When I set a fixed IP, everything works fine, so I'm a bit clueless about this.
Here are the NetworkManager configuration files
Fixed IP:
[802-3-ethernet]
port=mii
[connection]
id=Feste IP
uuid=ad2fb01e-55b9-4878-a9f1-2b1a8edeee79
type=802-3-ethernet
permissions=user:andreas:;
autoconnect=false
zone=
[ipv6]
method=auto
ip6-privacy=1
[ipv4]
method=manual
dns=192.168.178.1;
dns-search=fritz.box;
address1=192.168.178.19/24,192.168.178.1
may-fail=falseNormally used with DHCP:
[802-3-ethernet]
port=mii
[connection]
id=Kabelgebundene Verbindung
uuid=fc8abf87-7b73-45ae-a9d3-1bde72a326fc
type=802-3-ethernet
timestamp=1378315327
zone=
[ipv6]
method=auto
ip6-privacy=1
[ipv4]
method=auto
dhcp-client-id=ANDI
may-fail=falseAn interesting thing might be, that I dual boot the computer with Windows 8. There, DHCPv4 works, so the networking part seems to be fine.
The problem occured out of sudden and I am not aware of any configuration changes... But since I had IPv6 running all the time I might have noticed this very late so I can't blame an update or whatever.
Ethernet driver is r8169, it's an onboard Realtek chip.
Can anybody help me with this?
Last edited by And1G (2013-09-04 17:26:50)
Offline
I'm having the same issue. I get the IPv6 address but no IPv4.
Where can I look for the logs?
Offline
Bump
I just performed 'pacman -Syu' on one of my machines and since then I can no longer get any IPv4 address via DHCP (It's a IPv4 network).
The machine uses a "Intel Corporation 82579LM Gigabit Network Connection (rev 04)" network card. Having looked at 'ip link' and 'journalctl' I see no reason to suspect that there's something wrong with the network card
$ ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000
link/ether <MAC address> brd ff:ff:ff:ff:ff:ff"Found device 82579LM Gigabit Network Connection" occurs in the output of 'journalctl' at every reboot.
After having added the debug switch '-d' to my dhcpcd call 'systemctl status dhcpcd@eno1.service' produces (numbers replaced with <...>)
Nov 30 15:35:29 <hostname> systemd[1]: Starting dhcpcd on eno1...
Nov 30 15:35:29 <hostname> dhcpcd[1653]: version 6.1.0 starting
Nov 30 15:35:29 <hostname> dhcpcd[1653]: eno1: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks' PREINIT
Nov 30 15:35:29 <hostname> dhcpcd[1653]: eno1: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks' CARRIER
Nov 30 15:35:29 <hostname> dhcpcd[1653]: eno1: soliciting an IPv6 router
Nov 30 15:35:29 <hostname> dhcpcd[1653]: eno1: sending Router Solicitation
Nov 30 15:35:29 <hostname> dhcpcd[1653]: eno1: using ClientID <...>
Nov 30 15:35:29 <hostname> dhcpcd[1653]: eno1: reading lease `/var/lib/dhcpcd/dhcpcd-eno1.lease'
Nov 30 15:35:29 <hostname> dhcpcd[1653]: eno1: rebinding lease of <...>
Nov 30 15:35:29 <hostname> dhcpcd[1653]: eno1: sending REQUEST (xid <...>), next in 4.19 seconds
Nov 30 15:35:33 <hostname> dhcpcd[1653]: eno1: sending Router Solicitation
Nov 30 15:35:33 <hostname> dhcpcd[1653]: eno1: sending REQUEST (xid <...>), next in 9.00 seconds
Nov 30 15:35:34 <hostname> dhcpcd[1653]: eno1: soliciting a DHCP lease
Nov 30 15:35:34 <hostname> dhcpcd[1653]: eno1: sending DISCOVER (xid <...>), next in 4.87 seconds
Nov 30 15:35:37 <hostname> dhcpcd[1653]: eno1: sending Router Solicitation
Nov 30 15:35:39 <hostname> dhcpcd[1653]: eno1: sending DISCOVER (xid <...>), next in 7.42 seconds
Nov 30 15:35:41 <hostname> dhcpcd[1653]: eno1: sending Router Solicitation
Nov 30 15:35:41 <hostname> dhcpcd[1653]: eno1: no IPv6 Routers available
Nov 30 15:35:46 <hostname> dhcpcd[1653]: eno1: sending DISCOVER (xid <...>), next in 15.56 seconds
Nov 30 15:35:59 <hostname> dhcpcd[1653]: timed out
Nov 30 15:35:59 <hostname> dhcpcd[1653]: exited
Nov 30 15:35:59 <hostname> systemd[1]: dhcpcd@eno1.service: control process exited, code=exited status=1
Nov 30 15:35:59 <hostname> systemd[1]: Failed to start dhcpcd on eno1.
Nov 30 15:35:59 <hostname> systemd[1]: Unit dhcpcd@eno1.service entered failed state.I'm noting multiple attempts at "sending DISCOVER" and then timeout. I've tried using the 'ipv4only' option for dhcpcd but that only removes the talk about IPv6 router from the output.
Looking at "/var/log/pacman.log", among the many packages upgraded (last system upgrade was nov 8th), I see dhcpcd:
upgraded dhcpcd (6.0.5-1 -> 6.1.0-1)
I tried downgrading dhcpcd to 6.0.5-1 (including "/etc/dhcpcd.conf") and rebooting but it made no difference.
Is it possible to verify connection to the DHCP server somehow? Any ideas about what could be wrong?
I found a similar post:
https://bbs.archlinux.org/viewtopic.php?id=172637
where "Jumblemuddle" is having trouble with his/her computer "begins to solicite a dhcp lease then times out and exits".
Thank you for reading.
Offline
d'oh!! Un-bump!
I had a chat with my admin today and it turned out that the DHCP server was down for maintenance this weekend. So, as often is the case when one doesn't find a solution nor a bug report anywhere, the cause of my problem was trivial. If you happen to be an admin, feel free to remove my posts, or perhaps better yet, clarify how I can check the state of the DHCP server? (I still don't know this)
Thank you
Offline