I don’t see the multicast address for the BPDU in the bridge. Can you
explicitly add the BPDU multicast address to the Fortville HW filters using the
‘ip maddr’ command? Normally a service will register the associated multicast
addresses with the network interface but that doesn’t seem to be
I really can’t say for sure – as I mentioned a service that requires
registering a multicast address will usually do that and the address will get
added to the filters. Why the RSTP service isn’t registering the multicast
address is puzzling – or perhaps, it is registering the multicast
Sure enough, that did the trick!
Now, the next question is, why do I need to do that on i40e when I don't on
e1000? I don't see the BPDU maddr present in the 'ip mroute' or 'bridge fdb'
output on the e1000 side of the link, which works by default.
e1000 side of the link - 00:21:28:f9:09:5d
Hi:
I have a small 4 node private network where each node has 2 ports, with each
port directly connected to a port on another node in such a way that a ring
topology is formed. Two of the nodes have NIC's controlled by the e1000
driver, two of the nodes have NIC's controlled by the i40e
-Original Message-
From: Maule Mark [mailto:mark_ma...@yahoo.com]
Sent: Thursday, April 30, 2015 8:08 AM
To: e1000-devel@lists.sourceforge.net
Subject: [E1000-devel] i40e and RSTP
Hi:
I have a small 4 node private network where each node has 2 ports, with
each port directly
eth1 is the e40i port attached to the bridge. Currently I have only one port
bridged in order to prevent the loop.
eth1 Link encap:Ethernet HWaddr 00:10:E0:65:2E:65
WNFFEE # bridge fdb00:10:e0:65:2e:65 dev eth1
permanent00:21:28:f9:09:2c dev eth100:21:28:f9:09:5c dev
