The login dialogue for pfSense user admin confuses scp. Use another pfSense user OR login to pfSense and "pull" the file to pfSense rather than "push" it OR use the Upload function in pfSense web GUI Diagnostics -> Command Prompt.

@AudiAddict: I found a setting to do it manualy (dev.ath.0.diversity) but not sure where to check the current setting(s) and where to change this? The settings dev.ath.0.diversity are for a different type of device (ath) than the one you are using (run).

@markuhde: I know this doesn't make as neat of installation for you, but honestly, the best solution is to use a separate AP. I am leaning toward this as well. I have had nothing but problems with wireless cards. USB wireless cards, i tried 3 or 4 makes/models and none were supported /detected. Even PCI cards are really flaky.. A friend told me its because most cards are not designed to work as an AP. With cheap access points available sometimes on craigslist, its a nice option to just go with the tried and true wired ap. As an aside, pfsense as a wireless AP use to work with an old nic card i had, but that card died. Was generic no name funny enough. I am using 1.2.3 though so perhaps usb nics are now supported and or work. right now my personal card has an annoying problem where every 15 minutes or so it starts into this "auth" "deauth" cycle and pretty much just doesnt connect till an interface disable /reenable.  annoying to say the least. So for 40$ you cant go wrong with an old cisco ap is what im beginning to think. as fun as screwing around with my wireless interfaces are….

This is more Cisco site question, but i can answer some In cisco you can use vlans and you can assign SSID/VLAN to have multiple wireless networks. In some very rare occassions you can assign multiple SSID's / VLAN just make sure, that Fastethernet0 is in trunk mode and vlan's are tagged except webgui(management) vlan, because AP's can't handle VLAN tagged management when using webgui. KR, soon to be CCNA-Wireless(i hope) EDIT: Some more help

Generally (or possibly always?) this setting does nothing at its default value of 99.  The system rejects values that are higher than a set value (determined by the driver) and 99 is way over that in the cases I've seen.

@edmund: Now I re-read the WLAN config page I see that … thanks.  However, reading the manual (P366, sec 18.3.1) appears to suggest that BSS must be turned off if the WLAN is bridged ... so I've had it turned off since setting up the WLAN and I've been scratching my head about this for a year or more now. That's referring to BSS and IBSS modes, you're using hostap mode.

You don't. The wireless interface is for using pfSense to create a wireless access point. Create a LAN-type interface, and connect your UniFi APs and UniFi management station to that interface through a switch. P.S. I don't mean this to be rude but rather simply advice - to be honest, I think you made a huge mistake choosing UniFi based on the level of knowledge shown in your post. Why did you choose UniFi? It's a managed AP system requiring a separate controller computer and substantial networking knowledge. If you just wanted ceiling-mount smoke detector APs, EnGenius makes some good ones that are just standalone AP's.

i have 2 nic's in my pfsense. 1 WAN 1 LAN the LAN has ap wds connected the second ap wds is 300 meters away. when connected to ap wds on the LAN (wireless) everything works. when i connect to ap wds 2 (300 meters away) it will not five me an ip address. both ap have static ip and they are connected with eachother someone any ideas how to fox this

Finaly i got it working but it was a hard peace of trail and error. 1. create a new interface -> Opt2 2. Setup the interface IP for Opt2 (interfaces ->Opt2) and change the name if you want 3. Setup the DHCP Server for Opt2 4. Create a "Source=Bridge subnet; rest=any" Firewall rule for Opt2 5. create a bridge: Interfaces -> Bridges, and select LAN and Wifi 6. Select the Bridge as "Network port" for Opt2; Interfaces-> asign 7. Deactivate the DHCP server of LAN and Wifi 8. Set the Type of LAN and Wifi to "None" Now your LAN and Wifi clients should get an IP from the DHCP server configured for Opt2 and these clients should be able to access the internet. But they are currently not able to access each other WLAN <-> LAN. So solve that i added two rules for the Firewall: 1. LAN: Source=Bridge subnet; rest = any 2. WLAB: Source= Bridge subnet; rest=any Instead of adding these two rules you can also change the value at : System -> Advanced -> System tuneables -> net.link.bridge.pfil_member->  "0" At that point my clients where able to ping each other and also wake up on lan from my tablet to a PC was working. If you have any hints what i can do better on my configuration feel free to let me know.

@chriv: Simple problem: pfSense 2.0.1 doesn't load the driver for my atheros wireless card in my Acer netbook. Wrong diagnosis. The driver is already built in the kernel and it is effectively reporting the I/O subsystem is not correctly setup for the card. #: dmesg | grep -i ath ath0: <atheros 2424="" 5424=""> irq 17 at device 0.0 on pci3 ath0: 0x10000 bytes of rid 0x10 res 3 failed (0, 0xffffffff). ath0: cannot map register space device_attach: ath0 attach returned 6</atheros> After a quick look through the FreeBSD source code I suspect this means something like: 1. There isn't enough kernel address space or page table entries to map the 0x10000 (64k) bytes of PCI memory address space on the ath device into kernel memory space; or 2. An upstream PCI bridge doesn't have enough memory address space to allow access to all its downstream devices AND this device; Is this card a mini PCI-Express card replacing the netbook's standard WiFi card? Is pfSense running in some kind of virtual environment? Was the card in the system at boot time? Have you tried a snapshot build of pfSense 2.1?

As best I can tell the "rum" chipset went "end of life" a couple of years ago. It has been superseded by the "run" chipset which wasn't supported until pfSense 2.0. You might be able to pick up a suitable used USB dongle on eBay though take care because many suppliers of WiFi add-on devices quietly change the chipset without changing the model number. I think you might be better off upgrading to pfSense 2.0.1 and then you should be able to use a Tenda W311U or TP-Link WN321G. The Tenda is supported by the the run driver, the TP-Link by the rum driver (if you manage to get an "old" one) or the run driver. If you use a "run" device pfSense will need a tweak to get the device firmware loaded at boot time.

Have you added the needed line to the "loader.conf.local" here a Ralink based USB Wireless adapter example runfw_load="yes" add the line according to Your USB wireless Chipset / Driver

That mailing list post might be specific to the Intel iwn(4) driver.  From what I can tell, txpower is set in increments of .5dBm and stored, internally, as an integer.  When I set it to 20.5 it works, but 20.6 gives an error: ifconfig: invalid tx power (must be .5 dBm units) So, to me, that means the value shown by txpower is definitely in dBm.  I'm still confused about txpowmax being 50.0 though.  Is it 2xdBm?  I also don't know why txpower can be set above 26dBm for my specific card. I subscribed to the freebsd-wireless mailing list and sent a message to it to see if someone there can give a better explanation.  With the exception of the GUI setting it doesn't look like pfSense actually touches any of the parts involved. Here are a few links I found to related info.

Thanks for your reply, I solved the problem, it was an configuration issue.

Not sure really, I just grabbed two that had the 88W…. chip and they were both OK, though I don't have any in production.

Hi there ! I have many 54GLxxx (Linksys/Cisco) with the latest DDWRT firmware. They are attatched to my Opt1 interface - my Public Wifi acces network, PfSense = 192.168.2.1 - AP1 192.168.2.2 AP2 192.168.2.3 etc etc I have also 54GLxxx (Linksys/Cisco) with the latest DDWRT firmware in my LAN - PfSense = 192.168.1.1 (which is default) , the AP being 192.168.1.15 The gateway setting in the AP is (of course) 192.168.1.1 - DHCP server in the AP is set to off. Needles to say that I DO NOT use the "WAN" plug on the back of the 54GLxxx, but one of the four plugs of the built in switch. You could use one of your Pc's on your LAN section to see the web interface of the AP … and use the telnet (SSH) interface to see what happens in your AP. (Note that the AP DDWRT Firmware has a bare Linux kernel, so basic commands like ifconfig etc work). What I didn't understood from your wors is that you could put it (teh AP) to work when connected to your Opt1 network. Connecting it to the LAN network - and the AP stops working. DID you change the gateway when you switched ? If a connection on the switch from the AP always work, but not the Wifi part the the problem is situated in the AP. If I recall well, all I change to make a DDWRT AP work, is: Reset it. It should have a LAN IP that is 192.168.1.1 - dhcp server activated. Connect a PC to it - using LAN cable on the back. (NOT the WAN port). Change IP LAN from 192.168.1.1 to i.e. 192.168.1.2 While your at it, on the same page: Switch "Connection type" to "Dissabled" Local IP Address = 192.168.1.2 Mask 255.255.255.0 Gateway 192.168.1.1 (points to pfsense) Local DNS : 192.168.1.1 (points to pfSense) Shut down its DHCP. (Think about using a NTP server ...) Validate. The AP should be up now. Mine is.

@wallabybob: It looks to me that the GUI doesn't provide for configuration of a wireless client connecting to an AP which uses RADIUS authentication. In particular, there doesn't seem to be a way to input the RADIUS username (identity) and password. There doesn't seem to be a HOWTO for this type of configuration and it doesn't seem to be discussed in the pfSense book. It would probably be worth submitting a bug report on http://redmine.pfsense.org Better late than never ;) It works, but as you said, a bit fragile. Thank you. Issue submitted: http://redmine.pfsense.org/issues/2400