Host Server and Container IP address should be on different subnet series.

Retheesh

New Member
May 16, 2013
8
0
1
Bangalore, India
Hi,

My proxmox host is running on IP address 192.168.1.x ip address. My KVM Virtual instances are all running on 192.168.3.x series with the below given network configuration. I am able to communicate to the Proxmox host and the KVM Virtual Machines without any issues.

However the problem is with the Containers. All my container machines can be connected only if i were to configure them with 192.168.1.x series of IP address. I want to configure the container servers with 192.168.3.x

What configurations should be done to achieve this setup. Any pointers or suggestion is highly appreciated.

Thanks.
RK

# network interface settings
auto lo
iface lo inet loopback
dns-nameservers 192.168.1.1
dns-search vlab.com

auto eth0
iface eth0 inet manual

auto eth1
iface eth1 inet manual

auto vmbr0
iface vmbr0 inet static
address 192.168.1.7
netmask 255.255.255.0
gateway 192.168.1.250
bridge_ports eth0
bridge_stp off
bridge_fd 0
 
Hi,

My proxmox host is running on IP address 192.168.1.x ip address. My KVM Virtual instances are all running on 192.168.3.x series with the below given network configuration. I am able to communicate to the Proxmox host and the KVM Virtual Machines without any issues.

However the problem is with the Containers. All my container machines can be connected only if i were to configure them with 192.168.1.x series of IP address. I want to configure the container servers with 192.168.3.x

What configurations should be done to achieve this setup. Any pointers or suggestion is highly appreciated.

Thanks.
RK

# network interface settings
auto lo
iface lo inet loopback
dns-nameservers 192.168.1.1
dns-search vlab.com

auto eth0
iface eth0 inet manual

auto eth1
iface eth1 inet manual

auto vmbr0
iface vmbr0 inet static
address 192.168.1.7
netmask 255.255.255.0
gateway 192.168.1.250
bridge_ports eth0
bridge_stp off
bridge_fd 0

Hi,
don't see your 192.168.3.0/24 network! Do you have an extra bridge ( like vmbr3 - on eth1) for this network?

If you work with an own bridge simply use the same bridge for CTs - works without trouble.

Udo
 
Hi,

The eth0 port is connected to a trunk switch port which is configured to allow the following subnet IP's of 192.168.1.x, 192.168.2.x, 192.168.3.x.

Regards,
RK
 
Hi,

The eth0 port is connected to a trunk switch port which is configured to allow the following subnet IP's of 192.168.1.x, 192.168.2.x, 192.168.3.x.

Regards,
RK

Hi,
an trunk with one port only?
The right way for different networks over one connection is vlan-tagging. But if you use all networks over one cable you should also be able to use an IP from one of the networks inside the VM/CT with briged networking.

Use tcpdump on the host to find the issue.

Udo
 
if you use all networks over one cable you should also be able to use an IP from one of the networks inside the VM/CT with briged networking.

Yes, I was wrong... sorry.
If 192.168.1.250 can route between 192.168.1.0/24 and 192.168.3.0/24 networks, it should work...
I also do that, because I have a single LAN gateway which handle multiple private C and B class.

Marco
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!