OpenVZ Forum


Home » General » Support » *solved* OpenVZ on CentOS 5 network issues
Re: OpenVZ on CentOS 5 network issues [message #15841 is a reply to message #15838] Wed, 15 August 2007 02:41 Go to previous messageGo to previous message
locutius is currently offline  locutius
Messages: 125
Registered: August 2007
Senior Member
my /etc/sysctl.conf ...

# Controls IP packet forwarding
net.ipv4.ip_forward = 1
net.ipv4.conf.default.proxy_arp = 0
# Controls source route verification
net.ipv4.conf.default.rp_filter = 1
net.ipv4.conf.all.rp_filter = 1
# Enables the magic-sysrq key
kernel.sysrq = 1
# Do not accept source routing
net.ipv4.conf.default.accept_source_route = 0
# Controls the System Request debugging functionality of the kernel
kernel.sysrq = 0
# Controls whether core dumps will append the PID to the core filename.
# Useful for debugging multi-threaded applications.
kernel.core_uses_pid = 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

you can see it has the lines required by OpenVZ but also the following lines which were already in situ:

# Controls source route verification
net.ipv4.conf.default.rp_filter = 1
# Do not accept source routing
net.ipv4.conf.default.accept_source_route = 0

the instruction is to 'paste' which suggested to me that i replace any dupes with the OpenVZ line and keep everything else

there is one line in the PDF i find which may point to the problem:

pp29: ... or routing to the VPS has been set up via the Hardware Node

the server IPs are all set and working for the HN server. am i correct there is another layer of config as our friend suggested where the HN must be told how to route the external IPs to the VEs?

you can use the email locutius@gmail.com to contact me or send me your email i we can discuss you taking a look at the config

i really do appreciate the help

EDIT: the problem with problem 1 was after editing, saving and rebooting the HN the changes in sysctl.conf did not take effect. only when i made a service network restart did the sysctl.conf take effect .... yes very very strange, and that was what was confusing about the beginning of this thread, why would anyone expect an updated sysctl.conf not to take effect on a reboot :/

EDIT: confirmed iptables stopped in HN and VE, SELINUX off, HN IP and VE IP traceroutes are identical

[Updated on: Wed, 15 August 2007 02:50]

Report message to a moderator

 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: change inode_soft_limit
Next Topic: Problematic Hard Disk - Read Only Mode
Goto Forum:
  


Current Time: Sat Jun 28 21:17:15 GMT 2025

Total time taken to generate the page: 0.02143 seconds