"long range wireless is not allowed for import"

Ok.. Build it, pfsense would not be the correct tool..  Grab a cheap wifi router, put dd-wrt or openwrt on it.  Connect some cantenna's
http://www.turnpoint.net/wireless/cantennahowto.html

Put real AP in the area you need wifi coverage.  Or again buy some cheap wifi routers and use them in AP..

That is why that walkthrough recommends the sysctls for the bridge/members the way it does. So that doesn't happen.

The IP configuration and DHCP server should be on the bridge. Not one of the members.

"I don't know what I did"

Completely agree there.  You not knowing what you did is not a bug that is for sure ;)

"What other info can I provide to help troubleshoot this?"

How about some basics, like what version of pfsense for starters?  Is it hardware or VM?  Is wifi some AP or some card in pfsense - if so what card? do you have it as bridge or its own segment?  Are you using say captive portal..

And big one - what exactly is not working??  Wifi clients see no ssid being broadcast?  You can associate but no IP from dhcp?  etc. etc..

Do you really need someone to point out what kind of info would be relevant?

They are listed at the top of the first post ath0: <atheros 9287="">& ath1: <atheros 9280="">A little more information:  Using the TetherMe app on the iPhone.  Very little information available about the app.  Best I can tell it uses WPA2 (CCMP), no configurable settings.  The Wireless page under Status shows the iPhone SSID but the CAPS settings do not show WPA.  I know it uses WPA because my computers and iPad require it to connect.  Is it possible that pfSense (ath0 driver) does not try to connect because it does not see WPA as an option?  Of course, it does not connect if I de-select WPA.

It sounds like the TetherMe app uses AdHoc mode.  When I put the WiFi interface in AdHoc mode, pfSense crashes and reboots continually.  I believe I read somewhere that pfSense can't use WPA in AdHoc mode, why? Doesn't make much sense.</atheros></atheros>

I think Sierra makes a solid unit.
https://www.sierrawireless.com/products-and-solutions/routers-gateways/es450/

That is pretty awesome. I never heard of AT!GOBIIMPREF?

I used to switch using carriers firmwares found on the Sierra Source website.

The options were removed. They rarely did what they were supposed to do, and cards have been smarter about doing the right thing on their own.

Don't think it will work.

https://www.freebsd.org/releases/10.3R/hardware.html#wlan

[i386, amd64] Intel PRO/Wireless 2100 MiniPCI network adapter (ipw(4) driver)

[i386, amd64] Intel PRO/Wireless 2200BG/2915ABG MiniPCI and 2225BG PCI network adapters (iwi(4) driver)

[i386, amd64] Intel Wireless WiFi Link 4965AGN IEEE 802.11n PCI network adapters (iwn(4) driver)

Credit goes to Rickinfl for this solution.

What I have here is based upon what Rickinfl has typed up, but I've changed things up just a bit and added a few steps.  I kept getting locked out when changing settings on the LAN IP, but finally got it figured out.  This works for 2.2.6.

I'm posting because I thought it may be helpful for those trying to bridge the LAN and WIFI so they're on the same subnet.  Hope this helps.

Bridging Wifi to LAN Interface

1- Set up wizard - set the initial LAN IP address to be higher than the final LAN IP, and set the netmask to /30.
For example, if you want the LAN IP to be 192.168.1.1, set the IP for the LAN to be 192.168.1.50 /30  during this step.
2- Interfaces > Assign > Add (it will be auto-named Opt1)
3- Click on Opt1 to set up Wifi Settings
3.1 Rename to Wifi
3.2 Enable interface
3.3 Under “Network-Specific Wireless Configuration” Set mode to “Access Point”
3.4 Set channel to Operate on
3.5 Select WIFI name and passphrase
3.6 Check “Allow intra-BSS Communication”
3.7 Check “Enable WME”
4- Interfaces > Assign > Bridges > Create a Bridge [+ Add] >  Selected LAN and Wifi as the interfaces on this bridge > Save
5- Interfaces > Add new Interface [+ Add] > Opt2 > Set Network port = Bridge > Save
6- From Interfaces, click on Opt2 to change options
6.1 Enable Interface
6.2 Rename to “Bridge”
6.3 IPv4 Configuration Type = Static IPv4 >
6.4 IPv4 address = acutual desired IP address of LAN  [must set netmask to 30 for now - will change to 24 later] (example above would be 192.168.1.1)
6.5 Save
7- Services > DHCP Server > Turn on DHCP for Bridge > Enabled > Set Range (range with a /30 netmask will be small)
8- Disable DHCP on LAN and WiFi (if they are enabled)
9- Firewall > Rules > Added New Rule > Interface > LAN > Source = Protocol = ANY > Bridge Net > Reset to ANY.
10- Firewall > Rules > Added New Rule > Interface > WiFi > Source = Bridge Net > Protocol = ANY > Rest set to ANY.
11- Firewall > Rules > Added New Rule > Interface > Bridge > Source = Bridge Net > Protocol = ANY > Rest set to ANY.
12- From “Interfaces” set the IPv4 Configuration Type for both LAN and Wifi to None.
13- Router is now reachable by the Bridge IP address (192.168.1.1) and the LAN and WIFI are bridged.
14- Log into router by Bridge IP and change the netmask to /24
15- Change DHCP scope options

Maybe silly but do you have a switch or a button to turn wifi on if it is a laptop.

Once i was reinstalling os on a Hp and could not get wifi to work and all drivers ok .

And then i found out there is a switch on the side to enable wifi :)

@johnpoz:

CA package?  You mean the built in pfsense CA?

So your wanting to auth your wifi with eap-tls?  I have this running currently, guess I could throw together a how to.  I ran into one little issue with IOS devices like ipads and iphones and the .p12 package for the ca cert and user cert and key not having a password.  But easy enough to work around with openssl to create a .p12 and put a password on.

I have windows 7 machines, android nexus phone and iphones and ipads all using eap-tls to auth to my wifi.  Keep in mind that not all devices support wpa/wpa2 enterprise and you will still need to maintain a psk wifi ssid for these types of devices.

John, if you could put together a how-to what would be greatly appreciated. I have been trying to get the same setup as the OP.

I have been trying for years to get a backup "WiFi_WAN" link working.  Every time I start to tackle the problem, I have problems & no one is able to help.  I want to use my cell phone Hot Spot as a backup in case my cable modem goes down.  I have never had a wireless card in a pfSense box successfully see (much less connect) to my phone's SSID.  All of my other devices see and use the phone.  Good luck!

Great. Thank you.

Why exactly do you think you need to bridge your wifi network to your lan?

I have multiple wifi networks via vlans and different ssid, none of which are bridged to anything.  There is like zero need to bridge these networks, other than not understanding how name resolution works and wanting to be able to broadcast for a netbios name or something.  Wanting to use say airprint since doesn't really work out of the box across segments.  So use avahi or setup the records you need in dns, etc.

If you buy a supported card that can be an AP and is supported by pfsense then sure you could do that.  Why would be the question.  Pfsense no longer offers wifi cards as option when you purchase from pfsense.  I personally think that is a good direction, some wifi card in your router does not make for good AP.. Coverage and location for starters - it would be rare that your router is in best location for AP.. They normally are not mounted in the ceiling for starters ;)

As to twinning - you mean run the same ssid, sure you could do that.

Why exactly do you want to bridge your interfaces??  If you need more ports on a specific network use a switch.  A router interface is not a switch port trying to use it as such not going to provide you anywhere near the performance and just complicates the setup for why?  Because your too cheap to buy a switch??  Any $40 for a 8 port gig - can even get vlan support at that price would be better than trying to use a nic as a switch port.

Ohh good to know,
I though the card Dual Radio..
Now I understand why, when I'm trying to setup the parental wireless interface on a other frequenz, it keeps saving the same parameters for both IPs.
Anyway, I think I will better go for getting a new AP for this goal.