Hi lsf, am using a similar TP-Link router TP-WR740N for repeating function, it has WDS-bridging option.  but has similar problems, like all devices on the LAN of this router gets their own IP but their MACs are same as the router itself. one major problem is that anyone with a single access can just use one such router/repeater and many un-authenticated devices can use the net. I had posted a similar query in the following post: https://forum.pfsense.org/index.php?topic=80237.msg437605 Thanks Ashfaq

am not sure if this behavior is a bug or its normal, the way it should be with WDS bridging. should i be posting it in bug repository ? Ashfaq

i see that this is an older post. i have experienced the same problem and found it not to be my wifi but the walls in my house at one time had led based paint on the walls that was painted over.which turned out was blocking the signal. to check take a multimeter and set it to continuity then find a spot on the wall and stick the probes in. if it beeps, there is a high chance there is led based paint on the walls.

What are you going to add as opt1?  If you don't have more than 1 interface? While sure you can run multiple vlans on 1 physical interface - trying to run wan, lan and wlan all over 1 interface not really optimal solution. Creating a opt would require something to assign it too - what are you going to assign it too? If you don't have more than 1 physical interface - you can assign to same interface I guess..  But that is going to be cluster!! if you ask me. In a normal setup pfsense should have 2 interfaces at min.  One for the wan and one for the lan - you could then run vlans on those physical interfaces.  But your talking more complicated setup.  If you want pfsense to be the firewall/router between internet/wan - lan and a wlan I would suggest you have 3 physical interfaces. [image: optinterface.png] [image: optinterface.png_thumb] [image: vlanaddinterface.png] [image: vlanaddinterface.png_thumb]

wired is always going to be faster than wireless. what is your signal levels? keep in mind lower the signal level slower the speed. you may also want to check if there is any possible signal bleed in the area of the wifi.if there is you can try changing the wireless channel.

Have You "stuck…...beaconing" entries about WiFi in your pfsense syslog?

pfsense has really poor support for wifi, even with 2.2. If you want something that does wifi really well and has AC support try out MikroTik RouterOS, or just buy a stand-alone wireless AP.

Seem to have managed to get this working now. The bit I did not get was that to bridge LAN and WIFI interfaces, I actually need a third interface (say OPT3) assigned - which is then assigned to the bridge. I renamed this OPT3 interface to LANWIFIBRIDGE So, I have three interfaces (excluding WAN interface): I have a bridge (BRIDGE1) defined as LAN,WIFI LAN -> assigned to the network port em0 WIFI -> assigned to the network port ath0 LANWIFIBRIDGE -> assigned to the network Port BRIDGE1 LAN has a static IP address (other interfaces ie. LANWIFIBRIDGE and WIFI are set to "none"). DHCP is only defined on LAN. I have setup firewall rules to allow traffic between LAN and WIFI and LANWIFIBRIDGE. One thing, when you define all this, do not click apply until you have all the rules in place (incl firewall rules) or you may lose connectivity to the GUI. Still more to test, but seems to work. Hope that is correctly representing the steps and helps others who may struggle as i did with understanding this bit.

Hmm, well you might be able to do something within OpenWRT to achieve this. I'm unsure how OpenWRT handles client isolation (but now you've piqued my interest  :)). If it's at the radio level then you might be out of luck but if it's a layer 2 thing you might be able exclude MACs from the isolation. You could create a virual access point for the device you need to access and then allow traffic between them. If that doesn't work you can route traffic from that VAP via a different VLAN and route the traffic in pfSense. Many possibilities, all of them probably hours of fun!  ;) Steve

Wireless is not well supported in pfSense. Use an external wifi point, plug in switch or separate interface, and configure from there  :P

Thanks Jim, But, eh….  While we're ALL beta testers, really, I'm not ready to be an ALPHA tester! I've been able to look up which version of BSD has certain drivers, but have not been able to find match-ups between drivers and wireless devices/cards/chips... I'm not quite clear on the "ugen".  In the output I posted, earlier in the thread, where there are two similar entries with "ugen", with x.x & x.x.x numbers, the second entry has the driver info.  "ugen4.3" is the one without a driver, listing the Atheros chip of the WNDA3001....

Thanks kpa, But… 2.2 is in ALPHA, and I'm not ready to be an alpha tester. I've seen web pages that list what drivers are in each particular version of BSD.  But I've not been able to find which driver run specific  chips/cards/wireless devices...

Dear Forumer, I'm waiting for your hints…

So very late but still the same problem: Yes i run captive portal and I think there must be an error, because without capitve portal I don`t loos the internet connection. Maybe there is a problem with the token? I don`t know I am not a programmer! Can anybody help us?

None.  2.1 doesn't support any cards running in 802.11n mode.  There are a few "n" cards which will be detected and can be used in older modes though. Your best bet is to use an external access point.

@lbm_: Did you solve this? I am facing the same issue now on version 2.1.3. If you have addressed me: Yes, it is solved and in particularly for 2.1.3. You can find here some more detailed information: https://forum.pfsense.org/index.php/topic,68531.0.html Regards, Peter