I've had good results with a Marvell 88W8363.  Note that the driver was not available until FreeBSD 8, however.  This means it will not work on pfSense 1.2.3, only 2.0.

Thanks all,

I have managed to get things up and running… 
Had to reconfigure all interface the other way round :

LAN –> WAN
WAN --> WLAN

Things are running smoothly, I only had to force the gateway for It to work.
But now It seems ok…

Thx.

Mini-pci to pci adapters (with more than one slot) are not very common.  At the moment I can only find a 4 slot adapter.  The adapters have bridge chips so I guess it comes down to OS support for the bridge.

Ok. I follow what you are saying regarding the N card.

It would seem I would be better off with one of these then:

http://cgi.ebay.com/ws/eBayISAPI.dll?ViewItem&item=370387009123

http://cgi.ebay.com/ws/eBayISAPI.dll?ViewItem&item=330430725233 <–This one is a 5212

http://cgi.ebay.com/ws/eBayISAPI.dll?ViewItem&item=270581080563

Correct?

Thanks for the help. Once I get all the parts I will post about using a mini-pcie card if it works.

Bob

As I said, it is not possible if both have the same gateway.

Interface routing might work only in rare cases where the WAN is an actual point-to-point link which does not require a gateway.

I do understand WME was the original name for WMM but I guess my question should be can I set the following settings somehow for WMM devices (ie, wireless voip phone)

WMM access category
WMM Power Save
WMM Admission Control
DSCP (Differentiated Services Code Point)

In the GUI config for the interface it only has a check box to enable or disable WME.  I'm not apposed to logging in through a shell and adjusting a config file I just have no experience in this particular realm.

Thanks

I have three ap's 2 are operating on G and the other is on B/G

Yes I have followed every step, I am way ahead keeping track of notes in updates in src/sys/UPDATING

Well, I even added a 6dbi omni antenna attached to a pigtail. I am expecting for atleast the two ap's in G mode would appear in the list?
What could it be? Does anyone have the same card running on freebsd 7.2?

(Partly copied and pasted from another post of mine.)

The only 802.11n chipsets I know of that work as an access point in FreeBSD are the ones supported by the ath driver (Atheros) and the mwl driver (Marvell 88W8363).

Some supported 802.11n chipsets I know of for Atheros are 5416 (802.11b/g/n) and 5418 (similar to 5416, but I think also supports 802.11a and 5 GHz 802.11n).  802.11n rate control is not yet implemented in the FreeBSD driver for Atheros chipsets, so only up to 802.11a/g speeds will work.

The Marvell 88W8363 is an 802.11n chipset with support for 802.11a/b/g/n, but the driver doesn't seem to support 802.11n rates yet and was just added in FreeBSD 8.0, so it is not possible to use the card in anything before pfSense 2.0 beta.  I've only seen one model of card that I know uses it, a mini PCI card (though converters to regular PCI are available), and it only seems to be available on eBay from around 2 to 4 different sellers in China.

Thanks for the info.

WiFi is just for the internet, the file transfers are all done via ethernet hence the need for gigabit eth.
I'll probably keep the WRT54G as the WiFi AP anyways because it seems it will do a much better job than a WiFi card in the pfSense box.

Cool!

Ah,

you are right, i changed too much and also set the wlan-adapter to dhcp…
Changed it back.
Does this look correct?

LAN interface (vr0)
Status up
MAC address 00:0d:b9:1c:cc:ec
IP address 192.168.1.100 
Subnet mask 255.255.255.0
Media 100baseTX <full-duplex>In/out packets 6049689/8669774 (1.65 GB/1.38 GB)
In/out errors 0/0
Collisions 0
Bridge (bridge0) learning

WLAN interface (ath0)
Status associated
MAC address 00:80:48:68:5e:36
IP address 0.0.0.0 
Subnet mask 255.0.0.0
Media autoselect mode 11g <hostap>Channel 2
SSID Michas
In/out packets 995/8541 (179 KB/39 KB)
In/out errors 3407/0
Collisions 0</hostap></full-duplex>

I don't know how relevant it is to this thread, but the other ipod/iphone threads have been locked so…

I was running pfsense 1.2.2 as access point (wpa2/tkip) and my ipod was able to connect, but had timeout issues and could not download anything over WiFi.

Yesterday I upgraded to pfsense 2.0 beta (4-22-2010 build) and now everything is fine with exactly the same WiFi settings.  No timeout issues and downloads are great.

It does not currently have a channel width option, but I'm fairly sure the base system does.  It wouldn't be too difficult to add, though it would likely only be implemented for 2.0.

As for additional channels, if your card supports them, you should probably see them in the list.  Otherwise, they will not be listed.  There is also a possibility that ifconfig on FreeBSD does not support listing those channels, though.  ifconfig gets its information from /etc/regdomain.xml

I have the same problem with the same wifi card (CM9 Atheros chipset) on a Soekris net5505

miibus5: <mii bus=""> on sis1 nsphyter1: <dp83815 10="" 100="" media="" interface=""> PHY 0 on miibus5 nsphyter1:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto sis1: Ethernet address: 00:00:24:ca:df:d5 sis1: [ITHREAD] ath0: <atheros 5212=""> mem 0xa0010000-0xa001ffff irq 15 at device 17.0 on pci0 ath0: [ITHREAD] Fatal trap 1: privileged instruction fault while in kernel mode instruction pointer    = 0x20:0x3 stack pointer          = 0x28:0xc1020944 frame pointer          = 0x28:0xc1020958 code segment            = base 0x0, limit 0xfffff, type 0x1b                         = DPL 0, pres 1, def32 1, gran 1 processor eflags        = interrupt enabled, resume, IOPL = 0 current process        = 0 (swapper) trap number            = 1 panic: privileged instruction fault</atheros></dp83815></mii>

The dropdown represents the % of the maximum power not the absolute power.

OK, got my pigtail and set up the internal card, everything is working just fine now, looks like pfSense + Belkin G + OS X is a bad combination…

I use a Kelkin wireless N1 [+?] (MIMO) as my network AP and it works just fine for me…

It was a tp-link atheros card and bridged with the ethernet lan card.  The current netgear is just acting as an AP and all is well.

I usually keep my wireless network on channel 11 since most devices don't seem to use that channel (not sure why) or some other random channel that is "technically" meant for other countries (Mexico, Japan, etc), works wonders for me, but yea other wireless devices can really play havoc with wi-fi…effectively your phone was acting like a signal jammer to the wi-fi.