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

    pfsense unable to acces internet

    Scheduled Pinned Locked Moved Routing and Multi WAN
    3 Posts 2 Posters 388 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.
    • P
      pascalts
      last edited by pascalts

      Hi!

      Short setup information: I am running my pfsense firewall with 2 wan interfaces (192.168.178.0/24;192.168.188.0/24), a lan (192.168.0.0/24) and a wifi network (192.168.1.0/24). All PCs in the LAN having access to the internet via gateway-groups (port x to wan x and port y to wany and so on).

      This works fine.

      BUT: Somehow I managed it, that the firewall itself cannot access the internet... If I ping any host in the internet (accessible by LAN PCs), all packages are lost.

      PING golem.de (77.247.84.129) from 127.0.0.1: 56 data bytes
      
      --- golem.de ping statistics ---
      3 packets transmitted, 0 packets received, 100.0% packet loss
      

      If I use the WANx interface directly, I can ping the host.

      PING golem.de (77.247.84.129) from 192.168.188.21: 56 data bytes
      64 bytes from 77.247.84.129: icmp_seq=0 ttl=248 time=24.295 ms
      64 bytes from 77.247.84.129: icmp_seq=1 ttl=248 time=24.224 ms
      64 bytes from 77.247.84.129: icmp_seq=2 ttl=248 time=24.324 ms
      
      --- golem.de ping statistics ---
      3 packets transmitted, 3 packets received, 0.0% packet loss
      round-trip min/avg/max/stddev = 24.224/24.281/24.324/0.042 ms
      

      I believe I mady a routing fault... Any idea?

      Best regards

      Pascal

      1 Reply Last reply Reply Quote 0
      • V
        viragomann
        last edited by

        Seems you're missing an Outbound NAT rule for the second WAN.

        1 Reply Last reply Reply Quote 0
        • P
          pascalts
          last edited by

          As it happens, my question here kickstarted my brain and I got the problem solved: The "Default gateway IPv4" Setting was set to an no longer existing / working gateway-group.

          Well shit happens... Thank you!

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