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

    Gateway Switch Not Allowing Communication Between Interfaces

    Scheduled Pinned Locked Moved NAT
    3 Posts 2 Posters 846 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.
    • Q
      Quada
      last edited by

      When I change the gateway on my LAN rules from (IPv4 * LAN1 net * * * ***** none )    to      (IPv4 * LAN1 net * * * WAN1_DHCP none )  I lose connectivity to all other interfaces (other than WAN).  For instance I cannot access a server on a guest network.  When I change that gateway option back to default, I regain connectivity instantly.  I have tried matching the gateway specification on all interfaces but that didn't fix the issue.  I have also tried to remove all other gateways, only leaving the default (WAN1_DHCP) but the issue still persists.  This is repeatable on other interfaces as well, i.e. GEUST2 to GUEST1.  The allow_all rule is the only rule on the LAN interface other than the anti-lockout rule.  Again to reiterate the only option changing is the specifying the gateway from default to the only option available.  Any ideas on what to try?

      1 Reply Last reply Reply Quote 0
      • johnpozJ
        johnpoz LAYER 8 Global Moderator
        last edited by

        Well how are you going to access your other interfaces if your sending all data out your wan?

        If you want access to other interfaces on pfsense, then your going to have to put rules above that rule that allow access to those networks before you shove all traffic out a specific gateway that can not get to pfsense other interfaces.

        https://doc.pfsense.org/index.php/Bypassing_Policy_Routing
        Rules that match traffic to send connections out a specific WAN can cause local or VPN traffic destinations to exit the firewall WAN rather than following local routing,

        An intelligent man is sometimes forced to be drunk to spend time with his fools
        If you get confused: Listen to the Music Play
        Please don't Chat/PM me for help, unless mod related
        SG-4860 24.11 | Lab VMs 2.8, 24.11

        1 Reply Last reply Reply Quote 0
        • Q
          Quada
          last edited by

          @johnpoz:

          Well how are you going to access your other interfaces if your sending all data out your wan?

          This first statement made me go d'oh! Thanks, this was a very easy fix!

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