Unknown devices (ifconfig)

Xela

Member
Oct 12, 2017
41
0
11
52
Dear Support Forum
A Proxmox server with 1 VM is running. After an ifconfig, the result shows more devices than configured:

eth2: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
ether xx:xx:xx:xx:xx:xx txqueuelen 1000 (Ethernet)
RX packets 15780815 bytes 3513329871 (3.2 GiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 7625059 bytes 6019170701 (5.6 GiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

fwbr100i0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1450
ether xx:xx:xx:xx:xx:xx txqueuelen 1000 (Ethernet)
RX packets 8047366 bytes 435214914 (415.0 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

fwln100i0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
ether xx:xx:xx:xx:xx:xx txqueuelen 1000 (Ethernet)
RX packets 13674272 bytes 2006102662 (1.8 GiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 5004257 bytes 5308307316 (4.9 GiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

fwpr100p0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1450
ether xx:xx:xx:xx:xx:xx txqueuelen 1000 (Ethernet)
RX packets 5004257 bytes 5308307316 (4.9 GiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 13674272 bytes 2006102662 (1.8 GiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Local Loopback)
RX packets 687797 bytes 527723430 (503.2 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 687797 bytes 527723430 (503.2 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

tap100i0: flags=4419<UP,BROADCAST,RUNNING,PROMISC,MULTICAST> mtu 1450
ether xx:xx:xx:xx:xx:xx txqueuelen 1000 (Ethernet)
RX packets 5005655 bytes 5308423452 (4.9 GiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 12128114 bytes 1884226231 (1.7 GiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

vmbr0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1450
inet xxx.xxx.xxx.xxx netmask 255.255.255.0 broadcast 193.70.14.255
inet6 xxxx::xxxx:xxxx:xxxx:xxxx prefixlen 64 scopeid 0x20<link>
inet6 xxxx:xxxx:xxxx:xxxx:: prefixlen 64 scopeid 0x0<global>
ether xx:xx:xx:xx:xx:xx txqueuelen 1000 (Ethernet)
RX packets 9016115 bytes 1827689705 (1.7 GiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 811028 bytes 598267671 (570.5 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

Known: eth2, lo, vmbr0
Unknown: fwbr100i0, fwln100i0, fwpr100p0, tap100i0, tap100i0

Where do these unkown devices coming from??? Is it wanted like that?
 

wolfgang

Proxmox Staff Member
Oct 1, 2014
6,496
493
103
Hi Xela,

This are devices which will created when you start a Guest.
Or more presicely the Gust network ports.

fwbr<VMID>i<network interface X> is the firewall bridge where the filtering happens.
fwpr<VMID>i<network interface X> is the bridge in device.
fwln<VMID>i<network interface X> is the bridge out device.
tap<VMID>i<network interface X> is the connector port for the guest.

You have not to care about this devices they will handled by PVE.
 

Xela

Member
Oct 12, 2017
41
0
11
52
Dear Wolfgang, thank you for the information ;)

Best regards
Alexander
 

geckoneer

Member
Sep 24, 2010
3
0
21
Hi Xela,

This are devices which will created when you start a Guest.
Or more presicely the Gust network ports.

fwbr<VMID>i<network interface X> is the firewall bridge where the filtering happens.
fwpr<VMID>i<network interface X> is the bridge in device.
fwln<VMID>i<network interface X> is the bridge out device.
tap<VMID>i<network interface X> is the connector port for the guest.

You have not to care about this devices they will handled by PVE.

What do prefixes pr and ln mean? What are the mnemonics?

And why do we have to have 3 interfaces (br, pr and ln) for firewalling instead of just one?
 

wolfgang

Proxmox Staff Member
Oct 1, 2014
6,496
493
103

Lin4Fun

Member
Feb 19, 2018
5
0
6
44
Hello,rding this as well.

I had the same question while I came over maybe a problem. At least is Netdata reporting a lot of problems regarding this devices.
This for every single VM and device. If I look at the times between this messages are logged I would expect performance isseus do to this behavior?
Firewall is disabled in proxmox and no rules are defined.
What to do about this?

The kernel log is full of these messages:

Code:
Mar 19 05:54:51 pscl-91 kernel: [457057.483752] device fwln218o0 entered promiscuous mode
Mar 19 05:54:51 pscl-91 kernel: [457057.499014] fwbr218i0: port 2(fwln218o0) entered blocking state
Mar 19 05:54:51 pscl-91 kernel: [457057.499016] fwbr218i0: port 2(fwln218o0) entered disabled state
Mar 19 05:54:51 pscl-91 kernel: [457057.499149] fwbr218i0: port 2(fwln218o0) entered blocking state
Mar 19 05:54:51 pscl-91 kernel: [457057.499150] fwbr218i0: port 2(fwln218o0) entered forwarding state
Mar 19 06:13:42 pscl-91 kernel: [458188.755059] device tap219i0 entered promiscuous mode
Mar 19 06:31:42 pscl-91 kernel: [459268.737746] fwbr221i0: port 1(tap221i0) entered disabled state
Mar 19 06:31:42 pscl-91 kernel: [459268.783256] fwbr221i0: port 2(fwln221o0) entered disabled state
Mar 19 06:31:42 pscl-91 kernel: [459268.784058] device fwln221o0 left promiscuous mode
Mar 19 06:31:42 pscl-91 kernel: [459268.784065] fwbr221i0: port 2(fwln221o0) entered disabled state
Mar 19 06:31:44 pscl-91 kernel: [459270.003076] device tap221i0 entered promiscuous mode
Mar 19 06:31:44 pscl-91 kernel: [459270.031985] fwbr221i0: port 1(tap221i0) entered blocking state
Mar 19 06:31:44 pscl-91 kernel: [459270.031988] fwbr221i0: port 1(tap221i0) entered disabled state
Mar 19 06:31:44 pscl-91 kernel: [459270.032119] fwbr221i0: port 1(tap221i0) entered blocking state
Mar 19 06:31:44 pscl-91 kernel: [459270.032120] fwbr221i0: port 1(tap221i0) entered forwarding state
Mar 19 06:31:44 pscl-91 kernel: [459270.066431] device fwln221o0 entered promiscuous mode
Mar 19 06:31:44 pscl-91 kernel: [459270.080968] fwbr221i0: port 2(fwln221o0) entered blocking state
Mar 19 06:31:44 pscl-91 kernel: [459270.080971] fwbr221i0: port 2(fwln221o0) entered disabled state
Mar 19 06:31:44 pscl-91 kernel: [459270.081090] fwbr221i0: port 2(fwln221o0) entered blocking state
Mar 19 06:31:44 pscl-91 kernel: [459270.081092] fwbr221i0: port 2(fwln221o0) entered forwarding state

Br,
 

behnam

Member
Jul 29, 2017
19
0
6
35
Hello,rding this as well.

I had the same question while I came over maybe a problem. At least is Netdata reporting a lot of problems regarding this devices.
This for every single VM and device. If I look at the times between this messages are logged I would expect performance isseus do to this behavior?
Firewall is disabled in proxmox and no rules are defined.
What to do about this?

The kernel log is full of these messages:

Code:
Mar 19 05:54:51 pscl-91 kernel: [457057.483752] device fwln218o0 entered promiscuous mode
Mar 19 05:54:51 pscl-91 kernel: [457057.499014] fwbr218i0: port 2(fwln218o0) entered blocking state
Mar 19 05:54:51 pscl-91 kernel: [457057.499016] fwbr218i0: port 2(fwln218o0) entered disabled state
Mar 19 05:54:51 pscl-91 kernel: [457057.499149] fwbr218i0: port 2(fwln218o0) entered blocking state
Mar 19 05:54:51 pscl-91 kernel: [457057.499150] fwbr218i0: port 2(fwln218o0) entered forwarding state
Mar 19 06:13:42 pscl-91 kernel: [458188.755059] device tap219i0 entered promiscuous mode
Mar 19 06:31:42 pscl-91 kernel: [459268.737746] fwbr221i0: port 1(tap221i0) entered disabled state
Mar 19 06:31:42 pscl-91 kernel: [459268.783256] fwbr221i0: port 2(fwln221o0) entered disabled state
Mar 19 06:31:42 pscl-91 kernel: [459268.784058] device fwln221o0 left promiscuous mode
Mar 19 06:31:42 pscl-91 kernel: [459268.784065] fwbr221i0: port 2(fwln221o0) entered disabled state
Mar 19 06:31:44 pscl-91 kernel: [459270.003076] device tap221i0 entered promiscuous mode
Mar 19 06:31:44 pscl-91 kernel: [459270.031985] fwbr221i0: port 1(tap221i0) entered blocking state
Mar 19 06:31:44 pscl-91 kernel: [459270.031988] fwbr221i0: port 1(tap221i0) entered disabled state
Mar 19 06:31:44 pscl-91 kernel: [459270.032119] fwbr221i0: port 1(tap221i0) entered blocking state
Mar 19 06:31:44 pscl-91 kernel: [459270.032120] fwbr221i0: port 1(tap221i0) entered forwarding state
Mar 19 06:31:44 pscl-91 kernel: [459270.066431] device fwln221o0 entered promiscuous mode
Mar 19 06:31:44 pscl-91 kernel: [459270.080968] fwbr221i0: port 2(fwln221o0) entered blocking state
Mar 19 06:31:44 pscl-91 kernel: [459270.080971] fwbr221i0: port 2(fwln221o0) entered disabled state
Mar 19 06:31:44 pscl-91 kernel: [459270.081090] fwbr221i0: port 2(fwln221o0) entered blocking state
Mar 19 06:31:44 pscl-91 kernel: [459270.081092] fwbr221i0: port 2(fwln221o0) entered forwarding state

Br,

I Have Same log in /var/log/message and Server Network is down.

Code:
Server6 kernel: [184657.343743] e1000e: enp0s31f6 NIC Link is Up  1000 Mbps Full Duplex, Flow Control: Rx/Tx
May 15 03:09:41 Server6 kernel: [184657.343885] vmbr0: port 1(enp0s31f6) entered    blocking state
May 15 03:09:41 Server6 kernel: [184657.343967] vmbr0: port 1(enp0s31f6) entered    forwarding state
May 15 03:09:52 Server6 kernel: [184668.924387] vmbr0: port 1(enp0s31f6) entered    disabled state

and I should reboot the server to network UP again.
 
Last edited:

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 your own in 60 seconds.

Buy now!