28th jan snap wifi shows insecure where as in settings its wpa enabled

eri-- · Jan 30, 2013, 7:44 AM

I reverted the change later snapshots should be ok.
It works for me locally here not sure why it breaks yours!

xbipin · Jan 30, 2013, 7:47 AM

reverting the change make wifi work securely and the wireless systemlog also starts populating which didnt earlier but the first line always says
hostapd: ath0_wlan0: IEEE 802.11 Fetching hardware channel/rate support not supported.

has something changed related to its drivers etc?

eri-- · Jan 30, 2013, 7:58 AM

Not really.
Its just the clones never support that only the wireless device itself can do that iirc.

Probably that has been like that for a long time and you didn't notice?

xbipin · Jan 30, 2013, 8:07 AM

i always use to see all systemlog after ever upgrade in order to find bugs to report and after upgrading to these recent snaps only it started giving those messages when i was playing with those MTU values, i even compared saved config files from 2010, 2011 and 2012 and i dont find anything different in them that might cause this

xbipin · Jan 30, 2013, 8:22 AM

there is another issue, might not be related to this or pfsense at all but just need to confirm. everytime i reboot my alix with pfsense my windows 7 PC network connection shows yellow mark and says no internet connection whereas im able to surf just fine, now if i unplug its lan cable and replug then it says internet connected. i searched a lot of windows issues and mostly all pointed to some antivirus causing this which isnt true in my case so could it be that pfsense is not offering proper dhcp lease or dns address which mayb causing this as there were recent patches to dhcp

phil.davis · Jan 30, 2013, 8:30 AM

I discovered that the problem was just the order of parameters on the hostapd command line.
The pull request at https://github.com/bsdperimeter/pfsense/pull/361 fixes it.
My WiFi comes up with proper authentication happening after this. /var/run has a pid file:
-rw-r–r-- 1 root wheel 6 Jan 30 14:09 /var/run/hostapd_ath0_wlan0.pid
And there is a hostapd process:
22633 ?? Ss 0:00.02 /usr/sbin/hostapd -B -P /var/run/hostapd_ath0_wlan0.pid /var/etc/hostapd_ath0_wlan0.conf
All seems well with the world:)

xbipin · Jan 30, 2013, 9:14 AM

@phil.davis:

I discovered that the problem was just the order of parameters on the hostapd command line.
The pull request at https://github.com/bsdperimeter/pfsense/pull/361 fixes it.
My WiFi comes up with proper authentication happening after this. /var/run has a pid file:
-rw-r–r-- 1 root wheel 6 Jan 30 14:09 /var/run/hostapd_ath0_wlan0.pid
And there is a hostapd process:
22633 ?? Ss 0:00.02 /usr/sbin/hostapd -B -P /var/run/hostapd_ath0_wlan0.pid /var/etc/hostapd_ath0_wlan0.conf
All seems well with the world:)

yes tried ur patch and that works fine but i still get the
hostapd: ath0_wlan0: IEEE 802.11 Fetching hardware channel/rate support not supported.

eri-- · Jan 30, 2013, 11:03 AM

Those are setup by pfSense automagically xbipin
Do not worry no issues arise from that.
The backend will make sure and synchronize all your instances of wireless on the same device to your configured setting.s

xbipin · Jan 30, 2013, 11:22 AM

ok fine, one more thing, is the below an error

php: : The command '/usr/bin/killall dhcpd' returned exit code '1', the output was 'No matching processes were found'

eri-- · Jan 30, 2013, 11:53 AM

Nah but fixed to not get the warning anymore.

phil.davis · Jan 30, 2013, 4:38 PM

Now on 2.1-BETA1 (i386) built on Wed Jan 30 04:20:39 EST 2013 - which has the fixed up code to start hostapd with a PID file. WiFi and all is working fine and secured. But I still have this in syslog amongst the startup:

Jan 30 16:10:08 	php: : The command '/sbin/ifconfig 'ath0_wlan0' country 'NP' 'indoor'' returned exit code '1', the output was 'ifconfig: SIOCS80211: Invalid argument'

I have no idea if this is a "normal" message that has been there for months, or something recent - I guess it pays to look through boot logs when eberything is working, as well as when there are evident problems :) When I have a little more time I will track down how/why it is generated.
Can anyone say if this is a "normal" feature of the boot process or something special to my Alix2D13 with ath0 WiFi card?

joe_cowboy · Jan 30, 2013, 6:10 PM

My interface does not come up still do to the fact the pid file is missing from /var/run/. It is generating the /tmp/run0_wlan0_setup.sh file just fine.

Even with the code fix of it still does not allow interface to come up with missing pid:
fwrite($fd_set, "{$hostapd} -B -P {$g['varrun_path']}/hostapd_{$if}.pid {$g['varetc_path']}/hostapd_{$if}.conf\n");

Where in hostapd functions is it generating the pid file to go in /var/run/ because it is still not generating that file for me.

I was looking through the interfaces.inc file and I don't see where it's creating that file or does the function check isvalidpid check and create the pid file passed to it if it does not exist?

bardelot · Jan 30, 2013, 6:32 PM

The PID file does not have to be generated manually, it is created by the hostapd process where the location of the file is specified using the -P parameter.

joe_cowboy · Jan 30, 2013, 7:01 PM

@bardelot:

The PID file does not have to be generated manually, it is created by the hostapd process where the location of the file is specified using the -P parameter.

Thanks you are correct and thanks… I manually ran the lines in the setup file and it generated the pid file. Now when I disable and enable the Wireless interface it comes right back up. It should have done this without me having to run it manually but at least it's working agian. Should have tried that first. Many Thanks for all the good work.

xbipin · Jan 30, 2013, 8:05 PM

@phil.davis:

Now on 2.1-BETA1 (i386) built on Wed Jan 30 04:20:39 EST 2013 - which has the fixed up code to start hostapd with a PID file. WiFi and all is working fine and secured. But I still have this in syslog amongst the startup:
Jan 30 16:10:08 	php: : The command '/sbin/ifconfig 'ath0_wlan0' country 'NP' 'indoor'' returned exit code '1', the output was 'ifconfig: SIOCS80211: Invalid argument'
I have no idea if this is a "normal" message that has been there for months, or something recent - I guess it pays to look through boot logs when eberything is working, as well as when there are evident problems :) When I have a little more time I will track down how/why it is generated.
Can anyone say if this is a "normal" feature of the boot process or something special to my Alix2D13 with ath0 WiFi card?

Its not normal as I run almost the same hardware and I don't get that. There is something still wrong with WiFi that's y I get a different message on 2 hardwares

xbipin · Feb 1, 2013, 6:21 PM

with the latest snap, wifi works fine but suppose u go to interfaces and wifi and hit save and apply then wifi comes back up and wifi to lan works fine but wifi devices loose internet access

MrRocco · Feb 1, 2013, 9:02 PM

You are bridging Wifi-LAN and not routing Wifi-LAN correct? I'm wondering if I should skip updating from an older snap until this is sorted…

joe_cowboy · Feb 2, 2013, 4:26 PM

My wifi seems to work fine now. But I did have an issue similar about bridge only working with internet on Mulit-Wan Group but the bridge of LAN1, LAN2 LAN3, LAN4, WLAN1 not seeing the each other on the bridge. I finially figured out and changed under System -> Advanced -> System Tunables -> Tunable Name -> net.link.bridge.pfil_bridge back to 0 and all went to working correctly again. I also checked the box of System -> Advanced -> Firewall and NAT -> Disable reply-to but not real sure if this had any effect on things.

xbipin · Feb 2, 2013, 4:40 PM

i tried the newest snap just today again and it seems to work fine now, saving under wifi brings back wifi back to normal without issues