Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
D
dhcp
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 64
    • Issues 64
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 16
    • Merge Requests 16
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • ISC Open Source Projects
  • dhcp
  • Issues
  • #135

Closed
Open
Opened Sep 06, 2020 by Frederic Bor@f-bor

Virtual interface support

name: Virtual interface support
about: with the rise of VTI IPsec usage, there is a need for virtual interface support in dhcp relay.

Is your feature request related to a problem? Please describe.

I would like to use a remote dhcp server and relay request to it threw VTI interfaces.

Describe the solution you'd like

I'd like to have support for virtual interfaces so I can relay dhcp requests threw them.

Describe alternatives you've considered

The only alternative when using VTI is to have a local dhcp server, instead of a remote one. But when you start to have some small remote sites, it's a lot less convenient than simply activate dhcp relay and setting up the ip of the remote server.

Additional context

The attached patch is implementing this for IFT_TUNNEL interface type.

I had some trouble with BPF, getting the whole packet. I was only having the first 67 bytes. I'm not sure why. It was working correctly in a small POC code environnement but not within dhcrelay. I managed do get it works by adding a "load (uint)(-1) into the accumulator" instruction before returning the packet.

We are using this patch in production since march on a dozen of firewalls, it's working well. It's untested except on pfSense/FreeBSD.

Participating in development

I am willing to participate in the feature development, discusions, tests. I will see how to do this on linux. Could I have a project allocation to this intent ?

Contacting you

Here is nice, or github.

vti_support.patch

Edited Sep 06, 2020 by Frederic Bor
Assignee
Assign to
4.4.3
Milestone
4.4.3
Assign milestone
Time tracking
None
Due date
None
Reference: isc-projects/dhcp#135