https://redmine.pfsense.org/https://redmine.pfsense.org/favicon.ico?16780521162015-12-08T14:59:14ZpfSense bugtrackerpfSense - Feature #5616: Incorrect Wireless Channelhttps://redmine.pfsense.org/issues/5616?journal_id=232842015-12-08T14:59:14ZJim LohiserJimL@n2net.net
<ul></ul><p>Looks like the wiki parser got the better of me. The ifconfig info show correctly below.</p>
<pre>
ifconfig -v ath0_wlan0
ssid SSID1 channel 10 (2457 MHz 11g ht/40) bssid 04:f0:21:17:41:af
ifconfig -v ath0_wlan1
ssid SSID2 channel 6 (2437 MHz 11g ht/40+) bssid 06:f0:21:17:41:af
</pre> pfSense - Feature #5616: Incorrect Wireless Channelhttps://redmine.pfsense.org/issues/5616?journal_id=232852015-12-08T15:55:49ZJim LohiserJimL@n2net.net
<ul></ul><p>Please ignore my comments regarding wlan1 specifically being an issue. After restoring the configuration on the same device, ath0_wlan0 now has the random channel.</p>
<pre>
ifconfig -v ath0_wlan0
ssid SSID1 channel 6 (2437 MHz 11g ht/40+) bssid 04:f0:21:17:41:af
ifconfig -v ath0_wlan1
ssid SSID2 channel 10 (2457 MHz 11g ht/40-) bssid 06:f0:21:17:41:af
</pre> pfSense - Feature #5616: Incorrect Wireless Channelhttps://redmine.pfsense.org/issues/5616?journal_id=244332016-01-26T03:49:13ZJim Thompsonjim@netgate.com
<ul><li><strong>Tracker</strong> changed from <i>Bug</i> to <i>Feature</i></li><li><strong>Assignee</strong> set to <i>Jim Thompson</i></li></ul><p>downgraded to feature.</p>
<p>people attempting multiple 802.11 radios in the same device need a reality check.</p> pfSense - Feature #5616: Incorrect Wireless Channelhttps://redmine.pfsense.org/issues/5616?journal_id=244612016-01-26T08:08:52ZJim LohiserJimL@n2net.net
<ul></ul><p>Just to clarify, these units have a single Atheros 9280 card installed. It is, however, a dual-band radio, which I assume is the source of your comment. I am only using the 2.4Ghz band.</p> pfSense - Feature #5616: Incorrect Wireless Channelhttps://redmine.pfsense.org/issues/5616?journal_id=257172016-03-15T11:51:32ZJim LohiserJimL@n2net.net
<ul></ul><p>I am still having this problem on a number of pfSense devices.</p>
<p>ssid SSID1 channel 10 (2457 MHz 11g ht/40-) bssid 04:f0:21:14:c7:54<br />ssid SSID2 channel 1 (2412 MHz 11g ht/40+) bssid 06:f0:21:14:c7:54</p>
<p>The problem only seems to occur after pfSense is restarted. One of the SSIDs will be on a random channel. The other will be on the correct channel as per the configuration. If I log into the web interface, go to one of the wireless interfaces, select Save and then Apply (without making any changes), the problem is resolved (i.e. both SSIDs are then on the same channel). The problem is resolved until the next reboot when it may or may not occur. It seems as though something is not being sent properly on bootup or is possibly timing out. Perhaps the channel assignments need to be moved to later (near the end) of the boot process. I am on 2.2.6.</p>
<p>The problem cropped up after I setup multiple SSIDs. It would seem that is somehow related.</p>
<p>Jim, you made the comment about multiple 802.11 radios. Could you please clarify your comment as related to this issue? Are indicating that you believe this radio is not appropriate for use with pfSense because it has 2.4Ghz and 5Ghz radios? Do you believe that this random channel issue would not exist if there was only one radio in the card?</p>
<p>Thank you.</p> pfSense - Feature #5616: Incorrect Wireless Channelhttps://redmine.pfsense.org/issues/5616?journal_id=290312016-10-09T15:33:57ZAnonymous
<ul></ul><p>I ran into the same issue when using an ath interface and virtual interfaces in hostap mode (VAPs). I have a similar setup as yours. It seem that the 1st VAP interface is brought up successfully with the right parameters. What happens is that the 2nd interface is brought up and that results in the 1st interface losing its configured parameters and getting random parameters instead. I suspect this is a bug in the ath driver.</p>
<p>What I ended up doing to work around this issue is to split off the part that configures the interface from the part that brings up the interface, splitting a single operation (ifconfig athX_wlanY up <parameters>) into two consecutive operations (ifconfig athX_wlanY <parameters>; ifconfig athX_wlanY up). This seems to have fixed the issue for me. I've created pull request <a class="external" href="https://github.com/pfsense/pfsense/pull/3180">https://github.com/pfsense/pfsense/pull/3180</a> and hope to have it included into one of the following releases.</p>
I have found several other issues related to using virtual interfaces and have created 2 other pull requests:
<ul>
<li><a class="external" href="https://github.com/pfsense/pfsense/pull/3179">https://github.com/pfsense/pfsense/pull/3179</a></li>
<li><a class="external" href="https://github.com/pfsense/pfsense/pull/3169">https://github.com/pfsense/pfsense/pull/3169</a></li>
</ul>
<p>Using these 2 PRs in addition to the PR that I mentioned earlier provides a predictable and usable setup when using Virtual APs. You can apply the patches on a live box with the "System_Patches" package.</p>