OPNsense
  • Home
  • Help
  • Search
  • Login
  • Register

  • OPNsense Forum »
  • Archive »
  • 17.1 Legacy Series »
  • [solved] OpenVPN selective routing
« previous next »
  • Print
Pages: [1]

Author Topic: [solved] OpenVPN selective routing  (Read 2919 times)

cake

  • Jr. Member
  • **
  • Posts: 53
  • Karma: 13
    • View Profile
[solved] OpenVPN selective routing
« on: February 15, 2017, 09:24:07 am »
I had OpenVPN working previously, but have spent over a day on this with out any luck.
I have the Qotom box with 4 Intel LANs. Not sure how I broke this, but I had 1 whole interface that was routed to OpenVPN (Client to Server) Opnsense was the client.

Well the client connects, however all interfaces are getting routed through the vpn. I have played quite a bit with NAT and Firewall rules, but I still may be missing something. I could post some screen shots if someone on here could help me get this sorted. This kinda stopped working around the time I updated to 17.1
« Last Edit: February 16, 2017, 12:08:50 am by cake »
Logged

djGrrr

  • Full Member
  • ***
  • Posts: 112
  • Karma: 22
    • View Profile
Re: OpenVPN selective routing
« Reply #1 on: February 15, 2017, 03:02:11 pm »
Make sure you are on 17.1.1 first, if that does not fix the problems, then run this command in shell / console as root:
sysctl net.pf.share_forward=0
Logged

cake

  • Jr. Member
  • **
  • Posts: 53
  • Karma: 13
    • View Profile
Re: [solved] OpenVPN selective routing
« Reply #2 on: February 16, 2017, 12:12:16 am »
Thank you very much djGrrr. Your suggestion to update from 17.1 to 17.1.1 fixed it. Now it all (firewall rules) makes sense again! lol

Logged

  • Print
Pages: [1]
« previous next »
  • OPNsense Forum »
  • Archive »
  • 17.1 Legacy Series »
  • [solved] OpenVPN selective routing
 

OPNsense is an OSS project © Deciso B.V. 2015 - 2023 All rights reserved
  • SMF 2.0.19 | SMF © 2021, Simple Machines
    Privacy Policy
    | XHTML | RSS | WAP2