Как мне его переключить на старую версию, networks? Мне кажется все проблемы оттуда.
Поотключал все интерфейсы (включая gsm), остался только eth0.
Дропнул Network Manager, и?
На контроллере WB7 7.3.3E, wb-2304, stable, s/n AVZOK2XH стало так же как и на * WB7 7.3.3E, wb-2304, stable, s/n AP5CRMOL
Какие идеи?
SSH
Welcome to Wiren Board 7.3.3 (s/n AVZOK2XH), release wb-2304 (as stable)
Linux wirenboard-AVZOK2XH 5.10.35-wb133+wb101 #1 SMP Mon May 29 08:56:14 UTC 2023 armv7l GNU/Linux
System load: 6.08 1.62 0.55 Up time: 0 min
Memory usage: 19% of 997M Usage of /: 66% of 976M /mnt/data: 30% of 4.9G
8 package updates are available; type ‘apt update && apt upgrade’ to update them.
Last login: Fri Jul 21 06:35:08 2023 from 192.168.5.239
root@wirenboard-AVZOK2XH:~# ping 192.168.2.144
PING 192.168.2.144 (192.168.2.144) 56(84) bytes of data.
From 192.168.2.131 icmp_seq=1 Destination Host Unreachable
From 192.168.2.131 icmp_seq=2 Destination Host Unreachable
From 192.168.2.131 icmp_seq=3 Destination Host Unreachable
From 192.168.2.131 icmp_seq=4 Destination Host Unreachable
From 192.168.2.131 icmp_seq=5 Destination Host Unreachable
^C
— 192.168.2.144 ping statistics —
6 packets transmitted, 0 received, +5 errors, 100% packet loss, time 5166ms
pipe 4
root@wirenboard-AVZOK2XH:~# traceroute 192.168.2.144
traceroute to 192.168.2.144 (192.168.2.144), 30 hops max, 60 byte packets
1 wirenboard-AVZOK2XH.local (192.168.2.131) 2522.729 ms !H 2522.567 ms !H 2522.495 ms !H
root@wirenboard-AVZOK2XH:~#
ifconfig
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.2.131 netmask 255.255.240.0 broadcast 192.168.15.255
ether 00:85:01:01:57:cf txqueuelen 1000 (Ethernet)
RX packets 298782 bytes 21840850 (20.8 MiB)
RX errors 0 dropped 1838 overruns 0 frame 0
TX packets 501522 bytes 57628721 (54.9 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 65 base 0x5000
eth1: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether 00:85:01:01:f4:35 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 64
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
loop txqueuelen 1000 (Local Loopback)
RX packets 1167 bytes 65517 (63.9 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 1167 bytes 65517 (63.9 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.42.1 netmask 255.255.255.0 broadcast 192.168.42.255
ether c4:3c:b0:5f:d1:24 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 15 bytes 900 (900.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
Спустя 5 минут…
Пока писал предыдущий текст ситуация поменялась
Ping Trace
root@wirenboard-AVZOK2XH:~# ping 192.168.2.144
PING 192.168.2.144 (192.168.2.144) 56(84) bytes of data.
\64 bytes from 192.168.2.144: icmp_seq=1 ttl=255 time=8.81 ms
64 bytes from 192.168.2.144: icmp_seq=2 ttl=255 time=2.37 ms
64 bytes from 192.168.2.144: icmp_seq=3 ttl=255 time=3.72 ms
^C
— 192.168.2.144 ping statistics —
3 packets transmitted, 3 received, 0% packet loss, time 2008ms
rtt min/avg/max/mdev = 2.368/4.966/8.813/2.775 ms
root@wirenboard-AVZOK2XH:~# traceroute 192.168.2.144
traceroute to 192.168.2.144 (192.168.2.144), 30 hops max, 60 byte packets
1 * * *
2 * * *
3 * * *
4 * * *
5 * * *
6 *^C