| Re: Using NAT for VE with private IPs [message #10716 is a reply to message #10658] |
Mon, 26 February 2007 23:40   |
lloyd
Messages: 3
Registered: February 2007
|
Junior Member |
|
|
Hi,
Oops, still no satisfaction.
Unfortunately I'm off the Mexico in a few hours so won't have time
double-check my work until after I return on March 13.
Kir noted that I shouldn't have rebooted...
I think I was thrown off by the language in openVZ wiki -- Using NAT for
VE with private IPs. "... Also remember that if this module is loaded
without the option, unloading and reloading doesn't work! You need to
reboot the computer."
It's clearer to me now, I think. But it was ambiguous at the time.
Many thanks for your help. I hope I can get this going shortly after my
return.
All the best,
LRP
-----Original Message-----
From: "Vasily Tarasov" <vtaras@openvz.org>
Sent: Mon, February 26, 2007 4:55 am
To: users@openvz.org
Subject: Re: [Users] Using NAT for VE with private IPs
Kir Kolyshkin wrote:
> Lloyd R. Prentice wrote:
>> Then I rebooted
> Oops. Why a reboot?
>
> All the iptables commands, and modprobe as well, are not taking effect
> after the reboot. In order to make them persistent, you have to put
> those in some startup script.
To be more precise, all distribution I know use /etc/sysconfig/iptables
file to make rules persistent. After setting up your rules via
`iptables` command you should do `iptables-save >
/etc/sysconfig/iptables`, and at a boot time init script will
automagically use your rules.
HTH,
Vasily.
|
|
|
|
OpenVZ Forum
Members
Search
Help
Register
Login
Home
