Up and Down Problem with WiFi and LAN



  • I’m having an interesting problem with my LAN and WiFi Connections right now.  My lan connection is okay but when I ping the pfsense box I’m hitting .38ms times rather than the standard <1ms.  Now on the WiFi side I’m running into some wacky ping issues.  I am attaching the ping responses below…  I’m using a USB WiFi Ralink 3070 and a SUN GIGx 4 port Card...  I’m using todays snapshot 2.1 nano image (x386)

    Is there a way we can compile the new Ralink Driver?

    http://forums.freebsd.org/showthread.php?t=7562

    http://gitorious.org/run/run/trees/8.1_REL

    64 bytes from 10.10.5.250: icmp_seq=0 ttl=64 time=4.557 ms
    64 bytes from 10.10.5.250: icmp_seq=1 ttl=64 time=3.971 ms
    64 bytes from 10.10.5.250: icmp_seq=2 ttl=64 time=1.174 ms
    64 bytes from 10.10.5.250: icmp_seq=3 ttl=64 time=4.675 ms
    64 bytes from 10.10.5.250: icmp_seq=4 ttl=64 time=0.834 ms
    64 bytes from 10.10.5.250: icmp_seq=5 ttl=64 time=3.900 ms
    64 bytes from 10.10.5.250: icmp_seq=6 ttl=64 time=6.988 ms
    64 bytes from 10.10.5.250: icmp_seq=7 ttl=64 time=0.868 ms
    64 bytes from 10.10.5.250: icmp_seq=8 ttl=64 time=6.981 ms
    64 bytes from 10.10.5.250: icmp_seq=9 ttl=64 time=5.705 ms
    64 bytes from 10.10.5.250: icmp_seq=10 ttl=64 time=13.404 ms
    64 bytes from 10.10.5.250: icmp_seq=11 ttl=64 time=1.834 ms
    64 bytes from 10.10.5.250: icmp_seq=12 ttl=64 time=10.134 ms
    64 bytes from 10.10.5.250: icmp_seq=13 ttl=64 time=3.949 ms
    64 bytes from 10.10.5.250: icmp_seq=14 ttl=64 time=6.932 ms
    64 bytes from 10.10.5.250: icmp_seq=15 ttl=64 time=4.411 ms
    64 bytes from 10.10.5.250: icmp_seq=16 ttl=64 time=9.482 ms


  • Netgate Administrator

    I'm not seeing a problem here. 0.38ms is <1ms.  :-
    Your ping times look normal for wifi to me, better than mine.
    The driver you have linked to appears to be quite old anyway (Jan 2010). I didn't read the entire thread however.

    Steve



  • flynhawaiian, please clarify your expectation of WiFi ping times.

    There are limitations due to the way WiFi works. The Access Point has to have quiet time so clients can transmit. Consequently a ping response can be delayed until after the quiet time. Similarly the client can't transmit at any time - it has to wait until the AP gives it permission.



  • Hmmm does that mean I have the wireless setup wrong?  I shouldn't be using AP mode, it would seem normal that AP mode should be used, but I have no clue anymore…  Here's the log from the wireless system log.  I’m just wondering if I have something setup wrong...  As far as the drivers I was just hoping there was something I was missing and these would fix them.  I mean the ideal would be to nab the ones from ralink directly, but they only work on linux.  Maybe I'll ask them if they could port the driver for freebsd?

    Oct 19 08:24:30 hostapd: run0_wlan0: STA 20:c9:d0:c6:65:ff WPA: sending 1/2 msg of Group Key Handshake
    Oct 19 08:24:30 hostapd: run0_wlan0: STA 60:33:4b:0f:4a:d7 WPA: EAPOL-Key timeout
    Oct 19 08:24:30 hostapd: run0_wlan0: STA 60:33:4b:0f:4a:d7 WPA: sending 1/2 msg of Group Key Handshake
    Oct 19 08:24:30 hostapd: run0_wlan0: STA 20:c9:d0:c6:65:ff WPA: EAPOL-Key timeout
    Oct 19 08:24:30 hostapd: run0_wlan0: STA 20:c9:d0:c6:65:ff WPA: sending 1/2 msg of Group Key Handshake
    Oct 19 08:24:30 hostapd: run0_wlan0: STA 20:c9:d0:c6:65:ff WPA: received EAPOL-Key frame (2/2 Group)
    Oct 19 08:24:30 hostapd: run0_wlan0: STA 20:c9:d0:c6:65:ff WPA: group key handshake completed (RSN)
    Oct 19 08:24:30 hostapd: run0_wlan0: STA 20:c9:d0:c6:65:ff WPA: received EAPOL-Key 2/2 Group with unexpected replay counter
    Oct 19 08:24:30 hostapd: run0_wlan0: STA 60:33:4b:0f:4a:d7 WPA: received EAPOL-Key frame (2/2 Group)
    Oct 19 08:24:30 hostapd: run0_wlan0: STA 60:33:4b:0f:4a:d7 WPA: group key handshake completed (RSN)
    Oct 19 08:24:30 hostapd: run0_wlan0: STA 60:33:4b:0f:4a:d7 WPA: received EAPOL-Key 2/2 Group with unexpected replay counter
    Oct 19 08:25:30 hostapd: run0_wlan0: WPA rekeying GTK


  • Netgate Administrator

    I think you're seeing a problem where there isn't one.
    You are running in access point mode, as evidenced by hostapd, and you should be. Your ping times look normal.

    Steve


  • LAYER 8 Global Moderator

    "I’m hitting .38ms times rather than the standard <1ms."

    As stated .38ms is less then 1ms – and very normal for lan.  Lan ping times are typically below .5ms -- if your seeing higher than 1ms on a nonbusy wired lan there might be something to look into.

    And as stated already as well - those wireless ping times don't look wrong to me.

    So when you were seeing <1ms I would assume you were pinging from a windows box, and now your pinging from linux/bsd that gives better info is all.



  • I guess what concerns me is when the times go up to 13ms randomly.  The system seems a little laggy, but maybe I need to get a faster box?  Maybe the processor cannot keep up or something.  I’m running a neoware ca22 1GHz with 1GB Ram and a 512mb DOM.


  • Netgate Administrator

    Like we have already said the ping times look fine to me.
    Here are some pings from my laptop to my pfSense box.

    steve@steve-Equium-L40:~$ ping 192.168.10.1
    PING 192.168.10.1 (192.168.10.1) 56(84) bytes of data.
    64 bytes from 192.168.10.1: icmp_req=1 ttl=64 time=0.625 ms
    64 bytes from 192.168.10.1: icmp_req=2 ttl=64 time=0.334 ms
    64 bytes from 192.168.10.1: icmp_req=3 ttl=64 time=0.463 ms
    64 bytes from 192.168.10.1: icmp_req=4 ttl=64 time=0.645 ms
    64 bytes from 192.168.10.1: icmp_req=5 ttl=64 time=1.84 ms
    64 bytes from 192.168.10.1: icmp_req=6 ttl=64 time=1.01 ms
    64 bytes from 192.168.10.1: icmp_req=7 ttl=64 time=0.697 ms
    64 bytes from 192.168.10.1: icmp_req=8 ttl=64 time=0.599 ms
    64 bytes from 192.168.10.1: icmp_req=9 ttl=64 time=3.75 ms
    64 bytes from 192.168.10.1: icmp_req=10 ttl=64 time=6.84 ms
    ^C
    --- 192.168.10.1 ping statistics ---
    10 packets transmitted, 10 received, 0% packet loss, time 9003ms
    rtt min/avg/max/mdev = 0.334/1.681/6.842/1.975 ms
    
    

    The signal strength here is very good and I have very few devices using the AP (possibly only one). However due to the way wifi works, as pointed out by Wallabybob above, the ping times vary by a large amount. 0.3-6.8ms or 2200%!

    How do you mean 'seems a little laggy'?

    Steve


  • LAYER 8 Global Moderator

    wireless as already stated is going to be bumpy – just the nature of wireless as explained by wallabybob



  • Guess it's the "bumpyness" I’m having feeling.  I just wish there was a way to help correct it.  I may just have to use an external AP.


  • LAYER 8 Global Moderator

    external AP is not going to fix the bumpiness of wireless.  Now remove all other wireless clients off the wireless network. Make sure all the interference is at min.  Turn of anything running in the 2.4ghz range or 5 if your using N and that.  Make sure no other traffic is going on, make sure no other wireless networks in the area ;)  And then your pings might be smoother.

    If you want less bumpy ping times - use a wire!

    I thought Wallabybobs 1 sentence layman's explanation was pretty spot on to why your going to see bumps in wireless.

    Even if you got your wireless network as quiet as possible - the AP itself is going to be sending out becons, so while its sending those pings or responses can not be in the air.  Wireless is bumpy in its vary nature and high latency than a wire, your times look to be a pretty quiet wireless network.

    How many devices do you have on your wireless - I can send you pings when I get to the house.  But have multiple cells phones, multiple laptops, tablets and kindles, etc. etc.  Yes the pings are going to be bumpy ;)



  • @flynhawaiian:

    Guess it's the "bumpyness" I’m having feeling.

    I suspect ping response variations of a few mS are unlikely to lead to a feeling of "laggy" response. What are you doing that has a "laggy": response?



  • Honestly I'm just surfing the net and it the system starts lagging for about 30 seconds.  I'm also having issues with a server on my network that is connected to the wifi connection.  I'm having issues uploading a file from my laptop to the server.  The file is about 90mb.  I would figure it would be alot faster, but can take up to 60 minutes.  Sometimes the connection gets lost and I have to upload it again.



  • Perhaps you have WiFi signal quality issues, interference etc. See earlier reply from johnpoz about WiFi interference.

    In my home near the top of a hill in the suburbs I can see a couple of neighbouring WiFi networks at low signal strength so I have a fairly quiet WiFi environment. My file transfers of 20+MB files from laptop to a home server over a WiFi hop to a run device on a pfSense box are routinely reported as running at over 1.5MB/s.


  • Netgate Administrator

    Hmm that doesn't sound right.
    When you say 30 secs lag do you actually mean nothing happens for 30 seconds?
    At home I am in a densely populated urban area surrounded wifi (over 100 networks when I last used kismet) and have no such problems. I'm using a mini-pci card in the pfSense box.

    Steve


Log in to reply