You are not logged in.

#1 2016-12-11 16:23:07

ferdev
Member
Registered: 2013-06-07
Posts: 6

After a while, my local network machines can't access my Arch Linux

Hi,

I've been suffering this issue for several weeks now. Some time after a successful connection to my Arch Linux desktop (sometimes minutes, sometimes hours) from any of my other machines in my local network, it's impossible to access the arch machine again. The only way to gain access back is to perform a ping from the arch linux to the machine which wants to connect to the arch box. Then the machine can gain access to the machine again (ssh, http, the protocol doesn't matter).

I use the Arch Maxine as a plex server (among other things) and everytime I want to connect to the plex server from any machine, I have to manually login into the arch box, and send the ping to the machine wanting to connect to the plex server.

Dmesg shows this everytime the arch linux stablish a connection to the network router:

`brcmfmac: brcmf_inetaddr_changed: fail to get arp ip table err:-23`

The arch machine connects to the router via wireless, using netctl-auto and dhcpcd. All packages are up to date.

I have another arch linux in the network not suffering this issue at all, so I don't think it's something related to my router. Any ideas what could be happening?

Thanks!

Offline

#2 2016-12-11 16:47:10

ewaller
Administrator
From: Pasadena, CA
Registered: 2009-07-13
Posts: 19,808

Re: After a while, my local network machines can't access my Arch Linux

What are the make and model of the router?  Are you running custom firmware on it?
Are you using a static address on your Arch system? (Asking only for clarification -- dhcpcd seems to imply dynamic address)

What do you mean by "netctl-auto and dhcpcd" ?  Are you running them both as services?  You shouldn't.


Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way

Offline

#3 2016-12-11 19:03:58

ferdev
Member
Registered: 2013-06-07
Posts: 6

Re: After a while, my local network machines can't access my Arch Linux

My router is an ASUS RT-AC87U, running the latest Asus firmware.

The arch machine used to use static ip address, set in the router by MAC address, but it's currently disabled and it's using dynamic ip address as you said. I've checked and re-checked the config in the router so I'd say the router is properly configured.

I'm more concerned about the arch network config, to be honest. Yeah, I'm running both, netctl-auto and dhcpcd as systemd services... I didn't knew that was a bad idea. Should I disable dhcpcd?

I didn't mention it, but neither journctl nor dmesg display anything worth mentioning except for the line I posted in my previous message.

Thanks for the help!

Offline

#4 2016-12-11 19:40:24

jasonwryan
Anarchist
From: .nz
Registered: 2009-05-09
Posts: 30,424
Website

Re: After a while, my local network machines can't access my Arch Linux

ferdev wrote:

Yeah, I'm running both, netctl-auto and dhcpcd as systemd services... I didn't knew that was a bad idea. Should I disable dhcpcd?

Wiki Networking entry wrote:

Warning: Use a single method to manage the network, as several methods may conflict.


Arch + dwm   •   Mercurial repos  •   Surfraw

Registered Linux User #482438

Offline

#5 2016-12-12 09:22:11

ferdev
Member
Registered: 2013-06-07
Posts: 6

Re: After a while, my local network machines can't access my Arch Linux

Alright, I just disabled and stoped dhcpcd, and restarted netctl-auto. The issue is still there, though. Even restarting the network service, my other machines can't access my arch box. I have to ping them manually to fix the issue.

┌─[fer@archifer] - [~] - [2016-12-12 10:11:19]
└─[0] <> ip neigh
192.168.1.88 dev wls6 lladdr <MAC ADDRESS> STALE
192.168.1.1 dev wls6 lladdr  <MAC ADDRESS> REACHABLE

┌─[fer@archifer] - [~] - [2016-12-12 10:11:36]
└─[0] <> ping 192.168.1.213
PING 192.168.1.213 (192.168.1.213) 56(84) bytes of data.
64 bytes from 192.168.1.213: icmp_seq=1 ttl=64 time=58.1 ms
64 bytes from 192.168.1.213: icmp_seq=2 ttl=64 time=361 ms
^C
--- 192.168.1.213 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1001ms
rtt min/avg/max/mdev = 58.131/209.670/361.210/151.540 ms

┌─[fer@archifer] - [~] - [2016-12-12 10:11:48]
└─[0] <> arp -n
Address                  HWtype  HWaddress           Flags Mask            Iface
192.168.1.213           ether   <MAC ADDRESS>   C                     wls6
192.168.1.88             ether   <MAC ADDRESS>   C                     wls6
192.168.1.1               ether   <MAC ADDRESS>   C                     wls6

┌─[fer@archifer] - [~] - [2016-12-12 10:11:49]
└─[0] <> ip neigh
192.168.1.213 dev wls6 lladdr <MAC ADDRESS> REACHABLE
192.168.1.88 dev wls6 lladdr <MAC ADDRESS> STALE
192.168.1.1 dev wls6 lladdr <MAC ADDRESS> REACHABLE

Offline

Board footer

Powered by FluxBB