DHCP over ethernet problems

dilberto · 2014-01-26 02:20:39

I just moved, connected to the local wireless network through a NetGEAR wifi adapter. The adapter works fine for the same desktop under windows (dual boot) and also a small NIS box (Stora running CentOS). But under Arch I cannot connect to the network anymore. Things seem sort of OK. There was no update. I'm fairly stymied. Thanks for any input or ideas

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: enp2s0f0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT group default qlen 1000                                                                           
    link/ether 00:25:90:d1:bd:48 brd ff:ff:ff:ff:ff:ff                                                                                                                                   
3: enp2s0f1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000                                                                                   
    link/ether 00:25:90:d1:bd:49 brd ff:ff:ff:ff:ff:ff   

sudo systemctl start  dhcpcd@enp2s0f0.service

$ systemctl status dhcpcd@enp2s0f0.service
dhcpcd@enp2s0f0.service - dhcpcd on enp2s0f0
   Loaded: loaded (/usr/lib/systemd/system/dhcpcd@.service; disabled)
   Active: active (running) since Sat 2014-01-25 18:58:33 MST; 14min ago
  Process: 3957 ExecStop=/usr/bin/dhcpcd -x %I (code=exited, status=0/SUCCESS)
  Process: 4032 ExecStart=/usr/bin/dhcpcd -q -w %I (code=exited, status=0/SUCCESS)
 Main PID: 4130 (dhcpcd)
   CGroup: /system.slice/system-dhcpcd.slice/dhcpcd@enp2s0f0.service
           └─4130 /usr/bin/dhcpcd -q -w enp2s0f0

Jan 25 19:12:59 xri-geo dhcpcd[4130]: enp2s0f0: adding host route to 192.168.2.16 via 127.0.0.1
Jan 25 19:12:59 xri-geo dhcpcd[4130]: enp2s0f0: adding route to 192.168.2.0/24
Jan 25 19:12:59 xri-geo dhcpcd[4130]: enp2s0f0: adding default route via 192.168.2.1
Jan 25 19:12:59 xri-geo dhcpcd[4130]: enp2s0f0: carrier lost
Jan 25 19:12:59 xri-geo dhcpcd[4130]: enp2s0f0: deleting host route to 192.168.2.16 via 127.0.0.1
Jan 25 19:12:59 xri-geo dhcpcd[4130]: enp2s0f0: deleting route to 192.168.2.0/24
Jan 25 19:12:59 xri-geo dhcpcd[4130]: enp2s0f0: deleting default route via 192.168.2.1
Jan 25 19:13:01 xri-geo dhcpcd[4130]: enp2s0f0: carrier acquired
Jan 25 19:13:01 xri-geo dhcpcd[4130]: enp2s0f0: soliciting an IPv6 router
Jan 25 19:13:01 xri-geo dhcpcd[4130]: enp2s0f0: rebinding lease of 192.168.2.16

A little later

Jan 25 19:13:31 xri-geo dhcpcd[4130]: enp2s0f0: soliciting an IPv6 router
Jan 25 19:13:31 xri-geo dhcpcd[4130]: enp2s0f0: rebinding lease of 192.168.2.16
Jan 25 19:13:36 xri-geo dhcpcd[4130]: enp2s0f0: leased 192.168.2.16 for 1209600 seconds
Jan 25 19:13:36 xri-geo dhcpcd[4130]: enp2s0f0: adding host route to 192.168.2.16 via 127.0.0.1
Jan 25 19:13:36 xri-geo dhcpcd[4130]: enp2s0f0: adding route to 192.168.2.0/24
Jan 25 19:13:36 xri-geo dhcpcd[4130]: enp2s0f0: adding default route via 192.168.2.1
Jan 25 19:13:37 xri-geo dhcpcd[4130]: enp2s0f0: carrier lost
Jan 25 19:13:37 xri-geo dhcpcd[4130]: enp2s0f0: deleting host route to 192.168.2.16 via 127.0.0.1
Jan 25 19:13:37 xri-geo dhcpcd[4130]: enp2s0f0: deleting route to 192.168.2.0/24
Jan 25 19:13:37 xri-geo dhcpcd[4130]: enp2s0f0: deleting default route via 192.168.2.1

Jan 25 19:13:51 xri-geo dhcpcd[4130]: enp2s0f0: adding host route to 192.168.2.16 via 127.0.0.1
Jan 25 19:13:51 xri-geo dhcpcd[4130]: enp2s0f0: adding route to 192.168.2.0/24
Jan 25 19:13:51 xri-geo dhcpcd[4130]: enp2s0f0: adding default route via 192.168.2.1
Jan 25 19:13:51 xri-geo dhcpcd[4130]: enp2s0f0: carrier lost
Jan 25 19:13:51 xri-geo dhcpcd[4130]: enp2s0f0: deleting host route to 192.168.2.16 via 127.0.0.1
Jan 25 19:13:51 xri-geo dhcpcd[4130]: enp2s0f0: deleting route to 192.168.2.0/24
Jan 25 19:13:51 xri-geo dhcpcd[4130]: enp2s0f0: deleting default route via 192.168.2.1
Jan 25 19:13:53 xri-geo dhcpcd[4130]: enp2s0f0: carrier acquired
Jan 25 19:13:53 xri-geo dhcpcd[4130]: enp2s0f0: soliciting an IPv6 router
Jan 25 19:13:53 xri-geo dhcpcd[4130]: enp2s0f0: rebinding lease of 192.168.2.16


$ journalctl -xn
-- Logs begin at Thu 2013-09-05 08:46:59 MDT, end at Sat 2014-01-25 19:14:15 MST. --
Jan 25 19:14:13 xri-geo dhcpcd[4130]: enp2s0f0: carrier lost
Jan 25 19:14:13 xri-geo dhcpcd[4130]: enp2s0f0: deleting host route to 192.168.2.16 via 127.0.0.1
Jan 25 19:14:13 xri-geo dhcpcd[4130]: enp2s0f0: deleting route to 192.168.2.0/24
Jan 25 19:14:13 xri-geo dhcpcd[4130]: enp2s0f0: deleting default route via 192.168.2.1
Jan 25 19:14:13 xri-geo dhcpcd[17181]: enp2s0f0: MTU restored to 1500
Jan 25 19:14:13 xri-geo kernel: igb 0000:02:00.0: changing MTU from 1492 to 1500
Jan 25 19:14:15 xri-geo dhcpcd[4130]: enp2s0f0: carrier acquired
Jan 25 19:14:15 xri-geo kernel: igb: enp2s0f0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: RX/TX
Jan 25 19:14:15 xri-geo dhcpcd[4130]: enp2s0f0: soliciting an IPv6 router
Jan 25 19:14:15 xri-geo dhcpcd[4130]: enp2s0f0: rebinding lease of 192.168.2.16

$ ping -c 3 www.google.com
ping: unknown host www.google.com
 
tirons@xri-geo ~]$ ping -c 3 127.0.0.1
PING 127.0.0.1 (127.0.0.1) 56(84) bytes of data.
64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0.025 ms
64 bytes from 127.0.0.1: icmp_seq=2 ttl=64 time=0.017 ms
64 bytes from 127.0.0.1: icmp_seq=3 ttl=64 time=0.025 ms

--- 127.0.0.1 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 1999ms
rtt min/avg/max/mdev = 0.017/0.022/0.025/0.005 ms

$ ping -c 3 8.8.8.8
connect: Network is unreachable

lykwydchykyn · 2014-01-26 02:42:55

Are you using Network Manager? If you're using network manager you need to disable the dhcpcd service.

dilberto · 2014-01-26 02:49:26

Not using NetworkManager.

After fighting this for two nights I broke down and learned how to install packages offline. Another case of dhclient magic. Using dhclient instead works!
I have no idea why. Or what would have caused this. Thanks though for the idea.

WonderWoofy · 2014-01-26 03:57:42

I'm curious as to why your wifi adapter is being given an ethernet name (enp*). That seems particularly odd... as though the wifi device is misrepresenting itself. Can you tell more about your little piece of hardware there? I know you already solved this with dhclient, but I'm just curious.

If it is a pci device (which it probably isn't judging by the persistent name) use 'lspci -vnn' and post the section that tells about the device. Otherwise if it is a USB device, can you post the output of 'lsusb'?

dilberto · 2014-01-26 13:38:30

The actual product is a NetGEAR "Universal WiFI Adapter for Smart TV & Blu-ray". I should have called it an access point I suppose; so yes it is misrepresenting itself, but that is the point. It interfaces through ethernet cable, which is also plugged into an ethernet switch, and everything else on the switch works as expected. But arch only works with dhclient.

It's probably enough of a fringe case that I don't know if its worth spending peoples time on to track down exactly what is going on. It's quite plausible that NetGEAR is to blame, and that would be very difficult to diagnose I think.

Anyhow, I am not around the machine right now. In the sake of having the info out there I will post the lspce info to see if it shows up. But since its not really connected to the computer I don't think it will see it. The adapter should be invisible I would think.

WonderWoofy · 2014-01-26 16:06:03

Ah, okay. Thinkgs make a bit more sense now as to why you are running into this issue. Thanks for humoring me.

If your curiosity gets a hold of you, debugging might not actually be as hard as you think. Netgear actually uses OpenWRT for their firmware and although it is locked down, you might be able to employ the Netgear hack to allow yourself telnet access. If you are able to gain command line access to teh device, I think you'd be pleasantly surprised as to how familiar things are in there.

Arch Linux

#1 2014-01-26 02:20:39

DHCP over ethernet problems

#2 2014-01-26 02:42:55

Re: DHCP over ethernet problems

#3 2014-01-26 02:49:26

Re: DHCP over ethernet problems

#4 2014-01-26 03:57:42

Re: DHCP over ethernet problems

#5 2014-01-26 13:38:30

Re: DHCP over ethernet problems

#6 2014-01-26 16:06:03

Re: DHCP over ethernet problems

Board footer