Dotdash is right, what you ask about is called VAP code and is present in freebsd 8. I have doen some GUI and backend code on this in the past, but it's far from complete and userfriendly. If my code or someones elses code will endp up in pfSense is yet to be seen. My work and private life does not allow me to work much on free stuff atm. and I'm no longer a active developer on pfSense. You can try to make this a bounty and see if you can interest others. afaik. this code is not available to freebsd 7. Maybe ermal could backport it, but it's quite a extensive backport, due to many changes needed in order to get the updated 80211 stuff working.

Turbo mode should be available on channel 6 only. you can try to set tubo mode manually in CLI(shell) to see if it will do so. try "ifconfig ath0 list caps" from console, it should output somthing like: pfsense:~#  ifconfig ath0 list caps ath0=6783edcf <wep,tkip,aes,aes_ccm,ff,turbop,ibss,hostap,ahdemo,txpmgt,shslot,shpreamble,monitor,tkipmic,wpa1,wpa2,burst,wme,bgscan,txfrag></wep,tkip,aes,aes_ccm,ff,turbop,ibss,hostap,ahdemo,txpmgt,shslot,shpreamble,monitor,tkipmic,wpa1,wpa2,burst,wme,bgscan,txfrag> See: "this post" for a extensive explanation of what is listed here note the TURBOP (Turbo Protocol capablilty) listed. If you see on the interface config page i web GUI it should list a bunch of available channels. it should also show which channels (if any) are turbo capable. Normally in G mode it will only be channel 6 and it should be listed as the last choice of the 2.4GHz channels in the channel list, if your card is 802.11a capable it will also list the 802.1a channels and on the bottom it will list the 802.11a turbo capable channels. Also be aware that the interface will never report 108 as speed, it will allways be 54, with turbo it will connect as 54 turbo. Some manufacturers will list it as 108, but the real speed will never be anything but 54 with or without turbo mode (or 2X mode if you like). Hope this clears it up for you.

Thanks again I contacted the supplier (LinITX) and they told me to get in touch with Scott Ullrich as he supposedly has an FX5621 and it is apparently working according to them. They claim their own unit works OK with 1.2.2 but on CF embedded not CD -> hard disk version. I am using the CD install to hard disk (a DOM solid state disk on module 4GB unit) because I will want to install packages and that will be easier to do on the disk version than on the CF embedded version.

oh shoot, I just realized that all this may be moot… I still have to give out the WPA key because the security is in the wireless router and not in the psSense box.  Is there a way to make it work like I want? jw

We used the Compex WLM54AGP23 - http://www.atel-electronics.eu/produkt.php?hash=06268&dispLang=EN For the UMTS Modems we rented some from Swisscom. http://www.swisscom.ch/res/internet/mobilessurfen/mobile-unlimited/router/index.htm

The code is there in FreeBSD 8, but there is no pfSense code to use it yet. No idea on 2.0. It's in a feature freeze, but it's still quite alpha. It will be several months, probably early next year sometime, but don't quote me on that.

@Playmobil: My solution to run two cards on alix was to cover both 2.4Ghz a 5Ghz bands. Oh, that should be no problem. Netgate has some high power mini-pci cards. This one should work fine: http://www.netgate.com/product_info.php?cPath=26_34&products_id=694

i am using 1 pfsense server in basic mode and nothing else attached to it.

@misteragony: Or should I specifically begin stating every protocol(port) that I want to allow? No. Does a ping from the LAN to the wireless client get a response? Is sshd (or equivalent) up and running on the wireless client? Does it listen on the standard port? What does ssh on the LAN report when it can't connect?

@totalimpact: Alix 3d with Atheros CM9 PF 1.2.3 RC1 I have tried every possible combo, but I cannot get this thing to pass traffic on WPA, clients act like they authenticate, but no DHCP traffic can pass. I have a PCI WLAN card with Atheros chipset in my pfSense box. WLAN is bridged to LAN. If your WLAN is bridged to LAN you will need firewall rules to allow DHCP traffic from WLAN. See the DHCP and DNS forum for further discussion. What clients are you using? On my home network I have three Win Vista laptops using WPA2 successfully. I have a netbook running gOS (seems to be a variant of Ubuntu 8.10) but haven't been able to get that to work with the WLAN. I'm now using the netbook with a USB WLAN interface and no encryption.

For the moment it is not possible. pfSense frontend doesn't have that option and the backend doesn't have it too. I've been doing some testing with Kiffuser as you can see here…but so far no good. Have asked for some advice but no go too, it seems wireless development is for some reason in standby when it comes to authentication methods. I think we already got somewhere but we haven't had much time to go anyfurther, maybe in the next weeks. The easy part is making the frontend thing, which is creating the interface for the radius settings...our problem know is putting the correct values in the $config["wireless"]["…"] array…so it can pass the correct settings to hostapd_ath0.conf and save the configuration XML. For now we're getting a pretty messed up hostapd_ath0.conf, as there are some settings needed that we can't get from $config[] var. In here, at the bottom you can see an example for what is needed in hostapd_ath0.conf, but so far we haven't been successful. If you or someone else have something that could help, or if something that i said is wrong, please correct me.

I noticed the pfSense you are running is based on what is now a fairly old version of FreeBSD. It might be worth trying a recent 1.2.3 snapshot build.

Okay, fixed the problem. First thing was, the authentication setup was messed up (i think one can see that on the screenshot). basically i set it to WPA2/PSK/AES now. The phone will correctly connect to the wlan and authenticate. however i found that i could not reach the phones ip adress (e.g. ping). i tried a lot of things, until i found out i had to bridge then LAN interface with the WLAN interface too (as seen on the screenshot, the WLAN interface was already configured to bridge with LAN). i didnt know this, so right now i need to bridge WLAN -> LAN and also LAN -> WLAN. Saving this configuration & applying the wlan now works, i can access the phone by ip and i can access my lan/interet on the phone via wlan. now strange thing is that changing some unimportant setting in WLAN options breaks the wlan again, leaving the phone unable to connect. only if i go to LAN settings again and hit save followed by apply settings (without changing the configuration) solves this problem and the wlan works again. anyway it seems to work now, thanks for your support.

@wallabybob: This is a kernel problem generally caused by some code attempting to derefrence the NULL pointer. These are often quite difficult to debug without a crash dump. Sometimes they are difficult to debug with a crash dump. In this case its probably up to the FreeBSD developers to fix the problem and you would be doing the community a service by lodging a FreeBSD problem report at http://www.freebsd.org/support.html I believe the problem is the same as http://www.freebsd.org/cgi/query-pr.cgi?pr=119945.  It has been fixed long time ago in OpenBSD-current (see the URL), but I suppose the patch didn't make it into FreeBSD.  Is there a hope to include it in pfSense, because FreeBSD developers don't seem too worried about this particular problem?

Did you try the modules from FreeBSD 7.2? The ones linked are for 7.0. Any messages logged on startup? You could try kldloading the modules from a shell and see what the result is.

This is normal behavior for Bonjour. Bonjour uses a multicast address for each connected interface, local to that interface. It won't be pass ed through the bridge. What you need is a reflector for bonjour to broadcast mDNS info. Avahi is just that reflector. I couldn't install it via the package manager as of 1.2.3rc2 on tinybsd but a manual install worked fine. I used the tutorial here http://www.ucsecurity.com/article/2008/12/29/avahi-on-pfsense/ The added plus is now my pfsense box shows up as a device in bonjour for one click ssh and webgui, very cool. As a final resort, you could just map the addresses in dns, but thats work.

I seemed to have figured it out.  Well, I should say I don't know why it wasn't working before but I found some settings that seem to work. This card has a turbo mode and it seems to work best when set to turbo in pfsense.  Turbo mode requires channel 6 so it is set to channel 6.  I found some people using FreeBSD who had problems using WEP with this card so I am using WPA2.  You shouldn't use WEP anyway but whatever.  I had it off for several days but in the firewall.  I enabled it one night with these settings and it has worked ever since.  The range was pathetic so I bought a new 7db antenna which solved my range problems.  I spent some time testing with different angles and placements too to find the best position. All in all it seems to work now.  I guess Atheros based cards can work.  I am keep hearing on the forums that they are simply plug and play.  Not the case in my experience.  Lots of online research and monkeying around to find what works.

Search for 3g or evdo. Here is a recent thread: http://forum.pfsense.org/index.php/topic,17756.0.html Support for mini-pcie cards and usb modems is coming along, support for a phone as modem is unlikely. IMO, this should go somewhere else (hardware?), as this board is primarily concerned with 802.11