• Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Search
  • Register
  • Login
Netgate Discussion Forum
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Search
  • Register
  • Login

Openvpn Routing rules stop working

Scheduled Pinned Locked Moved Routing and Multi WAN
3 Posts 3 Posters 634 Views
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • K
    kormen
    last edited by Dec 9, 2014, 8:01 AM

    Hi!

    I read lot of forum messages to search a solution to my problem.

    i see a weird thing. I have a multi WAN  multi VLAN multi OpenVPN Pfsense (2.1.5-RELEASE (amd64) built on Mon Aug 25 07:44:45 EDT 2014 FreeBSD 8.3-RELEASE-p16)

    If i change system routing table, mostly the system not use the Openvpn routes. The routes showing in routing table but can't work. I must to restart openvpn to repair this issue.

    Have anybody an opinion or advice to resolve this?

    Sorry for my poor english!

    1 Reply Last reply Reply Quote 0
    • H
      heper
      last edited by Dec 9, 2014, 8:34 AM

      what are you using the system routing table for ?

      i've never had that issue personally … but i would think you have conflicting/overlapping routes and depending on what route is configured last, one or the other would work

      1 Reply Last reply Reply Quote 0
      • D
        Derelict LAYER 8 Netgate
        last edited by Dec 9, 2014, 8:07 PM

        OpenVPN "route" commands add entries to the system routing table telling pfSense to route traffic to OpenVPN.  Openvpn "iroute" commands tell the OpenVPN process, internally, which tunnel to send given traffic.  I have never used the system routing table to make changes to what traffic is interesting to OpenVPN.

        Chattanooga, Tennessee, USA
        A comprehensive network diagram is worth 10,000 words and 15 conference calls.
        DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
        Do Not Chat For Help! NO_WAN_EGRESS(TM)

        1 Reply Last reply Reply Quote 0
        1 out of 3
        • First post
          1/3
          Last post
        Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.
          This community forum collects and processes your personal information.
          consent.not_received