Hi Johann,
Also, note that VlanId is optional. It makes more sense for switch ports.
Regarding my “em1” (Ethernet management) interface, probably I should have send
an example without VLANId.
And “BridgeFDB”s are in the .network following the logic of routes.
To be clear look at the outputs below:
1. for a normal port:
>bridge fdb show dev em1
44:44:12:34:56:70 self permanent
44:44:12:34:56:71 self permanent
33:33:00:00:00:01 self permanent
01:00:5e:00:00:01 self permanent
33:33:ff:8f:e7:3f self permanent
01:00:5e:00:00:fc self permanent
33:33:00:01:00:03 self permanent
2. for a switch port:
>bridge fdb show dev sw0p1
14:44:12:34:56:70 vlan 2 self permanent
14:44:12:34:56:71 vlan 10 self permanent
/Alin
From: systemd-devel [mailto:systemd-devel-boun...@lists.freedesktop.org] On
Behalf Of "Jóhann B. Guðmundsson"
Sent: Thursday, December 18, 2014 5:51 AM
To: systemd-devel@lists.freedesktop.org
Subject: Re: [systemd-devel] [PATCH v3] Add FDB support
On 12/17/2014 05:46 PM, "Jóhann B. Guðmundsson" wrote:
On 12/17/2014 03:35 PM, Alin Rauta wrote:
Hi Tom,
I've formatted the patch based on our previous discussions. This one has
support only for adding FDB entries.
An example configuration is like below:
[Match]
Name=em1
[Network]
DHCP=v4
[BridgeFDB]
MACAddress=44:44:12:34:56:71
VLANId=9
[BridgeFDB]
MACAddress=44:44:12:34:56:70
VLANId=2
br0
Please let me know what you think.
Thanks,
Alin
If I start trying to match this with the entire type network files and their
path ( feel free to correct me where I'm wrong here )
It would have to look like this...
Ignore my mac address entry confusion with the bridge mac addresses in the MAC
learning table and the interface mac address here ( em1 ) which somewhat would
have been eliminated if we had [BridgePort] and arguably [BridgePortFDB]
sections in the network file
JBG
JBG
_______________________________________________
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
