| Container Networking Problem [message #37985] |
Sat, 07 November 2009 02:35  |
RogerHenry
Messages: 3
Registered: November 2009
|
Junior Member |
|
|
Hello:
I have completed a smooth install of openvz on centos 5 and was able to create a centos container with the standard template. The ip that i assigned to the container is still hitting the main server. I am using the default VENET, and a rented dedicated server. The server has a public ip and 7 other public ips etho:0 main ip etho:2 spare ip ETC.
I believe my sysctl.conf settings are correct they are as follows
# Kernel sysctl configuration file for Red Hat Linux
#
# For binary values, 0 is disabled, 1 is enabled. See sysctl( and
# sysctl.conf(5) for more details.
# On Hardware Node we generally need
# packet forwarding enabled and proxy arp disabled
net.ipv4.ip_forward = 1
net.ipv6.conf.default.forwarding = 1
net.ipv6.conf.all.forwarding = 1
net.ipv4.conf.default.proxy_arp = 0
# Enables source route verification
net.ipv4.conf.all.rp_filter = 1
# Enables the magic-sysrq key
kernel.sysrq = 1
# We do not want all our interfaces to send redirects
net.ipv4.conf.default.send_redirects = 1
net.ipv4.conf.all.send_redirects = 0
# Controls the System Request debugging functionality of the kernel
kernel.sysrq = 1
# Controls whether core dumps will append the PID to the core filename
# Useful for debugging multi-threaded applications
kernel.core_uses_pid = 1
# Controls the use of TCP syncookies
net.ipv4.tcp_syncookies = 1
# Controls the maximum size of a message, in bytes
kernel.msgmnb = 65536
# Controls the default maxmimum size of a mesage queue
kernel.msgmax = 65536
# Controls the maximum shared segment size, in bytes
kernel.shmmax = 4294967295
# Controls the maximum number of shared memory segments, in pages
kernel.shmall = 268435456
I noticed in another post something about checking arp. Arp currently only has one entry, im unsure what to do with this.
Is anyone able to offer some guidance please ?
*update*
I used the centos network GUI tool and gave venet0 an ip, i can now access the outside world from the container, but the ip is still hitting the main machine....
[Updated on: Sat, 07 November 2009 03:04] Report message to a moderator |
|
|
|
OpenVZ Forum
Members
Search
Help
Register
Login
Home
