WiFi suddenly gone (ath0 beacon stuck)

JonathanLee

@stephenw10 I will have to check something else to see if its the card.

stephenw10

Hmm, are you running that in the 2100? I don't believe it will work there. The wle200nx is the only wifi card I have seen work on that platform.

JonathanLee

@stephenw10 Yes I have the 2100 with arm architecture. Is that the problem ?? So other appliances support the other set of cards? Should the 2100 also support the other cards listed?

stephenw10

Yes that card should work in anything x86. arm (aarch64 here) platforms require far for specific code so if you want the PCIe bus to work that has to be setup. There is a conflict in that setup in 2100 which means some (most) PCIe cards are not seen on the bus. Since we never sold it with a wifi card, and the only card we have sold in recent memory was the wle200nx there is not huge incentive to correct it. It's non-trivial!

Steve

JonathanLee

@stephenw10 Thanks for the info. I will have to put the old card back, I got that other card hoping to use three antenna or test the diversity settings to see if they would turn on for the 2100. Dang :(

JonathanLee

@stephenw10 Is there anyway to enable that card or no?

stephenw10

Do you see the card in the output of pciconf -lv ?

If not does it show in the PCI output in uboot? For example:

Marvell>> pci
Scanning PCI devices on bus 0
BusDevFun  VendorId   DeviceId   Device Class       Sub-Class
_____________________________________________________________
00.00.00   0x168c     0x0030     Network controller      0x80

JonathanLee

@stephenw10

@stephenw10 said in WiFi suddenly gone (ath0 beacon stuck):

pciconf -lv

pciconf -lv showed none. I already put the compex back

stephenw10

Ok. I don't believe it will work in the 2100 but if you did want to dig further the next step would be to check that uboot sees it.

provels

@JonathanLee said in WiFi suddenly gone (ath0 beacon stuck):

@provels Apple iMac Mac A1311 A1312 Wireless WiFi Card 2011 AR5BXB112 607-7211-A 661-5946
arrived in the mail however the system does not detect it as usable.

It does however work with the Compex WLE200NX Wireless A/B/G/N Network Mini PCIe Adapter (A4343) just fine.

Just saw this. The Apple AR5BXB112 I have works at N speed in my x86 FW. Of course, I have pulled it out and put in my Compex 600, which now doesn't work either, sad face.

none1@pci0:5:0:0:       class=0x028000 rev=0x00 hdr=0x00 vendor=0x168c device=0x003c subvendor=0x0000 subdevice=0x0000
    vendor     = 'Qualcomm Atheros'
    device     = 'QCA986x/988x 802.11ac Wireless Network Adapter'
    class      = network

I tried the binaries compiled but failed due to my own ignorance. Any hints from @stephenw10 if available about what and where to put them would be appreciated. Trying to learn to compile but my compiling is a pile...
Anyway, here's a pic of my Apple card.

stephenw10

@provels said in WiFi suddenly gone (ath0 beacon stuck):

I tried the binaries compiled but failed due to my own ignorance.

The athp driver? Been a long time since I tried that. There is a thread for it with some details. I have no idea what the current state is though.

provels

@stephenw10
athp-driver
Yes, read through that thread several times. You referred to putting the files in the "correct locations"? Are those /boot/kernel for the if_athp.ko and /boot/modules for the rest? Do I need to do anything else to get it recognized? Can I even use the old binaries with 14?

KLD if_athp.ko: depends on kernel - not available or version mismatch
linker_load_file: /boot/kernel/if_athp.ko - unsupported file type

I don't care if it runs any better than N at this point. Appreciate any assist, but don't let it interfere with your day job!

stephenw10

Yeah I never got it running. It's more difficult now that pfSense is built on a FreeBSD snapshot effectively.
Try to load it in FreeBSD first. Though I'd have to dig into it again to know what might work currently.

JonathanLee

Hello I wanted to share that I have found a possible solution to the stuck beacon on my SG-2100

Screenshot 2023-10-25 at 4.19.48 PM.png

Make sure all of the following are checked under SystemAdvancedNetworking

Hardware Checksum Offloading
Hardware TCP Segmentation Offloading
Hardware Large Receive Offloading

They must be disabled for Snort's inline mode to function. When I was testing trying to activate Snort's inline mode I left them like this and the stuck beacon error stopped all day. It is completely gone now.