You are not logged in.

#1 2017-12-22 18:16:40

Simurgh
Member
From: Europe
Registered: 2016-01-16
Posts: 31

NetworkManager StaticIP Problem connectivity timed out

Hi,

so I'm using the University network (wired) in my student hall and in September/October everything worked. Then dhcp stopped working, and I assumed it was an error on the server side (wlan still worked on a different network). But apparently their stuff works and I was supposed to use a static IP. Initially that didn't work either, only after a network admin used his laptop and "my" IP and my LAN plug and then plugged my laptop back in it worked. Even after a reboot, but shorty after that reboot (some hours maybe) it stopped working again.
I couldn't ping the gateway from the wired network (or anything else), but I can reach the gateway over wireless network.

$ systemctl status NetworkManager.service

after I connect the wired connection, results in

Dec 22 18:12:23 beth NetworkManager[359]: <info>  [1513966343.9005] device (enp2s0): state change: disconnected -> prepare (reason 'non
Dec 22 18:12:23 beth NetworkManager[359]: <info>  [1513966343.9012] device (enp2s0): state change: prepare -> config (reason 'none', sy
Dec 22 18:12:23 beth NetworkManager[359]: <info>  [1513966343.9019] device (enp2s0): state change: config -> ip-config (reason 'none', 
Dec 22 18:12:23 beth NetworkManager[359]: <info>  [1513966343.9085] device (enp2s0): state change: ip-config -> ip-check (reason 'none'
Dec 22 18:12:23 beth NetworkManager[359]: <info>  [1513966343.9113] device (enp2s0): state change: ip-check -> secondaries (reason 'non
Dec 22 18:12:23 beth NetworkManager[359]: <info>  [1513966343.9115] device (enp2s0): state change: secondaries -> activated (reason 'no
Dec 22 18:12:24 beth NetworkManager[359]: <info>  [1513966344.3503] dns-mgr: Writing DNS information to /usr/bin/resolvconf
Dec 22 18:12:24 beth NetworkManager[359]: <info>  [1513966344.3644] device (enp2s0): Activation: successful, device activated.
Dec 22 18:12:55 beth NetworkManager[359]: <info>  [1513966375.0005] connectivity: (enp2s0) timed out

(enp2s0 is my "eth0")

Has anyone an idea?

Best regards


Signature is WIP

Offline

#2 2017-12-22 18:55:05

seth
Member
Registered: 2012-09-03
Posts: 49,981

Re: NetworkManager StaticIP Problem connectivity timed out

https://bbs.archlinux.org/viewtopic.php?id=232833

I doubt you're supposed to go for a static IP

Offline

#3 2017-12-22 20:42:45

Simurgh
Member
From: Europe
Registered: 2016-01-16
Posts: 31

Re: NetworkManager StaticIP Problem connectivity timed out

Well, this network admin from the University network who showed up in person did not only tell me to do so, but changed the settings in Network Manager accordingly himself.

So I'd say I'm supposed to use an static IP now?

It did work with DHCP in the beginning, then they had some troubles on this campus and it didn't work anymore.

I am currently using dhclient not the internal one, and it still doesn't work, this is the only thing I could conclude from your link, sorry.

Thanks for your help.


Signature is WIP

Offline

#4 2017-12-22 20:59:32

seth
Member
Registered: 2012-09-03
Posts: 49,981

Re: NetworkManager StaticIP Problem connectivity timed out

Ok...
Try a manual setup (stop networkmanager first!)
https://wiki.archlinux.org/index.php/Ne … IP_address

Offline

#5 2017-12-22 21:56:04

Simurgh
Member
From: Europe
Registered: 2016-01-16
Posts: 31

Re: NetworkManager StaticIP Problem connectivity timed out

Ok so I did

 # systemctl stop NetworkManager.service 

and followed the steps from the wiki.
But I still can't ping anything.
(Although firefox now says "Looking up..." instead of just trying to load forever, not sure if there is any meaning to that)


Signature is WIP

Offline

#6 2017-12-22 22:04:35

seth
Member
Registered: 2012-09-03
Posts: 49,981

Re: NetworkManager StaticIP Problem connectivity timed out

can you ping 8.8.8.8 ?

Offline

#7 2017-12-22 22:07:09

Simurgh
Member
From: Europe
Registered: 2016-01-16
Posts: 31

Re: NetworkManager StaticIP Problem connectivity timed out

No, I'm getting 100% packet loss

Last edited by Simurgh (2017-12-22 22:11:18)


Signature is WIP

Offline

#8 2017-12-22 22:13:34

seth
Member
Registered: 2012-09-03
Posts: 49,981

Re: NetworkManager StaticIP Problem connectivity timed out

can you ping the gateway?

ip route

You should ask the admin whether there's a special requirement (MAC filter or similar)

Offline

#9 2017-12-22 22:22:29

Simurgh
Member
From: Europe
Registered: 2016-01-16
Posts: 31

Re: NetworkManager StaticIP Problem connectivity timed out

100% packet loss to the gateway as well.

There is a MAC filter, and you're supposed to register on their site with your MAC and name, which I did, and it worked for 2 months.
The MAC I have is identically to the MAC I am registered with.


Signature is WIP

Offline

#10 2017-12-24 15:15:18

seth
Member
Registered: 2012-09-03
Posts: 49,981

Re: NetworkManager StaticIP Problem connectivity timed out

Ask the admin to check the server logs.
Since you can reach the gateway via wifi but not ethernet, I'd say you're registered with the MAC of the wifi chip, but not with the one of the ethernet chip.
That's really my best guess because if the router wouldn't silently reject your MAC, you'd not fail without an error message...

Offline

#11 2017-12-24 16:13:00

Simurgh
Member
From: Europe
Registered: 2016-01-16
Posts: 31

Re: NetworkManager StaticIP Problem connectivity timed out

Thanks for your help.
I checked via

$ ip link

and I used the MAC of enp2s0.
I'm going to ask for logs.


Signature is WIP

Offline

#12 2018-01-29 12:40:12

Simurgh
Member
From: Europe
Registered: 2016-01-16
Posts: 31

Re: NetworkManager StaticIP Problem connectivity timed out

Double Post as this is a month later.

They don't have access to the gateway logs.

But I found out, that if I boot into a live linux (kubuntu 16.04.3) dhcp works perfectly fine, and if I reboot into arch after that ethernet via static IP works great for about 6 hours, then it stops and doesn't work until the next boot into the live linux.
If I use dhcp in arch after the live linux boot and shutdown it doesn't work.

So there is something wrong with the networkmanager (?) in this installation I assume, is there a way to get all config files regarding that back to a default state or something?

Also sometimes I get error reports during shutdown like ath10k_pci (WiFi) firmware crashed and an endless "a stop job is running for WPA-supplicant", probably unrelated as they are wifi...


Signature is WIP

Offline

#13 2018-01-29 13:05:17

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 21,425

Re: NetworkManager StaticIP Problem connectivity timed out

Have you made sure that NetworkManager isn't changing your MAC? Look at https://wiki.archlinux.org/index.php/Ne … domization

Offline

#14 2018-01-29 18:38:22

Simurgh
Member
From: Europe
Registered: 2016-01-16
Posts: 31

Re: NetworkManager StaticIP Problem connectivity timed out

I tried to add that to my NetworkManager.conf (the ethernet version set to permant, so that it uses the permanent MAC of the device) the onyl noticeable effect was that I couldn't connect to my WiFi any longer (even if I only had the ethernet line in the .conf).

Is there a chance that just reinstalling the NetworkManager might help? Because it worked in November.


Signature is WIP

Offline

#15 2018-01-29 18:46:43

seth
Member
Registered: 2012-09-03
Posts: 49,981

Re: NetworkManager StaticIP Problem connectivity timed out

There is something about this thread what I do absolutely not get: you're somehow talking as if you were using a static IP config and dhcp at the same time what makes *absolutely* no sense. DHCP is all and only about configuring the clients network by the server - in direct contrast to a static configuration ("Dynamic Host Configuration Protocol")

So you say the admins say you need to use a static IP config (what I find weird for the context, but oh, well) - so where exactly come dhcp into this?? If you use a static config, you should stay away from dhcp as far as you can, because it will nuke your static config.

Offline

#16 2018-01-29 21:59:27

Simurgh
Member
From: Europe
Registered: 2016-01-16
Posts: 31

Re: NetworkManager StaticIP Problem connectivity timed out

Everyone here is supposed to use dhcp to get their dynamic IP, but for some unknown reason that stopped working for me after 2 months. So I reached out to the admins who told me to use Static IP (and they gave me the respective address and gateway).

Static IP works for me for ~6 hours after I booted into a live linux and rebooted into arch linux after that.
Dynamic IP doesn't work even after that.

So because my internet didn't work anymore while using the, for this network default, dynamic IP, they told me to use a static IP instead. But that doesn't work properly and now they have given up. Especially because it works out of the box on the live linux as that makes it look like the error is on my installation and therefore has to be fixed by me.

Sorry for any confusion.


Signature is WIP

Offline

#17 2018-01-30 15:44:21

seth
Member
Registered: 2012-09-03
Posts: 49,981

Re: NetworkManager StaticIP Problem connectivity timed out

Did you compare the MACs in the live linux boot and your arch installation?

Offline

#18 2018-01-31 14:00:03

Simurgh
Member
From: Europe
Registered: 2016-01-16
Posts: 31

Re: NetworkManager StaticIP Problem connectivity timed out

I compared the MACs for my ethernet interface with "ip link" and they are the same for the arch installation and in the live linux.


Signature is WIP

Offline

Board footer

Powered by FluxBB