https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264883
Bug ID: 264883
Summary: ena and epair interfaces cannot be members of the same
bridge
Product: Base System
Version: 13.1-RELEASE
Hardware: Any
OS: Any
Status: New
Severity: Affects Only Me
Priority: ---
Component: kern
Assignee: [email protected]
Reporter: [email protected]
Running FreeBSD in AWS EC2, it is not possible to join the ena0 interface to a
bridge at the same time as an epair interface.
The commands below result in the same error on FreeBSD 13.1, 12.3, 11.4.
With FreeBSD 10.4 in AWS EC2, the xn driver is used instead of the ena driver,
and this same sequence of commands then works without any issue.
This same sequence of commands also works in Vultr which uses the vtnet driver
instead of the ena driver. It also works on my laptop with the em driver
instead of the ena driver.
ec2-user@freebsd:~ $ su
root@freebsd:/home/ec2-user # ifconfig bridge create
bridge0
root@freebsd:/home/ec2-user # ifconfig epair create
epair0a
root@freebsd:/home/ec2-user # ifconfig bridge0 addm ena0
root@freebsd:/home/ec2-user # ifconfig bridge0 addm epair0a
ifconfig: BRDGADD epair0a: Invalid argument
root@freebsd:/home/ec2-user # ifconfig bridge0 deletem ena0
root@freebsd:/home/ec2-user # ifconfig bridge0 addm epair0a
root@freebsd:/home/ec2-user # ifconfig bridge0 addm ena0
ifconfig: BRDGADD ena0: Invalid argument
root@freebsd:/home/ec2-user # ifconfig
ena0: flags=8863<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 9001
options=422<TXCSUM,JUMBO_MTU,LRO>
ether xxx
inet6 xxx%ena0 prefixlen 64 scopeid 0x1
inet xxx netmask 0xfffff000 broadcast xxx
media: Ethernet autoselect (Unknown <full-duplex>)
status: active
nd6 options=23<PERFORMNUD,ACCEPT_RTADV,AUTO_LINKLOCAL>
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
options=680003<RXCSUM,TXCSUM,LINKSTATE,RXCSUM_IPV6,TXCSUM_IPV6>
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2
inet 127.0.0.1 netmask 0xff000000
groups: lo
nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
bridge0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
ether 58:9c:fc:00:20:47
inet 0.0.0.0 netmask 0xff000000 broadcast 255.255.255.255
id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15
maxage 20 holdcnt 6 proto rstp maxaddr 2000 timeout 1200
root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0
member: epair0a flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
ifmaxaddr 0 port 4 priority 128 path cost 2000
groups: bridge
nd6 options=3<PERFORMNUD,ACCEPT_RTADV>
epair0a: flags=8962<BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu
1500
options=8<VLAN_MTU>
ether 02:3c:b7:88:ff:0a
groups: epair
media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
status: active
nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
epair0b: flags=8862<BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=8<VLAN_MTU>
ether 02:3c:b7:88:ff:0b
groups: epair
media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
status: active
nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
--
You are receiving this mail because:
You are the assignee for the bug.
