Undeletable network interface after fresh install

Sasha

Sasha

Well-Known Member
Proxmox Subscriber
Oct 18, 2018
88
1
48
Kazahstan
Hi, guys!
Would You help me to figure out what this network interface eno2 is? It appears every time after installing PM on that dedicated server and after trying to delete it via PM's GUI it appears again. What does it mean? Some hardware?

Code: 
root@hq:~# ip address
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
2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master vmbr0 state UP group default qlen 1000
    link/ether 0c:c4:7a:34:3e:cc brd ff:ff:ff:ff:ff:ff
    altname enp4s0f0
3: eno2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 0c:c4:7a:34:3e:cd brd ff:ff:ff:ff:ff:ff
    altname enp4s0f1
4: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 0c:c4:7a:34:3e:cc brd ff:ff:ff:ff:ff:ff
    inet 88.888.888.88/28 scope global vmbr0
       valid_lft forever preferred_lft forever
5: vmbr1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
    link/ether f2:53:61:10:d0:65 brd ff:ff:ff:ff:ff:ff
    inet 10.1.1.112/24 scope global vmbr1
       valid_lft forever preferred_lft forever
1702526976422.png
 
Last edited:
Your Server just has 2 physical network Interfaces eno1 and eno2
 
  • Like
Reactions: Sasha
You can check with ethtool if it is connected
ethtool -i eno2
 
Code: 
oot@hq:~# ethtool -i eno1
driver: igb
version: 5.15.102-1-pve
firmware-version: 1.63, 0x800009fa
expansion-rom-version: 
bus-info: 0000:04:00.0
supports-statistics: yes
supports-test: yes
supports-eeprom-access: yes
supports-register-dump: yes
supports-priv-flags: yes

root@hq:~# ethtool -i eno2
driver: igb
version: 5.15.102-1-pve
firmware-version: 1.63, 0x800009fa
expansion-rom-version:
bus-info: 0000:04:00.1
supports-statistics: yes
supports-test: yes
supports-eeprom-access: yes
supports-register-dump: yes
supports-priv-flags: yes

root@hq:~# brctl show
bridge name    bridge id        STP enabled    interfaces
vmbr0        8000.0cc47a343ecc    no        eno1
vmbr1        8000.f2536110d065    no
 
Sasha said:
Hi, guys!
Would You help me to figure out what this network interface eno2 is? It appears every time after installing PM on that dedicated server and after trying to delete it via PM's GUI it appears again. What does it mean? Some hardware?

Code: 
root@hq:~# ip address
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
2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master vmbr0 state UP group default qlen 1000
    link/ether 0c:c4:7a:34:3e:cc brd ff:ff:ff:ff:ff:ff
    altname enp4s0f0
3: eno2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 0c:c4:7a:34:3e:cd brd ff:ff:ff:ff:ff:ff
    altname enp4s0f1
4: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 0c:c4:7a:34:3e:cc brd ff:ff:ff:ff:ff:ff
    inet 88.888.888.88/28 scope global vmbr0
       valid_lft forever preferred_lft forever
5: vmbr1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
    link/ether f2:53:61:10:d0:65 brd ff:ff:ff:ff:ff:ff
    inet 10.1.1.112/24 scope global vmbr1
       valid_lft forever preferred_lft forever
View attachment 59786
Click to expand...
 
Sorry, too early in the mornig, ethtool eno1 and ethtool eno2 without -i
 
brctl shows eno1 is the physical interface on vmbr0, while vmbr1 has no physical Interfaces connected
 
What is your setup, what are you trying to achieve, and how much do you know about networking?
 
  • Like
Reactions: Sasha
I'd like to achieve just a little more knowledge by carefully listening guru.
So it's a two physical network interface and eno2 is INactive, right?
Dedicated server description says just about one ))

Code: 
root@hq:~# ethtool eno1
Settings for eno1:
    Supported ports: [ TP ]
    Supported link modes:   10baseT/Half 10baseT/Full
                            100baseT/Half 100baseT/Full
                            1000baseT/Full
    Supported pause frame use: Symmetric
    Supports auto-negotiation: Yes
    Supported FEC modes: Not reported
    Advertised link modes:  10baseT/Half 10baseT/Full
                            100baseT/Half 100baseT/Full
                            1000baseT/Full
    Advertised pause frame use: Symmetric
    Advertised auto-negotiation: Yes
    Advertised FEC modes: Not reported
    Speed: 1000Mb/s
    Duplex: Full
    Auto-negotiation: on
    Port: Twisted Pair
    PHYAD: 1
    Transceiver: internal
    MDI-X: on (auto)
    Supports Wake-on: pumbg
    Wake-on: g
        Current message level: 0x00000007 (7)
                               drv probe link
    Link detected: yes
root@hq:~# ethtool eno2
Settings for eno2:
    Supported ports: [ TP ]
    Supported link modes:   10baseT/Half 10baseT/Full
                            100baseT/Half 100baseT/Full
                            1000baseT/Full
    Supported pause frame use: Symmetric
    Supports auto-negotiation: Yes
    Supported FEC modes: Not reported
    Advertised link modes:  10baseT/Half 10baseT/Full
                            100baseT/Half 100baseT/Full
                            1000baseT/Full
    Advertised pause frame use: Symmetric
    Advertised auto-negotiation: Yes
    Advertised FEC modes: Not reported
    Speed: Unknown!
    Duplex: Unknown! (255)
    Auto-negotiation: on
    Port: Twisted Pair
    PHYAD: 1
    Transceiver: internal
    MDI-X: off (auto)
    Supports Wake-on: d
    Wake-on: d
        Current message level: 0x00000007 (7)
                               drv probe link
    Link detected: no
 
I assume thIs this a hosted server?
Do you get multiple ip and mac adresses or just one?
 
  • Like
Reactions: Sasha
ubu said:
I assume thIs this a hosted server?
Do you get multiple ip and mac adresses or just one?
Click to expand...
Yes it's a hosted server. Host itself has one IP (one from IP's subnet we've got from provider).
And i use that IP to access Proxmox host itself.
But i intend to add container with apache and set second public IP to access web.

So physically that two IP (from host and from container) will use one network adapter, but here definitely a nuances with MAC exists,,,
 
Last edited:
Your ip for the proxmox host is configured on the vmbr0 interface, you can add the line
hwaddress 0c:c4:7a:34:3e:cc to your vmbr0 interface so i usses the mac from the eno1 interface (which is part of that bridge.

Your VMs and LXCs have their own ip and mac adresses on that bridge interface, ask your provider if that is ok.

The alternative is to have an internal network (eg. 192.168.1.0/24) on the vmbr1 bridge and have routing and nat/portforward on your proxmox host to the internet
 
  • Like
Reactions: Sasha
ubu said:
Your ip for the proxmox host is configured on the vmbr0 interface, you can add the line
hwaddress 0c:c4:7a:34:3e:cc to your vmbr0 interface so i usses the mac from the eno1 interface (which is part of that bridge.
Click to expand...
Do You mean a place /etc/network/interfaces?
But what is the goal of it?

Code: 
auto lo
iface lo inet loopback

iface eno1 inet manual

auto vmbr0
iface vmbr0 inet static
<------>address 88.888.888.88/28
<------>gateway 88.888.888.88
<------>bridge-ports eno1
<------>bridge-stp off
<------>bridge-fd 0

auto vmbr1
iface vmbr1 inet static
<------>address 10.1.1.112/24
<------>bridge-ports none
<------>bridge-stp off
<------>bridge-fd 0
 
auto lo
iface lo inet loopback

iface eno1 inet manual

auto vmbr0
iface vmbr0 inet static
<------>address 88.888.888.88/28
<------>hwaddress 0c:c4:7a:34:3e:cc Like this, some providers dont like it (that is block you) if you have another mac in their network
<------>gateway 88.888.888.88
<------>bridge-ports eno1
<------>bridge-stp off
<------>bridge-fd 0

auto vmbr1
iface vmbr1 inet static
<------>address 10.1.1.112/24
<------>bridge-ports none
<------>bridge-stp off
<------>bridge-fd 0
 
  • Like
Reactions: Sasha
You must log in or register to reply here.

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!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

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!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom
Back