Thank God another one on the same boat with non working Ath0 pci card on AP mode

tester100

hiya

sharp replies heheh, well i am runnign 2.2 from update it says i am now on the current update version..

so heres the update outcome.. reset all to factory default..

disabled wifi..

configured all up again. then enabled otp2 wifi AP via webinterface and i set it up to new ipv4 dhcp lan address…

then rebooted. and all up working normal now.. no more beacon stuck error messages.. believe it or not using same exact config i posted earlier.. now as for my WAN i cannot say the same still not comming up on DHCP something wrong. even do its enabled DHCP and modem is on BRIDGE mode completelly it should update the IP automatically.

but its not i have to enter on the wan interface, disable it, then save, then enabled it then save.. and it updates the IP from ISP

as for the working set i will post the pictures here to make this AP atheros wifi working still no encryption used at all, so will start playing with the encryption mode now

also created a rule on the Firewall, Rules, for the WIFI wlan, to allow all tcp access to internet on the wlan

![wifi rule.jpg](/public/imported_attachments/1/wifi rule.jpg)
![wifi rule.jpg_thumb](/public/imported_attachments/1/wifi rule.jpg_thumb)

cmb

The stuck beacon driver issue is something that appears, from our testing thus far, to be resolved with the driver in 2.2.1. That's what you should be on right now for any new wireless deployments with 11n. They're development snapshots and not yet an official stable release, but everything wireless has tested out much better on 2.2.1 than anything prior, and things overall are stable in snapshots at the moment.

pLu

@cmb:

The stuck beacon driver issue is something that appears, from our testing thus far, to be resolved with the driver in 2.2.1.

I'm sorry to report that I've had a stuck beacon three times with an AR9280 since I upgraded 14 hours ago. That being said, even 2.2.0 worked fine for me as a home AP.

cmb

@pLu:

I'm sorry to report that I've had a stuck beacon three times with an AR9280 since I upgraded 14 hours ago.

The messages still come up on occasion, that much is normal at times. The situations where you end up with a flood of stuck beacon logs and a non-functional AP shouldn't be an issue.

@pLu:

That being said, even 2.2.0 worked fine for me as a home AP.

what kind of config are you running with it? There are still some outstanding issues that I'm working on tracking down, knowing what works for you would help.

pLu

@cmb:

@pLu:

That being said, even 2.2.0 worked fine for me as a home AP.

what kind of config are you running with it? There are still some outstanding issues that I'm working on tracking down, knowing what works for you would help.


 <interfaces><opt2><if>ath0</if>
		 <wireless><mode>hostap</mode>
			<standard>11na</standard>
			<protmode>off</protmode>
			<ssid>Indeed</ssid>
			<channel>64</channel>
			 <authmode><txpower>99</txpower>
			 <distance><regdomain>etsi</regdomain>
			<regcountry>SE</regcountry>
			<reglocation>indoor</reglocation>
			 <wpa><macaddr_acl><auth_algs>1</auth_algs>
				<wpa_mode>2</wpa_mode>
				<wpa_key_mgmt>WPA-PSK</wpa_key_mgmt>
				<wpa_pairwise>CCMP</wpa_pairwise>
				<wpa_group_rekey>60</wpa_group_rekey>
				<wpa_gmk_rekey>3600</wpa_gmk_rekey>
				<passphrase>yes</passphrase>
				 <ext_wpa_sw><enable></enable></ext_wpa_sw></macaddr_acl></wpa> 
			 <auth_server_addr><auth_server_port><auth_server_shared_secret><auth_server_addr2><auth_server_port2><auth_server_shared_secret2><wme><enable></enable></wme> 
			 <pureg><enable></enable></pureg> 
			 <apbridge><enable></enable></apbridge> 
			 <puren><enable></enable></puren></auth_server_shared_secret2></auth_server_port2></auth_server_addr2></auth_server_shared_secret></auth_server_port></auth_server_addr></distance></authmode></wireless> 

		 <spoofmac><enable></enable></spoofmac></opt2></interfaces>

I noticed with 2.2.0 that standard 11na and channel auto gave me an 11ng 2.4GHz channel. Haven't tried it again with 2.2.1.

Edit: Hardware checksum offload doesn't work with Atheros AR9280 (at least not on 2.2.0). Packets will get dropped.

cmb

@pLu:

I noticed with 2.2.0 that standard 11na and channel auto gave me an 11ng 2.4GHz channel. Haven't tried it again with 2.2.1.

There is brokenness in auto channel selection, which is why 2.2.1 makes you pick a specific channel for host AP (and enforces picking a specific channel proper for the standard chosen). Otherwise it just picks whatever it wants, and seems to get stuck on 11b at times if it chooses anything. We have a couple FreeBSD bug reports open on that, though 2.2.1 is capable of working around those issues (and actually forces you to do so with input validation).

@pLu:

Edit: Hardware checksum offload doesn't work with Atheros AR9280 (at least not on 2.2.0). Packets will get dropped.

Hm, I've kept that enabled on all my 2.2.1 testing and haven't seen it be a problem and I have mostly 9280s. So that might be specific to the ath(4) in stock FreeBSD 10.1.

pLu

@cmb:

@pLu:

Edit: Hardware checksum offload doesn't work with Atheros AR9280 (at least not on 2.2.0). Packets will get dropped.

Hm, I've kept that enabled on all my 2.2.1 testing and haven't seen it be a problem and I have mostly 9280s. So that might be specific to the ath(4) in stock FreeBSD 10.1.

As soon as I uncheck "Disable hardware checksum offload" and click Save on 2.2.1, too, I lose 'connection' because the returning packets have a zero checksum (I didn't reboot). I have an APU with the Compex WLE200NX.

From tcpdump -v -i wlan0 on my Linux laptop:


08:07:51.650544 IP (tos 0x0, ttl 64, id 13111, offset 0, flags [none], proto UDP (17), length 160, bad cksum 0 (->c53d)!)
    192.168.0.1.domain > 192.168.0.135.6921: 53023 NXDomain 0/1/0 (132)

tester100

hi guys

back again ok so did some tests few days ago with the development version .. but my new firewall is x64 anyways so i updated it again today to 2.2.1

wifi now works i have set up a wlan address different from my lan address and allowed it to surf the web so far so good..

my only issue now is..

none of the wifi devices can get ip via DHCP i need to put fix static ip setup on my wifi on my notebook, also my iphone detects the ssid network name but cannot connect using DHCP settings i need to configure connection manualy with fix ip to work …

am i missing something??

I am using Static IPV4

Ipv4 address 192.168.xxx.1 /24

or do i need to enter the console config menu of pfsense and configure IP interfaces via console menu? cause on the LAN Ip port it asked me if i wanted to enabled DHCP for this LAN

but on the wifi i have configured via the WEBIF...

Derelict

Services > DHCP Server

Make a DHCP server for your interface.

tester100

@Derelict:

Services > DHCP Server

Make a DHCP server for your interface.

Hi

yes i eventually after typing my first message had the Console window of the server open on the screen also and configured the IP address via console menu and enabled DHCP there. now its all working also..

with dhcp