try this site for scientific antennas
http://www.wifi-plus.com/metrospotsystems.html

I managed to get my diagram setup working, however the security is backwards, Wifi clients can access LAN PCs but not the other way around

I see…  It's also interesting to see it for the first time, for me, where a single mini-pci card can have two radios operating independently and simultaneously, and at such low cost.

Apparently FreeBSD has some "generic" 802.11n support but doesn't yet have any device drivers for 802.11n devices.

See http://forum.pfsense.org/index.php/topic,14253.msg75550/topicseen.html#msg75550 and http://www.mail-archive.com/freebsd-net@freebsd.org/msg30294.html The latter post suggests that at least one Atheros 802.11n chipset can be made to work in 802.11g "compatibility mode" but not "full 802.11n" mode. Depending on what you want to do, this may or may not qualify as "802.11n". The latter post discusses "FreeBSD current"; I don't know if the discussed support is in any pfSense build.

@ wallabybob.

I have checked Enable Intra BSS communication and now I can ping the Win2k3 server from the ping util in PfSense. Thanks!

I don't want to use PfSense as the DHCP server because I have the W2k3 box setup and was going to reflect those DHCP setting on the PFSense box if the server whent down.

This little setup is for home use / studdy. So nothing to critical.

Thakns for the help!

Hi!

I'm testing now with another computer, this one has intel chipset, not Via…and it seems to work flawless, with the same USB dongles. it is working at full speed for about 4 hours without a single failure, so I can think that the problem is with USB support of via chipset....

do you know something about that?

Did you assign the interface in the GUI and configure it correctly?

Sometimes people are confusing the modes "infrastructure" with "access point".

Solved

I used this tutorial: http://www.dd-wrt.com/wiki/index.php/Wireless_Access_Point
to put the dd-wrt router into Wireless Access Point mode.  I gave the dd-wrt router an ip address in the same subnet of the main router that was outside the dhcp pool and then plugged the dd-wrt into the switch, not into the OPT1 port.

I was able to connect just fine after that and am now enjoying a blazing fast wireless signal  :D

-Dave

Hello Again,

Well, after long and exhausting work. I finally nailed down the issue, it was actually not from Pfsense routing at all. Apparently when I disable the SSID for WRT54GL, it becomes unreachable from anywhere including its own network port. But it still routes the traffic and everything else, only not reachable for administrative purpose :(

I guess, now we know that this issue is not particular for pfsense. However, I truly appreciate the assistance provided by this forum.

I hope this can help anyone else for future issue.

Nope. It's not that.

I brought everything home, and just took delivery of an ALIX 2D0 (2 ethernet, 2miniPCI).

vr0 (ethernet0) is always set to LAN.
If WAN is set to vr1, I can set OPT1 or OPT2 to AP mode, bridge them to the WAN, and it works fine (although very slow, very much slower than m0n0wall).
If WAN is set to ath0 (wireless0), even though the LAN works fine, and even though I receive no error message about bridging something to a wireless WAN, the bridge essentially does not work. The problem seems to be that you can't bridge anything to a wireless WAN.

So right now, I have several SBCs with a half dozen radio cards and working repeater stations.

So, do I try a Linux-based solution instead?

It's either that or I'm going to need to spend several months fixing m0n0wall to do what I want. I'd likely do it as a branch.

@wallabybob:

I think you will need some firewalls rules to allow the appropriate access between OPT1 and WAN.

@GruensFroeschli:

You have to set the "Mode" to "Access Point" and not to "Infrastructure (BSS)"

I have tried several configurations. Some from the wiki here.. http://doc.pfsense.org/index.php/Main_Page plus I tried the advice from the two post here (this thread), plus many other suggestions and configuration from the pfsense forums including - firewall rules, bridging, and so on. The result was the same, no internet/traffic to the network from/to the wireless but the laptop could see and connect to the pci wirelless card in the pfsense machine.

I did read up on subnets and configured them as well. I still did not get a functioning connection to the Internet from/to the wireless. It could be the wireless card, I'm not sure.

I'm not giving up just heading back to the forums and wiki's and until then I'll use my Linksys box for a semi-functioning, less secure network.

Thank you all for helping.

Lou

hm.
no edit feature?

Anywho - is there a way that I can make the packet sizes smaller in pf sense?

Thanks.

@chmodman:

Any idea why this would need to be disabled?
Thanks

Guess your AP had a firewall rule (or rules) that blocked your traffic from the laptop.

Looking at the firewall log on the AP or pf statistics can sometimes give a clue as to which rule is causing the blocking.

It seems that my questions/problems on here tent to be of the unanswerable breed..

anywho - i've noticed that the above problem always coincides with something. And that is; OUT errors.

whenever there's one of those, the internet drops out, and I have to release / renew once more ,to connect any program.

Any Ideas anyone?

@ashdavely : find a solution to your problem ?
I forced the channel (6) then all ok for me.