Opened 8 years ago

Last modified 2 years ago

#6 assigned Patch submission

VLAN-Tagging (Pull Request)

Reported by: David Sommerseth Owned by: fknittel
Priority: major Milestone:
Component: Networking Version: OpenVPN git master branch (Community Ed)
Severity: Patch Queue: New / awaiting ACK Keywords:


This patch set is available via the 'feat_vlan_tagging' branch in openvpn-testing.git for review. It is not merged into allmerged at the moment. It needs an ACK to take that step. The branch will be rebuilt based on a better branch from Fabian Knittel in the near future - and before a merge into allmerged.

Change History (3)

comment:1 Changed 7 years ago by fknittel

Unfortunately, the patch has gathered some cobwebs. I'm still very interested in getting the VLAN support into a form that is acceptable for official inclusion, but I've seriously lacked the time to work on this. Hopefully after my next exam things will be different ...

The current state is available from our unofficial branch. It has been in nearly-production use in two locations for several months now, so at least our specific use-cases appear to work nicely.

Things that need to be done:

  • Rebase the branch on top of the current master (and check whether that's what the OpenVPN devs want).
  • Throw out anything that we're not currently using (i.e. stream-line the configuration options).
  • Create and document a simple test setup (and check whether the OpenVPN devs have any existing setups that could be adapted).
  • Convince others to perform the tests so that the patches can be acked.

comment:2 Changed 6 years ago by David Sommerseth

Owner: set to fknittel
Status: newassigned

This can certainly be considered in v2.4 ... so if still interesting, catching up on the current 'master' branch is certainly a good idea.

comment:3 Changed 2 years ago by Gert Döring

This has been lying around for quite a bit - it was "bubbled up" by a user who wants to have it, mentioning it in (just for reference).

This is still interesting, to me at least, but priorization needs to be done and there are bits we consider important to a larger number of users that should go in first - but as it's here in trac, it won't be totally forgotten.

Note: See TracTickets for help on using tickets.