OpenVZ Forum: Support » connectivity again

Home » General » Support » connectivity again

Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend

Re: connectivity again [message #4781 is a reply to message #4775]

Wed, 26 July 2006 07:53

goeldi
Messages: 92
Registered: June 2006

Member

ifconfig -a (both in VE, HN)

in VE:
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:622 errors:0 dropped:0 overruns:0 frame:0
TX packets:622 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:338098 (330.1 KiB) TX bytes:338098 (330.1 KiB)

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:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:256 (256.0 b)

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

in HN:

eth0 Link encap:Ethernet HWaddr 00:0C:F1:94:A7:12
inet addr:195.141.143.42 Bcast:195.141.143.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:25585 errors:0 dropped:0 overruns:0 frame:0
TX packets:27554 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:3287071 (3.1 MiB) TX bytes:5102116 (4.8 MiB)
Interrupt:20 Base address:0xe000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:622 errors:0 dropped:0 overruns:0 frame:0
TX packets:622 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:338098 (330.1 KiB) TX bytes:338098 (330.1 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:26301 errors:0 dropped:0 overruns:0 frame:0
TX packets:23305 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:4518669 (4.3 MiB) TX bytes:2385399 (2.2 MiB)

route -n (both in VE, HN)

in VE:

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

in HN:

Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
195.141.1.94 0.0.0.0 255.255.255.255 UH 0 0 0 venet0
195.141.1.95 0.0.0.0 255.255.255.255 UH 0 0 0 venet0
195.141.1.92 0.0.0.0 255.255.255.255 UH 0 0 0 venet0
195.141.1.93 0.0.0.0 255.255.255.255 UH 0 0 0 venet0
195.141.143.0 0.0.0.0 255.255.255.0 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 195.141.143.1 0.0.0.0 UG 0 0 0 eth0

iptables -L -vn (both in VE, HN)

in VE:

Chain INPUT (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target prot opt in out source destination
0 0 RH-Firewall-1-INPUT all -- * * 0.0.0.0/0 0.0.0.0/0

Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target prot opt in out source destination
0 0 RH-Firewall-1-INPUT all -- * * 0.0.0.0/0 0.0.0.0/0

Chain OUTPUT (policy ACCEPT 4 packets, 288 bytes)
pkts bytes target prot opt in out source destination

Chain RH-Firewall-1-INPUT (2 references)
pkts bytes target prot opt in out source destination
0 0 ACCEPT all -- lo * 0.0.0.0/0 0.0.0.0/0
0 0 ACCEPT icmp -- * * 0.0.0.0/0 0.0.0.0/0 icmp type 255
0 0 ACCEPT esp -- * * 0.0.0.0/0 0.0.0.0/0
0 0 ACCEPT ah -- * * 0.0.0.0/0 0.0.0.0/0
0 0 ACCEPT udp -- * * 0.0.0.0/0 224.0.0.251 udp dpt:5353
0 0 ACCEPT udp -- * * 0.0.0.0/0 0.0.0.0/0 udp dpt:631
0 0 ACCEPT all -- * * 0.0.0.0/0 0.0.0.0/0 state RELATED,ESTABLISHED
0 0 ACCEPT tcp -- * * 0.0.0.0/0 0.0.0.0/0 state NEW tcp dpt:22
0 0 ACCEPT tcp -- * * 0.0.0.0/0 0.0.0.0/0 state NEW tcp dpt:80
0 0 ACCEPT tcp -- * * 0.0.0.0/0 0.0.0.0/0 state NEW tcp dpt:443
0 0 REJECT all -- * * 0.0.0.0/0 0.0.0.0/0 reject-with icmp-host-prohibited

in HN:

Chain INPUT (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target prot opt in out source destination
1929 532K RH-Firewall-1-INPUT all -- * * 0.0.0.0/0 0.0.0.0/0

Chain FORWARD (policy ACCEPT 50840 packets, 7054K bytes)
pkts bytes target prot opt in out source destination

Chain OUTPUT (policy ACCEPT 1291 packets, 208K bytes)
pkts bytes target prot opt in out source destination

Chain RH-Firewall-1-INPUT (1 references)
pkts bytes target prot opt in out source destination
2 100 ACCEPT all -- lo * 0.0.0.0/0 0.0.0.0/0
47 3948 ACCEPT icmp -- * * 0.0.0.0/0 0.0.0.0/0 icmp type 255
0 0 ACCEPT esp -- * * 0.0.0.0/0 0.0.0.0/0
0 0 ACCEPT ah -- * * 0.0.0.0/0 0.0.0.0/0
0 0 ACCEPT udp -- * * 0.0.0.0/0 224.0.0.251 udp dpt:5353
0 0 ACCEPT udp -- * * 0.0.0.0/0 0.0.0.0/0 udp dpt:631
1839 514K ACCEPT all -- * * 0.0.0.0/0 0.0.0.0/0 state RELATED,ESTABLISHED
0 0 ACCEPT tcp -- * * 212.98.47.70 0.0.0.0/0 state NEW tcp dpt:19150
0 0 ACCEPT tcp -- * * 212.98.47.70 0.0.0.0/0 state NEW tcp dpt:10000
1 60 ACCEPT tcp -- * * 0.0.0.0/0 0.0.0.0/0 state NEW tcp dpt:22
40 13196 REJECT all -- * * 0.0.0.0/0 0.0.0.0/0 reject-with icmp-host-prohibited

ping google by IP from VE: 64.233.167.99
Does it work?

no

pinging HW node, other VEs from the VE in question works?

both yes.

If it is possible, you can give me temporary access to your node and I'll try to fix the problem at place.

Unfortunately this is not possible because of the contracts.

[Updated on: Wed, 26 July 2006 07:53]

Report message to a moderator

[Message index]

		connectivity again By: goeldi on Mon, 24 July 2006 14:21
		Re: connectivity again By: Vasily Tarasov on Mon, 24 July 2006 14:29
		Re: connectivity again By: goeldi on Mon, 24 July 2006 14:35
		Re: connectivity again By: Valmont on Mon, 24 July 2006 19:56
		Re: connectivity again By: goeldi on Wed, 26 July 2006 07:17
		Re: connectivity again By: Vasily Tarasov on Wed, 26 July 2006 07:35
		Re: connectivity again By: goeldi on Wed, 26 July 2006 07:53
		Re: connectivity again By: Vasily Tarasov on Wed, 26 July 2006 08:15
		Re: connectivity again By: goeldi on Wed, 26 July 2006 09:32
		Re: connectivity again By: Vasily Tarasov on Wed, 26 July 2006 10:47
		Re: connectivity again By: goeldi on Wed, 26 July 2006 11:06
		Re: connectivity again By: Valmont on Wed, 26 July 2006 07:33
		Re: connectivity again By: aistis on Wed, 26 July 2006 10:46
		Re: connectivity again By: goeldi on Wed, 26 July 2006 11:07
		SOLVED: connectivity again By: goeldi on Thu, 27 July 2006 07:24
		NOT solved :-( By: goeldi on Thu, 27 July 2006 10:50
		Re: NOT solved :-( By: Vasily Tarasov on Thu, 27 July 2006 11:03
		Re: NOT solved :-( By: goeldi on Thu, 27 July 2006 11:08
		Re: NOT solved :-( By: Vasily Tarasov on Thu, 27 July 2006 11:18
		Re: NOT solved :-( By: goeldi on Thu, 27 July 2006 16:22
		Re: connectivity again By: aistis on Thu, 27 July 2006 15:17

Previous Topic:	SOLVED migration problem, right version now
Next Topic:	load balancing and migration between hardware nodes.

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Mon Sep 22 03:24:36 GMT 2025

Total time taken to generate the page: 0.06865 seconds