OpenVZ Forum: Support » networking, looking for pointers

Home » General » Support » networking, looking for pointers

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

networking, looking for pointers [message #13631]

Thu, 31 May 2007 10:25

slybob
Messages: 20
Registered: March 2007

Junior Member

We are having problems getting the VE's to see outside of the Vlan,

anyone got any ideas for debugging this? When I was using open VZ
before on a domestic netgear router, It just worked. The virtual machines could see in and I could route to the IP's I set no problem although the router couldnt see them as devices.

afaik, at the moment there is a cisco router connected to the pipe, with a firewall
connected to that, then my box is hooked into a switch which plugs
into the firewall (if that makes sense)

The sys admin has set up /24 vlan (192.168.101.0) for me

router routing table

  
S    192.168.101.0/24 [1/0] via 192.168.150.2  
S*   0.0.0.0/0 is directly connected, FastEthernet0/0

192.168.150.2 is the firewall, below is the rule for my subnet.

192.168.101/24     link#5             UC          0        0      -   hme2

Sorry if this doesn't make a lot of sense Smile

Cheers,

Andy

How I learned to stop worrying and love SMTP
http://www.moonet.co.uk/

Report message to a moderator

Re: networking, looking for pointers [message #13633 is a reply to message #13631]

Thu, 31 May 2007 11:03

dev
Messages: 1693
Registered: September 2005
Location: Moscow

Senior Member

From what I see on your machine, it had not tweaked sysctls
as described here: http://wiki.openvz.org/Quick_installation

I fixed this and now packets from VE go to eth2 device to the router, but see no replies on this interfaces :/

VE does:
ns:/# ping 194.85.83.97
PING 194.85.83.97 (194.85.83.97) 56(84) bytes of data.

while host node redirects these packets to eth2 as it should be.

debian:~# tcpdump -n -i eth2 host 194.85.83.97
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth2, link-type EN10MB (Ethernet), capture size 96 bytes
11:59:56.639608 IP 192.168.101.101 > 194.85.83.97: ICMP echo request, id 11570, seq 61, length 64
11:59:57.639608 IP 192.168.101.101 > 194.85.83.97: ICMP echo request, id 11570, seq 62, length 64
11:59:58.639664 IP 192.168.101.101 > 194.85.83.97: ICMP echo request, id 11570, seq 63, length 64

So you need to check router now, since packets are sent to this, but nothing returns back.
I'm also unsure why you meantion VLANs here, since all it looks like you have simple routed network, not a VLAN!

http://static.openvz.org/userbars/openvz-developer.png

[Updated on: Thu, 31 May 2007 11:04]

Report message to a moderator

Re: networking, looking for pointers [message #13637 is a reply to message #13633]

Thu, 31 May 2007 15:40

slybob
Messages: 20
Registered: March 2007

Junior Member

Ive been told its been set up on a Vlan

How come the HW can see out and I can ssh in but when we try to route to a VE we end up somehow routing to the firewall..

sorry, my networking not too hot.

Andy

How I learned to stop worrying and love SMTP
http://www.moonet.co.uk/

Report message to a moderator

Re: networking, looking for pointers [message #13661 is a reply to message #13637]

Fri, 01 June 2007 08:27

dev
Messages: 1693
Registered: September 2005
Location: Moscow

Senior Member

I'm unsure I understand fully your networking settings, but
even when I add IP 192.168.101.12 to the *host*, it still doesn't work:

[1]+ tcpdump -n -i eth2 host 194.87.0.50 &
debian:~#
debian:~# ping 194.87.0.50
PING 194.87.0.50 (194.87.0.50) 56(84) bytes of data.
09:26:31.617338 IP 192.168.101.12 > 194.87.0.50: ICMP echo request, id 30851, seq 1, length 64
09:26:32.618705 IP 192.168.101.12 > 194.87.0.50: ICMP echo request, id 30851, seq 2, length 64
09:26:33.618754 IP 192.168.101.12 > 194.87.0.50: ICMP echo request, id 30851, seq 3, length 64
09:26:34.618822 IP 192.168.101.12 > 194.87.0.50: ICMP echo request, id 30851, seq 4, length 64
09:26:35.618878 IP 192.168.101.12 > 194.87.0.50: ICMP echo request, id 30851, seq 5, length 64
09:26:36.618951 IP 192.168.101.12 > 194.87.0.50: ICMP echo request, id 30851, seq 6, length 64
09:26:37.619004 IP 192.168.101.12 > 194.87.0.50: ICMP echo request, id 30851, seq 7, length 64

--- 194.87.0.50 ping statistics ---
7 packets transmitted, 0 received, 100% packet loss, time 6001ms

i.e. no replies.

Can you reask your admin whether it is actually VLAN or simply a network IP's range which you can directly use and assign to your ethX devices?

if it is a vlan, then it should have an ID Smile

Report message to a moderator

Re: networking, looking for pointers [message #13666 is a reply to message #13661]

Fri, 01 June 2007 10:14

slybob
Messages: 20
Registered: March 2007

Junior Member

I put to him,

Quote:

Can you reask your admin whether it is actually VLAN or simply a network IP's range which you can directly use and assign to your ethX devices?

if it is a vlan, then it should have an ID

Quote:

the switch calls it a VLAN, at the moment there is an interface on the firewall which is also on that subnet - so in the strictest terms it is a routed LAN, this will be changing though as we sort out the VLAN trunking to the firewall/router

Andy

How I learned to stop worrying and love SMTP
http://www.moonet.co.uk/

Report message to a moderator

Re: networking, looking for pointers [message #13667 is a reply to message #13666]

Fri, 01 June 2007 11:36

dev
Messages: 1693
Registered: September 2005
Location: Moscow

Senior Member

ok. if it a routed LAN - then it should work.
please try something like I did ion the node (e.g. ping flood) and ask your administrator to check wether pings arrive to the firewall and why the reply is not received by the machine. the packet is definetely lost somewhere in network infrastructure.

Report message to a moderator

Previous Topic:	kernel: Oops: 0002 [1] SMP
Next Topic:	SOLVED Failed to initialize quota

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Tue Aug 27 23:16:08 GMT 2024

Total time taken to generate the page: 0.03542 seconds