You are not logged in.

Pages: 1

#1 2018-05-28 20:48:50

nambot
Member
Registered: 2016-11-05
Posts: 12

[SOLVED]Network connection only works after down/up and reset

Network connection only works after down/up and reset

I need help configuring my ethernet connection, please.
I want to connect via ethernet and set a static ipv4 address.
I can configure the connection manually, or via systemd-networkd or NetworkManager
only if I manually bring the device down and up again and then re-configure
a second time.


Gateway: 10.10.10.1
DNS: 10.10.10.1
Hardware: Supermicro A2SDi-4C-HLN4F with 4x Intel X553 1GbE (ixgbe)

I want to assign the ip 10.10.10.10.

Manual configuration test:
$ ls /sys/class/net
eno1
eno2
eno3
eno4
lo
$ ip link show eno1
2: eno1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
    link/ether ac:1f:6b:46:c8:64 brd ff:ff:ff:ff:ff:ff
$ dmesg | grep eno1
[    4.801932] ixgbe 0000:05:00.0 eno1: renamed from eth0
$ ip link set eno1 down
$ ip link set eno1 up
$ ip link show eno1
2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT group default qlen 1000
    link/ether ac:1f:6b:46:c8:64 brd ff:ff:ff:ff:ff:ff
$ dmesg | grep eno1
[    4.801932] ixgbe 0000:05:00.0 eno1: renamed from eth0
[ 1113.693262] ixgbe 0000:05:00.0: registered PHC device on eno1
[ 1113.869768] IPv6: ADDRCONF(NETDEV_UP): eno1: link is not ready
[ 1117.613943] ixgbe 0000:05:00.0 eno1: NIC Link is Up 1 Gbps, Flow Control: RX/TX
[ 1117.613961] IPv6: ADDRCONF(NETDEV_CHANGE): eno1: link becomes ready
$ ip address show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether ac:1f:6b:46:c8:64 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::ae1f:6bff:fe46:c864/64 scope link 
       valid_lft forever preferred_lft forever
3: eno2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether ac:1f:6b:46:c8:65 brd ff:ff:ff:ff:ff:ff
4: eno3: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether ac:1f:6b:46:c8:66 brd ff:ff:ff:ff:ff:ff
5: eno4: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether ac:1f:6b:46:c8:67 brd ff:ff:ff:ff:ff:ff

Add IP address 

$ ip address add 10.10.10.10/24 broadcast + dev eno1
$ ip address show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether ac:1f:6b:46:c8:64 brd ff:ff:ff:ff:ff:ff
    inet 10.10.10.10/24 brd 10.10.10.255 scope global eno1
       valid_lft forever preferred_lft forever
    inet6 fe80::ae1f:6bff:fe46:c864/64 scope link 
       valid_lft forever preferred_lft forever
3: eno2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether ac:1f:6b:46:c8:65 brd ff:ff:ff:ff:ff:ff
4: eno3: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether ac:1f:6b:46:c8:66 brd ff:ff:ff:ff:ff:ff
5: eno4: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether ac:1f:6b:46:c8:67 brd ff:ff:ff:ff:ff:ff

Add route 

$ ip route list
10.10.10.0/24 dev eno1 proto kernel scope link src 10.10.10.10 
$ ip route add default via 10.10.10.1 dev eno1
$ ip route show
default via 10.10.10.1 dev eno1 
10.10.10.0/24 dev eno1 proto kernel scope link src 10.10.10.10

Network doesnt work

$ ping 10.10.10.1 -c4
PING 10.10.10.1 (10.10.10.1) 56(84) bytes of data.
From 10.10.10.10 icmp_seq=1 Destination Host Unreachable
From 10.10.10.10 icmp_seq=2 Destination Host Unreachable
From 10.10.10.10 icmp_seq=3 Destination Host Unreachable
From 10.10.10.10 icmp_seq=4 Destination Host Unreachable

--- 10.10.10.1 ping statistics ---
4 packets transmitted, 0 received, +4 errors, 100% packet loss, time 3037ms

set device down/up again

$ ip address del 10.10.10.10/24 dev eno1
$ ip address flush dev eno1
$ ip link set eno1 down
$ ip link set eno1 up
$ dmesg | grep eno1
[    4.801932] ixgbe 0000:05:00.0 eno1: renamed from eth0
[ 1113.693262] ixgbe 0000:05:00.0: registered PHC device on eno1
[ 1113.869768] IPv6: ADDRCONF(NETDEV_UP): eno1: link is not ready
[ 1117.613943] ixgbe 0000:05:00.0 eno1: NIC Link is Up 1 Gbps, Flow Control: RX/TX
[ 1117.613961] IPv6: ADDRCONF(NETDEV_CHANGE): eno1: link becomes ready
[ 1532.310675] ixgbe 0000:05:00.0: removed PHC on eno1
[ 1536.241616] ixgbe 0000:05:00.0: registered PHC device on eno1
[ 1536.419378] IPv6: ADDRCONF(NETDEV_UP): eno1: link is not ready
[ 1540.098592] ixgbe 0000:05:00.0 eno1: NIC Link is Up 1 Gbps, Flow Control: RX/TX
[ 1540.098620] IPv6: ADDRCONF(NETDEV_CHANGE): eno1: link becomes ready

add ip address and route again

$ ip address add 10.10.10.10/24 broadcast + dev eno1
$ ip route show
10.10.10.0/24 dev eno1 proto kernel scope link src 10.10.10.10 
$ ip route add default via 10.10.10.1 dev eno1
$ ip route show
default via 10.10.10.1 dev eno1 
10.10.10.0/24 dev eno1 proto kernel scope link src 10.10.10.10

suddenly, network works

$ ping 10.10.10.1 -c4
PING 10.10.10.1 (10.10.10.1) 56(84) bytes of data.
64 bytes from 10.10.10.1: icmp_seq=1 ttl=64 time=0.480 ms
64 bytes from 10.10.10.1: icmp_seq=2 ttl=64 time=0.401 ms
64 bytes from 10.10.10.1: icmp_seq=3 ttl=64 time=0.550 ms
64 bytes from 10.10.10.1: icmp_seq=4 ttl=64 time=0.461 ms

--- 10.10.10.1 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3047ms
rtt min/avg/max/mdev = 0.401/0.473/0.550/0.053 ms



systemd-networkd

I want to configure the network via systemd-networkd.

systemd-networkd config file

$ cat /etc/systemd/network/wired-static.network
[Match]
Name=eno1

[Network]
Address=10.10.10.10/24
Gateway=10.10.10.1
DNS=10.10.10.1

enable and reboot

$ systemctl enable systemd-networkd.service
$ systemctl enable systemd-resolved.service
$ reboot

debug output

$ dmesg | grep eno1
[    4.866963] ixgbe 0000:05:00.0 eno1: renamed from eth0
[    4.921209] ixgbe 0000:05:00.0: registered PHC device on eno1
[    5.090346] IPv6: ADDRCONF(NETDEV_UP): eno1: link is not ready
[    8.099271] ixgbe 0000:05:00.0 eno1: NIC Link is Up 1 Gbps, Flow Control: RX/TX
[    8.099315] IPv6: ADDRCONF(NETDEV_CHANGE): eno1: link becomes ready
$ journalctl -b | grep eno1
Mai 28 22:13:09 orion kernel: ixgbe 0000:05:00.0 eno1: renamed from eth0
Mai 28 22:13:09 orion systemd-networkd[261]: eth0: Interface name change detected, eth0 has been renamed to eno1.
Mai 28 22:13:09 orion systemd-networkd[261]: eno1: udev initialized link
Mai 28 22:13:09 orion systemd-networkd[261]: eno1: Link state is up-to-date
Mai 28 22:13:09 orion systemd-networkd[261]: eno1: found matching network '/etc/systemd/network/wired-static.network'
Mai 28 22:13:09 orion systemd-networkd[261]: eno1: Bringing link up
Mai 28 22:13:09 orion systemd-networkd[261]: eno1: IPv6 successfully enabled
Mai 28 22:13:09 orion kernel: ixgbe 0000:05:00.0: registered PHC device on eno1
Mai 28 22:13:10 orion systemd-networkd[261]: eno1: Flags change: +UP
Mai 28 22:13:10 orion kernel: IPv6: ADDRCONF(NETDEV_UP): eno1: link is not ready
Mai 28 22:13:10 orion systemd-networkd[261]: eno1: Started LLDP.
Mai 28 22:13:13 orion systemd-networkd[261]: eno1: Flags change: +LOWER_UP +RUNNING
Mai 28 22:13:13 orion kernel: ixgbe 0000:05:00.0 eno1: NIC Link is Up 1 Gbps, Flow Control: RX/TX
Mai 28 22:13:13 orion kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eno1: link becomes ready
Mai 28 22:13:13 orion systemd-networkd[261]: eno1: Gained carrier
Mai 28 22:13:13 orion systemd-networkd[261]: eno1: Setting addresses
Mai 28 22:13:13 orion systemd-networkd[261]: eno1: Updating address: 10.10.10.10/24 (valid forever)
Mai 28 22:13:13 orion systemd-networkd[261]: eno1: Addresses set
Mai 28 22:13:13 orion systemd-networkd[261]: eno1: Setting routes
Mai 28 22:13:13 orion systemd-networkd[261]: eno1: Routes set
Mai 28 22:13:14 orion systemd-networkd[261]: eno1: Adding address: fe80::ae1f:6bff:fe46:c864/64 (valid forever)
Mai 28 22:13:14 orion systemd-networkd[261]: eno1: Gained IPv6LL
Mai 28 22:13:14 orion systemd-networkd[261]: eno1: Discovering IPv6 routers
Mai 28 22:13:26 orion systemd-networkd[261]: eno1: Configured
$ ip address show dev eno1
2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether ac:1f:6b:46:c8:64 brd ff:ff:ff:ff:ff:ff
    inet 10.10.10.10/24 brd 10.10.10.255 scope global eno1
       valid_lft forever preferred_lft forever
    inet6 fe80::ae1f:6bff:fe46:c864/64 scope link 
       valid_lft forever preferred_lft forever

network doesnt work

$ ping -c4 10.10.10.1
PING 10.10.10.1 (10.10.10.1) 56(84) bytes of data.
From 10.10.10.10 icmp_seq=1 Destination Host Unreachable
From 10.10.10.10 icmp_seq=2 Destination Host Unreachable
From 10.10.10.10 icmp_seq=3 Destination Host Unreachable
From 10.10.10.10 icmp_seq=4 Destination Host Unreachable

--- 10.10.10.1 ping statistics ---
4 packets transmitted, 0 received, +4 errors, 100% packet loss, time 3051ms

set device down/up again

$ ip address flush dev eno1
$ ip link set eno1 down
$ ip link set eno1 up
$ dmesg | grep eno1
[    4.866963] ixgbe 0000:05:00.0 eno1: renamed from eth0
[    4.921209] ixgbe 0000:05:00.0: registered PHC device on eno1
[    5.090346] IPv6: ADDRCONF(NETDEV_UP): eno1: link is not ready
[    8.099271] ixgbe 0000:05:00.0 eno1: NIC Link is Up 1 Gbps, Flow Control: RX/TX
[    8.099315] IPv6: ADDRCONF(NETDEV_CHANGE): eno1: link becomes ready
[  339.119562] ixgbe 0000:05:00.0: removed PHC on eno1
[  351.690600] ixgbe 0000:05:00.0: registered PHC device on eno1
[  351.866551] IPv6: ADDRCONF(NETDEV_UP): eno1: link is not ready
[  355.612265] ixgbe 0000:05:00.0 eno1: NIC Link is Up 1 Gbps, Flow Control: RX/TX
[  355.612290] IPv6: ADDRCONF(NETDEV_CHANGE): eno1: link becomes ready

suddenly, network works

$ ping -c4 10.10.10.1
PING 10.10.10.1 (10.10.10.1) 56(84) bytes of data.
64 bytes from 10.10.10.1: icmp_seq=1 ttl=64 time=0.503 ms
64 bytes from 10.10.10.1: icmp_seq=2 ttl=64 time=0.429 ms
64 bytes from 10.10.10.1: icmp_seq=3 ttl=64 time=0.442 ms
64 bytes from 10.10.10.1: icmp_seq=4 ttl=64 time=0.458 ms

--- 10.10.10.1 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3044ms
rtt min/avg/max/mdev = 0.429/0.458/0.503/0.027 ms

I also tried NetworkManager with similar results. Doesn't work until i bring the device down and up again and restart NetworkManager.
I'm out of ideas now and need you help, please.

Last edited by nambot (2018-06-09 23:58:02)

Offline

#2 2018-05-28 20:50:06

Slithery
Administrator
From: Norfolk, UK
Registered: 2013-12-01
Posts: 5,776

Re: [SOLVED]Network connection only works after down/up and reset

What's the output of...

systemctl --list-unit-files --state=enabled

No, it didn't "fix" anything. It just shifted the brokeness one space to the right. - jasonwryan
Closing -- for deletion; Banning -- for muppetry. - jasonwryan

aur - dotfiles

Offline

#3 2018-05-28 21:02:47

nambot
Member
Registered: 2016-11-05
Posts: 12

Re: [SOLVED]Network connection only works after down/up and reset

Hi Slithery,

thank you for your help.

$ systemctl list-unit-files --state=enabled
UNIT FILE                             STATE  
autovt@.service                       enabled
dbus-org.freedesktop.network1.service enabled
dbus-org.freedesktop.resolve1.service enabled
getty@.service                        enabled
systemd-networkd-wait-online.service  enabled
systemd-networkd.service              enabled
systemd-resolved.service              enabled
systemd-networkd.socket               enabled
remote-fs.target                      enabled

9 unit files listed.

Further information

$ cat /etc/resolv.conf
# Generated by resolvconf
nameserver 10.10.10.1
$ systemctl status -l systemd-networkd.service
● systemd-networkd.service - Network Service
   Loaded: loaded (/usr/lib/systemd/system/systemd-networkd.service; enabled; vendor preset: enabled)
  Drop-In: /etc/systemd/system/systemd-networkd.service.d
           └─override.conf
   Active: active (running) since Mon 2018-05-28 22:58:22 CEST; 3min 46s ago
     Docs: man:systemd-networkd.service(8)
 Main PID: 277 (systemd-network)
   Status: "Processing requests..."
    Tasks: 1 (limit: 4915)
   Memory: 2.0M
   CGroup: /system.slice/systemd-networkd.service
           └─277 /usr/lib/systemd/systemd-networkd

Mai 28 23:01:11 orion systemd-networkd[277]: Sent message type=signal sender=n/a destination=n/a path=/org/freedesktop/network1/link/_32 interface>
Mai 28 23:01:11 orion systemd-networkd[277]: eno1: Discovering IPv6 routers
Mai 28 23:01:11 orion systemd-networkd[277]: NDISC: Started IPv6 Router Solicitation client
Mai 28 23:01:11 orion systemd-networkd[277]: NDISC: Sent Router Solicitation, next solicitation in 3s
Mai 28 23:01:15 orion systemd-networkd[277]: NDISC: Sent Router Solicitation, next solicitation in 7s
Mai 28 23:01:23 orion systemd-networkd[277]: NDISC: Sent Router Solicitation, next solicitation in 14s
Mai 28 23:01:23 orion systemd-networkd[277]: NDISC: No RA received before link confirmation timeout
Mai 28 23:01:23 orion systemd-networkd[277]: NDISC: Invoking callback for 't'.
Mai 28 23:01:37 orion systemd-networkd[277]: NDISC: Sent Router Solicitation, next solicitation in 27s
Mai 28 23:02:05 orion systemd-networkd[277]: NDISC: Sent Router Solicitation, next solicitation in 56s
$ networkctl 
IDX LINK             TYPE               OPERATIONAL SETUP     
  1 lo               loopback           carrier     unmanaged 
  2 eno1             ether              routable    configured
  3 eno2             ether              off         unmanaged 
  4 eno3             ether              off         unmanaged 
  5 eno4             ether              off         unmanaged 

5 links listed.

I also changed  systemd-networkd log level to debug

$ systemctl edit systemd-networkd
[Service]
Environment=SYSTEMD_LOG_LEVEL=debug

Journal after starting the system with network broken:

$journalctl -b | grep systemd-networkd
Mai 28 23:58:30 orion systemd-networkd[266]: Bus n/a: changing state UNSET → OPENING
Mai 28 23:58:30 orion systemd-networkd[266]: Added inotify watch for /run on bus n/a: 2
Mai 28 23:58:30 orion systemd-networkd[266]: Added inotify watch for /run/dbus on bus n/a: -1
Mai 28 23:58:30 orion systemd-networkd[266]: Bus n/a: changing state OPENING → WATCH_BIND
Mai 28 23:58:30 orion systemd-networkd[266]: Failed to open configuration file '/etc/systemd/networkd.conf': No such file or directory
Mai 28 23:58:30 orion systemd-networkd[266]: timestamp of '/etc/systemd/network' changed
Mai 28 23:58:30 orion systemd-networkd[266]: Ignoring /etc/systemd/network/wired-static.network, because it's not a regular file with suffix .netdev.
Mai 28 23:58:30 orion systemd-networkd[266]: Ignoring /usr/lib/systemd/network/99-default.link, because it's not a regular file with suffix .netdev.
Mai 28 23:58:30 orion systemd-networkd[266]: Ignoring /usr/lib/systemd/network/80-container-host0.network, because it's not a regular file with suffix .netdev.
Mai 28 23:58:30 orion systemd-networkd[266]: Ignoring /usr/lib/systemd/network/80-container-vz.network, because it's not a regular file with suffix .netdev.
Mai 28 23:58:30 orion systemd-networkd[266]: Ignoring /usr/lib/systemd/network/80-container-ve.network, because it's not a regular file with suffix .netdev.
Mai 28 23:58:30 orion systemd-networkd[266]: Ignoring /usr/lib/systemd/network/99-default.link, because it's not a regular file with suffix .network.
Mai 28 23:58:30 orion systemd-networkd[266]: lo: Flags change: +LOOPBACK +UP +LOWER_UP +RUNNING
Mai 28 23:58:30 orion systemd-networkd[266]: lo: Link 1 added
Mai 28 23:58:30 orion systemd-networkd[266]: lo: link pending udev initialization...
Mai 28 23:58:30 orion systemd-networkd[266]: lo: Saved original MTU: 0
Mai 28 23:58:30 orion systemd-networkd[266]: lo: Adding address: ::1/128 (valid forever)
Mai 28 23:58:30 orion systemd-networkd[266]: lo: Adding address: 127.0.0.1/8 (valid forever)
Mai 28 23:58:30 orion systemd-networkd[266]: rtnl: received address with invalid family 129, ignoring
Mai 28 23:58:30 orion systemd-networkd[266]: rtnl: received address with invalid family 128, ignoring
Mai 28 23:58:30 orion systemd-networkd[266]: Enumeration completed
Mai 28 23:58:30 orion systemd-networkd[266]: lo: udev initialized link
Mai 28 23:58:30 orion systemd-networkd[266]: lo: Link state is up-to-date
Mai 28 23:58:30 orion systemd-networkd[266]: No virtualization found in DMI
Mai 28 23:58:30 orion systemd-networkd[266]: No virtualization found in CPUID
Mai 28 23:58:30 orion systemd-networkd[266]: Virtualization XEN not found, /proc/xen does not exist
Mai 28 23:58:30 orion systemd-networkd[266]: This platform does not support /proc/device-tree
Mai 28 23:58:30 orion systemd-networkd[266]: UML virtualization not found in /proc/cpuinfo.
Mai 28 23:58:30 orion systemd-networkd[266]: This platform does not support /proc/sysinfo
Mai 28 23:58:30 orion systemd-networkd[266]: Found VM virtualization none
Mai 28 23:58:30 orion systemd-networkd[266]: lo: Unmanaged
Mai 28 23:58:30 orion systemd-networkd[266]: Got inotify event on bus n/a.
Mai 28 23:58:30 orion systemd-networkd[266]: Added inotify watch for /run on bus n/a: 2
Mai 28 23:58:30 orion systemd-networkd[266]: Added inotify watch for /run/dbus on bus n/a: -1
Mai 28 23:58:30 orion systemd-networkd[266]: Got inotify event on bus n/a.
Mai 28 23:58:30 orion systemd-networkd[266]: Added inotify watch for /run on bus n/a: 2
Mai 28 23:58:30 orion systemd-networkd[266]: Added inotify watch for /run/dbus on bus n/a: -1
Mai 28 23:58:30 orion systemd-networkd[266]: Got inotify event on bus n/a.
Mai 28 23:58:30 orion systemd-networkd[266]: Added inotify watch for /run on bus n/a: 2
Mai 28 23:58:30 orion systemd-networkd[266]: Added inotify watch for /run/dbus on bus n/a: -1
Mai 28 23:58:30 orion systemd-networkd[266]: Got inotify event on bus n/a.
Mai 28 23:58:30 orion systemd-networkd[266]: Added inotify watch for /run on bus n/a: 2
Mai 28 23:58:30 orion systemd-networkd[266]: Added inotify watch for /run/dbus on bus n/a: -1
Mai 28 23:58:30 orion systemd-networkd[266]: Got inotify event on bus n/a.
Mai 28 23:58:30 orion systemd-networkd[266]: Added inotify watch for /run on bus n/a: 2
Mai 28 23:58:30 orion systemd-networkd[266]: Added inotify watch for /run/dbus on bus n/a: -1
Mai 28 23:58:30 orion systemd-networkd[266]: Got inotify event on bus n/a.
Mai 28 23:58:30 orion systemd-networkd[266]: Added inotify watch for /run on bus n/a: 2
Mai 28 23:58:30 orion systemd-networkd[266]: Added inotify watch for /run/dbus on bus n/a: -1
Mai 28 23:58:30 orion systemd-networkd[266]: Got inotify event on bus n/a.
Mai 28 23:58:30 orion systemd-networkd[266]: Bus n/a: changing state WATCH_BIND → AUTHENTICATING
Mai 28 23:58:30 orion systemd-networkd[266]: Bus n/a: changing state AUTHENTICATING → HELLO
Mai 28 23:58:30 orion systemd-networkd[266]: Sent message type=method_call sender=n/a destination=org.freedesktop.DBus path=/org/freedesktop/DBus interface=org.freedesktop.DBus member=Hello cookie=1 reply_cookie=0 signature=n/a error-name=n/a error-message=n/a
Mai 28 23:58:30 orion systemd-networkd[266]: Sent message type=method_call sender=n/a destination=org.freedesktop.DBus path=/org/freedesktop/DBus interface=org.freedesktop.DBus member=RequestName cookie=2 reply_cookie=0 signature=su error-name=n/a error-message=n/a
Mai 28 23:58:30 orion systemd-networkd[266]: Sent message type=method_call sender=n/a destination=org.freedesktop.DBus path=/org/freedesktop/DBus interface=org.freedesktop.DBus member=AddMatch cookie=3 reply_cookie=0 signature=s error-name=n/a error-message=n/a
Mai 28 23:58:30 orion systemd-networkd[266]: Sent message type=signal sender=n/a destination=n/a path=/org/freedesktop/network1/link/_31 interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=4 reply_cookie=0 signature=sa{sv}as error-name=n/a error-message=n/a
Mai 28 23:58:30 orion systemd-networkd[266]: Sent message type=signal sender=n/a destination=n/a path=/org/freedesktop/network1/link/_31 interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=5 reply_cookie=0 signature=sa{sv}as error-name=n/a error-message=n/a
Mai 28 23:58:30 orion systemd-networkd[266]: Got message type=method_return sender=org.freedesktop.DBus destination=:1.2 path=n/a interface=n/a member=n/a cookie=1 reply_cookie=1 signature=s error-name=n/a error-message=n/a
Mai 28 23:58:30 orion systemd-networkd[266]: Bus n/a: changing state HELLO → RUNNING
Mai 28 23:58:30 orion systemd-networkd[266]: Got message type=signal sender=org.freedesktop.DBus.Local destination=n/a path=/org/freedesktop/DBus/Local interface=org.freedesktop.DBus.Local member=Connected cookie=4294967295 reply_cookie=0 signature=n/a error-name=n/a error-message=n/a
Mai 28 23:58:30 orion systemd-networkd[266]: Got message type=signal sender=org.freedesktop.DBus destination=:1.2 path=/org/freedesktop/DBus interface=org.freedesktop.DBus member=NameAcquired cookie=2 reply_cookie=0 signature=s error-name=n/a error-message=n/a
Mai 28 23:58:30 orion systemd-networkd[266]: Got message type=signal sender=org.freedesktop.DBus destination=:1.2 path=/org/freedesktop/DBus interface=org.freedesktop.DBus member=NameAcquired cookie=3 reply_cookie=0 signature=s error-name=n/a error-message=n/a
Mai 28 23:58:30 orion systemd-networkd[266]: Got message type=method_return sender=org.freedesktop.DBus destination=:1.2 path=n/a interface=n/a member=n/a cookie=4 reply_cookie=2 signature=u error-name=n/a error-message=n/a
Mai 28 23:58:30 orion systemd-networkd[266]: Successfully acquired requested service name.
Mai 28 23:58:30 orion systemd-networkd[266]: Got message type=method_return sender=org.freedesktop.DBus destination=:1.2 path=n/a interface=n/a member=n/a cookie=5 reply_cookie=3 signature=n/a error-name=n/a error-message=n/a
Mai 28 23:58:30 orion systemd-networkd[266]: Match type='signal',sender='org.freedesktop.login1',path='/org/freedesktop/login1',interface='org.freedesktop.login1.Manager',member='PrepareForSleep' successfully installed.
Mai 28 23:58:31 orion systemd-networkd[266]: eth0: Flags change: +MULTICAST +BROADCAST
Mai 28 23:58:31 orion systemd-networkd[266]: eth0: Link 2 added
Mai 28 23:58:31 orion systemd-networkd[266]: eth0: link pending udev initialization...
Mai 28 23:58:31 orion systemd-networkd[266]: eth0: Saved original MTU: 1500
Mai 28 23:58:31 orion systemd-networkd[266]: eth1: Flags change: +MULTICAST +BROADCAST
Mai 28 23:58:31 orion systemd-networkd[266]: eth1: Link 3 added
Mai 28 23:58:31 orion systemd-networkd[266]: eth1: link pending udev initialization...
Mai 28 23:58:31 orion systemd-networkd[266]: eth1: Saved original MTU: 1500
Mai 28 23:58:32 orion systemd-networkd[266]: eth2: Flags change: +MULTICAST +BROADCAST
Mai 28 23:58:32 orion systemd-networkd[266]: eth2: Link 4 added
Mai 28 23:58:32 orion systemd-networkd[266]: eth2: link pending udev initialization...
Mai 28 23:58:32 orion systemd-networkd[266]: eth2: Saved original MTU: 1500
Mai 28 23:58:32 orion systemd-networkd[266]: eth3: Flags change: +MULTICAST +BROADCAST
Mai 28 23:58:32 orion systemd-networkd[266]: eth3: Link 5 added
Mai 28 23:58:32 orion systemd-networkd[266]: eth3: link pending udev initialization...
Mai 28 23:58:32 orion systemd-networkd[266]: eth3: Saved original MTU: 1500
Mai 28 23:58:32 orion systemd-networkd[266]: eth3: Interface name change detected, eth3 has been renamed to eno4.
Mai 28 23:58:32 orion systemd-networkd[266]: eno4: udev initialized link
Mai 28 23:58:32 orion systemd-networkd[266]: eth2: Interface name change detected, eth2 has been renamed to eno3.
Mai 28 23:58:32 orion systemd-networkd[266]: eno3: udev initialized link
Mai 28 23:58:32 orion systemd-networkd[266]: eth0: Interface name change detected, eth0 has been renamed to eno1.
Mai 28 23:58:32 orion systemd-networkd[266]: eno4: Link state is up-to-date
Mai 28 23:58:32 orion systemd-networkd[266]: eno4: Unmanaged
Mai 28 23:58:32 orion systemd-networkd[266]: Sent message type=signal sender=n/a destination=n/a path=/org/freedesktop/network1/link/_35 interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=6 reply_cookie=0 signature=sa{sv}as error-name=n/a error-message=n/a
Mai 28 23:58:32 orion systemd-networkd[266]: eno3: Link state is up-to-date
Mai 28 23:58:32 orion systemd-networkd[266]: eno3: Unmanaged
Mai 28 23:58:32 orion systemd-networkd[266]: Sent message type=signal sender=n/a destination=n/a path=/org/freedesktop/network1/link/_34 interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=7 reply_cookie=0 signature=sa{sv}as error-name=n/a error-message=n/a
Mai 28 23:58:32 orion systemd-networkd[266]: eno1: udev initialized link
Mai 28 23:58:32 orion systemd-networkd[266]: eth1: Interface name change detected, eth1 has been renamed to eno2.
Mai 28 23:58:32 orion systemd-networkd[266]: eno1: Link state is up-to-date
Mai 28 23:58:32 orion systemd-networkd[266]: eno1: found matching network '/etc/systemd/network/wired-static.network'
Mai 28 23:58:32 orion systemd-networkd[266]: eno4: Link is not managed by us
Mai 28 23:58:32 orion systemd-networkd[266]: eno2: Link is not managed by us
Mai 28 23:58:32 orion systemd-networkd[266]: lo: Link is not managed by us
Mai 28 23:58:32 orion systemd-networkd[266]: eno3: Link is not managed by us
Mai 28 23:58:32 orion systemd-networkd[266]: Sent message type=signal sender=n/a destination=n/a path=/org/freedesktop/network1/link/_32 interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=8 reply_cookie=0 signature=sa{sv}as error-name=n/a error-message=n/a
Mai 28 23:58:32 orion systemd-networkd[266]: eno1: Bringing link up
Mai 28 23:58:32 orion systemd-networkd[266]: eno1: IPv6 successfully enabled
Mai 28 23:58:33 orion systemd-networkd[266]: eno2: udev initialized link
Mai 28 23:58:33 orion systemd-networkd[266]: eno1: Flags change: +UP
Mai 28 23:58:33 orion systemd-networkd[266]: Sent message type=signal sender=n/a destination=n/a path=/org/freedesktop/network1/link/_32 interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=9 reply_cookie=0 signature=sa{sv}as error-name=n/a error-message=n/a
Mai 28 23:58:33 orion systemd-networkd[266]: LLDP: Started LLDP client
Mai 28 23:58:33 orion systemd-networkd[266]: eno1: Started LLDP.
Mai 28 23:58:33 orion systemd-networkd[266]: Sent message type=signal sender=n/a destination=n/a path=/org/freedesktop/network1 interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=10 reply_cookie=0 signature=sa{sv}as error-name=n/a error-message=n/a
Mai 28 23:58:33 orion systemd-networkd[266]: eno2: Link state is up-to-date
Mai 28 23:58:33 orion systemd-networkd[266]: eno2: Unmanaged
Mai 28 23:58:33 orion systemd-networkd[266]: Sent message type=signal sender=n/a destination=n/a path=/org/freedesktop/network1/link/_33 interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=11 reply_cookie=0 signature=sa{sv}as error-name=n/a error-message=n/a
Mai 28 23:58:36 orion systemd-networkd[266]: eno1: Flags change: +LOWER_UP +RUNNING
Mai 28 23:58:36 orion systemd-networkd[266]: Sent message type=signal sender=n/a destination=n/a path=/org/freedesktop/network1/link/_32 interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=12 reply_cookie=0 signature=sa{sv}as error-name=n/a error-message=n/a
Mai 28 23:58:36 orion systemd-networkd[266]: eno1: Gained carrier
Mai 28 23:58:36 orion systemd-networkd[266]: Sent message type=signal sender=n/a destination=n/a path=/org/freedesktop/network1/link/_32 interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=13 reply_cookie=0 signature=sa{sv}as error-name=n/a error-message=n/a
Mai 28 23:58:36 orion systemd-networkd[266]: eno1: Setting addresses
Mai 28 23:58:36 orion systemd-networkd[266]: Sent message type=signal sender=n/a destination=n/a path=/org/freedesktop/network1 interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=14 reply_cookie=0 signature=sa{sv}as error-name=n/a error-message=n/a
Mai 28 23:58:36 orion systemd-networkd[266]: eno1: Updating address: 10.10.10.10/24 (valid forever)
Mai 28 23:58:36 orion systemd-networkd[266]: Sent message type=signal sender=n/a destination=n/a path=/org/freedesktop/network1/link/_32 interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=15 reply_cookie=0 signature=sa{sv}as error-name=n/a error-message=n/a
Mai 28 23:58:36 orion systemd-networkd[266]: Sent message type=signal sender=n/a destination=n/a path=/org/freedesktop/network1 interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=16 reply_cookie=0 signature=sa{sv}as error-name=n/a error-message=n/a
Mai 28 23:58:36 orion systemd-networkd[266]: eno1: Addresses set
Mai 28 23:58:36 orion systemd-networkd[266]: Sent message type=signal sender=n/a destination=n/a path=/org/freedesktop/network1/link/_32 interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=17 reply_cookie=0 signature=sa{sv}as error-name=n/a error-message=n/a
Mai 28 23:58:36 orion systemd-networkd[266]: eno1: Setting routes
Mai 28 23:58:36 orion systemd-networkd[266]: eno1: Routes set
Mai 28 23:58:37 orion systemd-networkd[266]: eno1: Adding address: fe80::ae1f:6bff:fe46:c864/64 (valid forever)
Mai 28 23:58:37 orion systemd-networkd[266]: eno1: Gained IPv6LL
Mai 28 23:58:37 orion systemd-networkd[266]: eno1: Discovering IPv6 routers
Mai 28 23:58:37 orion systemd-networkd[266]: NDISC: Started IPv6 Router Solicitation client
Mai 28 23:58:37 orion systemd-networkd[266]: NDISC: Sent Router Solicitation, next solicitation in 3s
Mai 28 23:58:41 orion systemd-networkd[266]: NDISC: Sent Router Solicitation, next solicitation in 6s
Mai 28 23:58:48 orion systemd-networkd[266]: NDISC: Sent Router Solicitation, next solicitation in 13s
Mai 28 23:58:49 orion systemd-networkd[266]: NDISC: No RA received before link confirmation timeout
Mai 28 23:58:49 orion systemd-networkd[266]: NDISC: Invoking callback for 't'.
Mai 28 23:58:49 orion systemd-networkd[266]: eno1: Configured
Mai 28 23:58:49 orion systemd-networkd[266]: Sent message type=signal sender=n/a destination=n/a path=/org/freedesktop/network1/link/_32 interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=18 reply_cookie=0 signature=sa{sv}as error-name=n/a error-message=n/a
Mai 28 23:59:02 orion systemd-networkd[266]: NDISC: Sent Router Solicitation, next solicitation in 28s
Mai 28 23:59:30 orion systemd-networkd[266]: NDISC: Sent Router Solicitation, next solicitation in 58s

new lines after I flush the ip addr and bring the interface down and up again:

Mai 29 00:00:29 orion systemd-networkd[266]: NDISC: Sent Router Solicitation, next solicitation in 2min 1s
Mai 29 00:00:53 orion systemd-networkd[266]: eno1: Removing address: 10.10.10.10/24 (valid forever)
Mai 29 00:00:53 orion systemd-networkd[266]: Sent message type=signal sender=n/a destination=n/a path=/org/freedesktop/network1/link/_32 interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=19 reply_cookie=0 signature=sa{sv}as error-name=n/a error-message=n/a
Mai 29 00:00:53 orion systemd-networkd[266]: Sent message type=signal sender=n/a destination=n/a path=/org/freedesktop/network1 interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=20 reply_cookie=0 signature=sa{sv}as error-name=n/a error-message=n/a
Mai 29 00:00:53 orion systemd-networkd[266]: eno1: Removing address: fe80::ae1f:6bff:fe46:c864/64 (valid forever)
Mai 29 00:00:53 orion systemd-networkd[266]: Sent message type=signal sender=n/a destination=n/a path=/org/freedesktop/network1/link/_32 interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=21 reply_cookie=0 signature=sa{sv}as error-name=n/a error-message=n/a
Mai 29 00:00:53 orion systemd-networkd[266]: Sent message type=signal sender=n/a destination=n/a path=/org/freedesktop/network1 interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=22 reply_cookie=0 signature=sa{sv}as error-name=n/a error-message=n/a
Mai 29 00:00:58 orion systemd-networkd[266]: eno1: Flags change: -UP -LOWER_UP -RUNNING
Mai 29 00:00:58 orion systemd-networkd[266]: Sent message type=signal sender=n/a destination=n/a path=/org/freedesktop/network1/link/_32 interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=23 reply_cookie=0 signature=sa{sv}as error-name=n/a error-message=n/a
Mai 29 00:00:58 orion systemd-networkd[266]: LLDP: Stopping LLDP client
Mai 29 00:00:58 orion systemd-networkd[266]: eno1: Stopped LLDP.
Mai 29 00:00:58 orion systemd-networkd[266]: eno1: Lost carrier
Mai 29 00:00:58 orion systemd-networkd[266]: NDISC: Stopping IPv6 Router Solicitation client
Mai 29 00:00:58 orion systemd-networkd[266]: eno1: State is configured, dropping config
Mai 29 00:00:58 orion systemd-networkd[266]: Sent message type=signal sender=n/a destination=n/a path=/org/freedesktop/network1 interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=24 reply_cookie=0 signature=sa{sv}as error-name=n/a error-message=n/a
Mai 29 00:01:02 orion systemd-networkd[266]: eno1: Flags change: +UP
Mai 29 00:01:02 orion systemd-networkd[266]: Sent message type=signal sender=n/a destination=n/a path=/org/freedesktop/network1/link/_32 interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=25 reply_cookie=0 signature=sa{sv}as error-name=n/a error-message=n/a
Mai 29 00:01:02 orion systemd-networkd[266]: LLDP: Started LLDP client
Mai 29 00:01:02 orion systemd-networkd[266]: eno1: Started LLDP.
Mai 29 00:01:02 orion systemd-networkd[266]: Sent message type=signal sender=n/a destination=n/a path=/org/freedesktop/network1 interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=26 reply_cookie=0 signature=sa{sv}as error-name=n/a error-message=n/a
Mai 29 00:01:06 orion systemd-networkd[266]: eno1: Flags change: +LOWER_UP +RUNNING
Mai 29 00:01:06 orion systemd-networkd[266]: Sent message type=signal sender=n/a destination=n/a path=/org/freedesktop/network1/link/_32 interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=27 reply_cookie=0 signature=sa{sv}as error-name=n/a error-message=n/a
Mai 29 00:01:06 orion systemd-networkd[266]: eno1: Gained carrier
Mai 29 00:01:06 orion systemd-networkd[266]: Sent message type=signal sender=n/a destination=n/a path=/org/freedesktop/network1/link/_32 interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=28 reply_cookie=0 signature=sa{sv}as error-name=n/a error-message=n/a
Mai 29 00:01:06 orion systemd-networkd[266]: eno1: Setting addresses
Mai 29 00:01:06 orion systemd-networkd[266]: Sent message type=signal sender=n/a destination=n/a path=/org/freedesktop/network1 interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=29 reply_cookie=0 signature=sa{sv}as error-name=n/a error-message=n/a
Mai 29 00:01:06 orion systemd-networkd[266]: eno1: Updating address: 10.10.10.10/24 (valid forever)
Mai 29 00:01:06 orion systemd-networkd[266]: Sent message type=signal sender=n/a destination=n/a path=/org/freedesktop/network1/link/_32 interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=30 reply_cookie=0 signature=sa{sv}as error-name=n/a error-message=n/a
Mai 29 00:01:06 orion systemd-networkd[266]: Sent message type=signal sender=n/a destination=n/a path=/org/freedesktop/network1 interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=31 reply_cookie=0 signature=sa{sv}as error-name=n/a error-message=n/a
Mai 29 00:01:06 orion systemd-networkd[266]: eno1: Addresses set
Mai 29 00:01:06 orion systemd-networkd[266]: Sent message type=signal sender=n/a destination=n/a path=/org/freedesktop/network1/link/_32 interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=32 reply_cookie=0 signature=sa{sv}as error-name=n/a error-message=n/a
Mai 29 00:01:06 orion systemd-networkd[266]: eno1: Setting routes
Mai 29 00:01:06 orion systemd-networkd[266]: eno1: Routes set
Mai 29 00:01:07 orion systemd-networkd[266]: eno1: Adding address: fe80::ae1f:6bff:fe46:c864/64 (valid forever)
Mai 29 00:01:07 orion systemd-networkd[266]: eno1: Gained IPv6LL
Mai 29 00:01:07 orion systemd-networkd[266]: eno1: Configured
Mai 29 00:01:07 orion systemd-networkd[266]: Sent message type=signal sender=n/a destination=n/a path=/org/freedesktop/network1/link/_32 interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=33 reply_cookie=0 signature=sa{sv}as error-name=n/a error-message=n/a
Mai 29 00:01:07 orion systemd-networkd[266]: eno1: Discovering IPv6 routers
Mai 29 00:01:07 orion systemd-networkd[266]: NDISC: Started IPv6 Router Solicitation client
Mai 29 00:01:07 orion systemd-networkd[266]: NDISC: Sent Router Solicitation, next solicitation in 4s
Mai 29 00:01:12 orion systemd-networkd[266]: NDISC: Sent Router Solicitation, next solicitation in 8s
Mai 29 00:01:19 orion systemd-networkd[266]: NDISC: No RA received before link confirmation timeout
Mai 29 00:01:19 orion systemd-networkd[266]: NDISC: Invoking callback for 't'.
Mai 29 00:01:20 orion systemd-networkd[266]: NDISC: Sent Router Solicitation, next solicitation in 16s

Last edited by nambot (2018-05-28 22:04:01)

Offline

#4 2018-05-29 05:54:35

seth
Member
Registered: 2012-09-03
Posts: 61,232

Re: [SOLVED]Network connection only works after down/up and reset

I assume it works when eg. using dhcpcd instead of a static IP solicitation - assuming the router supports dhcp? (Ensure to stop systemd-networkd before trying a manual connect + dhcpcd or dhclient)
Did you check the router logs about its opinion on the desired IP?

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#5 2018-05-29 18:10:50

nambot
Member
Registered: 2016-11-05
Posts: 12

Re: [SOLVED]Network connection only works after down/up and reset

Hi seth,

thanks for the suggestion. I disabled systemd-networkd and systemd-resolved, rebooted and tried dhcpcd.
Same result: works on second try.


$ dhcpcd --debug eno1
dhcpcd-7.0.4 starting
eno1: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks' PREINIT
eno1: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks' NOCARRIER
eno1: waiting for carrier
eno1: carrier acquired
eno1: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks' CARRIER
DUID 00:01:00:01:22:9f:0f:c5:ac:1f:6b:46:c8:64
eno1: IAID 6b:46:c8:64
eno1: adding address fe80::4780:8656:741:78b2
eno1: pltime infinity, vltime infinity
eno1: delaying IPv6 router solicitation for 0.2 seconds
eno1: delaying IPv4 for 0.9 seconds
eno1: soliciting an IPv6 router
eno1: delaying Router Solicitation for LL address
eno1: soliciting a DHCP lease
eno1: sending DISCOVER (xid 0x48c77f52), next in 4.3 seconds
eno1: sending Router Solicitation
eno1: sending DISCOVER (xid 0x48c77f52), next in 7.7 seconds
eno1: sending Router Solicitation
eno1: sending Router Solicitation
eno1: sending DISCOVER (xid 0x48c77f52), next in 15.6 seconds
eno1: sending Router Solicitation
eno1: no IPv6 Routers available
timed out
dhcpcd exited

network is not working:

$ ping 10.10.10.1
connect: Das Netzwerk ist nicht erreichbar

manually flush interface and bring it down and up again:

$ ip address flush dev eno1
$ ip link set eno1 down
$ ip link set eno1 up

second try:

$ dhcpcd --debug eno1
dhcpcd-7.0.4 starting
eno1: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks' PREINIT
eno1: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks' CARRIER
DUID 00:01:00:01:22:9f:0f:c5:ac:1f:6b:46:c8:64
eno1: IAID 6b:46:c8:64
eno1: adding address fe80::4780:8656:741:78b2
eno1: pltime infinity, vltime infinity
eno1: delaying IPv6 router solicitation for 0.4 seconds
eno1: delaying IPv4 for 0.3 seconds
eno1: soliciting a DHCP lease
eno1: sending DISCOVER (xid 0xb1014c80), next in 3.9 seconds
eno1: soliciting an IPv6 router
eno1: delaying Router Solicitation for LL address
eno1: offered 10.10.10.103 from 10.10.10.1
eno1: sending REQUEST (xid 0xb1014c80), next in 4.7 seconds
eno1: acknowledged 10.10.10.103 from 10.10.10.1
eno1: probing address 10.10.10.103/24
eno1: probing for 10.10.10.103
eno1: ARP probing 10.10.10.103 (1 of 3), next in 1.3 seconds
eno1: sending Router Solicitation
eno1: ARP probing 10.10.10.103 (2 of 3), next in 1.9 seconds
eno1: ARP probing 10.10.10.103 (3 of 3), next in 2.0 seconds
eno1: sending Router Solicitation
eno1: DAD completed for 10.10.10.103
eno1: leased 10.10.10.103 for 86400 seconds
eno1: renew in 43200 seconds, rebind in 75600 seconds
eno1: writing lease `/var/lib/dhcpcd/eno1.lease'
eno1: adding IP address 10.10.10.103/24 broadcast 10.10.10.255
eno1: adding route to 10.10.10.0/24
eno1: adding default route via 10.10.10.1
eno1: ARP announcing 10.10.10.103 (1 of 2), next in 2.0 seconds
eno1: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks' BOUND
forking to background
forked to background, child pid 457

and suddenly its working:

$ ping 10.10.10.1 -c4
PING 10.10.10.1 (10.10.10.1) 56(84) bytes of data.
64 bytes from 10.10.10.1: icmp_seq=1 ttl=64 time=1.09 ms
64 bytes from 10.10.10.1: icmp_seq=2 ttl=64 time=0.488 ms
64 bytes from 10.10.10.1: icmp_seq=3 ttl=64 time=0.474 ms
64 bytes from 10.10.10.1: icmp_seq=4 ttl=64 time=0.523 ms

--- 10.10.10.1 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3037ms
rtt min/avg/max/mdev = 0.474/0.644/1.094/0.261 ms

About the router logs. I have an asus router DSL-AC52U but couldnt find anything useful in the logs in the webinterface.
I have ssh access to the router but dont know what to look for.

EDIT: booting systemrescuecd (a gentoo linux based distro) results in: eno1 gets a dhcp lease automatically after booting.
They seem to use NetworkManager. I've already tried NetworkManager on archlinux (as stated in the first post).

Last edited by nambot (2018-05-29 18:40:50)

Offline

#6 2018-05-29 19:59:38

seth
Member
Registered: 2012-09-03
Posts: 61,232

Re: [SOLVED]Network connection only works after down/up and reset

You're not receiving an offer on the first try; wild guess: do you use any power saving mechanisms? (TLP, laptop-mode-tools, powertop autotuning etcetrc.)

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#7 2018-05-29 22:29:29

nambot
Member
Registered: 2016-11-05
Posts: 12

Re: [SOLVED]Network connection only works after down/up and reset

I didnt install and activate any power saving mechanisms. Not that I know of. Its a fresh install with only a few additional packages (pkgfile, dhclient, dhcping, openssh). Also the Mainboard is new. I didnt install any other operating system.
The list of activated systemd units was posted in my second post in this thread.

I also tried 3 cables and all 4 Interfaces on the motherboard.
Ubuntu and systemrescuecd configure the network out of the box just fine.

Last edited by nambot (2018-05-29 22:45:26)

Offline

#8 2018-05-30 05:57:52

seth
Member
Registered: 2012-09-03
Posts: 61,232

Re: [SOLVED]Network connection only works after down/up and reset

For more poking around: which kernel in particular? Does it also happen w/ the LTS kernel?
Try to load ixgbe w/ debug=16 for more module messages to compare between the 1st and 2nd attempt.

The router should have a frontend to access the logs, http://screenshots.portforward.com/rout … al_Log.htm

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#9 2018-05-30 06:40:29

nambot
Member
Registered: 2016-11-05
Posts: 12

Re: [SOLVED]Network connection only works after down/up and reset

I am using linux-4.16.11-1. just upgraded to linux-4.16.12-1 and no luck.

$ uname -a
Linux orion 4.16.11-1-ARCH #1 SMP PREEMPT Tue May 22 21:40:27 UTC 2018 x86_64 GNU/Linux


But I tried linux-lts 4.14.41-1-lts and it seems to work. I dont have much time at the moment, so no time to test further. (Especially Option debug=16 for ixgbe).
But I am hopeful. Thank you very much for your help. :-)

Nonetheless, I will try to further test and see if I can come up with an explanation, why the linux-lts makes it work and linux-4.16.11-1 didnt work.
Maybe I can pinpoint the version thats breaking and use git besect afterwards to identify a commit responsible.

Last edited by nambot (2018-05-30 12:51:38)

Offline

#10 2018-06-03 02:12:43

nambot
Member
Registered: 2016-11-05
Posts: 12

Re: [SOLVED]Network connection only works after down/up and reset

I suspect that the problem is the configuration of the kernels >= 4.16.x

I did a git bisect run for the repository https://git.kernel.org/pub/scm/linux/ke … stable.git between the tags v4.15.15 and v4.16
To save time I compiled the kernels using 

$ make localmodconfig

as shown in https://wiki.archlinux.org/index.php/Ke … ompilation
To my surprise, they all worked.


To further test, I pulled the PKGBUILD for linux-4.16.1 from the archlinux build system
and compiled it using these variations:
a) unedited linux-4.16.1 --> does not work
b) used config from linux-4.15.15, hit [ENTER] for every additional configuration parameter --> does not work
c) used config via "make localmodconfig" --> does work


How would I further go about finding the cause? Do I need to test variants for every new or altered kernel Parameter?
I tried adding debug=16 as Parameter for ixgbe via

$ cat /etc/modprobe.d/ixgbe.conf
options ixgbe debug=16

but it doesnt show when using

$ systool -v -m ixgbe
Module = "ixgbe"

  Attributes:
    coresize            = "348160"
    initsize            = "0"
    initstate           = "live"
    refcnt              = "0"
    srcversion          = "53C84372833B4BD66B74CAA"
    taint               = ""
    uevent              = <store method only>
    version             = "5.1.0-k"

  Sections:

Offline

#11 2018-06-09 23:57:01

nambot
Member
Registered: 2016-11-05
Posts: 12

Re: [SOLVED]Network connection only works after down/up and reset

Update: the problem only occurs when the kernel config has CONFIG_INET_ESP_OFFLOAD=m or CONFIG_INET6_ESP_OFFLOAD=m set (as it is in the linux mainline kernel package).
I did a new kernel bisection with those kernel config parameters and found that

49a94d74d9489647dfc3449ee135af4bf8fab2c1 is the first bad commit
commit 49a94d74d9489647dfc3449ee135af4bf8fab2c1
Author: Shannon Nelson <shannon.nelson@oracle.com>
Date:   Tue Dec 19 15:59:55 2017 -0800

    ixgbe: add ipsec engine start and stop routines
    
    Add in the code for running and stopping the hardware ipsec
    encryption/decryption engine.  It is good to keep the engine
    off when not in use in order to save on the power draw.
    
    Signed-off-by: Shannon Nelson <shannon.nelson@oracle.com>
    Tested-by: Andrew Bowers <andrewx.bowers@intel.com>
    Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>

I also found that a few days ago, someone with similar hardware reported the same bug upstream already.
https://lists.osuosl.org/pipermail/inte … 13007.html

And I have the phenomenon. 50 minutes after boothing, ixgbe says "detected Tx Unit hang" -> "initiating reset due to tx timeout"

Jun 10 00:12:14 orion kernel: ixgbe 0000:05:00.0 eno1: renamed from eth0
Jun 10 00:12:14 orion kernel: ixgbe 0000:05:00.0: registered PHC device on eno1
Jun 10 00:12:18 orion kernel: ixgbe 0000:05:00.0 eno1: NIC Link is Up 1 Gbps, Flow Control: RX/TX
Jun 10 01:02:15 orion kernel: ixgbe 0000:05:00.0 eno1: Detected Tx Unit Hang 
Jun 10 01:02:15 orion kernel: ixgbe 0000:05:00.0 eno1: tx hang 1 detected on queue 3, resetting adapter
Jun 10 01:02:15 orion kernel: ixgbe 0000:05:00.0 eno1: initiating reset due to tx timeout
Jun 10 01:02:15 orion kernel: ixgbe: eno1            0000000000000003 00000001000C5FB0
Jun 10 01:02:15 orion kernel: ixgbe 0000:05:00.0 eno1: Reset adapter
Jun 10 01:02:15 orion kernel: ixgbe 0000:05:00.0 eno1: NIC Link is Down
Jun 10 01:02:19 orion kernel: ixgbe 0000:05:00.0 eno1: NIC Link is Up 1 Gbps, Flow Control: RX/TX

Patches are already being discussed in the mailing group.

Offline

Pages: 1

Board footer

Powered by FluxBB