OpenVZ Forum


Home » General » Support » problems with second container and venet
problems with second container and venet [message #42922] Sat, 18 June 2011 16:23 Go to next message
buxul is currently offline  buxul
Messages: 3
Registered: June 2011
Junior Member
I'm new with openvz and installed it now on a debian squeeze machine (Kernel linux-image-2.6.32-5-openvz-amd64 and vzctl 3.0.24-12).

I started with a first machine and set a public IP to it. All wents right.

Now I created a second container and set another public IP to it. But this machine can't get any contact beside it's subnet.

Hosts /etc/sysctl.conf
net.ipv4.conf.all.rp_filter=1
net.ipv4.icmp_echo_ignore_broadcasts=1
net.ipv4.conf.default.forwarding=1
net.ipv4.conf.default.proxy_arp = 0
net.ipv4.ip_forward=1
kernel.sysrq = 1
net.ipv4.conf.default.send_redirects = 1
net.ipv4.conf.all.send_redirects = 0
net.ipv4.conf.eth0.proxy_arp=1


Hosts ifconfig
eth0      Link encap:Ethernet  HWaddr 40:61:86:2b:81:a0
          inet addr:100.100.100.162  Bcast:100.100.100.191  Mask:255.255.255.224
          inet6 addr: fe80::4261:86ff:fe2b:81a0/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:443435 errors:0 dropped:0 overruns:0 frame:0
          TX packets:270292 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:568883238 (542.5 MiB)  TX bytes:33049351 (31.5 MiB)
          Interrupt:29 Base address:0x4000

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
          UP BROADCAST POINTOPOINT RUNNING NOARP  MTU:1500  Metric:1
          RX packets:210597 errors:0 dropped:0 overruns:0 frame:0
          TX packets:358576 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:22844885 (21.7 MiB)  TX bytes:478399318 (456.2 MiB)


VEs 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:8 errors:0 dropped:0 overruns:0 frame:0
          TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:568 (568.0 B)  TX bytes:568 (568.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:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:31 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 B)  TX bytes:2292 (2.2 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:100.100.100.172  P-t-P:100.100.100.172  Bcast:0.0.0.0  Mask:255.255.255.255
          UP BROADCAST POINTOPOINT RUNNING NOARP  MTU:1500  Metric:1


Hosts routes:
100.100.100.172 dev venet0  scope link
100.100.100.185 dev venet0  scope link
100.100.100.160/27 via 100.100.100.161 dev eth0
100.100.100.160/27 dev eth0  proto kernel  scope link  src 100.100.100.162
default via 100.100.100.161 dev eth0
broadcast 100.100.100.191 dev eth0  table local  proto kernel  scope link  src 100.100.100.162
broadcast 127.255.255.255 dev lo  table local  proto kernel  scope link  src 127.0.0.1
local 100.100.100.162 dev eth0  table local  proto kernel  scope host  src 100.100.100.162
broadcast 127.0.0.0 dev lo  table local  proto kernel  scope link  src 127.0.0.1
broadcast 100.100.100.160 dev eth0  table local  proto kernel  scope link  src 100.100.100.162
local 127.0.0.1 dev lo  table local  proto kernel  scope host  src 127.0.0.1
local 127.0.0.0/8 dev lo  table local  proto kernel  scope host  src 127.0.0.1
fe80::/64 dev eth0  proto kernel  metric 256  mtu 1500 advmss 1440 hoplimit 4294967295
unreachable default dev lo  table unspec  proto kernel  metric -1  error -101 hoplimit 255
local ::1 via :: dev lo  table local  proto none  metric 0  mtu 16436 advmss 16376 hoplimit 4294967295
local fe80::4261:86ff:fe2b:81a0 via :: dev lo  table local  proto none  metric 0  mtu 16436 advmss 16376 hoplimit 4294967295
ff00::/8 dev eth0  table local  metric 256  mtu 1500 advmss 1440 hoplimit 4294967295
unreachable default dev lo  table unspec  proto kernel  metric -1  error -101 hoplimit 255


VEs routes:
192.0.2.1 dev venet0  scope link
default via 192.0.2.1 dev venet0  src 100.100.100.172
broadcast 127.255.255.255 dev lo  table local  proto kernel  scope link  src 127.0.0.1
local 100.100.100.172 dev venet0  table local  proto kernel  scope host  src 100.100.100.172
broadcast 127.0.0.0 dev lo  table local  proto kernel  scope link  src 127.0.0.1
local 127.0.0.1 dev lo  table local  proto kernel  scope host  src 127.0.0.1
local 127.0.0.1 dev venet0  table local  proto kernel  scope host  src 127.0.0.1
local 127.0.0.0/8 dev lo  table local  proto kernel  scope host  src 127.0.0.1
unreachable default dev lo  table unspec  proto kernel  metric -1  error -101 hoplimit 255
local ::1 via :: dev lo  table local  proto none  metric 0  mtu 16436 advmss 16376 hoplimit 4294967295
unreachable default dev lo  table unspec  proto kernel  metric -1  error -101 hoplimit 255


Can you help me and tell me what I made wrong.

Greetings
Buxul

Report message to a moderator

Re: problems with second container and venet [message #42936 is a reply to message #42922] Tue, 21 June 2011 05:26 Go to previous messageGo to next message
buxul is currently offline  buxul
Messages: 3
Registered: June 2011
Junior Member
no hint?

Report message to a moderator

Re: problems with second container and venet [message #42940 is a reply to message #42936] Wed, 22 June 2011 06:21 Go to previous messageGo to next message
Paparaciz
Messages: 302
Registered: August 2009
Senior Member
I would recommend installing latest rhel6 vzkernel

http://wiki.openvz.org/Download/kernel/rhel6/042stab018.1

update vzctl to latest version (3.0.28.3).

Report message to a moderator

Re: problems with second container and venet [message #43020 is a reply to message #42940] Sat, 02 July 2011 11:51 Go to previous messageGo to next message
buxul is currently offline  buxul
Messages: 3
Registered: June 2011
Junior Member
Does your recommendation meen, that openvz doesn't run on debian squeeze? Why there are packages for debian, if this don't run?

Report message to a moderator

Re: problems with second container and venet [message #43022 is a reply to message #43020] Sat, 02 July 2011 12:25 Go to previous message
Paparaciz
Messages: 302
Registered: August 2009
Senior Member
sorry I realy don't know what exactly packages are in debian.

I'm using centos. And waiting for centos6 release to test rhel6 based openvz kernel.

I want to say that I see much more development on rhel6 based kernels compared to development on kernel 2.6.32

http://git.openvz.org/?p=linux-2.6.32-openvz;a=log
last actions was 3 months ago
while newest rhel6 based openvz kernel was released 2weeks ago.

and no, I don't want to say that openvz can not be run on debian squeeze.

If you want to stay with debian provided openvz kernel I would suggest to submit bug in debian. http://www.debian.org/Bugs/

Report message to a moderator

Previous Topic: VPS virtuozzo to openvz
Next Topic: IPSec-Server in a VPS
Goto Forum:
  

[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Wed Jul 17 18:23:15 GMT 2024

Total time taken to generate the page: 0.02639 seconds
Powered by FUDforum Powered by Virtuozzo Containers