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

    Every service in the gateway use only the default gateway

    Scheduled Pinned Locked Moved Routing and Multi WAN
    5 Posts 5 Posters 1.1k 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 Offline
      ruggero
      last edited by

      I thought that the problem was only related to squid.
      But I have noticed that any services installed in the router only uses the default gateway.
      The router does not use the firewall rules for packets coming from himself.

      1 Reply Last reply Reply Quote 0
      • M Offline
        mwixon
        last edited by

        I'm seeing the same thing.  I have PFSense 2.1p1 running captive portal.  It has 2 WANs with failover for redundancy.  Today we had a primary WAN failure and it correctly failed over to WAN2.  All connected captive portal clients worked without a hitch, however new portal customers could not login because the portal was using WAN1 as it's gateway to the portal auth server.  I sshed to the router during this period and from the shell I couldn't ping out to the internet, I could however from a connected LAN client.

        Is there some rule I'm missing to get traffic originating on PFSense itself to use the failover gateway group?

        1 Reply Last reply Reply Quote 0
        • Z Offline
          zerokool
          last edited by

          yea I cant get the stupid "default gateway" box to uncheck.

          it only passes traffic through a default gateway regardless of how many gateways I have.

          2.1 seams really broken.

          6 WAN 2 Lan pf multi-wan box
          2ed running static ip routes

          1 Reply Last reply Reply Quote 0
          • G Offline
            GeorgeM
            last edited by

            @zerokool:

            yea I cant get the stupid "default gateway" box to uncheck.

            I've been exploring 2.1 on a spare machine (2.0.3 is what's on the live one) and I noticed this problem myself when I got into setting up my dual WANs. In my case I want certain kinds of traffic to go over specific WAN links and that not working would be a real headache. (e.g., cloud backup needs to go over the link with the biggest upstream bandwidth.)

            1 Reply Last reply Reply Quote 0
            • P Offline
              phil.davis
              last edited by

              @GeorgeM:

              @zerokool:

              yea I cant get the stupid "default gateway" box to uncheck.

              I've been exploring 2.1 on a spare machine (2.0.3 is what's on the live one) and I noticed this problem myself when I got into setting up my dual WANs. In my case I want certain kinds of traffic to go over specific WAN links and that not working would be a real headache. (e.g., cloud backup needs to go over the link with the biggest upstream bandwidth.)

              Ordinary client traffic (like a big backup to cloud) is easily directed to the WAN (or group of WANs) that you want it to use, by specifying the gateway or gateway group in the rules. It is only traffic originated from pfSense itself that is tricky to direct.

              As the Greek philosopher Isosceles used to say, "There are 3 sides to every triangle."
              If I helped you, then help someone else - buy someone a gift from the INF catalog http://secure.inf.org/gifts/usd/

              1 Reply Last reply Reply Quote 0
              • First post
                Last post
              Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.