Community discussions

MikroTik App
  4. RouterOS
  5. Wireless Networking

ping delay 40-80ms

Post Reply
 
lfs0a
newbie
Topic Author
Posts: 36
Joined: Wed Jun 05, 2013 5:47 am

ping delay 40-80ms

Tue Jun 11, 2013 6:30 pm

i bought a RB751U-2HnD,and setup an ap,but when i ping from my laptop to RB751U-2HnD,some packets was delayed about 40-80ms,most of them are <1ms. i returned purchase.After the device been tested,they said it's normal.
1.Is it normal?
2.Does the RB751 RB951 series can get a stable ping(through radio)?

Have a nice day!
Thanks a lot!
Top
 
HaPe
Member Candidate
Member Candidate
Posts: 239
Joined: Fri Feb 10, 2012 10:24 pm
Location: Poland

Re: Dear normis,can you answer a question for me?

Tue Jun 11, 2013 7:39 pm

Which version of ros do you have?
I've rb751u (about 2 years)and all is ok.
Code: Select all
C:\Users\Hubert>ping 10.0.0.20

Pinging 10.0.0.20 with 32 bytes of data:
Reply from 10.0.0.20: bytes=32 time=2ms TTL=64
Reply from 10.0.0.20: bytes=32 time=1ms TTL=64
Reply from 10.0.0.20: bytes=32 time=1ms TTL=64
Reply from 10.0.0.20: bytes=32 time=1ms TTL=64

Ping statistics for 10.0.0.20:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 1ms, Maximum = 2ms, Average = 1ms

C:\Users\Hubert>
Top
 
lfs0a
newbie
Topic Author
Posts: 36
Joined: Wed Jun 05, 2013 5:47 am

Re: Dear normis,can you answer a question for me?

Tue Jun 11, 2013 8:00 pm

Thanks a lot for your reply,HaPe.
I had try 5.24 and 5.25.It's about every 80-100 packets,there will be 2-4 packets have a long delay(about 40-80ms),most of them are <1ms,when i upgrage to 5.25,most of them are =3ms.
Did you make a long test(more than 100 packets)?


Good night!
Top
 
HaPe
Member Candidate
Member Candidate
Posts: 239
Joined: Fri Feb 10, 2012 10:24 pm
Location: Poland

Re: Dear normis,can you answer a question for me?

Tue Jun 11, 2013 10:34 pm

Try to change channel, change channel from 40MHz to 20MHz.
Top
 
lfs0a
newbie
Topic Author
Posts: 36
Joined: Wed Jun 05, 2013 5:47 am

Re: Dear normis,can you answer a question for me?

Wed Jun 12, 2013 4:59 am

HaPe,i had try 20Mhz,the delay still happens.
Top
 
HaPe
Member Candidate
Member Candidate
Posts: 239
Joined: Fri Feb 10, 2012 10:24 pm
Location: Poland

Re: Dear normis,can you answer a question for me?

Wed Jun 12, 2013 7:39 am

Make supout.rif and send me it on email hubert@pluta.in
Top
 
lfs0a
newbie
Topic Author
Posts: 36
Joined: Wed Jun 05, 2013 5:47 am

Re: Dear normis,can you answer a question for me?

Wed Jun 12, 2013 8:46 am

sorry,HaPe,the device had been returned purchase.
now i just wonder can the rb751 rb951 series get a stable ping (above 100 packets) through radio.
Thanks a lot for your reply,could you make a long ping at your RB751U?
if they can,i'm gonna buy another one :)
Top
 
HaPe
Member Candidate
Member Candidate
Posts: 239
Joined: Fri Feb 10, 2012 10:24 pm
Location: Poland

Re: Dear normis,can you answer a question for me?

Wed Jun 12, 2013 1:30 pm

When I back home from school, I will do it.
Top
 
lfs0a
newbie
Topic Author
Posts: 36
Joined: Wed Jun 05, 2013 5:47 am

Re: ping delay 40-80ms

Wed Jun 12, 2013 2:05 pm

Thanks a lot!!! :)
Top
 
HaPe
Member Candidate
Member Candidate
Posts: 239
Joined: Fri Feb 10, 2012 10:24 pm
Location: Poland

Re: ping delay 40-80ms

Wed Jun 12, 2013 6:56 pm

C:\Users\Hubert>tracert 10.0.0.20

Tracing route to 10.0.0.20 over a maximum of 30 hops

1 1 ms <1 ms <1 ms router13.ipv4.net.htop.pl
2 1 ms <1 ms <1 ms router27.ipv4.net.htop.pl
3 2 ms <1 ms <1 ms teddy-bear1.ipv4.net.htop.pl
4 2 ms 1 ms 1 ms ap1-mt.ipv4.net.htop.pl

Trace complete.
C:\Users\Hubert>ping -t -n 101 10.0.0.20

Pinging 10.0.0.20 with 32 bytes of data:
Reply from 10.0.0.20: bytes=32 time=1ms TTL=64
Reply from 10.0.0.20: bytes=32 time=1ms TTL=64
Reply from 10.0.0.20: bytes=32 time=2ms TTL=64
Reply from 10.0.0.20: bytes=32 time=1ms TTL=64
Reply from 10.0.0.20: bytes=32 time=1ms TTL=64
Reply from 10.0.0.20: bytes=32 time=2ms TTL=64
Reply from 10.0.0.20: bytes=32 time=1ms TTL=64
Reply from 10.0.0.20: bytes=32 time=1ms TTL=64
Reply from 10.0.0.20: bytes=32 time=2ms TTL=64
Reply from 10.0.0.20: bytes=32 time=1ms TTL=64
Reply from 10.0.0.20: bytes=32 time=1ms TTL=64
Reply from 10.0.0.20: bytes=32 time=3ms TTL=64
Reply from 10.0.0.20: bytes=32 time=1ms TTL=64
Reply from 10.0.0.20: bytes=32 time=1ms TTL=64
Reply from 10.0.0.20: bytes=32 time=1ms TTL=64
Reply from 10.0.0.20: bytes=32 time=1ms TTL=64
Reply from 10.0.0.20: bytes=32 time=1ms TTL=64
Reply from 10.0.0.20: bytes=32 time=1ms TTL=64
Reply from 10.0.0.20: bytes=32 time=1ms TTL=64
Reply from 10.0.0.20: bytes=32 time=1ms TTL=64
Reply from 10.0.0.20: bytes=32 time=1ms TTL=64
Reply from 10.0.0.20: bytes=32 time<1ms TTL=64
Reply from 10.0.0.20: bytes=32 time=1ms TTL=64
Reply from 10.0.0.20: bytes=32 time=1ms TTL=64
Reply from 10.0.0.20: bytes=32 time=1ms TTL=64
Reply from 10.0.0.20: bytes=32 time=1ms TTL=64
Reply from 10.0.0.20: bytes=32 time<1ms TTL=64
Reply from 10.0.0.20: bytes=32 time=1ms TTL=64
Reply from 10.0.0.20: bytes=32 time=1ms TTL=64
Reply from 10.0.0.20: bytes=32 time=1ms TTL=64
Reply from 10.0.0.20: bytes=32 time=1ms TTL=64
Reply from 10.0.0.20: bytes=32 time=1ms TTL=64
Reply from 10.0.0.20: bytes=32 time=1ms TTL=64
Reply from 10.0.0.20: bytes=32 time<1ms TTL=64
Reply from 10.0.0.20: bytes=32 time=1ms TTL=64
Reply from 10.0.0.20: bytes=32 time=1ms TTL=64
Reply from 10.0.0.20: bytes=32 time<1ms TTL=64
Reply from 10.0.0.20: bytes=32 time=1ms TTL=64
Reply from 10.0.0.20: bytes=32 time=2ms TTL=64
Reply from 10.0.0.20: bytes=32 time=4ms TTL=64
Reply from 10.0.0.20: bytes=32 time=1ms TTL=64
Reply from 10.0.0.20: bytes=32 time<1ms TTL=64
Reply from 10.0.0.20: bytes=32 time=1ms TTL=64
Reply from 10.0.0.20: bytes=32 time=1ms TTL=64
Reply from 10.0.0.20: bytes=32 time=1ms TTL=64
Reply from 10.0.0.20: bytes=32 time=1ms TTL=64
Reply from 10.0.0.20: bytes=32 time<1ms TTL=64
Reply from 10.0.0.20: bytes=32 time=1ms TTL=64
Reply from 10.0.0.20: bytes=32 time=1ms TTL=64
Reply from 10.0.0.20: bytes=32 time=1ms TTL=64
Reply from 10.0.0.20: bytes=32 time=1ms TTL=64
Reply from 10.0.0.20: bytes=32 time=1ms TTL=64
Reply from 10.0.0.20: bytes=32 time=2ms TTL=64
Reply from 10.0.0.20: bytes=32 time=1ms TTL=64
Reply from 10.0.0.20: bytes=32 time=1ms TTL=64
Reply from 10.0.0.20: bytes=32 time=1ms TTL=64
Reply from 10.0.0.20: bytes=32 time=1ms TTL=64
Reply from 10.0.0.20: bytes=32 time=1ms TTL=64
Reply from 10.0.0.20: bytes=32 time=1ms TTL=64
Reply from 10.0.0.20: bytes=32 time=1ms TTL=64
Reply from 10.0.0.20: bytes=32 time=1ms TTL=64
Reply from 10.0.0.20: bytes=32 time=1ms TTL=64
Reply from 10.0.0.20: bytes=32 time=1ms TTL=64
Reply from 10.0.0.20: bytes=32 time=1ms TTL=64
Reply from 10.0.0.20: bytes=32 time=1ms TTL=64
Reply from 10.0.0.20: bytes=32 time=3ms TTL=64
Reply from 10.0.0.20: bytes=32 time=1ms TTL=64
Reply from 10.0.0.20: bytes=32 time=1ms TTL=64
Reply from 10.0.0.20: bytes=32 time=1ms TTL=64
Reply from 10.0.0.20: bytes=32 time=1ms TTL=64
Reply from 10.0.0.20: bytes=32 time<1ms TTL=64
Reply from 10.0.0.20: bytes=32 time=1ms TTL=64
Reply from 10.0.0.20: bytes=32 time<1ms TTL=64
Reply from 10.0.0.20: bytes=32 time=1ms TTL=64
Reply from 10.0.0.20: bytes=32 time<1ms TTL=64
Reply from 10.0.0.20: bytes=32 time=1ms TTL=64
Reply from 10.0.0.20: bytes=32 time=2ms TTL=64
Reply from 10.0.0.20: bytes=32 time=1ms TTL=64
Reply from 10.0.0.20: bytes=32 time=2ms TTL=64
Reply from 10.0.0.20: bytes=32 time=1ms TTL=64
Reply from 10.0.0.20: bytes=32 time<1ms TTL=64
Reply from 10.0.0.20: bytes=32 time=1ms TTL=64
Reply from 10.0.0.20: bytes=32 time=1ms TTL=64
Reply from 10.0.0.20: bytes=32 time=1ms TTL=64
Reply from 10.0.0.20: bytes=32 time=2ms TTL=64
Reply from 10.0.0.20: bytes=32 time=1ms TTL=64
Reply from 10.0.0.20: bytes=32 time=1ms TTL=64
Reply from 10.0.0.20: bytes=32 time=1ms TTL=64
Reply from 10.0.0.20: bytes=32 time=1ms TTL=64
Reply from 10.0.0.20: bytes=32 time=1ms TTL=64
Reply from 10.0.0.20: bytes=32 time=3ms TTL=64
Reply from 10.0.0.20: bytes=32 time=1ms TTL=64
Reply from 10.0.0.20: bytes=32 time<1ms TTL=64
Reply from 10.0.0.20: bytes=32 time=4ms TTL=64
Reply from 10.0.0.20: bytes=32 time=1ms TTL=64
Reply from 10.0.0.20: bytes=32 time=1ms TTL=64
Reply from 10.0.0.20: bytes=32 time=1ms TTL=64
Reply from 10.0.0.20: bytes=32 time=1ms TTL=64
Reply from 10.0.0.20: bytes=32 time<1ms TTL=64
Reply from 10.0.0.20: bytes=32 time<1ms TTL=64
Reply from 10.0.0.20: bytes=32 time=2ms TTL=64

Ping statistics for 10.0.0.20:
Packets: Sent = 101, Received = 101, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 4ms, Average = 1ms

C:\Users\Hubert>tracert 10.0.0.20

Tracing route to 10.0.0.20 over a maximum of 30 hops

1 1 ms <1 ms <1 ms 10.0.0.20
Sorry for long post :)
Top
 
lfs0a
newbie
Topic Author
Posts: 36
Joined: Wed Jun 05, 2013 5:47 am

Re: ping delay 40-80ms

Thu Jun 13, 2013 5:40 am

:D Thanks a lot for you long post.
dozens of people saw my post and didn't make a reply,maybe they don't have a rb751 or rb951 device?

so the teddy-bear1 connect to ap1-mt through radio,right?
the ping test looks good,the delay is small and stable.
so my device which had returned purchase is definitely something wrong.
i'm gonna buy another one :lol:
Top
 
lfs0a
newbie
Topic Author
Posts: 36
Joined: Wed Jun 05, 2013 5:47 am

Re: ping delay 40-80ms

Thu Jun 13, 2013 6:27 am

:lol: i missed the secend tracert.
Top
 
HaPe
Member Candidate
Member Candidate
Posts: 239
Joined: Fri Feb 10, 2012 10:24 pm
Location: Poland

Re: ping delay 40-80ms

Thu Jun 13, 2013 11:08 pm

Yes, it is via wireless. But interfaces to manage are in vlans and routing is need :)
Top
 
lfs0a
newbie
Topic Author
Posts: 36
Joined: Wed Jun 05, 2013 5:47 am

Re: ping delay 40-80ms

Fri Jun 14, 2013 5:11 pm

i saw the sudden raise of the time. :lol:
Top
Post Reply

Who is online

Users browsing this forum: Amazon [Bot], frankpp, infabo, mstanciu, quantumx and 34 guests
  4. RouterOS
  5. Wireless Networking