I use both lan and wlan connections and if the 2 are connected all is well.
if i deconet the lan i cannot connect through ssh or vnc with wifi.
but the connection seems normal internet is working fine.
and as soon as I reconnect the lan I can connect through the wifi
Any idea ?
When you remove the LAN cable, could you check the ifconfig and dmesg as attachment here?
What kind of wifi device are you using? The on-board wifi card?
No LAN:
docker0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 172.17.0.1 netmask 255.255.0.0 broadcast 172.17.255.255
ether 02:42:c8:be:85:9b txqueuelen 0 (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
eth0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether 48:b0:2d:3d:77:87 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 37
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10
loop txqueuelen 1 (Local Loopback)
RX packets 353 bytes 28345 (28.3 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 353 bytes 28345 (28.3 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
rndis0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether 22:f3:63:02:ee:dd 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
usb0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether 22:f3:63:02:ee:df 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
wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.2.21 netmask 255.255.255.0 broadcast 192.168.2.255
inet6 fe80::cf05:b8cb:bd67:f15e prefixlen 64 scopeid 0x20
ether 20:4e:f6:c5:f2:83 txqueuelen 1000 (Ethernet)
RX packets 5160 bytes 7380050 (7.3 MB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 1258 bytes 148531 (148.5 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
And with LAN:
docker0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 172.17.0.1 netmask 255.255.0.0 broadcast 172.17.255.255
ether 02:42:c8:be:85:9b txqueuelen 0 (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
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.2.20 netmask 255.255.255.0 broadcast 192.168.2.255
inet6 fe80::5065:ae9:f746:7471 prefixlen 64 scopeid 0x20
ether 48:b0:2d:3d:77:87 txqueuelen 1000 (Ethernet)
RX packets 102 bytes 14636 (14.6 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 51 bytes 8324 (8.3 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 37
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10
loop txqueuelen 1 (Local Loopback)
RX packets 413 bytes 33259 (33.2 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 413 bytes 33259 (33.2 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
rndis0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether 22:f3:63:02:ee:dd 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
usb0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether 22:f3:63:02:ee:df 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
wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.2.21 netmask 255.255.255.0 broadcast 192.168.2.255
inet6 fe80::cf05:b8cb:bd67:f15e prefixlen 64 scopeid 0x20
ether 20:4e:f6:c5:f2:83 txqueuelen 1000 (Ethernet)
RX packets 7335 bytes 10098546 (10.0 MB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 1705 bytes 192558 (192.5 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
I can connect directly after i connect LAN but through WLAN !
I start to make a fresh reinstall on a m.2 disk and i let’s you know if the problem persist.
Thansk
Please also share the dmesg.
No LAN:
Dmseg output to big to post here is a google drive link :dmseg.txt - Google Drive
Few items here.
-
Your “with LAN” case is also plugging the cable after system boots up for a while, right? I see it takes 4 mins until the eth0 interface ready.
-
I am not sure why there is always kernel panic from rtl8822ce driver. Not sure if this is related. Both LAN and NO LAN case has this log.
-
Where is the IP of your wlan0 coming from? Why does it look like in the same domain as eth0?
I boot without LAN and unable to connect remotly.
after i plug LAN and all work fine
Please reply the my question of the IP setting in (3).
Booth are connected on the same router ASUS RT-AC88U
Will the wlan0 back to life with no LAN case if you reset the interface with command ifconfig wlan0 down/up?
Yes i have try tu switch up/down wlan0 from termial and from desktop no change
Are you still able to ping the AP from the jetson?
Yes and internet work fine.
I make a fresh install to switch on m.2 the problem persist.
But i have try to switch from 2.4 to 5g and all work on 5g
Only 2.4G channel has this problem?
At first view after reinstall yes , i will make more test when i come back at home later
I can confirm the problem is only on 2.4g and 5g work fine.
Will you see such issue if you use other device as wifi AP? For example, enable the hotspot on your phone, let NX wifi connect to it with and without LAN cable.
2.4 connect fine on my phone hotspot, the problem comme from my router.
Tanks a lot for your time )