OPNsense
  • Home
  • Help
  • Search
  • Login
  • Register

  • OPNsense Forum »
  • Archive »
  • 17.1 Legacy Series »
  • 17.1.1 pbr
« previous next »
  • Print
Pages: [1]

Author Topic: 17.1.1 pbr  (Read 4184 times)

dragon2611

  • Jr. Member
  • **
  • Posts: 94
  • Karma: 4
    • View Profile
17.1.1 pbr
« on: February 11, 2017, 05:08:45 pm »
Pretty sure 17.1.1 doesn't fix all the policy routing issue as I've got a teamspeak server running on a host with 2 WAN uplinks on the DNS points to WAN2, since upgrading no-one can connect to it.

It's a NAT port forward from the secondary uplink.
« Last Edit: February 11, 2017, 05:14:34 pm by dragon2611 »
Logged

dragon2611

  • Jr. Member
  • **
  • Posts: 94
  • Karma: 4
    • View Profile
Re: 17.1.1 pbr
« Reply #1 on: February 11, 2017, 05:20:51 pm »
Specifically it looks like the reply doesn't automatically get routed to WAN2 to match the incoming, Not sure if I redirected all traffic from that host to WAN2 if it would work.


Edit: Even with a policy wan rule to put outbound traffic to WAN2 it still doesn't work, 17.1.x so far is a lemon if you have multiple wans/policy routing requirements it seems
« Last Edit: February 11, 2017, 05:41:19 pm by dragon2611 »
Logged

djGrrr

  • Full Member
  • ***
  • Posts: 112
  • Karma: 22
    • View Profile
Re: 17.1.1 pbr
« Reply #2 on: February 12, 2017, 03:53:55 pm »
Can you try running this from the shell as root?
sysctl net.pf.share_forward=0

This should restore the stock FreeBSD way of doing policy routing.
Logged

mbosner

  • Newbie
  • *
  • Posts: 43
  • Karma: 1
    • View Profile
Re: 17.1.1 pbr
« Reply #3 on: February 12, 2017, 05:21:44 pm »
I have also Teamspeak related problems, but they are different:

As soon as i have a 24h reconnect i have to restart the ts client. Before that it will not connect to the external TS server. Very strange but it is the same behavior on all devices. I will dig into it tonight.
Logged

dragon2611

  • Jr. Member
  • **
  • Posts: 94
  • Karma: 4
    • View Profile
Re: 17.1.1 pbr
« Reply #4 on: February 13, 2017, 03:08:25 pm »
Quote from: djGrrr on February 12, 2017, 03:53:55 pm
Can you try running this from the shell as root?
sysctl net.pf.share_forward=0

This should restore the stock FreeBSD way of doing policy routing.

I'm afraid I already restored the VM from a backup that was taken prior to upgrading
Logged

dragon2611

  • Jr. Member
  • **
  • Posts: 94
  • Karma: 4
    • View Profile
Re: 17.1.1 pbr
« Reply #5 on: February 15, 2017, 07:23:06 pm »
Right re-applied the update and sysctl net.pf.share_forward=0 does appear to resolve the issue.
Logged

franco

  • Administrator
  • Hero Member
  • *****
  • Posts: 13618
  • Karma: 1170
    • View Profile
Re: 17.1.1 pbr
« Reply #6 on: February 15, 2017, 10:48:04 pm »
Sorry, we are circling back to a default of net.pf.share_forward=0 and a GUI override to in 17.1.2 to get to see underlying base OS update issues first, then improve shared forwarding further.
Logged

  • Print
Pages: [1]
« previous next »
  • OPNsense Forum »
  • Archive »
  • 17.1 Legacy Series »
  • 17.1.1 pbr
 

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