Skip to content
GitLab
    • GitLab: the DevOps platform
    • Explore GitLab
    • Install GitLab
    • How GitLab compares
    • Get started
    • GitLab docs
    • GitLab Learn
  • Pricing
  • Talk to an expert
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    • Switch to GitLab Next
    Projects Groups Topics Snippets
  • Register
  • Sign in
  • ocserv ocserv
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
    • Locked files
  • Issues 80
    • Issues 80
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 11
    • Merge requests 11
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • Schedules
    • Test cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • OpenConnect VPN projectsOpenConnect VPN projects
  • ocservocserv
  • Issues
  • #316
Closed
Open
Issue created Jun 27, 2020 by William Dauchy@wdauchyContributor

minimal namespace support

We have a setup such as:

  • physical interface is in the root namespace
  • VIP being bind for ocserv listening is placed within a dedicated namespace

We would like to be able to keep the main ocserv process in the root namespace and bind the IP within a dedicated namespace. The main advantage is to easily isolate the public traffic on a given host and to minimise performance penalties associated with a conventional bridge + veth setup. As an example, other projects such as HAProxy made the choice to allow users to bind each IP in a specific netns, this allows the healtchecks and backend traffic to happen in the root netns (see https://cbonte.github.io/haproxy-dconv/2.1/configuration.html#5.1-namespace)

Do you think it would be an acceptable feature? I'm willing to work on a patch as a first proposal.

Edited Jun 27, 2020 by William Dauchy
Assignee
Assign to
Time tracking