1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Wifi problems / ping response

Discussion in 'Tomato Firmware' started by hadede, Mar 12, 2009.

  1. hadede

    hadede Addicted to LI Member

    Hi all,

    first of all, please excuse, if this is a reoccurent topic... I have already searched for it, but did not find anything comparable.

    Generally I'm pretty satisfied with the quality and the possibilities of Tomato. The only problem is, I'm having some problems to connect, if I'm in another room...
    So I changed the location of the WRT54GL today searching for the best spot and was pretty excited, that I could cover the flat with WiFi without connection problems (which I'm facing for the last weeks, if I'm at the other end of the flat).

    I decided to reduce the transmit power back to 42mW (from 70mW) and suddenly my problems occured:
    The connection seems slow and the ping times are really weird...
    It's now standing next to my MacBook and WiFi shows me full bars of connectivity (although 3 out of 4 appearing sometimes, which seems strange beause of the near distance)
    Anyway, ping times vary dramatically:

    64 bytes from 192.168.1.1: icmp_seq=964 ttl=64 time=0.883 ms
    64 bytes from 192.168.1.1: icmp_seq=965 ttl=64 time=0.895 ms
    64 bytes from 192.168.1.1: icmp_seq=966 ttl=64 time=0.928 ms
    64 bytes from 192.168.1.1: icmp_seq=971 ttl=64 time=2786.449 ms
    64 bytes from 192.168.1.1: icmp_seq=972 ttl=64 time=1786.363 ms
    64 bytes from 192.168.1.1: icmp_seq=973 ttl=64 time=786.265 ms
    64 bytes from 192.168.1.1: icmp_seq=974 ttl=64 time=0.916 ms
    64 bytes from 192.168.1.1: icmp_seq=975 ttl=64 time=0.883 ms
    64 bytes from 192.168.1.1: icmp_seq=976 ttl=64 time=0.933 ms
    64 bytes from 192.168.1.1: icmp_seq=977 ttl=64 time=1786.283 ms
    64 bytes from 192.168.1.1: icmp_seq=978 ttl=64 time=786.423 ms
    64 bytes from 192.168.1.1: icmp_seq=979 ttl=64 time=0.874 ms
    64 bytes from 192.168.1.1: icmp_seq=980 ttl=64 time=0.837 ms
    64 bytes from 192.168.1.1: icmp_seq=981 ttl=64 time=3.301 ms
    64 bytes from 192.168.1.1: icmp_seq=982 ttl=64 time=1787.292 ms
    64 bytes from 192.168.1.1: icmp_seq=983 ttl=64 time=787.165 ms
    64 bytes from 192.168.1.1: icmp_seq=984 ttl=64 time=0.864 ms
    64 bytes from 192.168.1.1: icmp_seq=985 ttl=64 time=0.884 ms
    64 bytes from 192.168.1.1: icmp_seq=986 ttl=64 time=0.815 ms
    64 bytes from 192.168.1.1: icmp_seq=987 ttl=64 time=1786.229 ms
    64 bytes from 192.168.1.1: icmp_seq=988 ttl=64 time=786.278 ms
    64 bytes from 192.168.1.1: icmp_seq=989 ttl=64 time=0.929 ms
    64 bytes from 192.168.1.1: icmp_seq=990 ttl=64 time=0.770 ms
    64 bytes from 192.168.1.1: icmp_seq=991 ttl=64 time=0.929 ms
    64 bytes from 192.168.1.1: icmp_seq=992 ttl=64 time=1784.993 ms
    64 bytes from 192.168.1.1: icmp_seq=993 ttl=64 time=785.073 ms
    64 bytes from 192.168.1.1: icmp_seq=994 ttl=64 time=0.828 ms
    64 bytes from 192.168.1.1: icmp_seq=995 ttl=64 time=0.936 ms
    64 bytes from 192.168.1.1: icmp_seq=996 ttl=64 time=0.881 ms
    64 bytes from 192.168.1.1: icmp_seq=997 ttl=64 time=1785.504 ms
    64 bytes from 192.168.1.1: icmp_seq=998 ttl=64 time=785.865 ms
    64 bytes from 192.168.1.1: icmp_seq=999 ttl=64 time=1.349 ms
    64 bytes from 192.168.1.1: icmp_seq=1000 ttl=64 time=0.902 ms
    64 bytes from 192.168.1.1: icmp_seq=1001 ttl=64 time=0.957 ms
    64 bytes from 192.168.1.1: icmp_seq=1002 ttl=64 time=1783.032 ms
    64 bytes from 192.168.1.1: icmp_seq=1003 ttl=64 time=783.530 ms
    64 bytes from 192.168.1.1: icmp_seq=1004 ttl=64 time=0.940 ms
    64 bytes from 192.168.1.1: icmp_seq=1005 ttl=64 time=0.959 ms
    64 bytes from 192.168.1.1: icmp_seq=1006 ttl=64 time=0.867 ms
    64 bytes from 192.168.1.1: icmp_seq=1007 ttl=64 time=1781.236 ms
    64 bytes from 192.168.1.1: icmp_seq=1008 ttl=64 time=781.330 ms
    64 bytes from 192.168.1.1: icmp_seq=1009 ttl=64 time=1.308 ms


    I'm don't know where the problem is located (I never saw this before).

    Some add. info:
    - I'm running a MacBook with Intel CoreDuo and I think as it has an Intel Chipset, the WiFi card will be Intel too...
    - I made the same ping test using the router firmware (GUI) and the response times seem to be the same:
    0 192.168.1.124 (192.168.1.124) 64 64 1.34
    1 192.168.1.124 (192.168.1.124) 64 64 1.78 0.44
    2 192.168.1.124 (192.168.1.124) 64 64 1969.10 1967.32
    3 192.168.1.124 (192.168.1.124) 64 64 969.70 -999.40
    4 192.168.1.124 (192.168.1.124) 64 64 1.10 -968.60
    5 192.168.1.124 (192.168.1.124) 64 64 1.06 -0.04
    6 192.168.1.124 (192.168.1.124) 64 64 1.10 0.04
    7 192.168.1.124 (192.168.1.124) 64 64 1968.18 1967.08
    8 192.168.1.124 (192.168.1.124) 64 64 968.52 -999.66
    9 192.168.1.124 (192.168.1.124) 64 64 1.11 -967.41
    10 192.168.1.124 (192.168.1.124) 64 64 2.58 1.47
    11 192.168.1.124 (192.168.1.124) 64 64 4.78 2.20
    12 192.168.1.124 (192.168.1.124) 64 64 694.45 689.67
    13 192.168.1.124 (192.168.1.124) 64 64 966.77 272.32
    14 192.168.1.124 (192.168.1.124) 64 64 1.10 -965.67
    15 192.168.1.124 (192.168.1.124) 64 64 1.10 0.00
    16 192.168.1.124 (192.168.1.124) 64 64 1.17 0.07
    17 192.168.1.124 (192.168.1.124) 64 64 1965.64 1964.47
    18 192.168.1.124 (192.168.1.124) 64 64 966.32 -999.32
    19 192.168.1.124 (192.168.1.124) 64 64 1.15 -965.18

    Any help appreciated.

    Best Regards,
    hadede
     
  2. hadede

    hadede Addicted to LI Member

    hi again,

    sorry for opening a thread... after restart of the computer, this does not occur any more... seems to be not router-related...

    @admin: you can delete this thread if you like... sorry again...
     

Share This Page