Wireless will not stay running

My wireless keeps shutting down and is not producing logs to see what the issue is.
Kind of new to using wireless in Ipfire what information is needed to trouble shoot this issue.

WiFi Status

Interface blue0
ifindex 7
wdev 0x1
addr 00:25:d3:40:21:f2
type AP
wiphy 0
txpower 30.00 dBm
multicast TXQ:
qsz-byt qsz-pkt flows drops marks overlmt hashcol tx-bytes tx-packets
0 0 0 0 0 0 0 0 0

Hey there,

best thing to start, would be if you take a screenshot of your “WlanAP”-Page (hide your PW of course and your SSID if you want).

Greetings

Alex

One thing I notice is I don’t see the “Wireless Client tab”
Here is the screenshot

This is the Driver assigned to the wireless.
BLUE : “usb: IMC Networks 802.11 n/g/b Wireless LAN USB ▒ ││ Mini-Card”

An old g/n card will never support WPA3. Try WPA2 only.

1 Like

Change to WPA2
No change still starting/stopping

Note:
From the " Wireless Access Point Configuration" only starts when I hit the save button.
It will start from the " Status information" it start from the “hostapd” but stops again

A lot of fixes were applied to the wlan.cgi code for what will be Core Update 190 to fix the sort of things that it sounds like you are experiencing.

Those fixes were also backported to Core Update 189 but it seems like for some reason they did not get properly implemented. I have looked at the backported changes and they seem to have been applied to Core Update 189 the same as they were to Core Update 190 but other users have had similar issues as you are describing.

I have a system running with Core Update 190 (Unstable) and that is running without any problems so the fixes in Core Update 190 seem to have fixed the issues but for some reason they have not worked properly with Core Update 189.

It might be worth reading through the following thread as some potential workarounds are described that might enable you to get a working system until Core Update 190 is released.

https://community.ipfire.org/t/core-189-update-hostapd-doesnt-start/13080

1 Like

You run into a bug of the cgi. (It always falls back to Automatic Channel Selection at first start)
Press Save and then choose a valid channel (1-11) from the list and press save again

ACS is only useable with Atheros based cards.

2 Likes

It is running now and not shutting down but new issue it is not pulling and IP when the device trying to connect and the client is not showing in the “client’s MAC address to the blue access page”. Being as this happen I disable MAC address filtering and allow all clients which I hate doing but it did connect has slow internet access.

That sounds like a problem with DHCP… did you activate DHCP on the BLUE interface?

Greetings

You have to add them.
Find them on the DHCP page.

1 Like

I did as it is currently set it pulls an IP with disable MAC address filtering.

Maybe I should switch to a Atheros based cards being as this one seems to be having setup issue and slow speeds. Any recommendation on a PCIe Atheros based cards that you guys use?

In my production setup i use an external AP because internal modules only support 2.4 or 5 Ghz and i need both.

ACS should work on all Atheros ATH9K and ATH10K cards. Not sure if old ATH5K cards also work.

2 Likes

Using access points instead of wireless adapters/cards is going to be the best way to use the blue network primarily because the wireless hardware is not dependent on the ipfire computer’s resources.

2 Likes