OpenVZ Forum


Home » General » Support » *SOLVED* VE networking not working properly- details included.
*SOLVED* VE networking not working properly- details included. [message #6816] Sun, 24 September 2006 02:59 Go to next message
HaroldB is currently offline  HaroldB
Messages: 61
Registered: June 2006
Member
Here is the problem:
Quote:


# vzctl enter 1000
entered into VPS 1000
-bash-3.00# traceroute 69.64.46.7
traceroute to 69.64.46.7 (69.64.46.7), 30 hops max, 38 byte packets
1 203.171.31.140 (203.171.31.140) 0.069 ms 0.032 ms 0.026 ms
2 203.171.31.140 (203.171.31.140) 0.030 ms !<10> 0.030 ms !<10> 0.026 ms !<10>
-bash-3.00#



VPS cannot estabilish connectivity to the net. Seems packets never leave the HN. (203.171.31.140 is the IP of the HN)

Here are the details:
----
HN Kernel:
Quote:


Linux digipower.vn 2.6.16-1.2133_FC5.026test015smp #1 SMP Thu Aug 3 18:17:42 MSD 2006 i686 athlon i386 GNU/Linux



Utils:
Quote:


# rpm -qa | grep vz
vzquota-3.0.8-1
vzctl-3.0.11-1
vzctl-lib-3.0.11-1
vzyum-2.4.0-11



HN ifconfig:
Quote:


# ifconfig
eth0 Link encap:Ethernet HWaddr 00:30:48:58:32:80
inet addr:203.171.31.140 Bcast:203.171.31.191 Mask:255.255.255.192
inet6 addr: fe80::230:48ff:fe58:3280/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:20560 errors:0 dropped:0 overruns:0 frame:0
TX packets:7406 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1779178 (1.6 MiB) TX bytes:920926 (899.3 KiB)
Interrupt:16

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:157 errors:0 dropped:0 overruns:0 frame:0
TX packets:157 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:17282 (16.8 KiB) TX bytes:17282 (16.8 KiB)

venet0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
UP BROADCAST POINTOPOINT RUNNING NOARP MTU:1500 Metric:1
RX packets:473 errors:0 dropped:0 overruns:0 frame:0
TX packets:385 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:42870 (41.8 KiB) TX bytes:32997 (32.2 KiB)



HN route:
Quote:


# route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
203.171.31.180 0.0.0.0 255.255.255.255 UH 0 0 0 venet0
203.171.31.128 0.0.0.0 255.255.255.192 U 0 0 0 eth0
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0
0.0.0.0 203.171.31.129 0.0.0.0 UG 0 0 0 eth0



HN vzlist:
Quote:


# vzlist
VPSID NPROC STATUS IP_ADDR HOSTNAME
1000 18 running 203.171.31.180 -



VPS ifconfig
Quote:


# ifconfig
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

venet0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
inet addr:127.0.0.1 P-t-P:127.0.0.1 Bcast:0.0.0.0 Mask:255.255.255.255
UP BROADCAST POINTOPOINT RUNNING NOARP MTU:1500 Metric:1
RX packets:101 errors:0 dropped:0 overruns:0 frame:0
TX packets:122 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:7544 (7.3 KiB) TX bytes:12992 (12.6 KiB)

venet0:0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
inet addr:203.171.31.180 P-t-P:203.171.31.180 Bcast:203.171.31.180 Mask:255.255.255.255
UP BROADCAST POINTOPOINT RUNNING NOARP MTU:1500 Metric:1



VPS route:
Quote:


# route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
191.255.255.0 0.0.0.0 255.255.255.0 U 0 0 0 venet0
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 venet0
0.0.0.0 191.255.255.1 0.0.0.0 UG 0 0 0 venet0



Tcpdump on HN for venet0 while VPS is pinging openvz.org:
Quote:


# tcpdump -vv -n -i venet0
tcpdump: WARNING: arptype 65535 not supported by libpcap - falling back to cooked socket
tcpdump: WARNING: venet0: no IPv4 address assigned
tcpdump: listening on venet0, link-type LINUX_SLL (Linux cooked), capture size 96 bytes
10:56:21.535226 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto: ICMP (1), length: 84) 203.171.31.180 > 69.64.46.7: ICMP echo request, id 40468, seq 0, length 64
10:56:21.965067 IP (tos 0x0, ttl 48, id 25858, offset 0, flags [none], proto: ICMP (1), length: 84) 69.64.46.7 > 203.171.31.180: ICMP echo reply, id 40468, seq 0, length 64
10:56:22.536141 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto: ICMP (1), length: 84) 203.171.31.180 > 69.64.46.7: ICMP echo request, id 40468, seq 1, length 64



Tcpdump on HN for eth0 while VPS is pinging openvz.org:
Quote:


[root@digipower ~]# tcpdump -vv -n -i eth0 dst net 69.64.46.7
tcpdump: listening on eth0, link-type EN10MB (Ethernet), capture size 96 bytes
10:57:26.917824 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto: ICMP (1), length: 84) 203.171.31.180 > 69.64.46.7: ICMP echo request, id 42772, seq 0, length 64
10:57:27.919136 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto: ICMP (1), length: 84) 203.171.31.180 > 69.64.46.7: ICMP echo request, id 42772, seq 1, length 64
10:57:28.923253 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto: ICMP (1), length: 84) 203.171.31.180 > 69.64.46.7: ICMP echo request, id 42772, seq 2, length 64




[Updated on: Tue, 26 September 2006 10:48] by Moderator

Report message to a moderator

Re: VE networking not working properly- details included. [message #6817 is a reply to message #6816] Sun, 24 September 2006 03:39 Go to previous messageGo to next message
HaroldB is currently offline  HaroldB
Messages: 61
Registered: June 2006
Member
Hi, I used the network diagnostics script ( http://forum.openvz.org/index.php?t=tree&goto=6358&# msg_6358) on this. Results are:

# ./test.sh
? (203.171.31.129) at 00:0A:8A:D8:49:FF [ether] on eth0
digipower.vn (203.171.31.180) at * PERM PUP on eth0

Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
203.171.31.180 0.0.0.0 255.255.255.255 UH 0 0 0 venet0
203.171.31.128 0.0.0.0 255.255.255.192 U 0 0 0 eth0
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0
0.0.0.0 203.171.31.129 0.0.0.0 UG 0 0 0 eth0

Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
191.255.255.0 0.0.0.0 255.255.255.0 U 0 0 0 venet0
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 venet0
0.0.0.0 191.255.255.1 0.0.0.0 UG 0 0 0 venet0

venet0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
inet addr:127.0.0.1 P-t-P:127.0.0.1 Bcast:0.0.0.0 Mask:255.255.255.255
UP BROADCAST POINTOPOINT RUNNING NOARP MTU:1500 Metric:1
RX packets:143 errors:0 dropped:0 overruns:0 frame:0
TX packets:179 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:11080 (10.8 KiB) TX bytes:17732 (17.3 KiB)

tcpdump: WARNING: arptype 65535 not supported by libpcap - falling back to cooked socket
tcpdump: WARNING: venet0: no IPv4 address assigned
tcpdump: listening on venet0, link-type LINUX_SLL (Linux cooked), capture size 96 bytes

[[[[ CONTROL C ]]]]


0 packets captured
0 packets received by filter
0 packets dropped by kernel
venet0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
inet addr:127.0.0.1 P-t-P:127.0.0.1 Bcast:0.0.0.0 Mask:255.255.255.255
UP BROADCAST POINTOPOINT RUNNING NOARP MTU:1500 Metric:1
RX packets:143 errors:0 dropped:0 overruns:0 frame:0
TX packets:179 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:11080 (10.8 KiB) TX bytes:17732 (17.3 KiB)
Re: VE networking not working properly- details included. [message #6820 is a reply to message #6816] Sun, 24 September 2006 05:45 Go to previous messageGo to next message
HaroldB is currently offline  HaroldB
Messages: 61
Registered: June 2006
Member
fixed by flushing HN firewall.. Rolling Eyes

moderator, you can delte this thread, its kinda silly..
Re: VE networking not working properly- details included. [message #6830 is a reply to message #6820] Sun, 24 September 2006 19:08 Go to previous message
John Kelly is currently offline  John Kelly
Messages: 97
Registered: May 2006
Location: Palmetto State
Member
HaroldB wrote on Sun, 24 September 2006 01:45

moderator, you can delte this thread, its kinda silly..


Please don't do that.

Vass asked me to write up the network diagnostics script in the wiki. Did the script help you see the problem? I need some feedback to get motivated ...

Previous Topic: Fastest/most efficient method to get list of PIDs for VE
Next Topic: *SOLVED* capabilities of vzmigrate
Goto Forum:
  


Current Time: Sat Nov 02 14:28:48 GMT 2024

Total time taken to generate the page: 0.03179 seconds