Community

View unanswered posts | View active topics


Board index » NeoRouter Forums » Mac OS X / Linux / FreeBSD / Android / in-a-box

All times are UTC - 5 hours




Post new topic Reply to topic  Page 1 of 1
  [ 4 posts ] 
  Print view Previous topic | Next topic 
Author Message
LilleCarl
 Post subject: Packet losses
PostPosted: Wed Jun 06, 2012 10:27 am 
Offline

Joined: Tue Jun 05, 2012 10:41 am
Posts: 5
Location: Sweden
Hello again!
I would just like to check if anyone else have/had packet loss issues and what might be causing them.

Here is a few ping's ive done

A friends computer:
Code:
Pinging 13.37.0.10 with 32 bytes of data:
Reply from 13.37.0.10: bytes=32 time=46ms TTL=128
Reply from 13.37.0.10: bytes=32 time=46ms TTL=128
Request timed out.
Reply from 13.37.0.10: bytes=32 time=45ms TTL=128
Reply from 13.37.0.10: bytes=32 time=62ms TTL=128
Reply from 13.37.0.10: bytes=32 time=292ms TTL=128
Reply from 13.37.0.10: bytes=32 time=135ms TTL=128
Reply from 13.37.0.10: bytes=32 time=47ms TTL=128
Reply from 13.37.0.10: bytes=32 time=47ms TTL=128
Request timed out.
Request timed out.
Reply from 13.37.0.10: bytes=32 time=164ms TTL=128
Reply from 13.37.0.10: bytes=32 time=161ms TTL=128
Reply from 13.37.0.10: bytes=32 time=47ms TTL=128
Reply from 13.37.0.10: bytes=32 time=46ms TTL=128
Reply from 13.37.0.10: bytes=32 time=46ms TTL=128
Reply from 13.37.0.10: bytes=32 time=113ms TTL=128
Reply from 13.37.0.10: bytes=32 time=70ms TTL=128
Reply from 13.37.0.10: bytes=32 time=156ms TTL=128
Reply from 13.37.0.10: bytes=32 time=46ms TTL=128
Reply from 13.37.0.10: bytes=32 time=135ms TTL=128
Reply from 13.37.0.10: bytes=32 time=46ms TTL=128
Reply from 13.37.0.10: bytes=32 time=88ms TTL=128
Request timed out.
Reply from 13.37.0.10: bytes=32 time=44ms TTL=128
Request timed out.
Reply from 13.37.0.10: bytes=32 time=45ms TTL=128
Reply from 13.37.0.10: bytes=32 time=45ms TTL=128
Reply from 13.37.0.10: bytes=32 time=51ms TTL=128
Request timed out.
Reply from 13.37.0.10: bytes=32 time=46ms TTL=128
Reply from 13.37.0.10: bytes=32 time=46ms TTL=128
Reply from 13.37.0.10: bytes=32 time=75ms TTL=128
Reply from 13.37.0.10: bytes=32 time=46ms TTL=128
Reply from 13.37.0.10: bytes=32 time=45ms TTL=128
Request timed out.
Reply from 13.37.0.10: bytes=32 time=46ms TTL=128
Reply from 13.37.0.10: bytes=32 time=48ms TTL=128
Reply from 13.37.0.10: bytes=32 time=48ms TTL=128
Request timed out.
Reply from 13.37.0.10: bytes=32 time=46ms TTL=128
Reply from 13.37.0.10: bytes=32 time=45ms TTL=128
Reply from 13.37.0.10: bytes=32 time=45ms TTL=128
Reply from 13.37.0.10: bytes=32 time=51ms TTL=128
Reply from 13.37.0.10: bytes=32 time=69ms TTL=128
Reply from 13.37.0.10: bytes=32 time=46ms TTL=128
Reply from 13.37.0.10: bytes=32 time=44ms TTL=128
Reply from 13.37.0.10: bytes=32 time=46ms TTL=128
Reply from 13.37.0.10: bytes=32 time=44ms TTL=128
Reply from 13.37.0.10: bytes=32 time=45ms TTL=128
Reply from 13.37.0.10: bytes=32 time=48ms TTL=128
Reply from 13.37.0.10: bytes=32 time=89ms TTL=128
Request timed out.
Reply from 13.37.0.10: bytes=32 time=85ms TTL=128
Reply from 13.37.0.10: bytes=32 time=46ms TTL=128
Reply from 13.37.0.10: bytes=32 time=48ms TTL=128
Reply from 13.37.0.10: bytes=32 time=47ms TTL=128

Ping statistics for 13.37.0.10:
    Packets: Sent = 57, Received = 48, Lost = 9 (15% lo
Approximate round trip times in milli-seconds:
    Minimum = 44ms, Maximum = 292ms, Average = 68ms


Client run on the NR server computer:
Code:
Pinging 13.37.0.19 with 32 bytes of data:
Reply from 13.37.0.19: bytes=32 time=59ms TTL=64
Reply from 13.37.0.19: bytes=32 time=58ms TTL=64
Reply from 13.37.0.19: bytes=32 time=59ms TTL=64
Reply from 13.37.0.19: bytes=32 time=59ms TTL=64
Reply from 13.37.0.19: bytes=32 time=59ms TTL=64
Reply from 13.37.0.19: bytes=32 time=59ms TTL=64
Reply from 13.37.0.19: bytes=32 time=59ms TTL=64
Reply from 13.37.0.19: bytes=32 time=59ms TTL=64
Reply from 13.37.0.19: bytes=32 time=59ms TTL=64
Reply from 13.37.0.19: bytes=32 time=308ms TTL=64
Reply from 13.37.0.19: bytes=32 time=59ms TTL=64
Reply from 13.37.0.19: bytes=32 time=60ms TTL=64
Reply from 13.37.0.19: bytes=32 time=60ms TTL=64
Reply from 13.37.0.19: bytes=32 time=316ms TTL=64
Reply from 13.37.0.19: bytes=32 time=59ms TTL=64
Reply from 13.37.0.19: bytes=32 time=117ms TTL=64
Reply from 13.37.0.19: bytes=32 time=62ms TTL=64
Reply from 13.37.0.19: bytes=32 time=129ms TTL=64
Reply from 13.37.0.19: bytes=32 time=377ms TTL=64
Request timed out.
Reply from 13.37.0.19: bytes=32 time=62ms TTL=64
Reply from 13.37.0.19: bytes=32 time=323ms TTL=64
Reply from 13.37.0.19: bytes=32 time=61ms TTL=64
Reply from 13.37.0.19: bytes=32 time=62ms TTL=64
Reply from 13.37.0.19: bytes=32 time=62ms TTL=64
Reply from 13.37.0.19: bytes=32 time=287ms TTL=64
Reply from 13.37.0.19: bytes=32 time=320ms TTL=64
Reply from 13.37.0.19: bytes=32 time=62ms TTL=64
Reply from 13.37.0.19: bytes=32 time=315ms TTL=64
Reply from 13.37.0.19: bytes=32 time=314ms TTL=64
Reply from 13.37.0.19: bytes=32 time=317ms TTL=64
Reply from 13.37.0.19: bytes=32 time=312ms TTL=64
Reply from 13.37.0.19: bytes=32 time=310ms TTL=64
Reply from 13.37.0.19: bytes=32 time=119ms TTL=64
Reply from 13.37.0.19: bytes=32 time=310ms TTL=64
Request timed out.
Request timed out.
Reply from 13.37.0.19: bytes=32 time=190ms TTL=64
Reply from 13.37.0.19: bytes=32 time=61ms TTL=64
Request timed out.
Request timed out.
Reply from 13.37.0.19: bytes=32 time=62ms TTL=64
Reply from 13.37.0.19: bytes=32 time=62ms TTL=64
Reply from 13.37.0.19: bytes=32 time=62ms TTL=64
Request timed out.
Reply from 13.37.0.19: bytes=32 time=63ms TTL=64
Reply from 13.37.0.19: bytes=32 time=119ms TTL=64

Ping statistics for 13.37.0.19:
    Packets: Sent = 47, Received = 41, Lost = 6 (12% loss),
Approximate round trip times in milli-seconds:
    Minimum = 58ms, Maximum = 377ms, Average = 144ms


Another friend:
Code:
Pinging 13.37.0.3 with 32 bytes of data:
Request timed out.
Reply from 13.37.0.3: bytes=32 time=76ms TTL=128
Reply from 13.37.0.3: bytes=32 time=76ms TTL=128
Reply from 13.37.0.3: bytes=32 time=72ms TTL=128
Reply from 13.37.0.3: bytes=32 time=75ms TTL=128
Request timed out.
Reply from 13.37.0.3: bytes=32 time=80ms TTL=128
Request timed out.
Reply from 13.37.0.3: bytes=32 time=72ms TTL=128
Reply from 13.37.0.3: bytes=32 time=71ms TTL=128
Request timed out.
Request timed out.
Request timed out.
Reply from 13.37.0.3: bytes=32 time=74ms TTL=128
Request timed out.
Reply from 13.37.0.3: bytes=32 time=70ms TTL=128
Reply from 13.37.0.3: bytes=32 time=72ms TTL=128
Request timed out.
Reply from 13.37.0.3: bytes=32 time=71ms TTL=128
Reply from 13.37.0.3: bytes=32 time=179ms TTL=128
Request timed out.
Reply from 13.37.0.3: bytes=32 time=72ms TTL=128
Reply from 13.37.0.3: bytes=32 time=79ms TTL=128
Reply from 13.37.0.3: bytes=32 time=84ms TTL=128
Reply from 13.37.0.3: bytes=32 time=65ms TTL=128
Reply from 13.37.0.3: bytes=32 time=74ms TTL=128
Reply from 13.37.0.3: bytes=32 time=77ms TTL=128
Reply from 13.37.0.3: bytes=32 time=66ms TTL=128
Reply from 13.37.0.3: bytes=32 time=67ms TTL=128

Ping statistics for 13.37.0.3:
    Packets: Sent = 29, Received = 20, Lost = 9 (31% loss),
Approximate round trip times in milli-seconds:
    Minimum = 65ms, Maximum = 179ms, Average = 78ms


If you need more information just tell me =) I just want to check out if the issue is related to my NR server or something else.

Also to note: I live in Sweden but my VPS is located in Holland (Amsterdam) But im goign to move it to Sweden to decrease possible lag

Best regards
Carl Hjerpe

_________________
Violence doesn't solve shit, but everything else.

Top
 Profile  
 
kevinz
 Post subject: Re: Packet losses
PostPosted: Wed Jun 06, 2012 11:57 am 
Offline

Joined: Sun Nov 16, 2008 6:41 am
Posts: 1878
Hi LilleCarl,

Maybe you can check this:

1.ping the public IP of the target machine, instead of the virtual IP, see what do you get. This can test your physical network stability.

2.check the CPU usage of both source and target machines while ping see if any other app use too much CPU and slow down NR service. NR service need to process the packets before/after send/receive them.

3.Other concerns:
Since it's a VPS hosted by a physical machine and other VPSs on this machine share the network/CPU with yours, if they use too much bandwidth or CPU, you cannot see it, but it DOES affect yours app and network usage. On the host machine, the provider may also put traffic shaper or other policy on it (Only can the provider see this)

Thanks,
KevinZ - NeoRouter team
Top
 Profile  
 
LilleCarl
 Post subject: Re: Packet losses
PostPosted: Wed Jun 06, 2012 1:34 pm 
Offline

Joined: Tue Jun 05, 2012 10:41 am
Posts: 5
Location: Sweden
Might have something with the server to do, i just moved it to Sweden (My VPS provider supports moving of openvz boxes) here is new feedback on ping

NeoRouter
Code:
Pinging 13.37.0.19 with 32 bytes of data:
Reply from 13.37.0.19: bytes=32 time=82ms TTL=64
Reply from 13.37.0.19: bytes=32 time=33ms TTL=64
Reply from 13.37.0.19: bytes=32 time=33ms TTL=64
Reply from 13.37.0.19: bytes=32 time=33ms TTL=64
Reply from 13.37.0.19: bytes=32 time=34ms TTL=64
Reply from 13.37.0.19: bytes=32 time=33ms TTL=64
Reply from 13.37.0.19: bytes=32 time=33ms TTL=64
Reply from 13.37.0.19: bytes=32 time=34ms TTL=64
Reply from 13.37.0.19: bytes=32 time=33ms TTL=64
Reply from 13.37.0.19: bytes=32 time=33ms TTL=64
Reply from 13.37.0.19: bytes=32 time=34ms TTL=64
Reply from 13.37.0.19: bytes=32 time=33ms TTL=64
Reply from 13.37.0.19: bytes=32 time=33ms TTL=64
Reply from 13.37.0.19: bytes=32 time=34ms TTL=64
Reply from 13.37.0.19: bytes=32 time=33ms TTL=64
Reply from 13.37.0.19: bytes=32 time=35ms TTL=64
Reply from 13.37.0.19: bytes=32 time=41ms TTL=64
Reply from 13.37.0.19: bytes=32 time=37ms TTL=64
Reply from 13.37.0.19: bytes=32 time=36ms TTL=64
Reply from 13.37.0.19: bytes=32 time=35ms TTL=64
Reply from 13.37.0.19: bytes=32 time=35ms TTL=64
Reply from 13.37.0.19: bytes=32 time=33ms TTL=64
Reply from 13.37.0.19: bytes=32 time=33ms TTL=64
Reply from 13.37.0.19: bytes=32 time=33ms TTL=64
Reply from 13.37.0.19: bytes=32 time=34ms TTL=64
Reply from 13.37.0.19: bytes=32 time=34ms TTL=64
Reply from 13.37.0.19: bytes=32 time=34ms TTL=64
Reply from 13.37.0.19: bytes=32 time=33ms TTL=64
Reply from 13.37.0.19: bytes=32 time=32ms TTL=64
Reply from 13.37.0.19: bytes=32 time=33ms TTL=64
Reply from 13.37.0.19: bytes=32 time=35ms TTL=64
Reply from 13.37.0.19: bytes=32 time=34ms TTL=64
Reply from 13.37.0.19: bytes=32 time=34ms TTL=64
Reply from 13.37.0.19: bytes=32 time=37ms TTL=64
Reply from 13.37.0.19: bytes=32 time=37ms TTL=64
Reply from 13.37.0.19: bytes=32 time=32ms TTL=64
Reply from 13.37.0.19: bytes=32 time=32ms TTL=64
Reply from 13.37.0.19: bytes=32 time=33ms TTL=64
Reply from 13.37.0.19: bytes=32 time=34ms TTL=64
Reply from 13.37.0.19: bytes=32 time=33ms TTL=64
Reply from 13.37.0.19: bytes=32 time=33ms TTL=64
Reply from 13.37.0.19: bytes=32 time=33ms TTL=64
Reply from 13.37.0.19: bytes=32 time=33ms TTL=64
Reply from 13.37.0.19: bytes=32 time=35ms TTL=64
Reply from 13.37.0.19: bytes=32 time=33ms TTL=64
Reply from 13.37.0.19: bytes=32 time=109ms TTL=64
Reply from 13.37.0.19: bytes=32 time=34ms TTL=64
Reply from 13.37.0.19: bytes=32 time=44ms TTL=64
Reply from 13.37.0.19: bytes=32 time=33ms TTL=64
Reply from 13.37.0.19: bytes=32 time=97ms TTL=64
Reply from 13.37.0.19: bytes=32 time=33ms TTL=64
Reply from 13.37.0.19: bytes=32 time=34ms TTL=64
Reply from 13.37.0.19: bytes=32 time=33ms TTL=64
Reply from 13.37.0.19: bytes=32 time=33ms TTL=64
Reply from 13.37.0.19: bytes=32 time=33ms TTL=64

Ping statistics for 13.37.0.19:
    Packets: Sent = 55, Received = 55, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 32ms, Maximum = 109ms, Average = 37ms


Public ip:
Code:
Pinging lillecarl.ath.cx [31.192.227.181] with 32 bytes of data:
Reply from 31.192.227.181: bytes=32 time=31ms TTL=51
Reply from 31.192.227.181: bytes=32 time=32ms TTL=51
Reply from 31.192.227.181: bytes=32 time=32ms TTL=51
Reply from 31.192.227.181: bytes=32 time=32ms TTL=51
Reply from 31.192.227.181: bytes=32 time=31ms TTL=51
Reply from 31.192.227.181: bytes=32 time=31ms TTL=51
Reply from 31.192.227.181: bytes=32 time=32ms TTL=51
Reply from 31.192.227.181: bytes=32 time=32ms TTL=51
Reply from 31.192.227.181: bytes=32 time=32ms TTL=51
Reply from 31.192.227.181: bytes=32 time=32ms TTL=51
Reply from 31.192.227.181: bytes=32 time=33ms TTL=51
Reply from 31.192.227.181: bytes=32 time=32ms TTL=51
Reply from 31.192.227.181: bytes=32 time=32ms TTL=51
Reply from 31.192.227.181: bytes=32 time=31ms TTL=51
Reply from 31.192.227.181: bytes=32 time=32ms TTL=51
Reply from 31.192.227.181: bytes=32 time=32ms TTL=51
Reply from 31.192.227.181: bytes=32 time=31ms TTL=51
Reply from 31.192.227.181: bytes=32 time=32ms TTL=51
Reply from 31.192.227.181: bytes=32 time=32ms TTL=51
Reply from 31.192.227.181: bytes=32 time=32ms TTL=51
Reply from 31.192.227.181: bytes=32 time=33ms TTL=51
Reply from 31.192.227.181: bytes=32 time=31ms TTL=51
Reply from 31.192.227.181: bytes=32 time=31ms TTL=51
Reply from 31.192.227.181: bytes=32 time=32ms TTL=51
Reply from 31.192.227.181: bytes=32 time=31ms TTL=51
Reply from 31.192.227.181: bytes=32 time=32ms TTL=51
Reply from 31.192.227.181: bytes=32 time=32ms TTL=51
Reply from 31.192.227.181: bytes=32 time=32ms TTL=51
Reply from 31.192.227.181: bytes=32 time=32ms TTL=51
Reply from 31.192.227.181: bytes=32 time=31ms TTL=51
Reply from 31.192.227.181: bytes=32 time=32ms TTL=51
Reply from 31.192.227.181: bytes=32 time=32ms TTL=51
Reply from 31.192.227.181: bytes=32 time=32ms TTL=51
Reply from 31.192.227.181: bytes=32 time=31ms TTL=51
Reply from 31.192.227.181: bytes=32 time=31ms TTL=51
Reply from 31.192.227.181: bytes=32 time=32ms TTL=51
Reply from 31.192.227.181: bytes=32 time=31ms TTL=51
Reply from 31.192.227.181: bytes=32 time=32ms TTL=51
Reply from 31.192.227.181: bytes=32 time=32ms TTL=51
Reply from 31.192.227.181: bytes=32 time=32ms TTL=51
Reply from 31.192.227.181: bytes=32 time=31ms TTL=51
Reply from 31.192.227.181: bytes=32 time=31ms TTL=51
Reply from 31.192.227.181: bytes=32 time=33ms TTL=51
Reply from 31.192.227.181: bytes=32 time=32ms TTL=51
Reply from 31.192.227.181: bytes=32 time=31ms TTL=51
Reply from 31.192.227.181: bytes=32 time=32ms TTL=51
Reply from 31.192.227.181: bytes=32 time=32ms TTL=51
Reply from 31.192.227.181: bytes=32 time=31ms TTL=51
Reply from 31.192.227.181: bytes=32 time=31ms TTL=51
Reply from 31.192.227.181: bytes=32 time=31ms TTL=51

Ping statistics for 31.192.227.181:
    Packets: Sent = 50, Received = 50, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 31ms, Maximum = 33ms, Average = 31ms


Seems like neorouter just have a few ms higher, which does not matter in my case (everything under 150 is good imo)

This is to wone of my friends:
Code:
Pinging 13.37.0.10 with 32 bytes of data:
Reply from 13.37.0.10: bytes=32 time=272ms TTL=128
Reply from 13.37.0.10: bytes=32 time=254ms TTL=128
Reply from 13.37.0.10: bytes=32 time=354ms TTL=128
Request timed out.
Reply from 13.37.0.10: bytes=32 time=275ms TTL=128
Reply from 13.37.0.10: bytes=32 time=245ms TTL=128
Reply from 13.37.0.10: bytes=32 time=270ms TTL=128
Reply from 13.37.0.10: bytes=32 time=75ms TTL=128
Reply from 13.37.0.10: bytes=32 time=78ms TTL=128
Reply from 13.37.0.10: bytes=32 time=410ms TTL=128
Reply from 13.37.0.10: bytes=32 time=223ms TTL=128
Reply from 13.37.0.10: bytes=32 time=311ms TTL=128
Reply from 13.37.0.10: bytes=32 time=72ms TTL=128
Request timed out.
Reply from 13.37.0.10: bytes=32 time=75ms TTL=128
Reply from 13.37.0.10: bytes=32 time=336ms TTL=128
Request timed out.
Reply from 13.37.0.10: bytes=32 time=318ms TTL=128
Reply from 13.37.0.10: bytes=32 time=77ms TTL=128
Reply from 13.37.0.10: bytes=32 time=123ms TTL=128
Request timed out.
Reply from 13.37.0.10: bytes=32 time=110ms TTL=128
Request timed out.

Ping statistics for 13.37.0.10:
    Packets: Sent = 23, Received = 18, Lost = 5 (21% loss),
Approximate round trip times in milli-seconds:
    Minimum = 72ms, Maximum = 410ms, Average = 215ms


Do this mean his connection is awful? And if i choose tcp/udp the data does not go trough NeoRouter, am i right?

EDIT: Regarding CPU usage, i think OpenVZ does allocate CPU's per user, but you are right about network to 100%. Tho, i do not have the money to rent a dedicated server :/

Thanks again
- Carl

_________________
Violence doesn't solve shit, but everything else.

Top
 Profile  
 
kevinz
 Post subject: Re: Packet losses
PostPosted: Wed Jun 06, 2012 3:45 pm 
Offline

Joined: Sun Nov 16, 2008 6:41 am
Posts: 1878
Hi LilleCarl,

Looks like the network of your friend is not good enough. If it is > 300ms, you can feel slow. I think it's on his side. If he run some apps, especially p2p file sharing apps like BT, it may eat a lot of network bandwidth.

NR Clients try to create UDP Peer to peer directly connections by default and relay packets over the NR server when it fails to create P2P connection.

Thanks,
KevinZ - NeoRouter team
Top
 Profile  
 
Display posts from previous:  Sort by  
Post new topic Reply to topic  Page 1 of 1
  [ 4 posts ] 

Board index » NeoRouter Forums » Mac OS X / Linux / FreeBSD / Android / in-a-box

All times are UTC - 5 hours


Who is online

Users browsing this forum: No registered users and 19 guests

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to: