Not possible to expose VM to internet using the dc

djebali

Renowned Member
Oct 25, 2016
2
1
68
55
Good Evening Eveyrone
I have a server installed in a rack with multiple network interfaces
  • one network eno1 behind the vmbr1 interface connected to local switch which is connected to the lan managed by pfsense : ip : 192.168.1.20 ==> i have access to the ui of proxmox ( v8.1.3 )
  • the second network interface eno2 behind the vmbr1 which is physically connected to a non managed switch and conencted to internet ( I have the network 81.95.119.129/26 ) on the same switch I have another running cluster of proxmox who works perfectly and ther are some VM connected to internet
my main problem is I'm not able to expose VM to internet if I use the vmbr1 ( behind the eno2) , I always have the message NO-CARRIER
Can someone help me to fix this issue ?
I thank you
Sami

here is the configuration of the /etc/network/interfaces:
auto lo
iface lo inet loopback
iface eno1 inet manual
auto vmbr0
iface vmbr0 inet static
address 192.168.1.20/24
gateway 192.168.1.1
bridge-ports eno1
bridge-stp off
bridge-fd 0

auto vmbr1
iface vmbr1 inet manual
bridge-ports eno2
bridge-stp off
bridge-fd 0
#Network Bridge to Want
this is the status of the network interfaces:
ip a | grep eno1
6: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master vmbr0 state UP group default qlen 1000
ip a | grep vmbr0
6: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master vmbr0 state UP group default qlen 1000
12: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
inet 192.168.1.20/24 scope global vmbr0
ip a | grep vmbr1
7: eno2: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq master vmbr1 state DOWN group default qlen 1000
13: vmbr1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
16: fwpr100p0@fwln100i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr1 state UP group default qlen 1000
 
Hey,

there is no eno2 iface defined in /etc/network/interfaces. Add it to your file and run ifreload -a and check if eno2 state changed to UP with it's designated IPv4 settings.

Best
 
Last edited:
Hello Hqu
sorry for the dealy , I reaaaly thank yo for your help
I finnally find out , it was my fault , i was not using the right interface
I really thank you
Sami
 
  • Like
Reactions: Hqu

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!