Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Wifi connection showing not connected - even when it is #31

Open
Ultraviolet93 opened this issue Jan 25, 2024 · 10 comments
Open

Wifi connection showing not connected - even when it is #31

Ultraviolet93 opened this issue Jan 25, 2024 · 10 comments

Comments

@Ultraviolet93
Copy link

Ultraviolet93 commented Jan 25, 2024

I've successfully installed Spyguard on RaspOs Bookworm on Raspberry Pi 4.

All works fine but it shows as Wifi not connected at the bottom right of the capture screen.

However, it is connected, scans and creates reports correctly.

I've tried swapping round the on board WiFi with usb dongle for AP and Internet link, but it makes no difference in either configuration.

Everything looks correct in the new network manager for bookworm sudo nmtui

Anyone else seen this issue and found a solution ?

image

@icedan
Copy link

icedan commented Jan 25, 2024

Hardware? OS? nmcli installed? This bootom not connected means ethernet connection - look in setting, maybe you have selected loopback not eth0.

@Ultraviolet93
Copy link
Author

Thank you for the suggestions - I have nmcli installed which was installed prior to installing Spyguard.

Hardware

Raspberry Pi 4 Model B Rev 1.4

OS

PRETTY_NAME="Debian GNU/Linux 12 (bookworm)"
NAME="Debian GNU/Linux"
VERSION_ID="12"
VERSION="12 (bookworm)"
VERSION_CODENAME=bookworm
ID=debian
Linux 6.1.0-rpi7-rpi-v8 #1 SMP PREEMPT Debian 1:6.1.63-1+rpt1 (2023-11-24) aarch64 GNU/Linux

eth0 and lo network Settings

eth0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether e4:5f:01:63:77:07 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

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 1000 (Local Loopback)
RX packets 55405 bytes 5091882 (4.8 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 55405 bytes 5091882 (4.8 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

Not sure if anything jumps out in the above ? I have swapped over wlan0 and wlan1 but that doesn't seem to make any difference. The scan and reports work in either of these configurations although I understand the preferred arrangement is wlan1 for internet and wlan0 for AP which is how I've got it set up ?

@CSerpent
Copy link

Sorry if this is looping the same question/answer as above, but have you gone into raspi-config (opt 5 then AA from memory) and changed the network handler to nmcli? This one got me repeatedly.

@Ultraviolet93
Copy link
Author

Ultraviolet93 commented Jan 30, 2024

Thanks for the suggestions - I've looked through the raspi-config menu and there does not appear to be a menu option for network handler anymore.

The menu options in raspi-config seem to have changed since the Bookworm update. The network configuration is now handled by a new graphical tool nmtui but this does not appear to have an option to select the network manager either? nmcli is running and reports the following:

wlan0: connected to D-link-943f
"Broadcom BCM43438 combo and Bluetooth Low Energy"
wifi (brcmfmac), E4:5F:01:63:77:09, hw, mtu 1500
inet4 10.42.0.1/24
route4 10.42.0.0/24 metric 602
inet6 fe80::d18f:3c4a:579e:6eb8/64
route6 fe80::/64 metric 1024

wlan1: connected to Netgear6267
"Ralink RT5370"
wifi (rt2800usb), 1C:BF:DE:F4:02:E4, hw, mtu 1500
ip4 default, ip6 default
inet4 192.168.38.214/21
route4 192.168.32.0/21 metric 601
route4 default via 192.168.32.254 metric 601
inet6 fe80::1efa:3442:9751:4344/64
route6 fe80::/64 metric 1024
route6 default via fe80::22c:c8fe:fe68:a385 metric 601
inet6 fe80::1efa:3443:9851:4344/64
route6 fe80::/64 metric 1024
route6 default via fe80::22c:c8ef:fe68:a385 metric 601

lo: connected (externally) to lo
"lo"
loopback (unknown), 00:00:00:00:00:00, sw, mtu 65536
inet4 127.0.0.1/8
inet6 ::1/128

p2p-dev-wlan0: disconnected
"p2p-dev-wlan0"
wifi-p2p, hw

eth0: unavailable
"eth0"
ethernet (bcmgenet), E4:5F:01:62:77:07, hw, mtu 1500

DNS configuration:
servers: 208.67.220.220
interface: wlan1_

I've carried out some more testing and when set-up using wlan1 for Internet and wlan0 for AP I see this :

image

If I swap them round I see this :

image

where the wifi connection on the left indicates its dropped.

I can't get my head round whats going on but something is clearly not right.

Happy to try any suggestions as I've run out of ideas.

@CSerpent
Copy link

CSerpent commented Jan 30, 2024

Yeah the raspi-config is different in bookworm. Out of interest, do you have a USB WiFi stick you can plug in and see if you get the same issue?

Also, is the clone up to date with a full uninstall/reinstall? There's been several mods of late to deal with some issues. I know it sounds obvious, but just a thought!

@Ultraviolet93
Copy link
Author

Good News ! I've reinstalled Spyguard and it now appears to be working !
Thank you for the suggestion - I should have tried that first !

The only weird thing is if I use wlan0 as the access point and wlan1 for the internet connection it fails to create the access point.

If I reverse the adapters in the backend its works fine. Not sure why its behaving that way. But at least its working with Access point wlan1 and internet wlan0 .

Be nice to understand what causes that issue but at least its up and running.

Thank you

@CSerpent
Copy link

I would tail syslog when setting wlan0 as the AP, see if you get the nl80211 driver interface is not designed to be used with ap_scan=2 error appearing?

@Ultraviolet93
Copy link
Author

Ultraviolet93 commented Feb 1, 2024

Just checked the syslog , and yes I see nl80211 driver interface is not designed to be used with ap_scan=2 message.

I guess this is an issue with the particular usb wifi dongle I'm using ( RALINK 5370 802.11N) I've also tried an Asus N150 -USB N10 Nano (Realtek 8188)

The RALINK will allow devices to connect and run scans but only when AP is set to Ralink adapter and Internet to onboard Wi-Fi (atheros 8495)

The ASUS creates the AP but nothing will connect,

I'm guessing this is a driver issue? Anyway to fix it or will I need to get hold of specific usb wifi adapter ?

@Ultraviolet93
Copy link
Author

Thanks for confirming I'll try and source an adapter with RTL8852 chipset and hopefully that will resolve the issue.

@b068931cc450442b63f5b3d276ea4297
Copy link
Collaborator

I'll have a look at it in the next few days and then answer you here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants