[Kea-users] KEA DHCP and VLANS...

Dajka Tamás viper at vipernet.hu
Sun Feb 2 20:14:14 UTC 2020


Hi,

 

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.

 

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).

 

With openvswitch you’ll to nearly the same, but virtually. If openvswitch honors the tagged/untagged scenario correctly, than it’ll work.

 

Cheers,

 

               Tom

 

From: Kea-users [mailto:kea-users-bounces at lists.isc.org] On Behalf Of Talkabout
Sent: Sunday, February 2, 2020 7:42 PM
To: Oehlrich, Benedikt <boe at codemanufaktur.com>
Cc: kea-users at lists.isc.org
Subject: Re: [Kea-users] KEA DHCP and VLANS...

 

Hi Ben,

 

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.

 

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.

 

Thanks!

 

Gesendet von Mail <https://go.microsoft.com/fwlink/?LinkId=550986>  für Windows 10

 

Von: Oehlrich, Benedikt <mailto:boe at codemanufaktur.com> 
Gesendet: Sonntag, 2. Februar 2020 19:25
An: Talkabout <mailto:talk.about at gmx.de> 
Cc: Dajka Tamás <mailto:viper at vipernet.hu> ; kea-users at lists.isc.org <mailto:kea-users at lists.isc.org> 
Betreff: Re: [Kea-users] KEA DHCP and VLANS...

 

Hey,

 

I sadly don't have any information about the openvswitch configuration, as I started to work on our DHCP when we migrated to the relay based solution.

But from my understanding you will get multiple interfaces e.g vlan30, vlan100 etc. where you only get the traffic from the specified vlans. That means if you have one connection from your switch to your dhcp server where all tagged vlan traffic is going through, you can get the untagged traffic separated into the openvswitch interfaces. 

These interfaces will then be handled like in your first emails kea configuration.

 

Cheers,

 

 

Am Sa., 1. Feb. 2020 um 23:15 Uhr schrieb Talkabout <talk.about at gmx.de <mailto:talk.about at gmx.de> >:

Hi Ben,

 

this sounds interesting. Can you give some more Information how you configured your System to work that way? I am running Debian Buster Linux Distribution and openvswitch seems to be available in the repos. In my case what I Need is Forwarding untagged traffic from eth0 to a new interface eth0.x which is tagged and can be used by KEA to handle DHCP requests.

 

Thanks!

 

Gesendet von Mail <https://go.microsoft.com/fwlink/?LinkId=550986>  für Windows 10

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/kea-users/attachments/20200202/5a3db2ba/attachment-0001.htm>


More information about the Kea-users mailing list