[SOLVED] Unable to connect to LAN

numb3rz · 2017-07-28 00:28:10

I have been running Arch for just over a year now and it's been going really well. Though recently my PC has been unable to connect via both Ethernet and WiFi to the router. After searching hours on end through the wiki and forums, I've not managed to find anything to help resolve the issue.

Connecting soley through dhcpcd without NetworkManager still causes the timeout error.
I have bumped up the timeout period from 30 seconds to 3 minutes as recommended in various posts.
WiFi and Ethernet cable to the router work perfectly fine from my laptop (also running Arch).
I've tried interchaning the following options in /etc/dhcpcd.conf: noipv4ll, duid, clientid, require dhcp_server_identifier
Worked through the entirety of the dhcpcd wiki page, including troubleshooting the timeout delay.

If you require any extra information than what I have already supplied, please let me know. Thank you.

> lspci

00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] RS780 Host Bridge
00:02.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] RS780 PCI to PCI bridge (ext gfx port 0)
00:04.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] RS780/RS880 PCI to PCI bridge (PCIE port 0)
00:06.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] RS780 PCI to PCI bridge (PCIE port 2)
00:07.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] RS780/RS880 PCI to PCI bridge (PCIE port 3)
00:11.0 SATA controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 SATA Controller [IDE mode]
00:12.0 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI0 Controller
00:12.1 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0 USB OHCI1 Controller
00:12.2 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB EHCI Controller
00:13.0 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI0 Controller
00:13.1 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0 USB OHCI1 Controller
00:13.2 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB EHCI Controller
00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 SMBus Controller (rev 3c)
00:14.1 IDE interface: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 IDE Controller
00:14.2 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 Azalia (Intel HDA)
00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 LPC host controller
00:14.4 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 PCI to PCI Bridge
00:14.5 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI2 Controller
00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h Processor Function 0
00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h Processor Function 1
00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h Processor Function 2
00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h Processor Function 3
00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h Processor Function 4
00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h Processor Function 5
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Turks XT [Radeon HD 6670/7670]
01:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Turks HDMI Audio [Radeon HD 6500/6600 / 6700M Series]
02:00.0 USB controller: Etron Technology, Inc. EJ168 USB 3.0 Host Controller (rev 01)
03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 06)
04:00.0 USB controller: Etron Technology, Inc. EJ168 USB 3.0 Host Controller (rev 01)
05:06.0 Network controller: Ralink corp. RT2561/RT61 802.11g PCI

> ip link

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000
    link/ether 94:de:80:7a:b7:85 brd ff:ff:ff:ff:ff:ff
3: wlp5s6: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN mode DORMANT group default qlen 1000
link/ether f2:a3:0d:da:e3:88 brd ff:ff:ff:ff:ff:ff

> journalctl

Jul 28 00:41:01 megatron NetworkManager[2017]: <info>  [1501198861.0851] device (enp3s0): Activation: starting connection 'Wired connection 1' (f3b682e7-01e9-4dfd-b075-566d8ff21487)
Jul 28 00:41:01 megatron NetworkManager[2017]: <info>  [1501198861.0854] audit: op="connection-activate" uuid="f3b682e7-01e9-4dfd-b075-566d8ff21487" name="Wired connection 1" pid=764 uid=1000 result="success"
Jul 28 00:41:01 megatron NetworkManager[2017]: <info>  [1501198861.0858] device (enp3s0): state change: disconnected -> prepare (reason 'none', internal state 'managed')
Jul 28 00:41:01 megatron NetworkManager[2017]: <info>  [1501198861.0862] manager: NetworkManager state is now CONNECTING
Jul 28 00:41:01 megatron NetworkManager[2017]: <info>  [1501198861.0883] device (enp3s0): state change: prepare -> config (reason 'none', internal state 'managed')
Jul 28 00:41:01 megatron NetworkManager[2017]: <info>  [1501198861.0900] device (enp3s0): state change: config -> ip-config (reason 'none', internal state 'managed')
Jul 28 00:41:01 megatron NetworkManager[2017]: <info>  [1501198861.0914] dhcp4 (enp3s0): activation: beginning transaction (timeout in 180 seconds)
Jul 28 00:44:01 megatron NetworkManager[2017]: <warn>  [1501199041.4860] dhcp4 (enp3s0): request timed out
Jul 28 00:44:01 megatron NetworkManager[2017]: <info>  [1501199041.4860] dhcp4 (enp3s0): state changed unknown -> timeout
Jul 28 00:44:01 megatron NetworkManager[2017]: <info>  [1501199041.5023] dhcp4 (enp3s0): canceled DHCP transaction
Jul 28 00:44:01 megatron NetworkManager[2017]: <info>  [1501199041.5023] dhcp4 (enp3s0): state changed timeout -> done
Jul 28 00:44:01 megatron NetworkManager[2017]: <info>  [1501199041.5026] device (enp3s0): state change: ip-config -> failed (reason 'ip-config-unavailable', internal state 'managed')
Jul 28 00:44:01 megatron NetworkManager[2017]: <info>  [1501199041.5027] manager: NetworkManager state is now DISCONNECTED
Jul 28 00:44:01 megatron NetworkManager[2017]: <warn>  [1501199041.5031] device (enp3s0): Activation: failed for connection 'Wired connection 1'
Jul 28 00:44:01 megatron NetworkManager[2017]: <info>  [1501199041.5044] device (enp3s0): state change: failed -> disconnected (reason 'none', internal state 'managed')
Jul 28 00:44:01 megatron NetworkManager[2017]: <info>  [1501199041.5117] policy: auto-activating connection 'Wired connection 1'
Jul 28 00:44:01 megatron NetworkManager[2017]: <info>  [1501199041.5171] device (enp3s0): Activation: starting connection 'Wired connection 1' (f3b682e7-01e9-4dfd-b075-566d8ff21487)
Jul 28 00:44:01 megatron NetworkManager[2017]: <info>  [1501199041.5177] device (enp3s0): state change: disconnected -> prepare (reason 'none', internal state 'managed')
Jul 28 00:44:01 megatron NetworkManager[2017]: <info>  [1501199041.5181] manager: NetworkManager state is now CONNECTING
Jul 28 00:44:01 megatron NetworkManager[2017]: <info>  [1501199041.5193] device (enp3s0): state change: prepare -> config (reason 'none', internal state 'managed')
Jul 28 00:44:01 megatron NetworkManager[2017]: <info>  [1501199041.5209] device (enp3s0): state change: config -> ip-config (reason 'none', internal state 'managed')
Jul 28 00:44:01 megatron NetworkManager[2017]: <info> [1501199041.5216] dhcp4 (enp3s0): activation: beginning transaction (timeout in 180 seconds)

Last edited by numb3rz (2017-07-28 13:01:40)

jasonwryan · 2017-07-28 00:34:20

Disable NM (and any other network services that you have enabled) and connect manually. That will narrow down the issue.

numb3rz · 2017-07-28 00:42:12

jasonwryan wrote:

Disable NM (and any other network services that you have enabled) and connect manually. That will narrow down the issue.

Yes, I forgot to mention I've done this also with the following:

systemctl stop NetworkManager
systemctl stop dhcpcd
ip link set enp3s0 up
ip addr add 192.168.1.9/24 broadcast 192.168.1.255 dev enp3s0
ip route add default via 192.168.1.1

No errors occur via the commands, though there is no useful output in journalctl for them either. Yet for some reason there is still no internet connection. Are there any other log files which can help me pinpoint this?

Last edited by numb3rz (2017-07-28 00:44:04)

jasonwryan · 2017-07-28 00:50:13

Please paste the output of `systemctl --list-unit-files --state=enabled`.

numb3rz · 2017-07-28 00:56:22

jasonwryan wrote:

Please paste the output of `systemctl --list-unit-files --state=enabled`.

Here:

UNIT FILE                 STATE  
autovt@.service           enabled
display-manager.service   enabled
gdm.service               enabled
getty@.service            enabled
systemd-timesyncd.service enabled
remote-fs.target          enabled

6 unit files listed.

jasonwryan · 2017-07-28 00:58:05

That looks good. Try a manual wifi connection.

numb3rz · 2017-07-28 01:02:09

jasonwryan wrote:

That looks good. Try a manual wifi connection.

Same thing, I've been switching up the IP to obtain also just to be sure that isn't the issue.

ip link set wlp5s6 up
ip addr add 192.168.1.12/24 broadcast 192.168.1.255 dev wlp5s6
ip route add default via 192.168.1.1

jasonwryan · 2017-07-28 01:15:57

That's not going to establish a wireless connection: https://wiki.archlinux.org/index.php/Wi … nual_setup

numb3rz · 2017-07-28 01:33:03

jasonwryan wrote:

That's not going to establish a wireless connection: https://wiki.archlinux.org/index.php/Wi … nual_setup

Thank you! It seems there is some driver issue, heres the output:

Successfully initialized wpa_supplicant
nl80211: deinit ifname=wlp5s6 disabled_11b_rates=0
wlp5s6: Failed to initialize driver interface

jasonwryan · 2017-07-28 02:34:56

Please paste the details of the card and driver, as well as the commands you used to generate that output.

R00KIE · 2017-07-28 10:14:10

I would start by trying to get a connection via ethernet before moving on to wifi.

Start with the basics, disable all network services that you have enabled (as you have done already), check the link with ethtool and see if the link is detected and if the negotiated speeds are what you would expected, then try to get the network configured with dhcpcd or dhclient, as a last resort try manually configuring the connection.

Make sure you check your hosts file, resolv.conf and nsswitch.conf and make sure the contents are correct. If you have done any modifications to these files undo the modifications.

numb3rz · 2017-07-28 12:34:25

I've resolved not being able to connect via ethernet now, it works (with NetworkManager enabled) if I change IPv4 addresses from automatic to manual.

Address: 192.168.1.<anything>
Netmask: 255.255.255.0
Gateway: 192.168.1.1

I also needed to switch from an automatically assigned nameserver and used the following instead:

8.8.8.8
8.8.4.4

So it seems for whatever reason DHCP is unable to automatically assign my PC an IPv4 address. I am still unsure of the underlying problem for all this though, if anyone could shed some light on this I'd appreciate it.

seth · 2017-07-28 13:32:56

If you're sure there's a dhcp server on the router, you may want to try setting up ethernet manually, but then run "dhcpcd -d" and also try "dhclient" in order to obtain a lease. This might give you more insight on why dhcp isn't working.

Arch Linux

#1 2017-07-28 00:28:10

[SOLVED] Unable to connect to LAN

#2 2017-07-28 00:34:20

Re: [SOLVED] Unable to connect to LAN

#3 2017-07-28 00:42:12

Re: [SOLVED] Unable to connect to LAN

#4 2017-07-28 00:50:13

Re: [SOLVED] Unable to connect to LAN

#5 2017-07-28 00:56:22

Re: [SOLVED] Unable to connect to LAN

#6 2017-07-28 00:58:05

Re: [SOLVED] Unable to connect to LAN

#7 2017-07-28 01:02:09

Re: [SOLVED] Unable to connect to LAN

#8 2017-07-28 01:15:57

Re: [SOLVED] Unable to connect to LAN

#9 2017-07-28 01:33:03

Re: [SOLVED] Unable to connect to LAN

#10 2017-07-28 02:34:56

Re: [SOLVED] Unable to connect to LAN

#11 2017-07-28 10:14:10

Re: [SOLVED] Unable to connect to LAN

#12 2017-07-28 12:34:25

Re: [SOLVED] Unable to connect to LAN

#13 2017-07-28 13:32:56

Re: [SOLVED] Unable to connect to LAN

Board footer