| Re: Packet loss problem [message #7215 is a reply to message #7143] |
Sat, 07 October 2006 07:27   |
enigmaYmee
Messages: 5
Registered: October 2006
|
Junior Member |
|
|
The problem is definately on the HN as I haven't setup any VE's yet. I have to solve this problem before I can procede since working over SSH with this problem is nearly impossilbe.
I am using standard ping tools to determine the packet loss. Here is some output:
1. Ping from a windows box to the server running OpenVZ
| Quote: |
ping 192.168.1.200 -n 20
Pinging 192.168.1.200 with 32 bytes of data:
Request timed out.
Reply from 192.168.1.200: bytes=32 time=1426ms TTL=64
Reply from 192.168.1.200: bytes=32 time=1ms TTL=64
Request timed out.
Request timed out.
Reply from 192.168.1.200: bytes=32 time=3418ms TTL=64
Reply from 192.168.1.200: bytes=32 time=13ms TTL=64
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.1.200: bytes=32 time=573ms TTL=64
Reply from 192.168.1.200: bytes=32 time=1908ms TTL=64
Reply from 192.168.1.200: bytes=32 time<1ms TTL=64
Reply from 192.168.1.200: bytes=32 time=3999ms TTL=64
Reply from 192.168.1.200: bytes=32 time<1ms TTL=64
Request timed out.
Reply from 192.168.1.200: bytes=32 time=2575ms TTL=64
Request timed out.
Request timed out.
Reply from 192.168.1.200: bytes=32 time=395ms TTL=64
Ping statistics for 192.168.1.200:
Packets: Sent = 20, Received = 11, Lost = 9 (45% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 3999ms, Average = 1300ms
|
2. Ping from the server to the same windows box
| Quote: |
ping 192.168.1.105 -c 20
PING 192.168.1.105 (192.168.1.105) 56(84) bytes of data.
64 bytes from 192.168.1.105: icmp_seq=4 ttl=128 time=1996 ms
64 bytes from 192.168.1.105: icmp_seq=5 ttl=128 time=996 ms
64 bytes from 192.168.1.105: icmp_seq=6 ttl=128 time=45.3 ms
--- 192.168.1.105 ping statistics ---
20 packets transmitted, 3 received, 85% packet loss, time 18991ms
rtt min/avg/max/mdev = 45.366/1012.779/1996.225/796.515 ms, pipe 2
|
3. Here is some TCP pings from the server to the windows box
| Quote: |
hping 192.168.1.105 -c 20
HPING 192.168.1.105 (eth0 192.168.1.105): NO FLAGS are set, 40 headers + 0 data bytes
len=46 ip=192.168.1.105 ttl=128 id=32653 sport=0 flags=RA seq=0 win=0 rtt=254.1 ms
len=46 ip=192.168.1.105 ttl=128 id=32668 sport=0 flags=RA seq=11 win=0 rtt=4973.9 ms
len=46 ip=192.168.1.105 ttl=128 id=32669 sport=0 flags=RA seq=12 win=0 rtt=3973.5 ms
len=46 ip=192.168.1.105 ttl=128 id=32670 sport=0 flags=RA seq=13 win=0 rtt=2973.0 ms
len=46 ip=192.168.1.105 ttl=128 id=32671 sport=0 flags=RA seq=14 win=0 rtt=1972.5 ms
len=46 ip=192.168.1.105 ttl=128 id=32672 sport=0 flags=RA seq=15 win=0 rtt=972.0 ms
len=46 ip=192.168.1.105 ttl=128 id=32692 sport=0 flags=RA seq=16 win=0 rtt=1242.7 ms
len=46 ip=192.168.1.105 ttl=128 id=32693 sport=0 flags=RA seq=17 win=0 rtt=242.2 ms
--- 192.168.1.105 hping statistic ---
20 packets tramitted, 8 packets received, 60% packet loss
round-trip min/avg/max = 242.2/2075.5/4973.9 ms
|
4. Here are the stats of ping from the server to the windows box without the OpenVZ kernel
| Quote: |
--- 192.168.1.105 ping statistics ---
20 packets transmitted, 20 received, 0% packet loss, time 19148ms
rtt min/avg/max/mdev = 0.121/0.146/0.152/0.007 ms
|
Also I tried the 022.078 openvz kernel today using the config file from the download site. The only thing that was changed from the standard kernel config was the processor type. Change to K7 which is what the server is. I then tried just compiling it as 686 but I received an error during the compile.
make[1]: *** [arch/i386/kernel/asm-offsets.s] Error 1
make: *** [arch/i386/kernel/asm-offsets.s] Error 2
I then tried leaving the processor type as the default(Pentium Pro). This compiled but had the same effect.
**EDIT
I just tried the precompiled OpenVZ kernel 022.078 and I had the same problem. So this has to be something on my system thats causing it, but what?
[Updated on: Sat, 07 October 2006 08:26] Report message to a moderator |
|
|
|
OpenVZ Forum
Members
Search
Help
Register
Login
Home
