| Re: OpenVZ on Fedora Core 5 (networking question) [message #2907 is a reply to message #2900] |
Wed, 26 April 2006 16:26   |
dev
Messages: 1693
Registered: September 2005
Location: Moscow
|
Senior Member |
|
|
Santi,
As replied in private email to you, this helps:
midori:~# echo 1 > /proc/sys/net/ipv4/conf/eth1/proxy_arp
midori:~# echo 1 > /proc/sys/net/ipv4/conf/venet0/proxy_arp
midori:~# echo 1 > /proc/sys/net/ipv4/conf/all/proxy_arp
I also wonder what host system you have? I didn't find lots of vz
scripts in /etc/sysconfig, so I suppose your installation of OVZ is
somehow broken or not full?
The same proxy_arp settings should have been automatically setup by
vzctl... Strange...
I also replaced you MASQUARADE rules with:
# iptables -t nat -A POSTROUTING -s 192.168.0.0/24 -d ! 192.168.0.0/24
-j MASQUERADE
i.e. packets coming to 192.168.0.0/24 should not be masquaraded.
Thanks,
Kirill
> El 25/04/2006, a las 14:49, Aleksandar escribió:
>
>> Hello,
>>
>> after installing and successfully running one OpenVZ VPS I wasn't
>> able to ping or ssh to the VPS. After analyzing a little bit I came
>> to the following:
>> 1) host venet0 isn't configured even after vzctl start 101
>> 2) venet0 in the guest (vps) is set to 127.0.0.1
>>
>> Is this normal ? I've assigned 10.0.0.1 to the VPS and if I manually
>> configure host's venet0 to 10.0.0.2 and guest's venet0 to 10.0.0.1
>> (through vzctl exec) I'm being able to ping and ssh to the vps.
>>
>> Also, could someone point me to some detailed information about the
>> OpenVZ networking concept ? Is it like vmware (separate interfaces) ?
>> Is it like jail (ethernet aliases) ? The only thing I found about
>> networking was "vzctl set XYZ --ipadd A.B.C.D" :)
>>
>
> Hello,
>
> I have similar problem with a freshly installed OpenVZ in a Debian
> Sarge box, it's described at:
>
> http://forum.openvz.org/index.php?t=tree&goto=2725
>
> Addtional command outputs:
>
> # uname -a
> Linux midori 2.6.8-022stab076-smp #1 SMP Sun Apr 16 16:32:30 CEST 2006
> i686 GNU/Linux
>
> # cat /proc/sys/net/ipv4/ip_forward
> 1
>
> # ip a l
> 2: lo: <LOOPBACK,UP> mtu 16436 qdisc noqueue
> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
> inet 127.0.0.1/8 scope host lo
> 4: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000
> link/ether 00:05:1c:19:67:f4 brd ff:ff:ff:ff:ff:ff
> inet xxx/19 brd 255.255.255.255 scope global eth0
> 6: eth1: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000
> link/ether 00:05:1c:03:26:36 brd ff:ff:ff:ff:ff:ff
> inet 192.168.0.210/24 brd 192.168.0.255 scope global eth1
> 3: venet0: <BROADCAST,POINTOPOINT,NOARP,UP> mtu 1500 qdisc noqueue
> link/void
>
> # ip r l
> 192.168.0.5 dev venet0 scope link src 83.213.134.130
> 192.168.0.6 dev venet0 scope link src 83.213.134.130
> 192.168.0.0/24 dev eth1 proto kernel scope link src 192.168.0.210
> 83.213.128.0/19 dev eth0 proto kernel scope link src xxx
> default via 83.213.128.1 dev eth0
>
> Regards!
>
> --
> Santi Saez
>
>
>
>
>
>
|
|
|
|
OpenVZ Forum
Members
Search
Help
Register
Login
Home
