It was, I think, resolved in the wrong direction however: The wireless clone's mode should be selected once upon creation and be readonly on the interface configuration page. I don't know what was the motivation for this change, but what I can see is that until then the mode could be selected on two pages (this one and interfaces.php), what is clearly an inconsistency, inherited from pfSense. This is strange since upon creating a new clone, where could a previous value for 'mode' come from? The page seems to be broken since September 2015 (commit ). Looking at its source code, there is indeed no input element for mode, instead there is a hidden field: It appears to me that what is broken in OPNsense is only the interfaces_wireless_edit.php page. As it turned out, this was all what was necessary to get the Access Point functionality of OPNsense working: After that, the interfaces could be configured in Access Point mode on their respective pages without any problems. I then substituted the config.xml's wireless section with the one from pfSense using an editor. (This is in heavy contrast to the fact that on the Wireless Devices page a column "Mode" is displayed.) Alas, creating a wireless clone in Access Point mode there was not possible: No selection element to choose the mode is shown on the page. They were also not set on the interface (after applying the saved changes - no SSID, no IP address and regulatory domain settings unchanged):Īrmed with the knowledge I gathered with pfSense I then did a fresh install of OPNsense 21.1, following the rule to not do anything wireless related until I get to the Web GUI's Wireless Devices page. However, although the Web GUI allowed me to configure it in Access Point mode, the result was the same as before: After the page refresh the access point settings were no longer displayed.
So I destroyed and created it in HOSTAP mode using the above commmands (without assigning an address or SSID), then used the opnsense shell to assign it to OPT2. Scanvalid 60 protmode CTS ampdulimit 64k ampdudensity 8 shortgi -ldpcĪfter several failed configuration attempts I hoped that the problem was that the ath0_wlan0 interface is created in infrastructure mode on boot.
Media: IEEE 802.11 Wireless Ethernet autoselect mode 11ng Scanvalid 60 protmode CTS wme burst dtimperiod 1 -dfs Regdomain FCC country US ecm authmode OPEN privacy OFF txpower 30
0 kommentar(er)
