You are not logged in.

#1 2018-05-20 16:59:03

sweetthdevil
Member
Registered: 2009-10-20
Posts: 415

Ethernet connection dropping - how to assess?

Hello all,

My ethernet connection drops regularly ( I know it's not the cables as it doesn't on the same machine running Windows 10)

Network is managed by systemd.netword and it drops without any warning nothing from the journal indicates the reasons and reappear after several minutes.

How can I investigate the issue? Is there a tool to monitor the connection?

Thanks,

Offline

#2 2018-05-20 17:08:53

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

Re: Ethernet connection dropping - how to assess?

Define 'Drop'.  Does the carrier go away?  Are the link lights on the computer on? how about the router?  Is it possible you still have a link but are losing your IP address?  If you still have an IP address, Is it possible that you can still see machines on your local network?


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 2018-05-20 18:48:01

sweetthdevil
Member
Registered: 2009-10-20
Posts: 415

Re: Ethernet connection dropping - how to assess?

The router is still working and online - I think I am losing the IP. But the journal doesn't give any indication.

Offline

#4 2018-05-20 18:54:52

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

Re: Ethernet connection dropping - how to assess?

When it drops, post the output of ip addr


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

#5 2018-05-20 19:03:09

seth
Member
Registered: 2012-09-03
Posts: 51,046

Re: Ethernet connection dropping - how to assess?

Sure about the journal?
Also, ceterum censeo: "systemctl list-unit-files --state=enabled"

Offline

#6 2018-05-21 19:10:56

sweetthdevil
Member
Registered: 2009-10-20
Posts: 415

Re: Ethernet connection dropping - how to assess?

Right,

Just got a lost of connection:

See ip addr: $ ip addr

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: enp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 30:5a:3a:07:c3:83 brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.95/24 brd 192.168.1.255 scope global enp3s0
       valid_lft forever preferred_lft forever
    inet6 2a00:23c4:6cba:1000:325a:3aff:fe07:c383/64 scope global dynamic mngtmpaddr noprefixroute 
       valid_lft 315359986sec preferred_lft 315359986sec
    inet6 fdaa:bbcc:ddee:0:325a:3aff:fe07:c383/64 scope global mngtmpaddr noprefixroute 
       valid_lft forever preferred_lft forever
    inet6 fe80::325a:3aff:fe07:c383/64 scope link 
       valid_lft forever preferred_lft forever

And just to answer regarding the journal see output:

May 21 19:54:02 Archlinux chromium.desktop[1091]: [1189:1189:0521/195402.274148:ERROR:buffer_manager.cc(452)] [.DisplayCompositor-0x3cecde0bc000]GL ERROR :GL_INVALID_OPERATION>
May 21 19:54:54 Archlinux nmbd[390]: [2018/05/21 19:54:54.371390,  0] ../source3/nmbd/nmbd_namequery.c:109(query_name_response)
May 21 19:54:54 Archlinux nmbd[390]:   query_name_response: Multiple (2) responses received for a query on subnet 192.168.1.95 for name MYGROUP<1d>.
May 21 19:54:54 Archlinux nmbd[390]:   This response was from IP 192.168.1.99, reporting an IP address of 192.168.1.99.
May 21 19:59:44 Archlinux chromium.desktop[1091]: [1189:1189:0521/195944.444760:ERROR:gles2_cmd_decoder.cc(18288)] [.DisplayCompositor-0x3cecd7a01800]GL ERROR :GL_INVALID_OPER>
May 21 19:59:44 Archlinux chromium.desktop[1091]: [1189:1189:0521/195944.444819:ERROR:gles2_cmd_decoder.cc(10129)] [.DisplayCompositor-0x3cecd7a01800]RENDER WARNING: texture b>
May 21 19:59:54 Archlinux nmbd[390]: [2018/05/21 19:59:54.648227,  0] ../source3/nmbd/nmbd_namequery.c:109(query_name_response)
May 21 19:59:54 Archlinux nmbd[390]:   query_name_response: Multiple (2) responses received for a query on subnet 192.168.1.95 for name MYGROUP<1d>.
May 21 19:59:54 Archlinux nmbd[390]:   This response was from IP 192.168.1.99, reporting an IP address of 192.168.1.99.
May 21 20:00:01 Archlinux CROND[7246]: (root) CMD (squid -k rotate)
May 21 20:00:01 Archlinux squid[407]: storeDirWriteCleanLogs: Starting...
May 21 20:00:01 Archlinux squid[407]:   Finished.  Wrote 0 entries.
May 21 20:00:01 Archlinux squid[407]:   Took 0.00 seconds (  0.00 entries/sec).
May 21 20:00:01 Archlinux squid[407]: logfileRotate: stdio:/var/log/squid/access.log
May 21 20:00:01 Archlinux squid[407]: Rotate log file stdio:/var/log/squid/access.log
May 21 20:00:01 Archlinux squid[407]: logfileRotate: stdio:/var/log/squid/my_access.log
May 21 20:00:01 Archlinux squid[407]: Rotate log file stdio:/var/log/squid/my_access.log
May 21 20:00:56 Archlinux dbus-daemon[669]: dbus-daemon[669]: [session uid=1000 pid=669] Activating via systemd: service name='org.gnome.Terminal' unit='gnome-terminal-server.>
May 21 20:00:56 Archlinux systemd[663]: Starting GNOME Terminal Server...
May 21 20:00:56 Archlinux dbus-daemon[669]: dbus-daemon[669]: [session uid=1000 pid=669] Successfully activated service 'org.gnome.Terminal'
May 21 20:00:56 Archlinux systemd[663]: Started GNOME Terminal Server.
May 21 20:00:56 Archlinux gnome-shell[723]: Object Clutter.Clone (0x5558a03a7470), has been already finalized. Impossible to get any property from it.
May 21 20:00:56 Archlinux gnome-shell[723]: Object Clutter.Clone (0x5558a03a7470), has been already finalized. Impossible to set any property to it.
May 21 20:00:56 Archlinux org.gnome.Shell.desktop[723]: == Stack trace for context 0x55589d34e060 ==
May 21 20:00:56 Archlinux org.gnome.Shell.desktop[723]: #0 0x7ffd1522cc90 b   resource:///org/gnome/shell/ui/tweener.js:73 (0x7ff7546c7cd0 @ 9)
May 21 20:00:56 Archlinux org.gnome.Shell.desktop[723]: #1 0x7ffd1522cd30 b   resource:///org/gnome/shell/ui/tweener.js:105 (0x7ff7546c7f78 @ 36)
May 21 20:00:56 Archlinux org.gnome.Shell.desktop[723]: #2 0x7ffd1522cdd0 b   resource:///org/gnome/shell/ui/tweener.js:92 (0x7ff7546c7de0 @ 52)
May 21 20:00:56 Archlinux org.gnome.Shell.desktop[723]: #3 0x7ffd1522d970 I   resource:///org/gnome/gjs/modules/tweener/tweener.js:208 (0x7ff7546d2918 @ 54)
May 21 20:00:56 Archlinux org.gnome.Shell.desktop[723]: #4 0x7ffd1522dac0 b   resource:///org/gnome/gjs/modules/tweener/tweener.js:337 (0x7ff7546d29a0 @ 1626)
May 21 20:00:56 Archlinux org.gnome.Shell.desktop[723]: #5 0x7ffd1522db70 b   resource:///org/gnome/gjs/modules/tweener/tweener.js:350 (0x7ff7546d2a28 @ 100)
May 21 20:00:56 Archlinux org.gnome.Shell.desktop[723]: #6 0x7ffd1522dc00 b   resource:///org/gnome/gjs/modules/tweener/tweener.js:365 (0x7ff7546d2ab0 @ 10)
May 21 20:00:56 Archlinux org.gnome.Shell.desktop[723]: #7 0x7ffd1522dc80 I   resource:///org/gnome/gjs/modules/signals.js:128 (0x7ff7546cff78 @ 386)
May 21 20:00:56 Archlinux org.gnome.Shell.desktop[723]: #8 0x7ffd1522dd30 b   resource:///org/gnome/shell/ui/tweener.js:207 (0x7ff7546cf5e8 @ 159)
May 21 20:00:56 Archlinux org.gnome.Shell.desktop[723]: #9 0x7ffd1522dda0 I   resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7ff7546b5de0 @ 71)
May 21 20:00:56 Archlinux org.gnome.Shell.desktop[723]: #10 0x7ffd1522dda0 I   resource:///org/gnome/shell/ui/tweener.js:182 (0x7ff7546cf560 @ 15)
May 21 20:00:56 Archlinux org.gnome.Shell.desktop[723]: == Stack trace for context 0x55589d34e060 ==
May 21 20:00:56 Archlinux org.gnome.Shell.desktop[723]: #0 0x7ffd1522cc90 b   resource:///org/gnome/shell/ui/tweener.js:80 (0x7ff7546c7cd0 @ 82)
May 21 20:00:56 Archlinux org.gnome.Shell.desktop[723]: #1 0x7ffd1522cd30 b   resource:///org/gnome/shell/ui/tweener.js:105 (0x7ff7546c7f78 @ 36)
May 21 20:00:56 Archlinux org.gnome.Shell.desktop[723]: #2 0x7ffd1522cdd0 b   resource:///org/gnome/shell/ui/tweener.js:92 (0x7ff7546c7de0 @ 52)
May 21 20:00:56 Archlinux org.gnome.Shell.desktop[723]: #3 0x7ffd1522d970 I   resource:///org/gnome/gjs/modules/tweener/tweener.js:208 (0x7ff7546d2918 @ 54)
May 21 20:00:56 Archlinux org.gnome.Shell.desktop[723]: #4 0x7ffd1522dac0 b   resource:///org/gnome/gjs/modules/tweener/tweener.js:337 (0x7ff7546d29a0 @ 1626)
May 21 20:00:56 Archlinux org.gnome.Shell.desktop[723]: #5 0x7ffd1522db70 b   resource:///org/gnome/gjs/modules/tweener/tweener.js:350 (0x7ff7546d2a28 @ 100)
May 21 20:00:56 Archlinux org.gnome.Shell.desktop[723]: #6 0x7ffd1522dc00 b   resource:///org/gnome/gjs/modules/tweener/tweener.js:365 (0x7ff7546d2ab0 @ 10)
May 21 20:00:56 Archlinux org.gnome.Shell.desktop[723]: #7 0x7ffd1522dc80 I   resource:///org/gnome/gjs/modules/signals.js:128 (0x7ff7546cff78 @ 386)
May 21 20:00:56 Archlinux org.gnome.Shell.desktop[723]: #8 0x7ffd1522dd30 b   resource:///org/gnome/shell/ui/tweener.js:207 (0x7ff7546cf5e8 @ 159)
May 21 20:00:56 Archlinux org.gnome.Shell.desktop[723]: #9 0x7ffd1522dda0 I   resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7ff7546b5de0 @ 71)
May 21 20:00:56 Archlinux org.gnome.Shell.desktop[723]: #10 0x7ffd1522dda0 I   resource:///org/gnome/shell/ui/tweener.js:182 (0x7ff7546cf560 @ 15)
May 21 20:01:01 Archlinux CROND[7290]: (root) CMD (run-parts /etc/cron.hourly)
May 21 20:05:03 Archlinux nmbd[390]: [2018/05/21 20:05:03.922337,  0] ../source3/nmbd/nmbd_namequery.c:109(query_name_response)
May 21 20:05:03 Archlinux nmbd[390]:   query_name_response: Multiple (2) responses received for a query on subnet 192.168.1.95 for name MYGROUP<1d>.
May 21 20:05:03 Archlinux nmbd[390]:   This response was from IP 192.168.1.99, reporting an IP address of 192.168.1.99.

The message regarding the ip 192.168.1.99 is the samba mount for my NAS.

Offline

#7 2018-05-21 19:17:25

seth
Member
Registered: 2012-09-03
Posts: 51,046

Re: Ethernet connection dropping - how to assess?

ip addr doesn't indicate a connection loss at all - since apparently neither does the journal, what does actually indicate to you that the connection dropped?
Can you still "ping 8.8.8.8" in this situation?

Offline

#8 2018-05-21 19:19:39

sweetthdevil
Member
Registered: 2009-10-20
Posts: 415

Re: Ethernet connection dropping - how to assess?

No I cannot ping any external or internal IP.

No connection from the browser neither - and as you can see the Journal indicate that the network samba share has lost the connection - cannot access the router through the webpage neither can I ping it.

However, my phone connecting to the wifi is still connected to the outside world?!

Last edited by sweetthdevil (2018-05-21 19:20:30)

Offline

#9 2018-05-21 19:27:59

seth
Member
Registered: 2012-09-03
Posts: 51,046

Re: Ethernet connection dropping - how to assess?

Ok, things to check:
- raise the systemd-networkd log level, https://unix.stackexchange.com/question … d-networkd
- ditch systemd-networkd and try dhclient or dhcpcd (and just wait whether this still happens)
- your router logs, eg. whether the connection drops correspond w/ lease expirations

Offline

#10 2018-05-21 19:34:51

sweetthdevil
Member
Registered: 2009-10-20
Posts: 415

Re: Ethernet connection dropping - how to assess?

Thanks,

Will raised the log level to debug, but I am using a fix ip address as opposed to DHCP.  In regards, to the router logs there isn't anything particular showing neither.

Will report once it happens again.

Offline

#11 2018-05-22 19:10:52

sweetthdevil
Member
Registered: 2009-10-20
Posts: 415

Re: Ethernet connection dropping - how to assess?

Right,

this is a lot more information - and unfortunatelly information that doesn't mean anything...

May 22 19:55:13 Archlinux systemd-networkd[279]: NDISC: Received Router Advertisement: flags OTHER preference medium lifetime 300 sec
May 22 19:55:13 Archlinux systemd-networkd[279]: NDISC: Invoking callback for 'r'.
May 22 19:55:13 Archlinux systemd-networkd[279]: DHCPv6 CLIENT: Started in Information request mode
May 22 19:55:13 Archlinux systemd-networkd[279]: enp3s0: Acquiring DHCPv6 lease on NDisc request
May 22 19:55:13 Archlinux systemd-networkd[279]: DHCPv6 CLIENT: Sent INFORMATION-REQUEST
May 22 19:55:13 Archlinux systemd-networkd[279]: DHCPv6 CLIENT: Next retransmission in 1s
May 22 19:55:13 Archlinux systemd-networkd[279]: enp3s0: Updating address: fdaa:bbcc:ddee:0:325a:3aff:fe07:c383/64 (valid forever)
May 22 19:55:13 Archlinux systemd-networkd[279]: enp3s0: Updating address: 2a00:23c4:6cba:1000:325a:3aff:fe07:c383/64 (valid for 9y 11month 3w 6d 22h 30min)
May 22 19:55:13 Archlinux systemd-networkd[279]: DHCPv6 CLIENT: Recv REPLY
May 22 19:56:05 Archlinux nmbd[392]: [2018/05/22 19:56:05.518251,  0] ../source3/nmbd/nmbd_namequery.c:109(query_name_response)
May 22 19:56:05 Archlinux nmbd[392]:   query_name_response: Multiple (2) responses received for a query on subnet 192.168.1.95 for name MYGROUP<1d>.
May 22 19:56:05 Archlinux nmbd[392]:   This response was from IP 192.168.1.99, reporting an IP address of 192.168.1.99.
May 22 19:56:07 Archlinux systemd-networkd[279]: NDISC: Received Router Advertisement: flags OTHER preference medium lifetime 300 sec
May 22 19:56:07 Archlinux systemd-networkd[279]: NDISC: Invoking callback for 'r'.
May 22 19:56:07 Archlinux systemd-networkd[279]: DHCPv6 CLIENT: Started in Information request mode
May 22 19:56:07 Archlinux systemd-networkd[279]: enp3s0: Acquiring DHCPv6 lease on NDisc request
May 22 19:56:07 Archlinux systemd-networkd[279]: DHCPv6 CLIENT: Sent INFORMATION-REQUEST
May 22 19:56:07 Archlinux systemd-networkd[279]: DHCPv6 CLIENT: Next retransmission in 1s
May 22 19:56:07 Archlinux systemd-networkd[279]: enp3s0: Updating address: fdaa:bbcc:ddee:0:325a:3aff:fe07:c383/64 (valid forever)
May 22 19:56:07 Archlinux systemd-networkd[279]: enp3s0: Updating address: 2a00:23c4:6cba:1000:325a:3aff:fe07:c383/64 (valid for 9y 11month 3w 6d 22h 30min)
May 22 19:56:07 Archlinux systemd-networkd[279]: DHCPv6 CLIENT: Recv REPLY
May 22 19:56:52 Archlinux systemd-networkd[279]: NDISC: Received Router Advertisement: flags OTHER preference medium lifetime 300 sec
May 22 19:56:52 Archlinux systemd-networkd[279]: NDISC: Invoking callback for 'r'.
May 22 19:56:52 Archlinux systemd-networkd[279]: DHCPv6 CLIENT: Started in Information request mode
May 22 19:56:52 Archlinux systemd-networkd[279]: enp3s0: Acquiring DHCPv6 lease on NDisc request
May 22 19:56:52 Archlinux systemd-networkd[279]: DHCPv6 CLIENT: Sent INFORMATION-REQUEST
May 22 19:56:52 Archlinux systemd-networkd[279]: DHCPv6 CLIENT: Next retransmission in 932ms
May 22 19:56:52 Archlinux systemd-networkd[279]: enp3s0: Updating address: fdaa:bbcc:ddee:0:325a:3aff:fe07:c383/64 (valid forever)
May 22 19:56:52 Archlinux systemd-networkd[279]: enp3s0: Updating address: 2a00:23c4:6cba:1000:325a:3aff:fe07:c383/64 (valid for 9y 11month 3w 6d 22h 30min)
May 22 19:56:52 Archlinux systemd-networkd[279]: DHCPv6 CLIENT: Recv REPLY
May 22 19:57:41 Archlinux systemd-networkd[279]: NDISC: Received Router Advertisement: flags OTHER preference medium lifetime 300 sec
May 22 19:57:41 Archlinux systemd-networkd[279]: NDISC: Invoking callback for 'r'.
May 22 19:57:41 Archlinux systemd-networkd[279]: DHCPv6 CLIENT: Started in Information request mode
May 22 19:57:41 Archlinux systemd-networkd[279]: enp3s0: Acquiring DHCPv6 lease on NDisc request
May 22 19:57:41 Archlinux systemd-networkd[279]: DHCPv6 CLIENT: Sent INFORMATION-REQUEST
May 22 19:57:41 Archlinux systemd-networkd[279]: DHCPv6 CLIENT: Next retransmission in 1s
May 22 19:57:41 Archlinux systemd-networkd[279]: enp3s0: Updating address: fdaa:bbcc:ddee:0:325a:3aff:fe07:c383/64 (valid forever)
May 22 19:57:41 Archlinux systemd-networkd[279]: enp3s0: Updating address: 2a00:23c4:6cba:1000:325a:3aff:fe07:c383/64 (valid for 9y 11month 3w 6d 22h 30min)
May 22 19:57:41 Archlinux systemd-networkd[279]: DHCPv6 CLIENT: Recv REPLY
May 22 19:58:31 Archlinux systemd-networkd[279]: NDISC: Received Router Advertisement: flags OTHER preference medium lifetime 300 sec
May 22 19:58:31 Archlinux systemd-networkd[279]: NDISC: Invoking callback for 'r'.
May 22 19:58:31 Archlinux systemd-networkd[279]: DHCPv6 CLIENT: Started in Information request mode
May 22 19:58:31 Archlinux systemd-networkd[279]: enp3s0: Acquiring DHCPv6 lease on NDisc request
May 22 19:58:31 Archlinux systemd-networkd[279]: DHCPv6 CLIENT: Sent INFORMATION-REQUEST
May 22 19:58:31 Archlinux systemd-networkd[279]: DHCPv6 CLIENT: Next retransmission in 913ms
May 22 19:58:31 Archlinux systemd-networkd[279]: enp3s0: Updating address: fdaa:bbcc:ddee:0:325a:3aff:fe07:c383/64 (valid forever)
May 22 19:58:31 Archlinux systemd-networkd[279]: enp3s0: Updating address: 2a00:23c4:6cba:1000:325a:3aff:fe07:c383/64 (valid for 9y 11month 3w 6d 22h 30min)
May 22 19:58:31 Archlinux systemd-networkd[279]: DHCPv6 CLIENT: Recv REPLY
May 22 19:59:31 Archlinux systemd-networkd[279]: NDISC: Received Router Advertisement: flags OTHER preference medium lifetime 300 sec
May 22 19:59:31 Archlinux systemd-networkd[279]: NDISC: Invoking callback for 'r'.
May 22 19:59:31 Archlinux systemd-networkd[279]: DHCPv6 CLIENT: Started in Information request mode
May 22 19:59:31 Archlinux systemd-networkd[279]: enp3s0: Acquiring DHCPv6 lease on NDisc request
May 22 19:59:31 Archlinux systemd-networkd[279]: DHCPv6 CLIENT: Sent INFORMATION-REQUEST
May 22 19:59:31 Archlinux systemd-networkd[279]: DHCPv6 CLIENT: Next retransmission in 1s
May 22 19:59:31 Archlinux systemd-networkd[279]: enp3s0: Updating address: fdaa:bbcc:ddee:0:325a:3aff:fe07:c383/64 (valid forever)
May 22 19:59:31 Archlinux systemd-networkd[279]: enp3s0: Updating address: 2a00:23c4:6cba:1000:325a:3aff:fe07:c383/64 (valid for 9y 11month 3w 6d 22h 30min)
May 22 19:59:31 Archlinux systemd-networkd[279]: DHCPv6 CLIENT: Recv REPLY
May 22 20:00:21 Archlinux systemd-networkd[279]: NDISC: Received Router Advertisement: flags OTHER preference medium lifetime 300 sec
May 22 20:00:21 Archlinux systemd-networkd[279]: NDISC: Invoking callback for 'r'.
May 22 20:00:21 Archlinux systemd-networkd[279]: DHCPv6 CLIENT: Started in Information request mode
May 22 20:00:21 Archlinux systemd-networkd[279]: enp3s0: Acquiring DHCPv6 lease on NDisc request
May 22 20:00:21 Archlinux systemd-networkd[279]: DHCPv6 CLIENT: Sent INFORMATION-REQUEST
May 22 20:00:21 Archlinux systemd-networkd[279]: DHCPv6 CLIENT: Next retransmission in 905ms
May 22 20:00:21 Archlinux systemd-networkd[279]: enp3s0: Updating address: fdaa:bbcc:ddee:0:325a:3aff:fe07:c383/64 (valid forever)
May 22 20:00:21 Archlinux systemd-networkd[279]: enp3s0: Updating address: 2a00:23c4:6cba:1000:325a:3aff:fe07:c383/64 (valid for 9y 11month 3w 6d 22h 30min)
May 22 20:00:21 Archlinux systemd-networkd[279]: DHCPv6 CLIENT: Recv REPLY
May 22 20:00:54 Archlinux systemd-networkd[279]: NDISC: Received Router Advertisement: flags OTHER preference medium lifetime 300 sec
May 22 20:00:54 Archlinux systemd-networkd[279]: NDISC: Invoking callback for 'r'.
May 22 20:00:54 Archlinux systemd-networkd[279]: DHCPv6 CLIENT: Started in Information request mode
May 22 20:00:54 Archlinux systemd-networkd[279]: enp3s0: Acquiring DHCPv6 lease on NDisc request
May 22 20:00:54 Archlinux systemd-networkd[279]: DHCPv6 CLIENT: Sent INFORMATION-REQUEST
May 22 20:00:54 Archlinux systemd-networkd[279]: DHCPv6 CLIENT: Next retransmission in 1s
May 22 20:00:54 Archlinux systemd-networkd[279]: enp3s0: Updating address: fdaa:bbcc:ddee:0:325a:3aff:fe07:c383/64 (valid forever)
May 22 20:00:54 Archlinux systemd-networkd[279]: enp3s0: Updating address: 2a00:23c4:6cba:1000:325a:3aff:fe07:c383/64 (valid for 9y 11month 3w 6d 22h 30min)
May 22 20:00:54 Archlinux systemd-networkd[279]: DHCPv6 CLIENT: Recv REPLY
May 22 20:01:05 Archlinux nmbd[392]: [2018/05/22 20:01:05.625742,  0] ../source3/nmbd/nmbd_namequery.c:109(query_name_response)
May 22 20:01:05 Archlinux nmbd[392]:   query_name_response: Multiple (2) responses received for a query on subnet 192.168.1.95 for name MYGROUP<1d>.
May 22 20:01:05 Archlinux nmbd[392]:   This response was from IP 192.168.1.99, reporting an IP address of 192.168.1.99.
May 22 20:01:43 Archlinux systemd-networkd[279]: NDISC: Received Router Advertisement: flags OTHER preference medium lifetime 300 sec
May 22 20:01:43 Archlinux systemd-networkd[279]: NDISC: Invoking callback for 'r'.
May 22 20:01:43 Archlinux systemd-networkd[279]: DHCPv6 CLIENT: Started in Information request mode
May 22 20:01:43 Archlinux systemd-networkd[279]: enp3s0: Acquiring DHCPv6 lease on NDisc request
May 22 20:01:43 Archlinux systemd-networkd[279]: DHCPv6 CLIENT: Sent INFORMATION-REQUEST
May 22 20:01:43 Archlinux systemd-networkd[279]: DHCPv6 CLIENT: Next retransmission in 1s
May 22 20:01:43 Archlinux systemd-networkd[279]: enp3s0: Updating address: fdaa:bbcc:ddee:0:325a:3aff:fe07:c383/64 (valid forever)
May 22 20:01:43 Archlinux systemd-networkd[279]: enp3s0: Updating address: 2a00:23c4:6cba:1000:325a:3aff:fe07:c383/64 (valid for 9y 11month 3w 6d 22h 30min)
May 22 20:01:43 Archlinux systemd-networkd[279]: DHCPv6 CLIENT: Recv REPLY
May 22 20:02:26 Archlinux systemd-networkd[279]: NDISC: Received Router Advertisement: flags OTHER preference medium lifetime 300 sec
May 22 20:02:26 Archlinux systemd-networkd[279]: NDISC: Invoking callback for 'r'.
May 22 20:02:26 Archlinux systemd-networkd[279]: DHCPv6 CLIENT: Started in Information request mode
May 22 20:02:26 Archlinux systemd-networkd[279]: enp3s0: Acquiring DHCPv6 lease on NDisc request
May 22 20:02:26 Archlinux systemd-networkd[279]: DHCPv6 CLIENT: Sent INFORMATION-REQUEST
May 22 20:02:26 Archlinux systemd-networkd[279]: DHCPv6 CLIENT: Next retransmission in 1s
May 22 20:02:26 Archlinux systemd-networkd[279]: enp3s0: Updating address: fdaa:bbcc:ddee:0:325a:3aff:fe07:c383/64 (valid forever)
May 22 20:02:26 Archlinux systemd-networkd[279]: enp3s0: Updating address: 2a00:23c4:6cba:1000:325a:3aff:fe07:c383/64 (valid for 9y 11month 3w 6d 22h 30min)
May 22 20:02:26 Archlinux systemd-networkd[279]: DHCPv6 CLIENT: Recv REPLY
May 22 20:03:26 Archlinux systemd-networkd[279]: NDISC: Received Router Advertisement: flags OTHER preference medium lifetime 300 sec
May 22 20:03:26 Archlinux systemd-networkd[279]: NDISC: Invoking callback for 'r'.
May 22 20:03:26 Archlinux systemd-networkd[279]: DHCPv6 CLIENT: Started in Information request mode
May 22 20:03:26 Archlinux systemd-networkd[279]: enp3s0: Acquiring DHCPv6 lease on NDisc request
May 22 20:03:26 Archlinux systemd-networkd[279]: DHCPv6 CLIENT: Sent INFORMATION-REQUEST
May 22 20:03:26 Archlinux systemd-networkd[279]: DHCPv6 CLIENT: Next retransmission in 917ms
May 22 20:03:26 Archlinux systemd-networkd[279]: enp3s0: Updating address: fdaa:bbcc:ddee:0:325a:3aff:fe07:c383/64 (valid forever)
May 22 20:03:26 Archlinux systemd-networkd[279]: enp3s0: Updating address: 2a00:23c4:6cba:1000:325a:3aff:fe07:c383/64 (valid for 9y 11month 3w 6d 22h 30min)
May 22 20:03:26 Archlinux systemd-networkd[279]: DHCPv6 CLIENT: Recv REPLY
May 22 20:04:00 Archlinux systemd-networkd[279]: NDISC: Received Router Advertisement: flags OTHER preference medium lifetime 300 sec
May 22 20:04:00 Archlinux systemd-networkd[279]: NDISC: Invoking callback for 'r'.
May 22 20:04:00 Archlinux systemd-networkd[279]: DHCPv6 CLIENT: Started in Information request mode
May 22 20:04:00 Archlinux systemd-networkd[279]: enp3s0: Acquiring DHCPv6 lease on NDisc request
May 22 20:04:00 Archlinux systemd-networkd[279]: DHCPv6 CLIENT: Sent INFORMATION-REQUEST
May 22 20:04:00 Archlinux systemd-networkd[279]: DHCPv6 CLIENT: Next retransmission in 937ms
May 22 20:04:00 Archlinux systemd-networkd[279]: enp3s0: Updating address: fdaa:bbcc:ddee:0:325a:3aff:fe07:c383/64 (valid forever)
May 22 20:04:00 Archlinux systemd-networkd[279]: enp3s0: Updating address: 2a00:23c4:6cba:1000:325a:3aff:fe07:c383/64 (valid for 9y 11month 3w 6d 22h 30min)
May 22 20:04:00 Archlinux systemd-networkd[279]: DHCPv6 CLIENT: Recv REPLY
May 22 20:04:39 Archlinux systemd-networkd[279]: NDISC: Received Router Advertisement: flags OTHER preference medium lifetime 300 sec
May 22 20:04:39 Archlinux systemd-networkd[279]: NDISC: Invoking callback for 'r'.
May 22 20:04:39 Archlinux systemd-networkd[279]: DHCPv6 CLIENT: Started in Information request mode
May 22 20:04:39 Archlinux systemd-networkd[279]: enp3s0: Acquiring DHCPv6 lease on NDisc request
May 22 20:04:39 Archlinux systemd-networkd[279]: DHCPv6 CLIENT: Sent INFORMATION-REQUEST
May 22 20:04:39 Archlinux systemd-networkd[279]: DHCPv6 CLIENT: Next retransmission in 1s
May 22 20:04:39 Archlinux systemd-networkd[279]: enp3s0: Updating address: fdaa:bbcc:ddee:0:325a:3aff:fe07:c383/64 (valid forever)
May 22 20:04:39 Archlinux systemd-networkd[279]: enp3s0: Updating address: 2a00:23c4:6cba:1000:325a:3aff:fe07:c383/64 (valid for 9y 11month 3w 6d 22h 30min)
May 22 20:04:39 Archlinux systemd-networkd[279]: DHCPv6 CLIENT: Recv REPLY
May 22 20:05:24 Archlinux systemd-networkd[279]: NDISC: Received Router Advertisement: flags OTHER preference medium lifetime 300 sec
May 22 20:05:24 Archlinux systemd-networkd[279]: NDISC: Invoking callback for 'r'.
May 22 20:05:24 Archlinux systemd-networkd[279]: DHCPv6 CLIENT: Started in Information request mode
May 22 20:05:24 Archlinux systemd-networkd[279]: enp3s0: Acquiring DHCPv6 lease on NDisc request
May 22 20:05:24 Archlinux systemd-networkd[279]: DHCPv6 CLIENT: Sent INFORMATION-REQUEST
May 22 20:05:24 Archlinux systemd-networkd[279]: DHCPv6 CLIENT: Next retransmission in 977ms
May 22 20:05:24 Archlinux systemd-networkd[279]: enp3s0: Updating address: fdaa:bbcc:ddee:0:325a:3aff:fe07:c383/64 (valid forever)
May 22 20:05:24 Archlinux systemd-networkd[279]: enp3s0: Updating address: 2a00:23c4:6cba:1000:325a:3aff:fe07:c383/64 (valid for 9y 11month 3w 6d 22h 30min)
May 22 20:05:24 Archlinux systemd-networkd[279]: DHCPv6 CLIENT: Recv REPLY
May 22 20:02:26 Archlinux systemd-networkd[279]: DHCPv6 CLIENT: Started in Information request mode
May 22 20:02:26 Archlinux systemd-networkd[279]: enp3s0: Acquiring DHCPv6 lease on NDisc request
May 22 20:02:26 Archlinux systemd-networkd[279]: DHCPv6 CLIENT: Sent INFORMATION-REQUEST
May 22 20:02:26 Archlinux systemd-networkd[279]: DHCPv6 CLIENT: Next retransmission in 1s
May 22 20:02:26 Archlinux systemd-networkd[279]: enp3s0: Updating address: fdaa:bbcc:ddee:0:325a:3aff:fe07:c383/64 (valid forever)
May 22 20:02:26 Archlinux systemd-networkd[279]: enp3s0: Updating address: 2a00:23c4:6cba:1000:325a:3aff:fe07:c383/64 (valid for 9y 11month 3w 6d 22h 30min)
May 22 20:02:26 Archlinux systemd-networkd[279]: DHCPv6 CLIENT: Recv REPLY
May 22 20:03:26 Archlinux systemd-networkd[279]: NDISC: Received Router Advertisement: flags OTHER preference medium lifetime 300 sec
May 22 20:03:26 Archlinux systemd-networkd[279]: NDISC: Invoking callback for 'r'.
May 22 20:03:26 Archlinux systemd-networkd[279]: DHCPv6 CLIENT: Started in Information request mode
May 22 20:03:26 Archlinux systemd-networkd[279]: enp3s0: Acquiring DHCPv6 lease on NDisc request
May 22 20:03:26 Archlinux systemd-networkd[279]: DHCPv6 CLIENT: Sent INFORMATION-REQUEST
May 22 20:03:26 Archlinux systemd-networkd[279]: DHCPv6 CLIENT: Next retransmission in 917ms
May 22 20:03:26 Archlinux systemd-networkd[279]: enp3s0: Updating address: fdaa:bbcc:ddee:0:325a:3aff:fe07:c383/64 (valid forever)
May 22 20:03:26 Archlinux systemd-networkd[279]: enp3s0: Updating address: 2a00:23c4:6cba:1000:325a:3aff:fe07:c383/64 (valid for 9y 11month 3w 6d 22h 30min)
May 22 20:03:26 Archlinux systemd-networkd[279]: DHCPv6 CLIENT: Recv REPLY
May 22 20:04:00 Archlinux systemd-networkd[279]: NDISC: Received Router Advertisement: flags OTHER preference medium lifetime 300 sec
May 22 20:04:00 Archlinux systemd-networkd[279]: NDISC: Invoking callback for 'r'.
May 22 20:04:00 Archlinux systemd-networkd[279]: DHCPv6 CLIENT: Started in Information request mode
May 22 20:04:00 Archlinux systemd-networkd[279]: enp3s0: Acquiring DHCPv6 lease on NDisc request
May 22 20:04:00 Archlinux systemd-networkd[279]: DHCPv6 CLIENT: Sent INFORMATION-REQUEST
May 22 20:04:00 Archlinux systemd-networkd[279]: DHCPv6 CLIENT: Next retransmission in 937ms
May 22 20:04:00 Archlinux systemd-networkd[279]: enp3s0: Updating address: fdaa:bbcc:ddee:0:325a:3aff:fe07:c383/64 (valid forever)
May 22 20:04:00 Archlinux systemd-networkd[279]: enp3s0: Updating address: 2a00:23c4:6cba:1000:325a:3aff:fe07:c383/64 (valid for 9y 11month 3w 6d 22h 30min)
May 22 20:04:00 Archlinux systemd-networkd[279]: DHCPv6 CLIENT: Recv REPLY
May 22 20:04:39 Archlinux systemd-networkd[279]: NDISC: Received Router Advertisement: flags OTHER preference medium lifetime 300 sec
May 22 20:04:39 Archlinux systemd-networkd[279]: NDISC: Invoking callback for 'r'.
May 22 20:04:39 Archlinux systemd-networkd[279]: DHCPv6 CLIENT: Started in Information request mode
May 22 20:04:39 Archlinux systemd-networkd[279]: enp3s0: Acquiring DHCPv6 lease on NDisc request
May 22 20:04:39 Archlinux systemd-networkd[279]: DHCPv6 CLIENT: Sent INFORMATION-REQUEST
May 22 20:04:39 Archlinux systemd-networkd[279]: DHCPv6 CLIENT: Next retransmission in 1s
May 22 20:04:39 Archlinux systemd-networkd[279]: enp3s0: Updating address: fdaa:bbcc:ddee:0:325a:3aff:fe07:c383/64 (valid forever)
May 22 20:04:39 Archlinux systemd-networkd[279]: enp3s0: Updating address: 2a00:23c4:6cba:1000:325a:3aff:fe07:c383/64 (valid for 9y 11month 3w 6d 22h 30min)
May 22 20:04:39 Archlinux systemd-networkd[279]: DHCPv6 CLIENT: Recv REPLY
May 22 20:05:24 Archlinux systemd-networkd[279]: NDISC: Received Router Advertisement: flags OTHER preference medium lifetime 300 sec
May 22 20:05:24 Archlinux systemd-networkd[279]: NDISC: Invoking callback for 'r'.
May 22 20:05:24 Archlinux systemd-networkd[279]: DHCPv6 CLIENT: Started in Information request mode
May 22 20:05:24 Archlinux systemd-networkd[279]: enp3s0: Acquiring DHCPv6 lease on NDisc request
May 22 20:05:24 Archlinux systemd-networkd[279]: DHCPv6 CLIENT: Sent INFORMATION-REQUEST
May 22 20:05:24 Archlinux systemd-networkd[279]: DHCPv6 CLIENT: Next retransmission in 977ms
May 22 20:05:24 Archlinux systemd-networkd[279]: enp3s0: Updating address: fdaa:bbcc:ddee:0:325a:3aff:fe07:c383/64 (valid forever)
May 22 20:05:24 Archlinux systemd-networkd[279]: enp3s0: Updating address: 2a00:23c4:6cba:1000:325a:3aff:fe07:c383/64 (valid for 9y 11month 3w 6d 22h 30min)
May 22 20:05:24 Archlinux systemd-networkd[279]: DHCPv6 CLIENT: Recv REPLY
May 22 20:05:43 Archlinux kernel: perf: interrupt took too long (4074 > 4021), lowering kernel.perf_event_max_sample_rate to 48900
May 22 20:06:09 Archlinux systemd-networkd[279]: NDISC: Received Router Advertisement: flags OTHER preference medium lifetime 300 sec
May 22 20:06:09 Archlinux systemd-networkd[279]: NDISC: Invoking callback for 'r'.
May 22 20:06:09 Archlinux systemd-networkd[279]: DHCPv6 CLIENT: Started in Information request mode
May 22 20:06:09 Archlinux systemd-networkd[279]: enp3s0: Acquiring DHCPv6 lease on NDisc request
May 22 20:06:09 Archlinux systemd-networkd[279]: DHCPv6 CLIENT: Sent INFORMATION-REQUEST
May 22 20:06:09 Archlinux systemd-networkd[279]: DHCPv6 CLIENT: Next retransmission in 915ms
May 22 20:06:09 Archlinux systemd-networkd[279]: enp3s0: Updating address: fdaa:bbcc:ddee:0:325a:3aff:fe07:c383/64 (valid forever)
May 22 20:06:09 Archlinux systemd-networkd[279]: enp3s0: Updating address: 2a00:23c4:6cba:1000:325a:3aff:fe07:c383/64 (valid for 9y 11month 3w 6d 22h 30min)
May 22 20:06:09 Archlinux systemd-networkd[279]: DHCPv6 CLIENT: Recv REPLY
May 22 20:06:13 Archlinux nmbd[392]: [2018/05/22 20:06:13.807320,  0] ../source3/nmbd/nmbd_namequery.c:109(query_name_response)
May 22 20:06:13 Archlinux nmbd[392]:   query_name_response: Multiple (2) responses received for a query on subnet 192.168.1.95 for name MYGROUP<1d>.
May 22 20:06:13 Archlinux nmbd[392]:   This response was from IP 192.168.1.99, reporting an IP address of 192.168.1.99.
May 22 20:06:16 Archlinux dbus-daemon[666]: dbus-daemon[666]: [session uid=1000 pid=666] Activating via systemd: service name='org.gnome.Terminal' unit='gnome-terminal-server.>
May 22 20:06:16 Archlinux systemd[659]: Starting GNOME Terminal Server...
May 22 20:06:16 Archlinux dbus-daemon[666]: dbus-daemon[666]: [session uid=1000 pid=666] Successfully activated service 'org.gnome.Terminal'
May 22 20:06:16 Archlinux systemd[659]: Started GNOME Terminal Server.
May 22 20:06:16 Archlinux gnome-shell[718]: Object Clutter.Clone (0x5596851263d0), has been already finalized. Impossible to get any property from it.
May 22 20:06:16 Archlinux org.gnome.Shell.desktop[718]: == Stack trace for context 0x5596819d0060 ==
May 22 20:06:16 Archlinux org.gnome.Shell.desktop[718]: #0 0x7ffca83cb2f0 b   resource:///org/gnome/shell/ui/tweener.js:73 (0x7fa44c2c7cd0 @ 9)
May 22 20:06:16 Archlinux org.gnome.Shell.desktop[718]: #1 0x7ffca83cb390 b   resource:///org/gnome/shell/ui/tweener.js:105 (0x7fa44c2c7f78 @ 36)
May 22 20:06:16 Archlinux org.gnome.Shell.desktop[718]: #2 0x7ffca83cb430 b   resource:///org/gnome/shell/ui/tweener.js:92 (0x7fa44c2c7de0 @ 52)
May 22 20:06:16 Archlinux org.gnome.Shell.desktop[718]: #3 0x7ffca83cc350 b   resource:///org/gnome/gjs/modules/tweener/tweener.js:208 (0x7fa44c2d2918 @ 54)
May 22 20:06:16 Archlinux org.gnome.Shell.desktop[718]: #4 0x7ffca83cc4a0 b   resource:///org/gnome/gjs/modules/tweener/tweener.js:337 (0x7fa44c2d29a0 @ 1626)
May 22 20:06:16 Archlinux org.gnome.Shell.desktop[718]: #5 0x7ffca83cc550 b   resource:///org/gnome/gjs/modules/tweener/tweener.js:350 (0x7fa44c2d2a28 @ 100)
May 22 20:06:16 Archlinux org.gnome.Shell.desktop[718]: #6 0x7ffca83cc5e0 b   resource:///org/gnome/gjs/modules/tweener/tweener.js:365 (0x7fa44c2d2ab0 @ 10)
May 22 20:06:16 Archlinux org.gnome.Shell.desktop[718]: #7 0x7ffca83cc660 I   resource:///org/gnome/gjs/modules/signals.js:128 (0x7fa44c2cff78 @ 386)
May 22 20:06:16 Archlinux org.gnome.Shell.desktop[718]: #8 0x7ffca83cc710 b   resource:///org/gnome/shell/ui/tweener.js:207 (0x7fa44c2cf5e8 @ 159)
May 22 20:06:16 Archlinux org.gnome.Shell.desktop[718]: #9 0x7ffca83cc780 I   resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7fa44c2b5de0 @ 71)
May 22 20:06:16 Archlinux org.gnome.Shell.desktop[718]: #10 0x7ffca83cc780 I   resource:///org/gnome/shell/ui/tweener.js:182 (0x7fa44c2cf560 @ 15)
May 22 20:06:16 Archlinux org.gnome.Shell.desktop[718]: == Stack trace for context 0x5596819d0060 ==
May 22 20:06:16 Archlinux org.gnome.Shell.desktop[718]: #0 0x7ffca83cb2f0 b   resource:///org/gnome/shell/ui/tweener.js:80 (0x7fa44c2c7cd0 @ 82)
May 22 20:06:16 Archlinux org.gnome.Shell.desktop[718]: #1 0x7ffca83cb390 b   resource:///org/gnome/shell/ui/tweener.js:105 (0x7fa44c2c7f78 @ 36)
May 22 20:06:16 Archlinux org.gnome.Shell.desktop[718]: #2 0x7ffca83cb430 b   resource:///org/gnome/shell/ui/tweener.js:92 (0x7fa44c2c7de0 @ 52)
May 22 20:06:16 Archlinux org.gnome.Shell.desktop[718]: #3 0x7ffca83cc350 b   resource:///org/gnome/gjs/modules/tweener/tweener.js:208 (0x7fa44c2d2918 @ 54)
May 22 20:06:16 Archlinux org.gnome.Shell.desktop[718]: #4 0x7ffca83cc4a0 b   resource:///org/gnome/gjs/modules/tweener/tweener.js:337 (0x7fa44c2d29a0 @ 1626)
May 22 20:06:16 Archlinux org.gnome.Shell.desktop[718]: #5 0x7ffca83cc550 b   resource:///org/gnome/gjs/modules/tweener/tweener.js:350 (0x7fa44c2d2a28 @ 100)
May 22 20:06:16 Archlinux org.gnome.Shell.desktop[718]: #6 0x7ffca83cc5e0 b   resource:///org/gnome/gjs/modules/tweener/tweener.js:365 (0x7fa44c2d2ab0 @ 10)
May 22 20:06:16 Archlinux org.gnome.Shell.desktop[718]: #7 0x7ffca83cc660 I   resource:///org/gnome/gjs/modules/signals.js:128 (0x7fa44c2cff78 @ 386)
May 22 20:06:16 Archlinux org.gnome.Shell.desktop[718]: #8 0x7ffca83cc710 b   resource:///org/gnome/shell/ui/tweener.js:207 (0x7fa44c2cf5e8 @ 159)
May 22 20:06:16 Archlinux gnome-shell[718]: Object Clutter.Clone (0x5596851263d0), has been already finalized. Impossible to set any property to it.
May 22 20:06:16 Archlinux org.gnome.Shell.desktop[718]: #9 0x7ffca83cc780 I   resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7fa44c2b5de0 @ 71)
May 22 20:06:16 Archlinux org.gnome.Shell.desktop[718]: #10 0x7ffca83cc780 I   resource:///org/gnome/shell/ui/tweener.js:182 (0x7fa44c2cf560 @ 15)

Offline

#12 2018-05-22 19:28:17

seth
Member
Registered: 2012-09-03
Posts: 51,046

Re: Ethernet connection dropping - how to assess?

There's a hell lot of IPv6 dhcp negotiations, try https://wiki.archlinux.org/index.php/IP … networkd_2

Offline

#13 2018-05-24 06:30:26

sweetthdevil
Member
Registered: 2009-10-20
Posts: 415

Re: Ethernet connection dropping - how to assess?

Right, Only used my computer twice for a very short time both time - but the journal doesn't show any IPV6 DHCP negotiations and no dropout.

Thank you so much!

Offline

Board footer

Powered by FluxBB