SSID invisible from other devices; RTL8811AU,supported ?

[opnthib]

Hello.

first of all, thank you team. I've been using OPNSense for some time now and even the major updates have gone smoothly. So thank you for that.

My current problem is with the wifi.
I've just updated to 24.7, but I don't think it's related.
I've always had problems connecting my other machines to my OPNSense wireless networks,  I'm a bit confused.

So

Code Select Expand


root@onpsense:~ # usbconfig list
ugen0.1: <Intel XHCI root HUB> at usbus0, cfg=0 md=HOST spd=SUPER (5.0Gbps) pwr=SAVE (0mA)
ugen0.2: <RTL8811AU 802.11a/b/g/n/ac WLAN Adapter Realtek Semiconductor Corp.> at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON (500mA)
root@onpsense:~ # sysctl -n net.wlan.devices
rtwn0

ok, we have my usb wifi card.
And I have :

• Interfaces > Wireless -> rtwn0_wlan1
• Interfaces > Assignement -> rtwn0_wlan1 = Wifi, (identifier : opt8)
• Interfaces > [Wifi] ->
  
  • Enable: checked
  • Identifier opt8
  • Device  rtwn0_wlan1
  • IPv4 Configuration Type: static IPV4
  • IPv4 address: 192.168.60.1
  • Standard: it worked with 802.11ng, but it doesn't work. I tried again with 802.11g or 802.11a, same result KO
  • 802.11g OFDM Protection Mode: Protection mode off
  • Transmit power: default
  • channel: auto
  • Regulatory settings: ETSI; FR ETSI; Indoor
  • Mode: Access Point (Note: when I use Infrastructure, I see other  wirless ssid on Interfaces > Wireless -> Wifi status)
  • Minimum standard: Any
  • Enable Hide SSID: UNchecked
  • WPA: Enable
  • WPA Mode: WPA2
  • WPA Key Management Mode: Pre-Shared Key
  • Access Point Authentication: Shared Key Authentication
  • WPA Pairwise: AES
  • Key Rotation: 60
  • Master Key Regeneration: 3600

But my others devices, can't see my SSID.  :o

But:

Code Select Expand


root@onpsense:~ # dmesg | grep -A5 -B5 rtwn0
ig4iic3: <Intel Gemini Lake I2C Controller-7> mem 0xa171a000-0xa171afff,0xa1719000-0xa1719fff irq 34 at device 23.3 on pci0
ig4iic3: Using MSI
iicbus3: <Philips I2C bus (ACPI-hinted)> on ig4iic3
ichsmb0: <Intel Gemini Lake SMBus controller> port 0xf040-0xf05f mem 0xa1716000-0xa17160ff at device 31.1 on pci0
smbus0: <System Management Bus> on ichsmb0
rtwn0 on uhub0
rtwn0: <Realtek 802.11ac WLAN Adapter, class 0/0, rev 2.10/2.00, addr 1> on usbus0
rtwn0: MAC/BB RTL8821AU, RF 6052 1T1R
lo0: link state changed to UP
pflog0: permanently promiscuous mode enabled
re1: link state changed to UP
vlan0: changing name to 'vlan01'
vlan1: changing name to 'vlan02'
--
re0: link state changed to UP
re4: link state changed to UP
nd6_dad_timer: called with non-tentative address fe80:6::21e:6ff:fe45:487f(re5)
wg0: link state changed to UP
wlan0: Ethernet address: 20:0d:b0:46:68:02
wlan0: changing name to 'rtwn0_wlan1'
nd6_dad_timer: called with non-tentative address fe80:d::21e:6ff:fe45:5c5e(vlan03)
rtwn0: rtwn_tx_beacon_check: cannot push beacon into chip, error 60!
rtwn0: unable to push beacon into the chip, error 60
rtwn0: rtwn_newstate: could not move to RUN state


I don't understand, if I can see other networks ... then the driver is loaded and working, right?
I don't see RTL8811AU on https://www.freebsd.org/releases/14.1R/hardware/, but but it was the same for the previous version.

What did I do wrong?  :-\

[Patrick M. Hausen]

OPNsense is really not recommended as a WiFi access point. Get a dedicated one.

The software is flakey, but nobody is going to fix it in the near future. The FreeBSD WiFi team is already busy making FreeBSD work reliably as a WiFi client. No manpower and frequently lack of vendor documentation/cooperation for the AP side of things.

[opnthib]

No manpower and frequently lack of vendor documentation/cooperation for the AP side of things.

Yes, I see that, many opensource drivers are reverse engineering .

From what I understand the driver is ok for client access but not as point access.

If I don't find another solution, I'll actually use an dedicated access point.

[freakmaxi]

It looks okay to me. I believe you should change the "channel" from "auto" to something desirable. In my experience, my device couldn't automatically choose the proper channel and it led me to have a non-working AP and invisible SSID. After I set it manually, it started working.