If D-Link didn't switch the chipset without telling anyone (they do that sometimes), it should be based on the Atheros 5416 chipset. Should work, but not in 801.11n mode. Per the man page: AR5416-class devices are capable of 802.11n operation but are supported only in legacy modes (802.11a, 11b, 11g).
It should work in any mode you want. Generally, you want to set it up in AP mode. There are a couple of howto's available here: http://doc.pfsense.org/index.php/Category:Howto

what i did was go on the freebsd forum and see what people were using with 7.2

i chose to use the newest atheros chipset that 7.2 supported.
Atheros  AR5008 Wireless Mini PCI Card 802.11n

yes, its 802.11n, which doesnt work, but the 802.11g part of it still does
cost a bit more than the older ones, but i like getting the newer parts, and people have said it worked

Normally these cards just fake the power output reported to the driver.
Like if you set it to use 20db it would use 20 + XX in order to be compatible with normal equipment.
So when you set it to 20 it would really output 26 or somthing like that.
Ask you mfg. how much they double the selected power.

Thanks all..

Seem solved now

I need separate them to two subnet, it work now. Bridge mode have problem

May be onboard realtek giga LAN cannot bridge with wireless (Atheros chips)

Found the following:

dturbo  Enable the use of Atheros Dynamic Turbo mode when communicating
            with another Dynamic Turbo-capable station.  Dynamic Turbo mode
            is an Atheros-specific mechanism by which stations switch between
            normal 802.11 operation and a ``boosted'' mode in which a 40MHz
            wide channel is used for communication.  Stations using Dynamic
            Turbo mode operate boosted only when the channel is free of non-
            dturbo stations; when a non-dturbo station is identified on the
            channel all stations will automatically drop back to normal oper-
            ation.  By default, Dynamic Turbo mode is not enabled, even if
            the device is capable.  Note that turbo mode (dynamic or static)
            is only allowed on some channels depending on the regulatory con-
            straints; use the list chan command to identify the channels
            where turbo mode may be used.  To disable Dynamic Turbo mode use
            -dturbo

It looks like the driver is miss behaving because here it says it should not be enabled by default. I tried to set the channel back to auto and the do a ifconfig ath0 -dturbo but after the reboot it's back to channel 6 with turbo enabled. the -dturbo does not seem to do anything.

Could we disable turbo mode with systcls or prevent the system from selecting channel 6?

Could it be that the Wireless configuration->Standard dropdown control of the pfSense Web Administration is not writing the proper configuration when you choose 802.11g?

Any movement on this?

I have the exact card and the no carrier issue as well, running 1.2.3 RC3.  I have not tried the manual bridging yet…

read http://forum.pfsense.org/index.php/topic,19887.0.html

@danswartz:

I would think you could just use one rule and specify any for the source IP, no?

0.0.0.0 is not a valid IP on the OPT interface so no.

that was the only reason, to be honest.  well, and also, the tp-link card i got was specifically recommended, and i don't see it in mini-pci format.

There have been a lot of reports of trouble with newer builds (1.2.3 snaps at least, it may have started earlier when the base went to 7) when people use autoselect and AP mode. I think something changed in FreeBSD. Perhaps it should be noted on the doc site. IIRC, the AP howto specified auto. In my opinion, one should hard set the channel in AP mode as a best practice.

Good to hear!

If it seems to be working fine, don't worry about it. You can find many posts about this in the wireless forum- my experience is that you can see huge amounts of in errors without having a problem.

Sorry for my late reply. Been to frustrated to continue playing with the configs.

I have Manual Outbound NAT rule generation enabled with

  WAN    192.168.10.0/24  *  *  *  *  *  YES Auto created rule for LAN      WAN1    192.168.10.0/24  *  *  *  *  *  YES Auto created rule for LAN      WLAN1    192.168.10.0/24  *  *  *  *  *  YES Auto created rule for LAN 

I also enabled bridge to LAN from the WLAN interface. So far i have been able to get windows laptops all talking and Nokia E series phones talking but the iPhone still refuses to talk properly.

It's serving the WAN1, but danswartz is right and it would be an absolute nightmare of a hideously hideously bad setup. So bad the raptors will get me.

We've actually got some spare ADSL wireless routers, but it didn't want to play nice when I tried it last night. Might have another try and see if I can find a way to get it to work.

Incidentally, pfSense is pretty damn awesome, normally our connection dies as soon as 9 o clock comes but the load balancer has worked like a dream.

Yes

Si se puede, si entendí correctamente la pregunta, de un lugar a otro esta conectado mediante 2 nano uquititi, la interface es por cable de red, yo recientemente instale y funciona correctamente.

Lugar1 –------------------ Lugar2 ------ Pfsense
Note que Lugar1 y 2 estan separados por 10kms y lugar 2 se conecta mediante un cable de red a la wan del pfsense
lugar 1 y lugar 2 usan nanostation5

Lamento que mi ingles sea malo
Saludos

In mode "infrastructure"
You can configure WEP on the config page of the interface. (in your case probably OPT2?)

After that just follow the standard multiWAN guide an treat the wireless interface as a normal interface.

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