would this work the same for VXLAN?<br><br><div class="gmail_quote">On Thu Dec 11 2014 at 11:59:05 AM Rauta, Alin <<a href="mailto:alin.rauta@intel.com">alin.rauta@intel.com</a>> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Lennart,<br>
<br>
Thanks for your quick response.<br>
<br>
Regarding the naming "FDBEntry". My inspiration was the bridge tool command.<br>
To add an entry using bridge command:<br>
"bridge fdb add 44:44:12:34:56:73 dev em1 vlan 10 "<br>
<br>
If "FDBControlled" is no (default value) then the forwarding database table for current port is not touched even if we have entries in the [FDBEntry] section of the file.<br>
The reason behind introducing "FDBControlled" is that we want to have the table cleared even if we don't want to add entries.<br>
<br>
So, if FDBControlled is set to yes, networkd clears the existing entries (if any) and adds those specified in the FDBEntry section(if any).<br>
<br>
Do you have any other suggestion for [FDBEntry] ?<br>
<br>
Best Regards,<br>
Alin<br>
-----Original Message-----<br>
From: Lennart Poettering [mailto:<a href="mailto:lennart@poettering.net" target="_blank">lennart@poettering.net</a><u></u>]<br>
Sent: Thursday, December 11, 2014 4:16 PM<br>
To: Rauta, Alin<br>
Cc: <a href="mailto:systemd-devel@lists.freedesktop.org" target="_blank">systemd-devel@lists.<u></u>freedesktop.org</a>; Kinsella, Ray<br>
Subject: Re: [systemd-devel] [PATCH] Add FDB support<br>
<br>
On Thu, 11.12.14 08:07, Alin Rauta (<a href="mailto:alin.rauta@intel.com" target="_blank">alin.rauta@intel.com</a>) wrote:<br>
<br>
> Hi,<br>
><br>
> I've added support for handling the forwarding database table for a port.<br>
> FDB entries can be configured statically through the ".network" files.<br>
><br>
> To resume,<br>
> - I've added a new boolean for the main network structure, named "FDBControlled" which is read from the .network file and defaults to false.<br>
> - I've added a new section "FDBEntry" accepting 2 key-value pairs:<br>
> -MACAddress (mandatory)<br>
> -VLAN (optional)<br>
><br>
> When FDBControlled is set to "yes" in the network section, networkd:<br>
> - gets the FDB entries for current port;<br>
> - clears them<br>
> - configures those specified in the [FDBEntry] section.<br>
><br>
> Configuration example:<br>
><br>
> [Network]<br>
> DHCP=v4<br>
> FDBControlled=yes<br>
><br>
> [FDBEntry]<br>
> MACAddress=44:44:12:34:56:71<br>
> VLAN=9<br>
><br>
> [FDBEntry]<br>
> MACAddress=44:44:12:34:56:72<br>
> VLAN=10<br>
<br>
<br>
Hmm, quick thoughts regarding the naming: can we find a better name than [FDBEntry] for this? At least I cannot really make much sense of this.<br>
<br>
Could you improve the man page a bit, explaining what "fdb" actually is?<br>
<br>
Currently VLANs are configured in a [VLAN] section, with an Id= setting to configure the id. Maybe following this naming the setting you introduce above should be called VLANId?<br>
<br>
What happens if FDBControlled is no, but still FDBEntrys specified?<br>
<br>
Lennart<br>
<br>
--<br>
Lennart Poettering, Red Hat<br>
______________________________<u></u>_________________<br>
systemd-devel mailing list<br>
<a href="mailto:systemd-devel@lists.freedesktop.org" target="_blank">systemd-devel@lists.<u></u>freedesktop.org</a><br>
<a href="http://lists.freedesktop.org/mailman/listinfo/systemd-devel" target="_blank">http://lists.freedesktop.org/<u></u>mailman/listinfo/systemd-devel</a><br>
</blockquote></div>