How setup wifi 802.11N with PF2.2.1 ?
-
Do you suppose that only listening to answers you like will make the card work well? Pfsense really, for now, doesn't well support wireless cards in a way that equals the performance of an external AP. I doubt any OS does.
-
I disagree.
Most "commercial" APs have linux as a basis.
The cards/drivers which work well are those which have contributions by the manufacturer of the chipset of the cards. (qualcom atheros, broadcom, come to mind).
However using pfsense as an AP only makes sense in a home environment.
You don't want an AP in a 19" rack.I dont have any experience with the linked card, but it seems it is an USB device.
My recommendation for usb network devices is: dont use usb network devices.To be able to use n speeds, make sure wme (qos) is enabled.
-
@yon:
You need to select 802.11ng in the "Standard" dropdown.
If this option isn't there, then either your card or the driver for your card don't support 11n.this option isn't there, my card supported 802.11N. my card is ralink 3072 NIC
http://item.jd.com/1309402.html#product-detail
the card driver downlaod here:
http://pan.baidu.com/s/1sj5EMbbplease build it in PF.
Even if you get it to work, probably most you are probably going to get is very weak AP signal. Searching in google shows that it's been reported as an issue in linux.
You can have decent Wifi AP using pfSense but it presumes sticking to certain hardware. Atheros AR9280/AR9285/AR928X chipset based PCIe x1 cards for example work well @2,4Ghz out-of-the-box. After you patch their EEPROM for 5Ghz (by default locked) they should become usable for "a/n" as well. Cards and chipsets are capable, limits are hardcoded into EEPROM which for 92xx series is luckily not OTP EEPROM (One-Time-Programmable). You won't need programmator or soldering, it's doable by using software. Search for Atheros EEPROM Tool and iwleeprom
-
you have a USB nic that uses rt3072? and it actually works? See my post here: https://forum.pfsense.org/index.php?topic=90558.0
-
I'm well aware that linux is at the core at many if not most routers and wireless APs. I'm not suggesting that running wireless AP on Linux is a bad idea. I'm suggesting that while there is built in functionality in pfsense to handle wireless that in most situations where you need an AP, an external AP is probably going to be better on PFSENSE.
If you already have the hardware, like in this case, of course, use it. But if you don't already have the internal card, an external ubiquity AP or Cisco AP looks pretty good.
-
Yea funny thing is, the last Linksys Access Point i disassembled had a cardbus radio just like my laptop would use. Special Radio? I don't think so…What a joke of an answer. Try another excuse.
Seems people who can't seem to figure it out -think its broke- and then proceed to propagate these false statements.
-
@Phishfry:
Yea funny thing is, the last Linksys Access Point i disassembled had a cardbus radio just like my laptop would use.
That's a good news. Could disassemble and repurpose a bunch of Linksys boxes that serve as paperweight here due to the original firmware being utterly unusable garbage. (No, DD-WRT is not an option, the models are either unsupported or totally unstable.)
-
Linksys != Ubiquiti, Cisco, Ruckus, Aruba.
Regardless of whether your subject AP used the same cardbus card or not, the real issue is that driver support was transferred from pfSense to the AP. If it sucks, buy another AP.
Last year I put a Ruckus 7372 in a lunchroom. I see anywhere between 100 and 130 concurrent associations on this one AP. Every day. How many complaints have I heard since placing it? Zero. And I know it works because I eat there every day, too. It could handle more. And that's all with a 10Mbit/s shared limiter on the lunch room VLAN.
Place your linksys AP with an embedded cardbus card in the same situation and tell me there's no such thing as a "Special Radio."
-
OK I dont want to argue about that topic. I see "Use an Access Point" as a cookie cutter answer in the wireless section when many of us are not serving wireless to hundreds of users. We would simply like to use the wireless features that have been built in and have worked since 2005. Not use an access point.
Tonight I was also able to create a second guest network, just like i thought was possible, with just one physical module. Wireless clone worked exactly as advertised and dual SSID network up and running…One with WPA2 and one with CP... So more greatness for free. -
More power to you. You'd be happier with VLANs tagged to a solid access point. Even a DDWRT or Tomato. It's really not about the density or capacity. It's about what device is responsible for the wireless associations.
I, personally, find it discouraging to see cmb spending time on pfSense Wi-Fi. This is a solved problem. Screw the neanderthals that think pfSense should be an AP - bridges and all.
-
Well i posted Rules based approaches in that other post where you bash bridges.
I was hoping that would score some points with ya.. -
Anyone who knows anything about Wi-Fi knows that FreeBSD's support for cards is at least 5 years behind. Do what you gotta do. Me, I'll use an AP or 650.
-
Lets just agree to disagree. You have offered very good advice and i appreciate it. Your captive portal suggestion on the landing page was spot on for the Arecont neighborhood cam setup. In fact with the html embedded window approach I may be able to quad screen it with 4 camera views.
