Troubleshooting • Re: Which kernel to roll back to?

On Bullseye
eth1 192.168.3.10 is the Dongle connecting 192.168.3.1
eth2 192.168.2.10 is the Pluto connecting 192.168.2.1

pi@txtouch:~ $ ifconfig eth1
eth1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.3.10 netmask 255.255.255.0 broadcast 192.168.3.255
inet6 fe80::7c46:bb62:d7f4:c2a4 prefixlen 64 scopeid 0x20<link>
ether 00:e0:4c:88:44:bc txqueuelen 1000 (Ethernet)
RX packets 1306 bytes 1752668 (1.6 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 73 bytes 14895 (14.5 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

pi@txtouch:~ $ ifconfig eth2
eth2: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.2.10 netmask 255.255.255.0 broadcast 192.168.2.255
inet6 fe80::d175:e17b:591b:57e prefixlen 64 scopeid 0x20<link>
ether 00:e0:22:6f:28:9a txqueuelen 1000 (Ethernet)
RX packets 18 bytes 7998 (7.8 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 2562 bytes 3530318 (3.3 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

On Bookworm
eth1 192.168.2.10 is the Pluto connecting 192.168.2.1
eth2 should be the Dongle

pi@txtouch:~ $ ifconfig eth1
eth1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.2.10 netmask 255.255.255.0 broadcast 192.168.2.255
inet6 fe80:68fd:7b7f:61c7 prefixlen 64 scopeid 0x20<link>
ether 00:e0:22:6f:28:9a txqueuelen 1000 (Ethernet)
RX packets 15 bytes 2348 (2.2 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 57 bytes 10271 (10.0 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

pi@txtouch:~ $ ifconfig eth2
eth2: error fetching interface information: Device not found

Statistics: Posted by mbn — Mon Aug 12, 2024 2:29 pm

---