Slow wireless access point

krazykev

Hi Wallaby,

the screenshots weren't meant to cause offence - I apologise if they did. I thought they were very telling, and I do appreciate your help.

The first screenshot shows all available wi fi networks when I am not connected to the pfSense access point and indicates that they are available to be connected to.

The second screen shot was taken once I had connected to the pfSense access point. Once connected to pfSense all other wifi networks are not available as shown in the screenshot which shouldn't be the case.

This suggests to me that connecting to pfSense access point is causing 'interference' for want of a better word, creating large amounts of traffic maybe stopping the SSID detection working?

Really am at my wits end. I do intend to try another usb wifi device once I ahve obtained one, maybe even a wifi pci card. But something odd is happenning and I would love to find out what.

Thanks again

Kevin

wallabybob

@krazykev:

the screenshots weren't meant to cause offence - I apologise if they did.

I wasn't in any way offended by the screenshots. I just didn't know why you posted them because there wasn't much of an explanation. Now its much clearer.

What about trying your USB WiFi NIC in the Windows laptop to connect to the ADSL modem to see if it gives reliable service. (You might need to download a driver from the TP-Link support site or Ralink support web site.) That, at least would be another data point. If it doesn't work well from the laptop that might suggest the device itself. Maybe ther

Another thing to try: 802.11G actually has overlapping channel frequencies so channel 2 (which your pfSense WiFI is using) overlaps the band centred on channel 1. For least interference, different networks should use channels numbers that are at least 5 apart. That's not possible in your environment but it would be worth seeing if you get different results if you move your pfSense AP to either channel 6 or channel 11.

krazykev

Thanks Wallaby - time for an update! Swapping channels didn't have any effect :(

I have used the TP-LINK in my laptop as a receiver and works very very well. As a Windows USB wifi dongle I highly recommend it.

However, as a pfSense I am stumped! Is there another drier out there I can build?

If not, if anyone in the UK wants to try it I will happily post it to you. Bin fodder if you can't get it working - or maybe if you figure something out I overlooked you'd return it?

Kev

jimp

Looking back in the thread I see you're using 1.2.3, have you tried a 2.0 snapshot?

Much newer drivers, lots of wireless changes/fixes since 1.2.3.

krazykev

Hi Jim,

Thanks for the idea. I did actually try a version 2 snapshot live CD last night. Two in fact as the most recent (pfSense-2.0-BETA4-20101130-0342.iso) doesn't work at all (a build error I think - problem with a config file). The version I did try, pfSense-2.0-BETA4-20101129-2231.iso, consistently causes a kernel fault and reboots everytime a wi fi client tries to connect. I have ordered a different usb dongle to try. If that doesn't work I think I may go down the standalone wireless router road on my lan rather than as a pfSense intterface.

If anyone has got pfSense working as a wi fi access point with a USB dongle can you let me know what dongle (and version if poss) you are using.

Thanks

Kev

wallabybob

I have used a Tenda W311U with pfSense 2.0 BETA snapshots. The driver for this NIC (run) is new to pfSense 2.0 BETA.

On pfSense 1.2.3 I have used a TP-Link TL-WN321G and a D-Link DWL-G122 Rev C1 both of which are driven by the rum driver. (Other revisions of the DWL-G122 might use a different chipset, possibly unsupported by FreeBSD/pfSense.) Some months ago I tried these on pfSense 2.0 and kernel panics resulted. I can't recall if I tried then on pfSense 2.0 since then.

krazykev

I am now in possession of a Cisco WUSB54GC usb dongle to give that a try - but not moer different problems. But hopefully much easier to fix.

When I insert the dongle I get this output on the local terminal (and dmesg)

ugen0: <ralink 0="" 2="" 802.11="" g="" wlan,="" class="" 0,="" rev="" 2.00="" 1.01,="" addr="">on uhub1

The adaptor isn't getting an ethernet address and as such I cannot configure it in pfSense web gui.

The TP-Link would display this
rum0: <ralink 0="" 3="" 54m.usb…....,="" class="" 0,="" rev="" 2.00="" 0.01,="" addr="">on uhub1
rum0: MAC/BBP RT2573 (rev 0x2573a), RF RT2528
rum0: WARNING: using obsoleted IFF_NEEDSGIANT flag
rum0: Ethernet address: d8:5d:4c:8e:63:4f

As it gets an ethernet address it is recognised to be configured. I have read various reports on the Cisco using the ral driver. Is it possible to override the driver chosen by pfSense or does it depend on the chipset in the usb device?

Thanks

Kev</ralink></ralink>

krazykev

Quick update. After inserting the Cicso device into pfSense 1.2.3 and not getting an ethernet addres the pfSense loses all connectivity and services like DHCP freeze (probably the driver issue). But what has made me want to cry is trying it in pfSense 2 Beta 4. When I insert the device I see

ugen1.2: <ralink>at usbus1
run0: <1.0> on usbus1
run0: MAC/BBP RT3070 (rev 0x0201), RF RT2020 (MIMO 1T1R), address 68:7f:74:66:fc:90
run0: firmware RT2870 loaded

I thougt I had cracked it. But when I configure the device as OPT1 interface as an access point it cannot be found by wi fi clients :(

Think I may just got down the independent wireless router road but we have all tried so hard with this I really don't want to be beaten.

Kev</ralink>

wallabybob

My Tenda W311U shows up in my pfSense 2.0 startup as:


ugen3.2: <ralink>at usbus3
run0: <1.0> on usbus3
run0: MAC/BBP RT3070 (rev 0x0201), RF RT3020 (MIMO 1T1R), address c8:3a:35:c4:ee:f3
run0: firmware RT2870 loaded</ralink>

My ifconfig shows (run0 related information only):


run0: flags=8a43 <up,broadcast,running,allmulti,simplex,multicast>metric 0 mtu 2290
	ether c8:3a:35:c4:ee:f3
	media: IEEE 802.11 Wireless Ethernet autoselect mode 11g <hostap>status: running
run0_wlan0: flags=8843 <up,broadcast,running,simplex,multicast>metric 0 mtu 1500
	ether c8:3a:35:c4:ee:f3
	inet6 fe80::ca3a:35ff:fec4:eef3%run0_wlan0 prefixlen 64 scopeid 0x9 
	inet 192.168.xxx.xxx netmask 0xffffff00 broadcast 192.168.xxx.xxx
	nd6 options=3 <performnud,accept_rtadv>media: IEEE 802.11 Wireless Ethernet autoselect mode 11g <hostap>status: running
	ssid xxx channel 11 (2462 MHz 11g) bssid c8:3a:35:c4:ee:f3
	country xxx authmode WPA2/802.11i privacy MIXED deftxkey 3
	AES-CCM 2:128-bit AES-CCM 3:128-bit txpower 0 scanvalid 60
	protmode OFF -apbridge dtimperiod 1 -dfs</hostap></performnud,accept_rtadv></up,broadcast,running,simplex,multicast></hostap></up,broadcast,running,allmulti,simplex,multicast>

I have had no trouble connecting to this AP from my Linux netbook. I'm running build pfSense-Full-Update-2.0-BETA4-20101127-0055.tgz

brcisna

krazykev,

Just curious if you ever got your wifi mystery resolved? From reading this thread I am not really able to add any useful information,,,but seeing how from what you have posted the usb dongle,is causing the pfSense machine to randomly reboot, I am sure you are going to have problems with the given usb dongle you are using. I would guess you do not have an open slot inside your pfSense machine to utilize an pci wifi card?
I would guess this would solve all of your wifi dodgyness.
It would appear to me the chipset and/or the physical usb is not right on the usb dongle you are using thus causing your machine to randomly reboot.

Take Care,
Barry