OpenVZ Forum - RDF feed
type: channel
items: Container unreachable from LAN
items: Re: Container unreachable from LAN

Container unreachable from LAN
type: item
description: Trying to set up the most basic container, I'm failing to make the container reachable from computers located on the same LAN of the hardware host via IPv4. Only the host can reach (ping) the container. This is the configuration: kernel: 3.8.13 vanilla, non-OpenVZ VZ tools: vzctl version 4.3.1-21.git.68038a5 compiled from Git container OS template: debian-6.0-x86.tar.gz host OS: Debian Wheezy 7.1 network infrastructure: DSL connection reaches a domestic modem/router with dynamic IPv4; a few ethernet cables connect this router with individual computers within one single subnetwork; among these computers there's the OpenVZ hardware host. Router IP: 192.168.1.1, netmask 255.255.255.0; the router assigns IPs by using an internal DHCP daemon. This routher always assigns 192.168.1.10 to the hardware host (MAC binding). Hardware host can reach internet and the other computers on LAN. Routing: no rules; no iptables, no netfilters, nothing except a NAT on the DSL modem/router. This is how I attempt to set up the container: #> /usr/handsoftware/sbin/vzctl create 101 --ostemplate debian-6.0-x86 Directory /proc/vz not found, assuming non-OpenVZ kernel Creating container private area (debian-6.0-x86) Performing postcreate actions CT configuration saved to /etc/vz/conf/101.conf Container private area was created #> /usr/handsoftware/sbin/vzctl set 101 --onboot yes --save Directory /proc/vz not found, assuming non-OpenVZ kernel CT configuration saved to /etc/vz/conf/101.conf #> vzctl set 101 --ipadd 192.168.1.101 --save Directory /proc/vz not found, assuming non-OpenVZ kernel CT configuration saved to /etc/vz/conf/101.conf #> /usr/handsoftware/sbin/vzct set 101 --nameserver 192.168.1.1 --save Directory /proc/vz not found, assuming non-OpenVZ kernel CT configuration saved to /etc/vz/conf/101.conf #> /usr/handsoftware/sbin/vzctl start 101 Directory /proc/vz not found, assuming non-OpenVZ kernel Starting container... Container is mounted Could not properly cleanup container: No such …
creator: Davide
date: 2013-07-19T14:04:47-00:00

Re: Container unreachable from LAN
type: item
description: I have no clue at all, so even a bare crude hypothesis could turn me on track toward using OpenVZ.
creator: Davide
date: 2013-07-20T06:50:17-00:00

Re: Container unreachable from LAN
type: item
description: do you masquerade CT ip addresses to outside? please provide more information about network setup in HN with interfaces and ip addresses and what do you want to achieve
creator: Paparaciz
date: 2013-07-26T19:45:14-00:00

Re: Container unreachable from LAN
type: item
description: I have no kind of professional network configuration, not in CT0 nor in the VE. Iptables, masquerading and NAT: never customized these from their defaults. CT0 connects to the modem/router using dhclient, and is assigned the IP 192.168.1.10 by the router, which stands on 192.168.1.1. The goal is to let the VE have its own IP address assigned directly from the router, if possible.
creator: Davide
date: 2013-07-26T23:28:17-00:00

Re: Container unreachable from LAN
type: item
description: http://forum.openvz.org/index.php?t=msg&th=5501&star t=0&
creator: Paparaciz
date: 2013-07-29T10:47:27-00:00