Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • F foris-controller-openvpn-module
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 12
    • Issues 12
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 1
    • Merge requests 1
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Turris
  • Foris Controller
  • foris-controller-openvpn-module
  • Issues
  • #22

Closed
Open
Created Mar 08, 2021 by Vojtech Myslivec@vmyslivec

VPN server is not accessible after transport protocol change

Steps to reproduce

Tried with reForis on MOX in HBT/TOS 5.1.10

  1. Setup default (via UDP) and working OpenVPN server.
  2. Restart a router to make sure everything works as expected after reboot
  3. Go to reforis, exchange trasport protocol to UDP and click save

Now, OpenVPN server becomes inaccessible - it does not listen on UDP anymore and TCP port 1194 is closed by the firewall.

Recommended solution

The root cause is IMO in reloading the firewall which leads to not applying the rule to open TCP prot (it also let the UDP port open!). Once I restart the firewall manually via ssh, the openvpn server becomes accessible.

Please also verify that the openvpn service is restarted after the change in step 3.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking