Venet Interface...some problem

[BiagioParuolo]

Hi,

I've moved some containers to new server, but that containers (with venet interfcace) don't reach WAN, but in old server yes.

I try to ping some server but I have not any reply.

They communicate only with host.

Is there some routing or firewall problems with venet ?

Config:


# Auto generated lo interface
auto lo
iface lo inet loopback

# Auto generated venet0 interface
auto venet0
iface venet0 inet static
address 127.0.0.1
netmask 255.255.255.255
broadcast 0.0.0.0
up route add -net 192.0.2.1 netmask 255.255.255.255 dev venet0
up route add default gw 192.0.2.1
auto venet0:0
iface venet0:0 inet static
address 95.110.200.xyz
netmask 255.255.255.255
broadcast 0.0.0.0

 

[BiagioParuolo]

I see old container and server, but change only IP of host and container...

Uhm..the host server has IP

95.110.197.xy/255.255.248.0


but IP addresses for VMs are 95.110.200.xyz and mask 255.255.248.0


I think that there is some problem on routing or similar...


Help!


Thank you

 

[BiagioParuolo]

I think that problem is that IP subnet of CT is different from that HOST and also GW.

How setup subnet and gw ( different from host ) for CT with venet?

I think that is best to use veth because I tried and work.

 

[dietmar]

I think that problem is that IP subnet of CT is different from that HOST and also GW.

How setup subnet and gw ( different from host ) for CT with venet?

I think that is best to use veth because I tried and work.

see 'man vz.conf' (parameters VE_ROUTE_SRC_DEV, NEIGHBOUR_DEVS)