Netgate SG-1000 microFirewall

Author Topic: Policy based routing  (Read 291 times)

0 Members and 1 Guest are viewing this topic.

Offline townsenk

  • Jr. Member
  • **
  • Posts: 46
  • Karma: +0/-0
    • View Profile
Policy based routing
« on: November 13, 2017, 06:07:47 pm »
I'm running snapshot 2.4.2.a.20171113.0825 but I think my issue started two snapshots ago.

When making policy configuration change in advanced settings Firewall/Rules/<lan interface>

Making changes in Advanced Options to specify a gateway utilizing policy based routing causes system to force to default gateway. The only way I'm able to restore desired operation is by restoring a previous configuration file.

The visual representation of the gateway entries in the listed rules also changes and displays more information (this appears intentional)

Offline jimp

  • Administrator
  • Hero Member
  • *****
  • Posts: 21387
  • Karma: +1432/-26
    • View Profile
Re: Policy based routing
« Reply #1 on: November 14, 2017, 08:47:28 am »
Could you elaborate some more on the behavior you see?

There were some changes in that area a couple days ago, see https://redmine.pfsense.org/issues/8053

Need to see some more specifics about the rule, how it shows on the edit screen and on the rule list, and if possible, the rule entry from /tmp/rules.debug
Need help fast? Commercial Support!

Co-Author of pfSense: The Definitive Guide. - Check the Doc Wiki for FAQs.

Do not PM for help!

Offline jimp

  • Administrator
  • Hero Member
  • *****
  • Posts: 21387
  • Karma: +1432/-26
    • View Profile
Re: Policy based routing
« Reply #2 on: November 14, 2017, 09:34:44 am »
I was able to reproduce the problem here, we'll get it fixed up ASAP.
Need help fast? Commercial Support!

Co-Author of pfSense: The Definitive Guide. - Check the Doc Wiki for FAQs.

Do not PM for help!

Offline Steve_B

  • Global Moderator
  • Sr. Member
  • *****
  • Posts: 391
  • Karma: +110/-0
    • View Profile
Re: Policy based routing
« Reply #3 on: November 14, 2017, 02:14:47 pm »
Fixed in the next snapshot