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

upstream gateway routing issue

Scheduled Pinned Locked Moved Routing and Multi WAN
4 Posts 2 Posters 516 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.
  • R
    Rico29
    last edited by Rico29 Sep 15, 2020, 2:58 PM Sep 15, 2020, 2:54 PM

    Hello,
    I'm running latest version of pfSense.
    Please see the attached schema for architecture description :
    pfsense.png

    Problem description :

    when an upstream gateway is set on WAN2 to 1.2.100.35, 10.90.0.0/24 is unreachable
    when no upstream gateway is set on WAN2, 10.90.0.0/24 is reachable

    upstream gateway HAS TO BE SET on WAN2 for reply-to

    pfctl -sa rules diff between with and without upstream gateway :

    with upstream gateway set, I have 2 more rules :

    • pass out route-to (vtnet2 1.2.100.35) inet from 1.2.100.41 to ! 1.2.100.32/27 flags S/SA keep state allow-opts label "let out anything from firewall host itself"
    • pass in quick on vtnet2 reply-to (vtnet2 1.2.100.35) inet proto icmp all keep state label "USER_RULE"

    It seems that the first one of these two rules does something wrong but I'm not a pf expert.
    can anybody here tell me if there is a solution please ?

    Regards

    1 Reply Last reply Reply Quote 0
    • R
      Rico29
      last edited by Sep 22, 2020, 8:29 AM

      Still looking for a solution...

      1 Reply Last reply Reply Quote 0
      • R
        Rico29
        last edited by Sep 24, 2020, 8:49 AM

        issue seems to be fixed by adding a rule on top of WAN2 interface :
        check "disable reply-to" when src-addr = 10.90.0.0/24

        1 Reply Last reply Reply Quote 0
        • H
          himanshus
          last edited by Sep 25, 2020, 9:09 PM

          Hi,

          Without seeing other details of your configuration, it seems that you may have to use "policy based routing" in your LAN rules, meaning you may have to assign two rules and specify which gateway to use for the two different destinations.
          in the rules section, click on Advanced, and scroll down and then specify which gateway.
          this may help. we had a similar issue recently with our multi-wan setup.

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