You are not logged in.
I don't know why, but when i power on my pc everything works fine. Then after say 30 mins, the ethernet connection stops working. Pinging 8.8.8.8 gives me me this:
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
From 192.168.1.100 icmp_seq=1 Destination Host Unreachable
I am also connected with wifi, so i type:
sudo ip route del default dev enp2s0
to route everything trough it. This way i have internet connection back, but i want it trough the ethernet cable. So trying to insert back the route:
sudo ip route add 0/0 via 192.168.1.254 metric 100 dev enp2s0
but it gives me the same problem. I can talk to lan devices, but can't reach wan. Everything in the routing tables seem fine:
┌andrei:~ [19:29:10]
└─(✓)─> ip route
default via 192.168.1.254 dev enp2s0 proto static metric 100
default via 192.168.1.254 dev wlp3s0 proto static metric 600
192.168.1.0/24 dev wlp3s0 proto kernel scope link src 192.168.1.91
192.168.1.0/24 dev enp2s0 proto kernel scope link src 192.168.1.100 metric 100
192.168.1.0/24 dev wlp3s0 proto kernel scope link src 192.168.1.91 metric 600
and the ip address didn't change.
I am not connected to the main router directly. There is a powerline (Netgear AV500) attached to it, then one in my room that connects to a second router, to which is attached my pc and a raspberry pi. They are in the same subnet, and everything has a static ip assigned (actually i always request the same ip with DHCP): 192.168.1.254 is the main router (the one attached to wan), .253 is the one in my room, .100 is my pc. Wifi is taken directly from the original router. I am not sure if the problem comes from the powerline or from my pc, however if i reboot the computer everything works again.
Can someone help me understand, please?
PS: 192.168.1.91 is one of the powerline's ip, don't know which one though
Last edited by xnand (2017-03-18 18:54:56)
Offline
How do you manage the connection? Please paste the output of:
systemctl list-unit-files --state enabled
Offline
With NetWorkManager (Gnome 3)
┌andrei:~ [19:54:44]
└─(✓)─> sudo systemctl list-unit-files --state enabled
[sudo] password for andrei:
UNIT FILE STATE
org.cups.cupsd.path enabled
autovt@.service enabled
dbus-fi.w1.wpa_supplicant1.service enabled
dbus-org.freedesktop.NetworkManager.service enabled
dbus-org.freedesktop.nm-dispatcher.service enabled
display-manager.service enabled
gdm.service enabled
getty@.service enabled
NetworkManager-dispatcher.service enabled
NetworkManager.service enabled
org.cups.cupsd.service enabled
sshd.service enabled
systemd-timesyncd.service enabled
wol@.service enabled
wpa_supplicant.service enabled
org.cups.cupsd.socket enabled
tftpd.socket enabled
remote-fs.target enabled
fstrim.timer enabled
pkgfile-update.timer enabled
20 unit files listed.
andrei:~ [20:05:23]
└─(✓)─> sudo systemctl status NetworkManager
● NetworkManager.service - Network Manager
Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled; vendor preset: disabled)
Active: active (running) since Sat 2017-03-18 18:10:49 CET; 1h 55min ago
Docs: man:NetworkManager(8)
Main PID: 335 (NetworkManager)
Tasks: 5 (limit: 4915)
CGroup: /system.slice/NetworkManager.service
├─ 335 /usr/bin/NetworkManager --no-daemon
└─27280 /usr/bin/dhclient -d -q -sf /usr/lib/NetworkManager/nm-dhcp-helper -pf /run/dhclient-wlp3s0.pid -lf /var/lib/NetworkManager/
Mar 18 19:39:26 nebula NetworkManager[335]: <info> [1489862366.5101] dhcp4 (wlp3s0): address 192.168.1.91
Mar 18 19:39:26 nebula NetworkManager[335]: <info> [1489862366.5101] dhcp4 (wlp3s0): plen 24 (255.255.255.0)
Mar 18 19:39:26 nebula NetworkManager[335]: <info> [1489862366.5102] dhcp4 (wlp3s0): gateway 192.168.1.254
Mar 18 19:39:26 nebula NetworkManager[335]: <info> [1489862366.5102] dhcp4 (wlp3s0): server identifier 192.168.1.254
Mar 18 19:39:26 nebula NetworkManager[335]: <info> [1489862366.5102] dhcp4 (wlp3s0): lease time 3600
Mar 18 19:39:26 nebula NetworkManager[335]: <info> [1489862366.5102] dhcp4 (wlp3s0): nameserver '192.168.1.254'
Mar 18 19:39:26 nebula NetworkManager[335]: <info> [1489862366.5102] dhcp4 (wlp3s0): nameserver '62.101.93.101'
Mar 18 19:39:26 nebula NetworkManager[335]: <info> [1489862366.5103] dhcp4 (wlp3s0): nameserver '83.103.25.250'
Mar 18 19:39:26 nebula NetworkManager[335]: <info> [1489862366.5103] dhcp4 (wlp3s0): state changed bound -> bound
Mar 18 19:39:26 nebula dhclient[27280]: bound to 192.168.1.91 -- renewal in 1738 seconds.
Offline
Disable all the other network services and just enable NetworkManager.service.
Offline
Okay, now i only have these
UNIT FILE STATE
autovt@.service enabled
dbus-org.freedesktop.NetworkManager.service enabled
dbus-org.freedesktop.nm-dispatcher.service enabled
display-manager.service enabled
gdm.service enabled
getty@.service enabled
NetworkManager-dispatcher.service enabled
NetworkManager.service enabled
sshd.service enabled
systemd-timesyncd.service enabled
wol@.service enabled
tftpd.socket enabled
remote-fs.target enabled
fstrim.timer enabled
pkgfile-update.timer enabled
15 unit files listed.
Let's see if it was one of the services i disabled. However, i don't see any conflicting service among those
Last edited by xnand (2017-03-18 22:25:09)
Offline
Nope, i still have the same problem.
I noticed that on the raspberry pi the connection is stable, where i don't use NetworkManager. On the raspberry i only have these:
autologin@.service enabled
avahi-daemon.service enabled
bluetooth.service enabled
cron.service enabled
dbus-org.bluez.service enabled
dbus-org.freedesktop.Avahi.service enabled
dhcpcd.service enabled
fake-hwclock.service enabled
hciuart.service enabled
hwclock-save.service enabled
rpi-display-backlight.service enabled
rsyslog.service enabled
ssh.service enabled
sshswitch.service enabled
syslog.service enabled
avahi-daemon.socket enabled
default.target enabled
multi-user.target enabled
remote-fs.target enabled
Offline
If dhcpcd is stable on the Pi for you, consider using it everywhere?
Offline