Hints for network setup

Jun 11, 2019
41
2
13
52
Hi all,

I have this situation: server hosted on a hosting provider; they assigned to eno1 port of the ProxMox host four different public IP addresses; main IP (82.195.231.243) is dedicated to ProxMox web management consolle; I would like to use the next three addresses (82.195.231.244 / 245 and 246) to reach three different VM.

Which kind of setup do you suggest?

Note: As underlined on another thread here, I cannot assign the public IP address to the VMs because they are already assigned to the host port.

Thanks for any help.
 
Hey,

could you post the output of ip a?

Maybe consider hiding part of your public IPs.
 
Hey,

could you post the output of ip a?

Maybe consider hiding part of your public IPs.
This is the actual setup that is causing issues, so I ask for an alternate setup.

Code:
root@vmhost01:~# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master vmbr0 state UP group default qlen 1000
    link/ether 94:40:c9:4c:f0:3c brd ff:ff:ff:ff:ff:ff
3: eno2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 94:40:c9:4c:f0:3d brd ff:ff:ff:ff:ff:ff
4: enp1s0f4u4: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 0a:25:18:01:0f:f1 brd ff:ff:ff:ff:ff:ff
5: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 94:40:c9:4c:f0:3c brd ff:ff:ff:ff:ff:ff
    inet 82.195.231.243/29 brd 82.195.231.247 scope global vmbr0
       valid_lft forever preferred_lft forever
    inet 82.195.231.244/29 brd 82.195.231.247 scope global secondary vmbr0
       valid_lft forever preferred_lft forever
    inet 82.195.231.245/29 brd 82.195.231.247 scope global secondary vmbr0
       valid_lft forever preferred_lft forever
    inet 82.195.231.246/29 brd 82.195.231.247 scope global secondary vmbr0
       valid_lft forever preferred_lft forever
    inet6 fe80::9640:c9ff:fe4c:f03c/64 scope link 
       valid_lft forever preferred_lft forever
6: vmbr1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether fe:a2:39:f3:56:dd brd ff:ff:ff:ff:ff:ff
    inet6 fe80::e4de:88ff:feb7:64f7/64 scope link 
       valid_lft forever preferred_lft forever
9: veth103i0@if2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr1 state UP group default qlen 1000
    link/ether fe:a2:39:f3:56:dd brd ff:ff:ff:ff:ff:ff link-netnsid 0
10: veth103i1@if3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr1 state UP group default qlen 1000
    link/ether fe:9d:38:f8:12:54 brd ff:ff:ff:ff:ff:ff link-netnsid 0
11: tap104i0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master fwbr104i0 state UNKNOWN group default qlen 1000
    link/ether aa:94:73:74:50:18 brd ff:ff:ff:ff:ff:ff
12: fwbr104i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 62:ce:82:32:31:bd brd ff:ff:ff:ff:ff:ff
13: fwpr104p0@fwln104i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr1 state UP group default qlen 1000
    link/ether ee:fd:2d:51:e9:d6 brd ff:ff:ff:ff:ff:ff
14: fwln104i0@fwpr104p0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr104i0 state UP group default qlen 1000
    link/ether 62:ce:82:32:31:bd brd ff:ff:ff:ff:ff:ff
15: tap104i1: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master fwbr104i1 state UNKNOWN group default qlen 1000
    link/ether aa:2b:5a:e8:b3:74 brd ff:ff:ff:ff:ff:ff
16: fwbr104i1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether ce:a2:0a:44:21:a4 brd ff:ff:ff:ff:ff:ff
17: fwpr104p1@fwln104i1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr1 state UP group default qlen 1000
    link/ether b6:78:d6:67:72:1e brd ff:ff:ff:ff:ff:ff
18: fwln104i1@fwpr104p1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr104i1 state UP group default qlen 1000
    link/ether ce:a2:0a:44:21:a4 brd ff:ff:ff:ff:ff:ff
41: tap111i0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vmbr1 state UNKNOWN group default qlen 1000
    link/ether be:26:f3:f1:9a:68 brd ff:ff:ff:ff:ff:ff
42: tap111i1: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vmbr1 state UNKNOWN group default qlen 1000
    link/ether 52:33:57:d9:7c:16 brd ff:ff:ff:ff:ff:ff
350: tap100i0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master fwbr100i0 state UNKNOWN group default qlen 1000
    link/ether 52:15:96:8e:61:4b brd ff:ff:ff:ff:ff:ff
351: fwbr100i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 1e:57:35:fb:b8:9d brd ff:ff:ff:ff:ff:ff
352: fwpr100p0@fwln100i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr0 state UP group default qlen 1000
    link/ether 16:07:6a:9d:cb:fe brd ff:ff:ff:ff:ff:ff
353: fwln100i0@fwpr100p0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr100i0 state UP group default qlen 1000
    link/ether 1e:57:35:fb:b8:9d brd ff:ff:ff:ff:ff:ff
354: tap100i1: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vmbr1 state UNKNOWN group default qlen 1000
    link/ether ea:0e:63:4d:0a:2f brd ff:ff:ff:ff:ff:ff
355: tap101i0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vmbr1 state UNKNOWN group default qlen 1000
    link/ether 5e:9b:8d:f9:4b:a3 brd ff:ff:ff:ff:ff:ff
356: tap101i1: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vmbr1 state UNKNOWN group default qlen 1000
    link/ether e2:b6:fe:ab:88:91 brd ff:ff:ff:ff:ff:ff
357: veth105i0@if2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr1 state UP group default qlen 1000
    link/ether fe:75:0b:50:5b:a7 brd ff:ff:ff:ff:ff:ff link-netnsid 1
358: veth105i1@if3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr1 state UP group default qlen 1000
    link/ether fe:70:bd:c0:e6:bd brd ff:ff:ff:ff:ff:ff link-netnsid 1
359: tap106i0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master fwbr106i0 state UNKNOWN group default qlen 1000
    link/ether 5e:4d:a1:f2:56:71 brd ff:ff:ff:ff:ff:ff
360: fwbr106i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether ba:bc:75:bc:ae:20 brd ff:ff:ff:ff:ff:ff
361: fwpr106p0@fwln106i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr0 state UP group default qlen 1000
    link/ether ae:17:c2:80:2c:de brd ff:ff:ff:ff:ff:ff
362: fwln106i0@fwpr106p0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr106i0 state UP group default qlen 1000
    link/ether ba:bc:75:bc:ae:20 brd ff:ff:ff:ff:ff:ff
363: tap106i1: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vmbr1 state UNKNOWN group default qlen 1000
    link/ether ea:fd:e8:82:c5:a7 brd ff:ff:ff:ff:ff:ff
364: tap106i2: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vmbr1 state UNKNOWN group default qlen 1000
    link/ether e6:ae:d1:32:98:2f brd ff:ff:ff:ff:ff:ff
365: tap107i0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vmbr1 state UNKNOWN group default qlen 1000
    link/ether d2:ed:4d:4e:2d:fb brd ff:ff:ff:ff:ff:ff
366: tap108i0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vmbr1 state UNKNOWN group default qlen 1000
    link/ether 96:ce:b6:a1:3f:3f brd ff:ff:ff:ff:ff:ff
367: tap108i1: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vmbr1 state UNKNOWN group default qlen 1000
    link/ether 46:0b:35:4a:ee:68 brd ff:ff:ff:ff:ff:ff
368: tap109i0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vmbr1 state UNKNOWN group default qlen 1000
    link/ether 02:cb:1e:43:b8:18 brd ff:ff:ff:ff:ff:ff
369: tap109i1: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vmbr1 state UNKNOWN group default qlen 1000
    link/ether 56:8b:d6:c9:1a:fb brd ff:ff:ff:ff:ff:ff
370: tap110i0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vmbr1 state UNKNOWN group default qlen 1000
    link/ether 4e:6c:de:07:a1:24 brd ff:ff:ff:ff:ff:ff
371: tap110i1: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vmbr1 state UNKNOWN group default qlen 1000
    link/ether 9a:8b:ce:dc:e9:f9 brd ff:ff:ff:ff:ff:ff
149: tap102i0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master fwbr102i0 state UNKNOWN group default qlen 1000
    link/ether 0a:15:ff:ce:85:04 brd ff:ff:ff:ff:ff:ff
150: fwbr102i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether f2:ae:0f:78:c9:fb brd ff:ff:ff:ff:ff:ff
151: fwpr102p0@fwln102i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr0 state UP group default qlen 1000
    link/ether 0e:d3:21:19:e6:98 brd ff:ff:ff:ff:ff:ff
152: fwln102i0@fwpr102p0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr102i0 state UP group default qlen 1000
    link/ether f2:ae:0f:78:c9:fb brd ff:ff:ff:ff:ff:ff
153: tap102i1: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vmbr1 state UNKNOWN group default qlen 1000
    link/ether e6:63:37:10:74:e3 brd ff:ff:ff:ff:ff:ff
 
And could you also post the output of cat /etc/network/interfaces? In /etc/network/interfaces you should be able to remove all except one address from vmbr0. Then your VMs should be able to use those instead.
 
And could you also post the output of cat /etc/network/interfaces? In /etc/network/interfaces you should be able to remove all except one address from vmbr0. Then your VMs should be able to use those instead.

Code:
# network interface settings; autogenerated
# Please do NOT modify this file directly, unless you know what
# you're doing.
#
# If you want to manage parts of the network configuration manually,
# please utilize the 'source' or 'source-directory' directives to do
# so.
# PVE will preserve these directives, but will NOT read its network
# configuration from sourced files, so do not attempt to move any of
# the PVE managed interfaces into external files!

auto lo
iface lo inet loopback

iface eno1 inet manual

iface eno2 inet manual

iface enp1s0f4u4 inet manual

auto vmbr0
iface vmbr0 inet static
        address 82.195.231.243/29
        gateway 82.195.231.241
        bridge-ports eno1
        bridge-stp off
        bridge-fd 0
#wan - Only exposed hosts here!

auto vmbr1
iface vmbr1 inet manual
        bridge-ports none
        bridge-stp off
        bridge-fd 0
#Internal bridge

What about the disclaimer on the header? It's so possible to modify this file directly?
Beside that there is just the main IP address in this file. The other address seems to be assigned directly by the provider ... weird because is a static configuration not DHCP.
 
Weird indeed, if you reboot, do they stay(ip a)?
 
First of all: Solved, and thank you for pointing me on the right direction.

The issue
When I installed this host, I created all my VM as linux container; in the last months I converted quite all lxc to vm. Then the problem appeared (see my other post).

When looking on /etc/network/interfaces nothing strange appeared but ip address shows all my public IP addresses on vmbr0 and (of course) in eno1.

When creating the new VM the most logical setup for me was to assign the public IP address to the main eth interface; but the result was to have two devices on the same network with the same IP address...

Solution
When user create a linux container, the file /etc/network/interfaces.d/vmbr0.conf is created, that contains "additional IP addresses to main Eth interface via vmbr0".

Removing this file solved all the issues.
 
  • Like
Reactions: Hannes Laimer

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!