WireLess WAN - Infrastructure (BBS) mode? Wireless Client - 2.0 RC3
-
@Bo:
I am refuse to believe that I am the first one to bump into this issue and strongly have the feeling that there is some easy workaround, but …...............
My readings of the forums suggest it is much more common to use a pfSense WiFi link as an AP than as an AP client. I think your post is the first mention I have seen of a Fritzbox. This suggests your configuration is probably fairly rare.
@Bo:
what's causing the security conflict? based on the ifconfig ath0_wlan0 output I have the feeling that the box is switching to IPv6 mode without having it configured (see log in my reply on Posted on: August 06, 2011, 04:17:23 pm).
I don't know what is causing the security conflict. I don't know what facilities there are in FreeBSD to debug this kind of issue. Concerning the IPv6: for some releases now FreeBSD has "automatically" configured "link local" IPv6 addresses based on MAC address for those interfaces with a MAC address. It is rather unlikely that enabling encryption on a WiFi interface would also turn it into "drop IPv4 traffic" mode if the interface is in client mode but not if it is in AP mode. (I have an ath interface in AP mode using encryption and successfully passing IPv4 traffic.)
-
Well I've used the same pfSense box for multiple years as an Wifi AP using WPA+WPA2 as encryption and never experienced any problems. It might be the other side of the line: the Fritz!Box causing all the issues.
I'll go and look for another AP and check if the pfSense box can establish a secured connection in Infrastructure mode with this AP.
-
Yesterday i tried to connect an ALIX with ath0 cards to a Linksys WRT54GL wireless AP (which is running DD-WRT).
I was able to get an IP from the DHCP pool (hence encryption [WPA2 AES] is working) but wasn't able to pass traffic. I couldn't even ping anything on ALIX WAN.And you were right, Bo, Infrastructure mode only works on the virtual ath0_wlan1 interface, not the native card IF ath0.
I think there were issues with some of the snapshot builds in the past where you couldn't assign IFs correctly. Will try a recent snapshot tonight and report back. -
Good to hear I am not alone out there!
-
I think there were issues with some of the snapshot builds in the past where you couldn't assign IFs correctly. Will try a recent snapshot tonight and report back.
Any news on the recent snapshots? Are these issues resolved in these snapshots?
-
Sorry, didn't have the time to do anything with pfSense in the last days.
Busy at work and even more busy at home, fixing other stuff.I'll report back as soon as I had the time to test.
-
Chris, great that your still willing to spend some time testing the recent snapshots!
Take your time, since I'll be on holidays the next three weeks! -
Any news already on the new snapshots?
-
Have you had any luck with this? I am having the same problem with the 2.0 release on an Alix board. The router I am connecting to is a Sierra Wireless AirCard 754s (AT&T Elevate). I can get an IP from it when security is turned off, but not with WPA/WPA2.
-
I've been in the same boat, can't ever connect to any wireless AP using WPA, but I can if it's open.
EDIT: I just switched to a different Wi-Fi adapter, and it worked.
The issue here is with the driver for that device. I know it supports WPA and WPA2 since it works in Windows.
Didn't work:
ural
runWorked
utrwTwo of the USB devices wouldn't even show up. One of them was a TP-Link TL-WN722N which showed up as <atheros>and the other I can't figure out which it is until I start unplugging them.</atheros>