OPNsense Forum

Archive => 18.7 Legacy Series => Topic started by: atmurphy on November 05, 2018, 05:11:02 am

Title: No Wifi (APU2. WLE200NX)
Post by: atmurphy on November 05, 2018, 05:11:02 am

Hello OPNSense,

I've got a PCEngines APU2 with a WLE200NX wifi card (Atheros AR9280).  I've switched from pfSense to OPNSense, and while I like some of the changes, I can't get the card to run as an AP.  This worked perfectly under pfSense.  Here's what I've tried so far:

- 2.4 n and 5 na (not simultaneously)
- WME on
- WPA2, AES, Open Shared, Passphrase
- most other settings auto or default
- regulatory domain FCC/Canada/Indoor
- no IP set on this interface, interface is bridged, other members of the bridge work perfectly

With pfSense, the same setup with the same hardware worked.  What happens now:

- OPNSense accepts all the parameters, saves, applies
- SSID is broadcast
- clients attempt to connect, but never succeed
- no client error messages so far (not sure why not)

If anyone knows what's up, that'd be great.  Failing that, a pointer to the correct log file(s) will let me run the setup a few times and post the results.

Title: Re: No Wifi (APU2. WLE200NX)
Post by: miczyg on February 25, 2019, 01:59:13 pm

Hi atmurphy,

Could You tell me what firmware version do You use?

Which mPCIe slot do You use for the card?

Title: Re: No Wifi (APU2. WLE200NX)
Post by: atmurphy on February 26, 2019, 10:28:30 pm

Good timing.  Was not working under 18.7, until I wiped and reinstalled, then it did work (never figured out what the problem was).  However, I have since updated to 19.1 and it's failing again.  This time however, I get an error message:

Code: [Select]

kernel: ath0: stuck beacon; resetting (bmiss count 4)
I'm not sure how to enumerate the PCIe slots, but viewed from the front it's the far-right slot.

Title: Re: No Wifi (APU2. WLE200NX)
Post by: newsense on February 27, 2019, 03:10:50 am

I think he was inquiring about physical slots on the board...

Title: Re: No Wifi (APU2. WLE200NX)
Post by: miczyg on March 04, 2019, 12:09:43 pm

The slots should have labels near the connectors. If the slot is mPCIe1, it is correct then. We had no issues with those modems under Debian and pfsense. I wonder if this is related: https://github.com/pcengines/coreboot/issues/206

There is also a WLAN DISABLE signal on pin20 of the connector which may be acting as a RF kill switch. Currently, its setting is set to OUTPUT HIGH in BIOS which may cause issues. The pin should be driven 1.8V, but currently is driven at 3.3V. We are still investigating possible impacts.