Hopefully this will help you help me but I have no idea what any of this meens.
Here is the output of 'ip route list table all' from my working kernel (with network working)
192.168.10.0/24 dev eth0 proto kernel scope link src 192.168.10.2
default via 192.168.10.1 dev eth0
broadcast 127.255.255.255 dev lo table 255 proto kernel scope link src 127.0.0.1
broadcast 192.168.10.255 dev eth0 table 255 proto kernel scope link src 192.168.10.2
local 192.168.10.2 dev eth0 table 255 proto kernel scope host src 192.168.10.2
broadcast 192.168.10.0 dev eth0 table 255 proto kernel scope link src 192.168.10.2
broadcast 127.0.0.0 dev lo table 255 proto kernel scope link src 127.0.0.1
local 127.0.0.1 dev lo table 255 proto kernel scope host src 127.0.0.1
local 127.0.0.0/8 dev lo table 255 proto kernel scope host src 127.0.0.1
local ::1 via :: dev lo proto none metric 0 mtu 16436 advmss 16376 hoplimit 4294967295
local fe80::208:a1ff:fe03:f114 via :: dev lo proto none metric 0 mtu 16436 advmss 16376 hoplimit 4294967295
fe80::/64 dev eth0 metric 256 expires 8532984sec mtu 1500 advmss 1440 hoplimit 4294967295
ff00::/8 dev eth0 metric 256 expires 8532984sec mtu 1500 advmss 1440 hoplimit 4294967295
unreachable default dev lo proto none metric -1 error -101 hoplimit 255
Now, here is the output of the same command using the ovz kernel.
192.168.10.0/24 dev eth0 proto kernel scope link src 192.168.10.2
default via 192.168.10.1 dev eth0
broadcast 127.255.255.255 dev lo table 255 proto kernel scope link src 127.0.0.1
broadcast 192.168.10.255 dev eth0 table 255 proto kernel scope link src 192.168.10.2
local 192.168.10.2 dev eth0 table 255 proto kernel scope host src 192.168.10.2
broadcast 192.168.10.0 dev eth0 table 255 proto kernel scope link src 192.168.10.2
broadcast 127.0.0.0 dev lo table 255 proto kernel scope link src 127.0.0.1
local 127.0.0.1 dev lo table 255 proto kernel scope host src 127.0.0.1
local 127.0.0.0/8 dev lo table 255 proto kernel scope host src 127.0.0.1
local ::1 via :: dev lo proto none metric 0 mtu 16436 advmss 16376 hoplimit 4294967295
local fe80::208:a1ff:fe03:f114 via :: dev lo proto none metric 0 mtu 16436 advmss 16376 hoplimit 4294967295
fe80::/64 dev eth0 metric 256 expires 2133431sec mtu 1500 advmss 1440 hoplimit 4294967295
ff00::/8 dev eth0 metric 256 expires 2133431sec mtu 1500 advmss 1440 hoplimit 4294967295
unreachable default dev lo proto none metric -1 error -101 hoplimit 255
And here is the outpuit of 'netstat -s' from my working kernel.
Ip:
36 total packets received
0 forwarded
0 incoming packets discarded
36 incoming packets delivered
36 requests sent out
Icmp:
0 ICMP messages received
0 input ICMP message failed.
ICMP input histogram:
0 ICMP messages sent
0 ICMP messages failed
ICMP output histogram:
Tcp:
0 active connections openings
0 passive connection openings
0 failed connection attempts
0 connection resets received
0 connections established
0 segments received
0 segments send out
0 segments retransmited
0 bad segments received.
0 resets sent
Udp:
36 packets received
0 packets to unknown port received.
0 packet receive errors
36 packets sent
TcpExt:
0 packet headers predicted
0 TCP data loss events
Finally, here is the output of the same command using the ovz kernel. This was ran after I ran 'ping -c 10 google.com' which ended up dying with 35% packet loss, after that I had no connection at all.
Ip:
53 total packets received
0 forwarded
0 incoming packets discarded
53 incoming packets delivered
58 requests sent out
Icmp:
9 ICMP messages received
1 input ICMP message failed.
ICMP input histogram:
destination unreachable: 2
echo replies: 7
2 ICMP messages sent
0 ICMP messages failed
ICMP output histogram:
destination unreachable: 2
Tcp:
1 active connections openings
0 passive connection openings
1 failed connection attempts
0 connection resets received
0 connections established
0 segments received
1 segments send out
1 segments retransmited
0 bad segments received.
0 resets sent
Udp:
44 packets received
0 packets to unknown port received.
0 packet receive errors
44 packets sent
TcpExt:
0 packet headers predicted
0 TCP data loss events
1 other TCP timeouts
Im not sure what ip address to use with the suggested 'ip route get <ip_addr>' command as I really do not understand any of what is going on.
Am I seriosuly the only person this has happened too? I cannot find any information at all.
Thankyou very much for your time. I feel like an absolute newb again. Ive used Linux (Gentoo and now Debian) for around 4 years, just never had any network trouble.
[Updated on: Tue, 04 March 2008 05:26]
Report message to a moderator
OpenVZ Forum
Members
Search
Help
Register
Login
Home
