Quantcast
Channel: Proxmox Support Forum
Viewing all articles
Browse latest Browse all 170705

Networking Setup for OpenVZ and Qemu and multiple subnets

$
0
0
So i've been searching all day trying to figure out the best way to achieve this but still wondering what the best way to do this would be. I've found a lot of different information and have looked through Server Overflow, Proxmox Wiki, and Google and still not sure.

I've been assigned two public subnets from my provider on the same uplink port, eth1.

My current configuration:
Code:

    auto lo
    iface lo inet loopback
   
    iface eth1 inet manual

    auto vmbr0
    iface vmbr0 inet static
        address 209.x.x.42
        netmask 255.255.255.248
        gateway 209.x.x.41
        bridge_ports eth1
        bridge_stp off
        bridge_fd 0

This configuration works correctly for the subnet specified above with the OpenVZ containers using venet0, and I have yet to try Qemu yet as I ran into problems trying to get the other subnet working.

I was assigned another subnet on the same uplink port eth1:
Code:

Range: 209.x.x.96/27
Netmask: 255.255.255.224
Usable: 209.x.x.98-126

So from everything I've read online it looks like my best option is to use the routed method to support both OpenVZ and Qemu but i'm still not too sure how I should setup the network configuration to support both of these subnets. I also want to set it up so when I need to add another subnet I don't have to play around with the settings too much as I will have servers running on there I will not want to shutdown while I tinker.

Can someone please help me or point me in the right direction on what I should research to setup the network config? I've been messing with this all day and want to make sure i'm doing it correctly and not just using a workaround that may come back to bite me later on.

Thank you for any help in advance it is greatly appreciated!

Viewing all articles
Browse latest Browse all 170705

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>