It's easiest to assign the interface via the webgui. Go to interfaces>assign. Then add the [+] icon. It will add an OPTx interface. Hit save and go to Interfaces>OPTx (the one you just assigned). There you'll find all the wireless settings. If you want to do it from the shell answer no to the vlan question and assign the wireless interface just the way you assigned other interfaces too. Then do the configuration of the parameters like described above.

OK.  Well now that you know what version I am using would you like me to post some log or something?  I'm not sure where to go from here.  I would really like to use this feature and all of you keep saying that it is possible but for some reason I am unable to make it work. And your right that this SHOULD be simple and very possible, considering that off the shelf wireless routers do it all the time. All I want is this:  (a recap just to make sure we are all on the same page) Specs on Box running pfSense: –--------------------------------------------------------------------- AMD Thunderbird 900megahertz 768 megs of memory ATI All-In-Wonder 128 Pro Video Card (overkill but this box was not origionally a router) 5-10gig Hard Drive (Can't remember size) 3 - 10/100 NIC's 1 - B/G Wireless Card CD Drive Floppy Drive Current Setup: Internet:  Charter Cable Modem - 1 Dynamic IP Address WAN:  10/100 Wired NIC - DHCP for IP from Internet LAN:  10/100 Wired NIC - 192.168.1.1/24 - Connected to multiple switches for the many wired computers. OPT1(Server):  10/100 Wired NIC - Disabled at this time.  May be used in future as a DMZ. OPT2(Wireless):  Foxconn (Ral) B/G Wireless NIC - 192.168.2.1/23 DHCP server is turned on for the LAN & Wireless connections. Traffic Shaping is turned on for LAN. Squid Proxy package is installed and running. Dynamic DNS is sending WAN IP to DYNDNS service. ==LAN Internet === WAN==|pfSense|                                             ==WIRELESS What I want: LAN & Wireless to both be on 192.168.1.1/24 range. Single DHCP server to hand out addresses for both LAN & Wireless All other features that are currently running to keep running.  (Though I could live without traffic shaper if necessary) This machine should be able to handle being the Firewall / Router / Wireless Access Point / Squid Proxy What I DON'T want: Turn off any of the firewall features.  This is my only firewall between me and the net and I don't plan to add another one. Conclusion: The whole point of this thread (and the prior support ticket) is that due to how things are currently setup, in order for you to browse a computer on the wireless network you must know the IP address of the computer.  (Of course the opposite is true as well) You cannot just type in the machine name like you would for a computer on the LAN.  I just want the internal network to be able to talk to each other. I have tried rules.  I have tried bridging.  I've tried a combo of both.  I've tried just putting them on the same subnet but giving them different IP ranges in the DHCP servers. Nothing works. I am a FreeBSD / Linux NOOB.  I know PC's rinning windows or even dos like the back of my hand and have been building and maintaining said computers since I was like 12.  If someone knows the steps I need to follow in order to fix my problem PLEASE let me know.  I would like a step by step solution if possible.  What I am trying to avoid is instructions for something else that is simmilar and you want me to figure out how to modify them to fix my problem.  (aka Transparent Bridge on WAN ???  I'm sorry but that pdf file made no sense and did not seem to have anything to do with my problem)  Maybe I'm being dense / stupid.  It's possible.  Just please explain. Thank you all for your help!

WDS is not supported afaik. WDS is in general somewhat vendor specific and there is no standard for WDS. (the wifi alliance has what can be refered to as the defacto standard for WDS, but this is still not considered a full standard) You could mail the freebsd-mobile mailinglist for more info.

ok. Is there a way to get USB support on the embedded version? it would be VERY nice and i belive a lot of people would like to see that happen. It would open up for cheaper/easier wifi for the Soekris box (mini pci is expensive and its a nightmare to drill holes in the soekris cabinet..) Thanks Zap

There is a distance setting at the mentioned page too.

Wow.  I had no idea you guys were working on mesh incorporation into pfSense until just now.  Good job guys! I've been set back about 3-4 months on doing mesh here, but it'll be forthcoming.  Hopefully I can contribute on this front as well.  There have been some very interesting developments coming out of cuwireless.net, but I don't recall which of the mesh protocols they've been using, but I DO know they've been tweaking the routing protocol itself and have a city-wide mesh going already.  I'll need to bookmark this thread and come back to it later after I've had a chance to speak with Sascha over there a bit further.

Fixed in testing snapshots. Try an image from http://www.pfsense.com/~sullrich/1.0-BETA1-TESTING-SNAPSHOT-2-19-06/

I have disable the Turbo mode an now the wlan works  :) my version  TESTING-SNAPSHOT-02-19-06

Thank you for the quick responce and the proper lead for the channels problem.

I used Asus WL-167G and works very well… then I buy D-Link DWL-520 (PCI): this is work fine! Hi! Filippo

Hello, BETA-1 is great so far.  ;) I have a question on making an automatic conneciton on power up. I'm a Robotics experimenter and utlizing 2 Wrap boards each with dual CM9 cards. The wireless parts are very stable now with the new release thanks. I have setup one card on each for Turbo mode between themselves ATH1 <-> ATH1 and each boards ATH0 to G mode for regular server / client usage at either end. My question is how can I automatically make the connection between my 2 wrap boards ATH1 <-> ATH1 without doing it by hand once they are both booted. Thanks in advance. –RW

@squarepusher: I'm now trying out the latesta madwifi drivers in linux and there now seems to be support for turbo mode in 11g, when will the drivers (HAL) be updated in pfSense? btw Merry Christmas When Sam updates the firmware in FreeBSD.org