<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;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:36.0pt;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
.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;}
/* List Definitions */
@list l0
{mso-list-id:1819688915;
mso-list-type:hybrid;
mso-list-template-ids:2025462208 -1 67567641 67567643 67567631 67567641 67567643 67567631 67567641 67567643;}
@list l0:level1
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
ol
{margin-bottom:0cm;}
ul
{margin-bottom:0cm;}
--></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>let me get this straight:</p><p class=MsoNormal><o:p> </o:p></p><ol style='margin-top:0cm' start=1 type=1><li class=MsoListParagraph style='margin-left:0cm;mso-list:l0 level1 lfo1'>Create VLAN on switch (vlan20)</li><li class=MsoListParagraph style='margin-left:0cm;mso-list:l0 level1 lfo1'>Create VLAN 20 interface on dhcp server and move the physical address to the new interface</li><li class=MsoListParagraph style='margin-left:0cm;mso-list:l0 level1 lfo1'>Bridge native VLAN port on swtich to VLAN 20 port on switch</li></ol><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>The result should be that the dhcp Server gets all packages in VLAN 20. What I am a Little bit confused About is why the „bridging“ causes the packets to arrive as vlan20 tag. Is it because the switch sends received packets on the untagged port, receives them on the tagged port and Forwards them (tagged) again to all ports that are members of the tag? In such a case what I also Need to do is to make sure that the port, where the dhcp Server is connected, is a tagged member of VLAN 1, correct?</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>What are the disadvantages of this „hack“? It seems to me that the Network traffic increases. Basically traffic that was send previously only to untagged ports now will also find its way to all ports tagged with VLAN 1. Is this all or do I have to expect other issues?</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Thanks!</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><p class=MsoNormal><span lang=HU style='color:#1F497D;mso-fareast-language:EN-US'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal><b><span lang=HU>From:</span></b><span lang=HU> Kea-users [mailto:kea-users-bounces@lists.isc.org] <b>On Behalf Of </b>Talkabout<br><b>Sent:</b> Sunday, February 2, 2020 7:42 PM<br><b>To:</b> Oehlrich, Benedikt <boe@codemanufaktur.com><br><b>Cc:</b> kea-users@lists.isc.org<br><b>Subject:</b> Re: [Kea-users] KEA DHCP and VLANS...<o:p></o:p></span></p></div></div><p class=MsoNormal><span lang=HU><o:p> </o:p></span></p><p class=MsoNormal>Hi Ben,<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>in my case I think the prerequisite is a Little bit different. I already have 3 vlans on the dhcp Server, and if I configure only those for dhcp then everything works as expected. The Problem occurs when I want to add the physical device (eth0, untagged) to dhcp, because then, as KEA dhcp Server binds in „raw“ mode, untagged and tagged traffic is delivered via this interface. Because the implementation in KEA dhcp Server does not correctly handle this „mixed“ (untagged/tagged) traffic, it is assigning incorrect ips. I am not sure if using openvswitch can solve that for me.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>My hope is that the KEA Team will take care of that and fix it, because in my eyes this is a bug and big Limitation.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Thanks!<o:p></o:p></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<o:p></o:p></p></div></body></html>