how to create IP redirect with vmbr1

[starnetwork]

Hi,
I have openvz containers on node, this node connected to eth0 (internet connection)
and eth1 (via vmbr1, for backups)
Backup drive Internal IP: 192.168.20.30
Server Internal IP: 192.168.20.35

/etc/network/interfaces:

# network interface settings
auto lo
iface lo inet loopback

iface eth0 inet manual

auto eth1
iface eth1 inet manual

auto vmbr0
iface vmbr0 inet static
        address  212.100.100.59
        netmask  255.255.255.192
        gateway  212.100.100.1
        bridge_ports eth0
        bridge_stp off
        bridge_fd 0

auto vmbr1
iface vmbr1 inet static
        address  192.168.20.35
        netmask  255.255.255.0
        bridge_ports eth1
        bridge_stp off
        bridge_fd 0

I just try to add eth1 to the containers, add internal IP, but it's didn't help
traceroute from container Going through 212.100.100.59 (internet IP)
* the internet IP is not the real IP...

Best Regards,
Star Network.

 

[udo]

Hi,
I have openvz containers on node, this node connected to eth0 (internet connection)
and eth1 (via vmbr1, for backups)
Backup drive Internal IP: 192.168.20.30
Server Internal IP: 192.168.20.35

/etc/network/interfaces:

# network interface settings
auto lo
iface lo inet loopback

iface eth0 inet manual

auto eth1
iface eth1 inet manual

auto vmbr0
iface vmbr0 inet static
        address  212.100.100.59
        netmask  255.255.255.192
        gateway  212.100.100.1
        bridge_ports eth0
        bridge_stp off
        bridge_fd 0

auto vmbr1
iface vmbr1 inet static
        address  192.168.20.35
        netmask  255.255.255.0
        bridge_ports eth1
        bridge_stp off
        bridge_fd 0

I just try to add eth1 to the containers, add internal IP, but it's didn't help
traceroute from container Going through 212.100.100.59 (internet IP)
* the internet IP is not the real IP...

Best Regards,
Star Network.

Hi,
how looks your NETIF-Entry for the container?
Here is an working Entry for two bridges networkcards:

NETIF="ifname=eth0,bridge=vmbr0,mac=DE:BE:3C:2A:52:60,host_ifname=veth310.0,host_mac=A2:DE:56:93:82:6D;ifname=eth1,bridge=vmbr1,mac=96:02:DB:FC:C0:B5,host_ifname=veth310.1,host_mac=56:F8:89:E3:14:60"

of course you need to define eth1 inside the container (in /etc/network/interfaces for debian).

Udo

PS: For troubleshooting post the CT-conf and interface inside the CT and something like "ip route" and "ifconfig -a".

 

[starnetwork]

Hi,
the NETIF is only with eth1
NETIF="ifname=eth1,bridge=vmbr1,mac=B6:FD:5D:92:13:AA,host_ifname=veth454.0,host_mac=66:22:02:E1:A2:E4"

additional question:
what about nfs that I use for nodes backups, there is no security issue that VPS root can Connect to NFS Share?
(it's look like it work with the main node internal IP that Approved for NFS - the NFS authentication is performed only by IP)

Best Regards,
Star Network.

 

[starnetwork]

adding:
ifconfig eth1 192.168.20.36 netmask 255.255.255.0
inside the CT make the tracking work but after restart he forgets the settings.
any Idea?

Best Regards,
Star Network.