@ktims:

Yeah you can change it in the webui. Not a big deal really, just change the DHCP server configuration first and then change the interface address, then release/renew on your client. Even if you break DHCP or something you can always statically configure the client to go in and repair the config.

I tried this last night.
And LOORD, the heachaces.

Its something that I've noticed with PF sense for a while now.
Its like if I fiddle around with the WAN/LAN interface options too much - I'm unable to connect to the router.
And even when I restore factory defaults - whatever sub level settings have thrown the system haywire, I cant revert!

The only thing I could do last night, and in the previous instances, was reinstall.

Ever had the like?

Glad you got it sorted out. But take my advice - hold unto that other wireless card. Dont count him out just yet ;)

Its far more normal that the card would behave THAT way. Its understandable that it wouldnt use as much power to scan for a network, than to actively transceive. Many cards, and radio devices behave that way.

What WAS strange, is when it did the exact OPPOSITE! :|
in that case - I dunno. Noise I suppose. (Picked up raw Radio frequency from where ever, ALONG WITH wifi.)

Hop over here:
  http://forum.pfsense.org/index.php/topic,15705.msg86740.html#msg86740

The problem with Ubiquiti (bullet/nanostation) and similar equipment is they are normally based in atheros SoC that generally clock at 180Mhz. While this is ok with 802.11a/g non-turbo 20-25Mbps, when you go with Turbo Mode the CPU simply isn't capable of achieving much more than that. The testing i've done in the last years using x86 hardware I concluded that to fully saturate a radio in 802.11a Turbo (40Mhz channels) you need more than 300Mhz CPU power, but you can get 50Mbps with a single radio :)

You can only bridge on an accesspoint, but not on a wireless-client.
–> It's not possible to set up a wireless bridge.

You will have to resort to a routed scenario.

@GruensFroeschli:

Create an alias containing all subnets which should not be accessible.

Modify the default "allow rule" on the wireless-OPT interface.
Change the "destination: any" to "NOT "alias""

Hello,GruensFroeschlino

Thanks for the input. I tried that method with the Default LAN Rule because I have no wireless Antenna setup on this box. However I am in need of a little clarity here please. This only works for me if I add another rule not just modifying the default LAN rule.

Also,what is the bolded NOT for in the Source and Destination sections?

Another thing is I have to reboot the box everytime I make a rule change for it to take effect. Is this normal?

I am using version 1.2.3 RC1

Thank you
Joseph

@bbzidane:

so a second antenna of the same db doesn't help?  than what is the point of having an aux connector?

With a second antenna you can use diversity if you set your wireless accordingly.
Usually you gain more stability in reception with moving transmitters.

I had mentioned this as a second part to a previous question regarding DNS forwarding. After the fact, I realized it was unrelated and would be better suited as its own question in the proper section.

As for it being an issue with DD-WRT, that is very possible, but I had recently changed my setup from 3 routers (1 main Linksys router splitting into two separate LANs, DD-WRT router and pfSense router) into my current setup. The once I changed the setup so that the DD-WRT router was running off the OPT1 on pfSense, the wireless issue began.

In reply to your PM (which is probably the least appropriate use of a PM I've ever seen), you should use words that seem relevant (for instance, "stable" or "scale").  You may have to do multiple searches to find relevant threads, trying different words.

You should keep the use of PMs for things that shouldn't be posted in the forum.  Asking simple questions can certainly be done in the forum, that's what it's for.

@wallabybob:

Sorry I didn't spell it out. My configuration in an earlier post in this topic is configured as an access point and acts as an access point.

Not all wireless LAN NICs that are supported by FreeBSD (and pfSense) are supported as access points. The Atheros PCI chipsets supported by the ath drivers are supported in infrastructure mode (uses an external access point) and "access point" mode.

That's cool, preferably I would like a wireless NIC to be configured as a AP - I didn't think that would have to be configured but it makes total sense.  Prior to my first post I new I had to get a Atheros PCI chipset and that's the plan.  I just need to figure out which NIC is most effective for my home.  I've been doing some searching but I'm not doing so well :P….  wireless PCI NIC with a Atheros chipset that supports being an AP and can handle decent amount of load + have good range!

Adam

You can't just stick an antenna on and expect to get 500m of effective range, even outdoors with clear LoS. If you're lucky and have good visibility across your site you might manage with poor signal at 1mbps, but I'm doubtful. Antennas work by focusing the energy more - it becomes a more directional signal. 'Omnidirectional' antennas really aren't - they attempt to focus the energy into a plane instead of radiating in all directions, but they only gets you so far (not very). You can't just up the power due to FCC regulations (or your local radiotelecom regulator). What might work for you is using several radios at the same location, each with sector antennas to each cover a portion of the radius.

I would suggest that you contract a local wireless consultant to come take a look at your site and figure out a plan that will work for you and your particular site. Getting what you seem to need working is definitely non-trivial and probably not doable with a single radio/AP. It would also be a good idea to make sure you don't run afoul of any telecom regulations, as there are some complications when you get into high gain antennas and multiple colocated radios.

but I can't understand why there is no option for WAN acting as a wireless client with options to choose which access points to connect to

The way you tell pfSense which access point to connect to is to give pfSense the wireless parameters used by the Access Point: SSID, wireless channel, encryption type, standard (802.11b, 802.11g, etc), etc

Your access point may "hide" some of these parameters by having a set of defaults. That configuration technique works OK until you need to have multiple access points or your close-by neighbour uses the same access point in default configuration.

@waiwai:

Multiple Radio APs  share the same SSID would really share the load?

It depends.

@waiwai:

or just using AP build-in function WDS (Wireless Distribution System)?

Nope, WDS is a totally different journey and not what you need!

I get the impression you know alot about engines or gear-boxes but your car is still missing tires and such.
Get some professional service frm your area to solve your needs, really!

I have run into a similar problem. In order to have the LAN be available on two ports, I have bridged LAN and OPT1 (Referred to as LAN2). However I can only access external FTP servers from a machine connected to LAN, but not from LAN2, I have tried with the FTP helper both enabled and disabled, in either case FTP doesn't work.

Does anybody know if there's a problem with bridged interfaces and the FTP helper?

You could either create a diff and send it to someone on the core team, or create a git clone and submit the changes for review. You would just need to add an interface for the mac: commands and maybe have the wireless status also show the list mac output.