OpenVZ Forum


Home » General » Support » Internal ant external ip (Multiple subnets)
Internal ant external ip [message #51949] Fri, 27 March 2015 09:52
Fenixoid is currently offline  Fenixoid
Messages: 7
Registered: August 2007
Location: Lithuania
Junior Member

From: *telelanas.lt
To be short:

in the pass the was a 192.168.1.0/24 computer network, one of the them was a server with 192.168.1.77 ip, so other computers could reach samba on it like via simple windows network share. The server had also external ip's range with several networks like:

11.22.33.84 - net
11.22.33.85 - ip
11.22.33.86 - gw
11.22.33.87 - brd

11.22.33.88 - net
11.22.33.89 - ip
11.22.33.90 - gw
11.22.33.91 - brd

Config on gentoo was like:

config_eth0=(
"11.22.33.85/30 brd 11.22.33.87"
"11.22.33.89/30 brd 11.22.33.91"
"192.168.1.77/24 brd 192.168.1.255"
)

routes_eth0=(
"default gw 11.22.33.86"
"default gw 11.22.33.90"
"default gw 192.168.1.254"
)


NOW, everything moved to proxmox virtual system, ant the server now is slipt in to openvz containers: one for samba, other for web, another for mail ant so on.
I also have aditional ip's:

6.7.8.8 - ip
6.7.8.9 - ip
6.7.8.10 - bw
6.7.8.11 - brd

(I'm ritch in ip's).


Current main proxmox node ip is 6.7.8.8

- Is there a no-pain way for clients from 192.168.1.0/24 network to reach o openvz vps with the same 192.168.1.77 ip (local network)
- Is there an easy way for other containers to use old 11.22.33.** ip's?
running container with 6.7.8.9 ip has no problem.

Sorry for my bad english.
Previous Topic: iptables: No chain/target/match by that name while setting IP Rotation
Next Topic: Container starving for CPU resources?
Goto Forum:
  


Current Time: Sun Aug 25 11:32:53 GMT 2019