<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 2.0cm 70.85pt;}
div.WordSection1
{page:WordSection1;}
--></style></head><body lang=DE link=blue vlink="#954F72"><div class=WordSection1><p class=MsoNormal>Hi Tom,</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I tried your „dirty“ solution but unfortunately it is now compatible with my nfsroot boot mechanism. Nevertheless I was able to solve my issue in a different way. For anybody who might have the same Problem in the future:</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>- Create a macvlan device via systemd-networkd:</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>eth1.netdev</p><p class=MsoNormal>[code][NetDev]</p><p class=MsoNormal>Name=eth1</p><p class=MsoNormal>Kind=macvlan</p><p class=MsoNormal>MACAddress=xx:xx:xx:xx:xx:xx (generate a unique mac address and put it here)</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>[MACVLAN]</p><p class=MsoNormal>Mode=bridge[/code]</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>eth1.network</p><p class=MsoNormal>[code][Match]</p><p class=MsoNormal>Name=eth1</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>[Network]</p><p class=MsoNormal>Address=192.168.xx.xx/24 (put a valid ip from your subnet for all 3 values)</p><p class=MsoNormal>Gateway=192.168.xx.x</p><p class=MsoNormal>DNS=192.168.xx.xx</p><p class=MsoNormal>IPForward=yes[/code]</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>- on the physical device definition you need to define that it belongs to the created mac vlan:</p><p class=MsoNormal>[code][Match]</p><p class=MsoNormal>Name=eth0 (your physical device)</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>[Network]</p><p class=MsoNormal>... (keep previous values)</p><p class=MsoNormal>MACVLAN=eth1</p><p class=MsoNormal>...[/code]</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>When now systemd-networkd gets restarted, eth1 device is considered a separate network interface with a valid hardware address and ip. Now creating a "raw" bind on that device does not interfere with the vlan any more and KEA DHCP Server is assigning correct ips.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Bye</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Gesendet von <a href="https://go.microsoft.com/fwlink/?LinkId=550986">Mail</a> für Windows 10</p><p class=MsoNormal><o:p> </o:p></p><div style='mso-element:para-border-div;border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal style='border:none;padding:0cm'><b>Von: </b><a href="mailto:viper@vipernet.hu">Dajka Tamás</a><br><b>Gesendet: </b>Sonntag, 2. Februar 2020 21:14<br><b>An: </b><a href="mailto:talk.about@gmx.de">'Talkabout'</a>; <a href="mailto:boe@codemanufaktur.com">'Oehlrich, Benedikt'</a><br><b>Cc: </b><a href="mailto:kea-users@lists.isc.org">kea-users@lists.isc.org</a><br><b>Betreff: </b>RE: [Kea-users] KEA DHCP and VLANS...</p></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span lang=HU style='color:#1F497D;mso-fareast-language:EN-US'>Hi,<o:p></o:p></span></p><p class=MsoNormal><span lang=HU style='color:#1F497D;mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span lang=HU style='color:#1F497D;mso-fareast-language:EN-US'>that’s why I’ve written the dirty workaround. Since you’ve only trouble with the native vlan, than a possible solution is to ’tag’ the native vlan with a crosslink on the swicht (looping back to itself). This way you can tag the native vlan transparently.<o:p></o:p></span></p><p class=MsoNormal><span lang=HU style='color:#1F497D;mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span lang=HU style='color:#1F497D;mso-fareast-language:EN-US'>So you create a new vlan – vlan 20 let’s say – remove the ip from the pysical interface and assign it to interface vlan20. On the switch you cross connect a native vlan port with a vlan 20 access port „bridgeing” it together (all packets in the native vlan will appear to KEA as vlan 20 packets).<o:p></o:p></span></p><p class=MsoNormal><span lang=HU style='color:#1F497D;mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span lang=HU style='color:#1F497D;mso-fareast-language:EN-US'>With openvswitch you’ll to nearly the same, but virtually. If openvswitch honors the tagged/untagged scenario correctly, than it’ll work.<o:p></o:p></span></p><p class=MsoNormal><span lang=HU style='color:#1F497D;mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span lang=HU style='color:#1F497D;mso-fareast-language:EN-US'>Cheers,<o:p></o:p></span></p><p class=MsoNormal><span lang=HU style='color:#1F497D;mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span lang=HU style='color:#1F497D;mso-fareast-language:EN-US'> Tom<o:p></o:p></span></p></div></body></html>