The pfSense Store

Author Topic: WLAN ap-problems and tinydns broken  (Read 2808 times)

0 Members and 1 Guest are viewing this topic.

Offline n1ko

  • Jr. Member
  • **
  • Posts: 75
    • View Profile
WLAN ap-problems and tinydns broken
« on: January 25, 2009, 07:42:24 am »
1.2.3 seems to be working for except for couple things:

1.) Tinydns is broken somehow. If i turn it on (with the same config as before) no dns request gets trough.

2.) Atheros wlan-driver driver still b0rked, as with 1.2.1/2. Timeouts after some time, for example if I leave ssh session open and nothing else for couple minutes it will be frozen.

3.) DHCP request doesnt get trough with WLAN bridged to LAN. Not even with the rules that I had to put in 1.2.2.

Everything else (phpsysinfo,squid,lightsquid, dhcp-server etc. ) seems to be working as usual.

Seems that with every new pfSense version wlan gets worse and worse and everything else gets better. Maybe I should just go buy a real AP :)

Offline cmb

  • Administrator
  • Hero Member
  • *****
  • Posts: 6283
    • LinkedIn
    • Twitter
    • View Profile
    • Chris Buechler
Re: WLAN ap-problems and tinydns broken
« Reply #1 on: January 25, 2009, 01:54:24 pm »
1.) Tinydns is broken somehow. If i turn it on (with the same config as before) no dns request gets trough.

Haven't tried it.

2.) Atheros wlan-driver driver still b0rked, as with 1.2.1/2. Timeouts after some time, for example if I leave ssh session open and nothing else for couple minutes it will be frozen.

FreeBSD issues outside our control. We're moving 2.0 to 8-current to hopefully get some FreeBSD developer attention to these issues.

3.) DHCP request doesnt get trough with WLAN bridged to LAN. Not even with the rules that I had to put in 1.2.2.

Works for me.

Offline n1ko

  • Jr. Member
  • **
  • Posts: 75
    • View Profile
Re: WLAN ap-problems and tinydns broken
« Reply #2 on: January 25, 2009, 03:26:56 pm »
I still couldnt get tinydns working. I will look into it when I have more time. If its working for you then theres probably something in my config that is b0rked.

About the wlan: its not only dhcp thats not getting trough. Actually the laptop I was trying to connect didnt even get to the phase where it tries to get an address, it jams before that. No packets go either way for some reason. My phone on the other hand (nokia E90) works fine. Also the laptop (t40p,b43xx chipset wlan, ubuntu hardy) worked fine with 1.22. I will try to look in to this too when I have more time.

I tried with TKIP and AES and both WPA and WPA2. Previously in 1.22 I had both wpa and wpa2 on and both TKIP and AES on. I also tried removing all settings from the laptop and made the opt1-interface settings from the scratch -> still nothing.

Offline cmb

  • Administrator
  • Hero Member
  • *****
  • Posts: 6283
    • LinkedIn
    • Twitter
    • View Profile
    • Chris Buechler
Re: WLAN ap-problems and tinydns broken
« Reply #3 on: January 29, 2009, 07:17:27 pm »
Oh - tinydns, sorry, I misread that as dnsmasq for some reason. Not sure on that.

Wireless is in the midst of significant changes, pulling in some newer kernel code recommended by FreeBSD developers. I would stick with 1.2.2 right now with wireless until we can better test it ourselves.

Offline n1ko

  • Jr. Member
  • **
  • Posts: 75
    • View Profile
Re: WLAN ap-problems and tinydns broken
« Reply #4 on: January 30, 2009, 04:48:16 am »
Actually the wireless started working after I updated to a newer snapshot and updated&rebooted the linuxlaptop.

I am hoping that 2.0 will be moving in to openbsd8 soon so that I can test out if they have fixed the powersave(?) bug with ath-driver. I am open to all kinds of beta-alpha-test tweaks that might fix this.

On another note; i have an usb wlan-stick with zydas1211 chipset. It should be supported in openbsd7 but still pfsense doesnt recognize it (it is detected as ugen0). Is there anything I could do to get that working for the timebeing?

I wouldnt want to go back to 1.2

Offline cmb

  • Administrator
  • Hero Member
  • *****
  • Posts: 6283
    • LinkedIn
    • Twitter
    • View Profile
    • Chris Buechler
Re: WLAN ap-problems and tinydns broken
« Reply #5 on: February 01, 2009, 06:46:26 pm »
The power save bug is confirmed fixed in the 1.2.3 snapshots, we applied a patch to resolve that.

2.0 will be moving to FreeBSD 8-current in the not too distant future.

What driver should your card be using?  It's possible there is a new driver that we aren't including, though we include everything in FreeBSD GENERIC.

Offline cmb

  • Administrator
  • Hero Member
  • *****
  • Posts: 6283
    • LinkedIn
    • Twitter
    • View Profile
    • Chris Buechler
Re: WLAN ap-problems and tinydns broken
« Reply #6 on: February 01, 2009, 11:41:25 pm »
The wireless you are on in the newer snapshot is likely the new code imported, which should also have the power save fix.

Offline n1ko

  • Jr. Member
  • **
  • Posts: 75
    • View Profile
Re: WLAN ap-problems and tinydns broken
« Reply #7 on: February 02, 2009, 03:53:48 am »
Just updated to newest snapshot and also changed from my 3com 905 (LAN-interface)  to intel 10/100 card (cant remember the exact chipset). Seems that either the new snapshot fixed the problem or there was something wrong with the 3com (wlan is bridged to lan) since the bug is now fixed! At last I can properly use my AP again without restarting ssh sessions over and over again :)


Offline misteragony

  • Jr. Member
  • **
  • Posts: 26
    • View Profile
Re: WLAN ap-problems and tinydns broken
« Reply #8 on: February 20, 2009, 02:57:37 pm »
Hello,

I have very shaky wireless connection with my ATH5212 wireless pci nic. From a wireless client, suddenly internet access stops working, as well as rdp, ssh sessions to server on my LAN connection. The odd thing is my wireless connection stays connected, I can even log into the webinterface of Pfsense. But that's the only box I seem to be able to connect to.

I'm not 100% sure if my problem is related to the problem described above, but I thought I'd share it.

I'm running the build from 19feb

Best regards,
Jan

Offline n1ko

  • Jr. Member
  • **
  • Posts: 75
    • View Profile
Re: WLAN ap-problems and tinydns broken
« Reply #9 on: February 21, 2009, 02:27:44 am »
My problem was fixed quickly after the first 1.2.3 snapshot so it probably aint the same problem.

Does your problem occur with LAN-connection too or is it isolated to WLAN? Have you checked if theres some pointers in the logs?

Offline misteragony

  • Jr. Member
  • **
  • Posts: 26
    • View Profile
Re: WLAN ap-problems and tinydns broken
« Reply #10 on: February 22, 2009, 04:09:14 am »
Hello,

I haven't looked in the logs yet. As far as I have seen it's only WLAN clients that are affected. To fix the problem I temporary switch off my wireless nic and after reconnecting my internet connection works again. My connections towards my LAN is restored then as well.

Since the connection to my AP is not broken when I don't have internet access, I first thought that perhaps the DNS server on the pfsense box gets screwed up but that wouldn't explain why I can't access my LAN servers (I connect based on IP address not on FQDN).

A bit more background information:

It's a ATH5212 card and I use WPA2 as security. I had to change the default setting 'auto' for the channel selection. Apparently pfsense by default chooses channel 6, but that's a turbo G channel (at least it lists it that way in the channel list). The problem is that this channel doesn't work for this card, under 'status interfaces' the card doesn't associate when using channel 6. So in the wireless interface configuration dialogue I choose channel 10, plus under 'standard' I chose for 802.11G and not for ' 802.11G Turbo'  or otherwise clients don't get connected at all.

I will check the logs and do some futher investigation.

Best regards,
Jan

Offline misteragony

  • Jr. Member
  • **
  • Posts: 26
    • View Profile
Re: WLAN ap-problems and tinydns broken
« Reply #11 on: February 27, 2009, 04:03:26 am »
Hi,

I investigated this problem a bit futher:

apparently when I lose my internet connection (I'm still connected to my AP at this point), it's my DNS that doesn't work anymore. DNS settings for my client are dynamically assigned by DHCP on my pfsense box.  An ipconfig /all showed me that the DNS server is 192.168.6.0 (shouldn't this be 192.168.6.1?). In the DHCP server settings in pfsense I left the DNS entry blank.

I did a ping to a website from one of my stations that has a wired network connection, and I received answers. When I lost internet connection (again my connection to the AP was ok) I did the same ping and my wireless client couldn't resolve the DNS name. I tried to ping base on the IP address of the website and I received answers. Also surfing based on that IP proved to work.

The strange thing is when I switch of my wireless nic and reconnect the problem is gone (for some time). So it would seem this is a client side issue. However I have 5 different wireless clients and they all have the same problem since I switched to 1.2.3.

I'm running the snapshot from 25feb at the moment.

Best regards,
Jan
« Last Edit: February 27, 2009, 04:05:17 am by misteragony »