A bad romance: unable to wireless ping outside the LAN

Help and Support
1

Dear Volumio friends,
I’ve been lurking the forum ad using Volumio since Nov 2022, with great satisfaction.

My setup is:

  • Board: Raspberry Pi 2 Model B Rev 1.1, Version: a01041, Firmware: Jan 20 2022 13:58:22
  • Router: Tp-Link TL-MR6400 (ILIAD 4G connection)
  • Wireless adapter: probably a MT7601U chipset (hardware ID: USB\VID_148F&PID_7601)
  • DAC: InnoMaker Raspberry HAT PCM5122 (Allo Boss equivalent)
  • Audio source: USB external 512Gb SSD

Everything was fine, I could mount the USB drive and copy FLAC from/to PC, enjoy the music…
…until deciding to use my Synology NAS running DSM6 as the audio source, connected to a 100Mbit Eth port of the router.
No luck following the NFS official guide (and the countless problem-solving multi-thread I’ve read).

A little troubleshooting with SSH made me realize that I have problems when I’m wireless connected the the Pi but not when wired:

Wireless facts:

  • I can see and use Volumio via web interface and SSH
  • I cannot ping ouside the LAN
  • I cannot ping the gateway (192.168.1.1)
  • I can ping (some) of the clients connected to the wireless LAN
  • of course I do have errors (“Cannot call home” “can’t connect to the ntp servers” “can’t connect to web radios”)
  • I can see the MAC address of the wireless card in the wireless statistics of the router (sending and receiving packets)
  • I cannot see the Volumio/Pi in the connected wireless clients of the router (very strange, since IT IS connected!)

Wired facts:

  • I can ping everything every address inside and outside the LAN
  • of course I can “call home”, update, see the plugins section etc…

Already made a factory reset (no solution) and already flashed the SD (no solution).

After two days of trouble(shooting) I’m STUCK.

Any idea?
I suspect a bad romance between the router and wireless adapter…but how to investigate further?

2

Please validate (router) if you’re WL running on the same subnet as your wired connection.
If this is different like below, these errors will occure.
Wired: 192.168.1.x and WL: 192.168.2.xx.
They should run on the same subnet.

3

Yup! they are…I’ve tried to rule out all the obvious, of course.

But anything is obvious until it is…so, thanks for the suggestion!

Following ifconfig when SSH’ed to wlan0:

eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.1.101 netmask 255.255.255.0 broadcast 192.168.1.255
ether (…omissis…) txqueuelen 1000 (Ethernet)
RX packets 2312 bytes 434678 (424.4 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 4116 bytes 3311013 (3.1 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

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 1497 bytes 201446 (196.7 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 1497 bytes 201446 (196.7 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.1.155 netmask 255.255.255.0 broadcast 192.168.1.255
ether (…omissis…) txqueuelen 1000 (Ethernet)
RX packets 243 bytes 48602 (47.4 KiB)
RX errors 0 dropped 2 overruns 0 frame 0
TX packets 83 bytes 17372 (16.9 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

Same command SSH connected to eth0:

eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.1.101 netmask 255.255.255.0 broadcast 192.168.1.255
ether (…omissis…) txqueuelen 1000 (Ethernet)
RX packets 2615 bytes 466021 (455.0 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 4369 bytes 3356745 (3.2 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

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 1713 bytes 232994 (227.5 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 1713 bytes 232994 (227.5 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.1.155 netmask 255.255.255.0 broadcast 192.168.1.255
ether (…omissis…) txqueuelen 1000 (Ethernet)
RX packets 342 bytes 65896 (64.3 KiB)
RX errors 0 dropped 2 overruns 0 frame 0
TX packets 111 bytes 23242 (22.6 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

4

I AM A DUMBASS!

Wireless adapter MAC address was blacklisted in the router!

Don’t ask me why I forgot I’ve done this…
never light up one AND listen to Grateful Dead '69 Fillmore concerts AND fiddle with router’s settings thinking it’s your neighbour’s mobile phone draining all the data…NEVER!