OpenVPN/Supporting "route-gateway dhcp" on non-Windows platforms

From Secure Computing Wiki
Revision as of 06:16, 12 March 2010 by Mattock (Talk | contribs) (Rationale)

Jump to: navigation, search

Rationale

At this point it makes sense to involve the users as much as possible.

  • Why should this feature be implemented?
    • What benefit would this feature provide to users?
    • What benefit would this feature provide to developers?
  • How many would benefit from this feature?

Alternatives

  • What can be done to circumvent lack of this feature?

Implementation options

Option 1: add a DHCP client to OpenVPN itself

Overview

High-level overview of this solution.

Benefits

Benefits compared to other solutions.

  • Does not depend on package maintainers as much as option 2

Concerns

Potential problems with taking this approach (and how to address them)

  • Adds complexity to OpenVPN. There's no way to address this issue.
  • May not completely remove complexity from the package maintainers

Tasks

List of things that need to done to make this work.

  • Sort out how to manage /etc/resolv.conf (or equavalent)

Option 2: let distribution maintainers handle DHCP integration

Overview

High-level overview of this solution.

Benefits

Benefits compared to other solutions.

  • Allows us to leverage the non-OpenVPN OSS community (OpenVPN packages) to the integration, saving OpenVPN developers a lot of trouble.

Concerns

Potential problems with taking this approach (and how to address them)

  • Some distribution maintainers might not do a good job in integrating their DHCP clients with OpenVPN. This problem can be mitigated by proving good sample scripts, documentation etc. so that the integration is as straightforward as possible.

Tasks

List of things that need to done to make this work.

References