@johnpoz:

Prob be cheaper and easier if you really want 1 box to do a case modification and take the guts of these, or put them in a new little case and attach to the top of your box if you can not put them in side..  The antennas detach so you could prob mount the antennas to your case and if there is any room inside the case put these inside and have a ethernet connection.. You would have to work out the details if you want it all in the same box.  But this prob be easier and faster and better speeds than what your dicking with ;)

Unfortunately it wasn't my decision to wrestle with these wireless cards :\ Fortunately, I set up one of the boxed with the guts of a particular OEM's AP unit and got the approval to go ahead with this setup. Now it's off to figure out heat dissipation and case modeling.

@Per:

Would be interesting to hear what you have tried.

Man, attempting to get a solid setup had been up uphill battle going nowhere. Originally, we had an atheros card that only occasionally gave the ath beacon error. The speed was terrible, and we also found out about the limitation of 10.3. We started up some demo units, and got all different cards to test out (Atheros, Apple, Intel, Realtek). Eventually, I began just building new kernels with either the 2.3 or 2.4 drivers. The apple card, surprisingly, worked the best on the 2.3 box and a little bit on the 2.4 boxes. After working with the 2.4 atheros driver for a while it became pretty clear that it just didn't like pfSense at all. So, after getting down into the different drivers, we rolled back to just 2.3 stable. Lo and behold, the cards had started working worse. The beacon error was joined by the "Ath_tx_default_comp". We quickly found that the disconnects were linked to the amount of traffic on the particular wireless network.

In short, the instability of wireless in 2.3 is still present in 2.4 and, because of the efforts being made to get 2.4 released, any errors in 2.3 will probably be there indefinitely. If you want to get one working, you'll most likely have to get your hands dirty with the drivers and the pfsense kernel itself.

I removed all the copies of your post that were cross-posted to other language forums. Please do not do that.

If English is not your first language and you want to post in English and in that forum, that would be acceptable.

@johnpoz:

If you're pointing your wifi clients to pfsense for dns, are you running dns on that interface?

Do an ifconfig /all on your w7 machine and post the results.

Do a traceroute to 8.8.8.8 and post the results.

IMO you'd be better connecting an access-point to your LAN port rather than using a WiFi NIC, 802.11ac isn't supported by FreeBSD.

Using pfsense as just AP seems wasteful at best.. For starters wifi is not a strong point of pfsense anyway.  2nd you could pick up any cheap 20$ wifi router and use it as just an AP.  More than likely that would be smaller, cheaper and use less power then some pfsense box with a wifi card in it.  And more then likely provide better wifi coverage to boot.

After re reading my post i realised it could cause a "huh?" haha, ill try your suggestions tonight, it could very well be the duplex

Hi,
I have the same model and no wifi with pfsense 2.3.2-RELEASE-p1.
Did you solve this problem?

@Derelict:

Everything you are talking about above is IPv4, yet that rule is IPv6-only. That is not going to work.

no. i just put the image with the first thing that i clicked.i have the same with IPv4.Now without the bridge , the wifi disconnects from the phone when i try to browse.i have the wifi put in access point.

@jsaad:

They even recommend an AP in every room!

Yeah, that's usually done with IP-TV settop boxes (mostly from Amino IIRC).
Some of them have an AP built in, are PoE powered and require a single cat cable for everything. Except for creating another VLAN in the switch you have zero installation costs.
The APs are nothing fancy and low power but good for a laptop, a tablet and one smartphone in that room.

"long range wireless is not allowed for import"

Ok.. Build it, pfsense would not be the correct tool..  Grab a cheap wifi router, put dd-wrt or openwrt on it.  Connect some cantenna's
http://www.turnpoint.net/wireless/cantennahowto.html

Put real AP in the area you need wifi coverage.  Or again buy some cheap wifi routers and use them in AP..

That is why that walkthrough recommends the sysctls for the bridge/members the way it does. So that doesn't happen.

The IP configuration and DHCP server should be on the bridge. Not one of the members.

"I don't know what I did"

Completely agree there.  You not knowing what you did is not a bug that is for sure ;)

"What other info can I provide to help troubleshoot this?"

How about some basics, like what version of pfsense for starters?  Is it hardware or VM?  Is wifi some AP or some card in pfsense - if so what card? do you have it as bridge or its own segment?  Are you using say captive portal..

And big one - what exactly is not working??  Wifi clients see no ssid being broadcast?  You can associate but no IP from dhcp?  etc. etc..

Do you really need someone to point out what kind of info would be relevant?

They are listed at the top of the first post ath0: <atheros 9287="">& ath1: <atheros 9280="">A little more information:  Using the TetherMe app on the iPhone.  Very little information available about the app.  Best I can tell it uses WPA2 (CCMP), no configurable settings.  The Wireless page under Status shows the iPhone SSID but the CAPS settings do not show WPA.  I know it uses WPA because my computers and iPad require it to connect.  Is it possible that pfSense (ath0 driver) does not try to connect because it does not see WPA as an option?  Of course, it does not connect if I de-select WPA.

It sounds like the TetherMe app uses AdHoc mode.  When I put the WiFi interface in AdHoc mode, pfSense crashes and reboots continually.  I believe I read somewhere that pfSense can't use WPA in AdHoc mode, why? Doesn't make much sense.</atheros></atheros>

I think Sierra makes a solid unit.
https://www.sierrawireless.com/products-and-solutions/routers-gateways/es450/

That is pretty awesome. I never heard of AT!GOBIIMPREF?

I used to switch using carriers firmwares found on the Sierra Source website.

The options were removed. They rarely did what they were supposed to do, and cards have been smarter about doing the right thing on their own.

Don't think it will work.

https://www.freebsd.org/releases/10.3R/hardware.html#wlan

[i386, amd64] Intel PRO/Wireless 2100 MiniPCI network adapter (ipw(4) driver)

[i386, amd64] Intel PRO/Wireless 2200BG/2915ABG MiniPCI and 2225BG PCI network adapters (iwi(4) driver)

[i386, amd64] Intel Wireless WiFi Link 4965AGN IEEE 802.11n PCI network adapters (iwn(4) driver)