This is kind of unusual. Raspberry Pi 3 B+ with Aarch64 image. My SSH session keeps dying. I've noticed it happens about every half hour. When I log into the physical machine I see the IP address has changed.
My DHCP server's default lease time is 60 minutes (max lease 120 minutes). 60 minutes is aggressive and it is intended to scavenge old leases quickly because of of device activity in my lab. Many devices are started up, a test is run, and then shutdown immediately. If I allow them to hang around for days or weeks then I sometimes run out of addresses in the subnet.
I'm guessing the RPI is trying to renew at 30 minutes. Looking at DMESG I don't see a renew request; only a message about wlan0:
[ 33.641372] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 33.658658] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 33.701586] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 33.776179] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 33.839349] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 34.384878] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 35.183999] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 380.555159] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 696.561166] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 1012.565499] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 1328.575936] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 1644.604460] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready <disconnect around here>
The RPI is the only device exhibiting the behavior.
Does anyone know how to sidestep the problem?
Thanks in advance.
On Fri, 1 Mar 2019, Jeffrey Walton wrote:
This is kind of unusual. Raspberry Pi 3 B+ with Aarch64 image. My SSH session keeps dying. I've noticed it happens about every half hour. When I log into the physical machine I see the IP address has changed.
This sounds like the IPv6 privacy option.
https://blog.linitx.com/control-privacy-addressing-ipv6-linux/
On Fri, Mar 1, 2019 at 8:31 PM Stuart D. Gathman stuart@gathman.org wrote:
On Fri, 1 Mar 2019, Jeffrey Walton wrote:
This is kind of unusual. Raspberry Pi 3 B+ with Aarch64 image. My SSH session keeps dying. I've noticed it happens about every half hour. When I log into the physical machine I see the IP address has changed.
This sounds like the IPv6 privacy option.
https://blog.linitx.com/control-privacy-addressing-ipv6-linux/
You are probably right.
I shutdown the radio with a command similar to 'dcicm radio off' and I stopped getting kicked of the wired LAN. I can't find the command in my Bash history, which is kind of odd.
What does wireless IPv6 have to do with wired IPv4 LAN addresses?
Jeff
On Fri, Mar 1, 2019 at 10:31 PM Jeffrey Walton noloader@gmail.com wrote:
On Fri, Mar 1, 2019 at 8:31 PM Stuart D. Gathman stuart@gathman.org wrote:
On Fri, 1 Mar 2019, Jeffrey Walton wrote:
This is kind of unusual. Raspberry Pi 3 B+ with Aarch64 image. My SSH session keeps dying. I've noticed it happens about every half hour. When I log into the physical machine I see the IP address has changed.
This sounds like the IPv6 privacy option.
https://blog.linitx.com/control-privacy-addressing-ipv6-linux/
You are probably right.
I shutdown the radio with a command similar to 'dcicm radio off' and I stopped getting kicked of the wired LAN. I can't find the command in my Bash history, which is kind of odd.
Here was the command:
nmcli radio wifi off
CRTL+R 'off' did not work in Bash (nothing found), but I found it cat'ing .bash_history. Weird.
This device just keeps getting weirder. I miss the old days when things just worked...
Jeff
This is kind of unusual. Raspberry Pi 3 B+ with Aarch64 image. My SSH session keeps dying. I've noticed it happens about every half hour. When I log into the physical machine I see the IP address has changed.
Weird, I have around a dozen RPi 2/3 class devices on both wired and wireless network with a dual stack IPv4/IPv6 and I don't see that at all (and never have).
Nor have I had other reports.
This sounds like the IPv6 privacy option.
https://blog.linitx.com/control-privacy-addressing-ipv6-linux/
You are probably right.
I shutdown the radio with a command similar to 'dcicm radio off' and I stopped getting kicked of the wired LAN. I can't find the command in my Bash history, which is kind of odd.
Here was the command:
nmcli radio wifi off
That will turn the wifi off but if you're not connected to a wireless network it won't have any effect.
To disable IPv6 privacy on the wired interface you can do:
nmcli connection modify eth0 ipv6.ip6-privacy 0
There's a couple of blog posts with some good details: https://major.io/2016/04/17/enable-ipv6-privacy-networkmanager/ https://blogs.gnome.org/lkundrak/2015/12/03/networkmanager-and-privacy-in-th...
This device just keeps getting weirder. I miss the old days when things just worked...
Is it just the unstable addressing that's weird, or something else?
On Sat, Mar 2, 2019 at 7:35 AM Peter Robinson pbrobinson@gmail.com wrote:
This is kind of unusual. Raspberry Pi 3 B+ with Aarch64 image. My SSH session keeps dying. I've noticed it happens about every half hour. When I log into the physical machine I see the IP address has changed.
Weird, I have around a dozen RPi 2/3 class devices on both wired and wireless network with a dual stack IPv4/IPv6 and I don't see that at all (and never have).
Nor have I had other reports.
This sounds like the IPv6 privacy option.
https://blog.linitx.com/control-privacy-addressing-ipv6-linux/
You are probably right.
I shutdown the radio with a command similar to 'dcicm radio off' and I stopped getting kicked of the wired LAN. I can't find the command in my Bash history, which is kind of odd.
Here was the command:
nmcli radio wifi offThat will turn the wifi off but if you're not connected to a wireless network it won't have any effect.
To disable IPv6 privacy on the wired interface you can do:
nmcli connection modify eth0 ipv6.ip6-privacy 0
There's a couple of blog posts with some good details: https://major.io/2016/04/17/enable-ipv6-privacy-networkmanager/ https://blogs.gnome.org/lkundrak/2015/12/03/networkmanager-and-privacy-in-th...
This problem showed back up this morning. This morning the kernel was updated to 4.20.13-200 and the machine was rebooted.
Sigh...
This device just keeps getting weirder. I miss the old days when things just worked...
Is it just the unstable addressing that's weird, or something else?
This IP address problem, Bash's reverse search not working, missing utilities, ...
Jeff
On Sat, Mar 2, 2019 at 5:33 PM Jeffrey Walton noloader@gmail.com wrote:
On Sat, Mar 2, 2019 at 7:35 AM Peter Robinson pbrobinson@gmail.com wrote:
This is kind of unusual. Raspberry Pi 3 B+ with Aarch64 image. My SSH session keeps dying. I've noticed it happens about every half hour. When I log into the physical machine I see the IP address has changed.
Weird, I have around a dozen RPi 2/3 class devices on both wired and wireless network with a dual stack IPv4/IPv6 and I don't see that at all (and never have).
Nor have I had other reports.
This sounds like the IPv6 privacy option.
https://blog.linitx.com/control-privacy-addressing-ipv6-linux/
You are probably right.
I shutdown the radio with a command similar to 'dcicm radio off' and I stopped getting kicked of the wired LAN. I can't find the command in my Bash history, which is kind of odd.
Here was the command:
nmcli radio wifi offThat will turn the wifi off but if you're not connected to a wireless network it won't have any effect.
To disable IPv6 privacy on the wired interface you can do:
nmcli connection modify eth0 ipv6.ip6-privacy 0
There's a couple of blog posts with some good details: https://major.io/2016/04/17/enable-ipv6-privacy-networkmanager/ https://blogs.gnome.org/lkundrak/2015/12/03/networkmanager-and-privacy-in-th...
This problem showed back up this morning. This morning the kernel was updated to 4.20.13-200 and the machine was rebooted.
This device just keeps getting weirder. I miss the old days when things just worked...
Is it just the unstable addressing that's weird, or something else?
This IP address problem, Bash's reverse search not working, missing utilities, ...
For the reverse search I suggest filing a bug with bash [1], all the utilities you're missing should be installable with dnf (you don't actually mention what you think is missing) and the IP address is a hard one, network issues are very dependent on the local network to debug.
-
Jeffrey Walton -
Peter Robinson -
Stuart D. Gathman