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

    LAN can't connect to WAN on new install

    Scheduled Pinned Locked Moved Problems Installing or Upgrading pfSense Software
    18 Posts 5 Posters 7.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.
    • KOMK
      KOM
      last edited by

      I'm not sure if pfSense knows about your gateway. Since you have it set to DHCP, the Gateway field is blank as it's expecting to get it from your DHCP server.

      If I were you, I would punt DHCP and give your WAN port a static IP address, and then define your gateway.

      1 Reply Last reply Reply Quote 0
      • N
        nb
        last edited by

        @podilarius:

        can you ping by ip address? perhaps a traceroute from a computer 8.8.8.8 so that you can see where the packet is getting to. What does your routing table look like?

        I can't even ping my router from pfsense LAN network, Traceroute stops at LAN (192.168.10.1), Where would I find my routing table?

        1 Reply Last reply Reply Quote 0
        • N
          nb
          last edited by

          @KOM:

          I'm not sure if pfSense knows about your gateway. Since you have it set to DHCP, the Gateway field is blank as it's expecting to get it from your DHCP server.

          If I were you, I would punt DHCP and give your WAN port a static IP address, and then define your gateway.

          I tried setting the the WAN to static then added a gateway (used ip of my router). Still no luck.

          1 Reply Last reply Reply Quote 0
          • DerelictD
            Derelict LAYER 8 Netgate
            last edited by

            Post a shot of Firewall->NAT->Outbound please.

            Chattanooga, Tennessee, USA
            A comprehensive network diagram is worth 10,000 words and 15 conference calls.
            DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
            Do Not Chat For Help! NO_WAN_EGRESS(TM)

            1 Reply Last reply Reply Quote 0
            • N
              nb
              last edited by

              @Derelict:

              Post a shot of Firewall->NAT->Outbound please.

              NAT_outbound.png
              NAT_outbound.png_thumb

              1 Reply Last reply Reply Quote 0
              • DerelictD
                Derelict LAYER 8 Netgate
                last edited by

                There are no NAT rules for your LAN network.  Why not use automatic?

                Chattanooga, Tennessee, USA
                A comprehensive network diagram is worth 10,000 words and 15 conference calls.
                DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
                Do Not Chat For Help! NO_WAN_EGRESS(TM)

                1 Reply Last reply Reply Quote 0
                • DerelictD
                  Derelict LAYER 8 Netgate
                  last edited by

                  If you must use manual, something like this should get you going:

                  Interface: WAN_RE0
                  Source: 192.168.10.0/24
                  Source Port: *
                  Destination: *
                  Destination Port: *
                  NAT Address: WAN_RE0 address
                  NAT Port: *
                  Static Port: No

                  Chattanooga, Tennessee, USA
                  A comprehensive network diagram is worth 10,000 words and 15 conference calls.
                  DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
                  Do Not Chat For Help! NO_WAN_EGRESS(TM)

                  1 Reply Last reply Reply Quote 0
                  • N
                    nb
                    last edited by

                    @Derelict:

                    If you must use manual, something like this should get you going: …

                    Woo hoo. That did the trick.

                    Out of curiosity – what did I just do? (in layman's terms).

                    1 Reply Last reply Reply Quote 0
                    • DerelictD
                      Derelict LAYER 8 Netgate
                      last edited by

                      Well, first thing is you took the default configuration, set it to manual NAT, and broke your network.  I have no idea why you want NAT rules for loopback addresses.  The default, automatic NAT rules work in probably 99.9% of "newb" install situations.

                      Second, you told pfSense that traffic heading out WAN_RE0 with a source address in 192.168.10.0/24 should have the source address dynamically NAPT translated using the interface address of WAN_RE0.

                      Chattanooga, Tennessee, USA
                      A comprehensive network diagram is worth 10,000 words and 15 conference calls.
                      DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
                      Do Not Chat For Help! NO_WAN_EGRESS(TM)

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

                        loopbacks are set for pfsense internal services to get to the internet. They are created automatically when you switch to manual. No idea why you switched to manual outbound NAT. So far your setup doesn't need it. Automatic outbound nat would work well.

                        1 Reply Last reply Reply Quote 0
                        • DerelictD
                          Derelict LAYER 8 Netgate
                          last edited by

                          I didn't know that about the loopback NAT.  Thanks.

                          Chattanooga, Tennessee, USA
                          A comprehensive network diagram is worth 10,000 words and 15 conference calls.
                          DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
                          Do Not Chat For Help! NO_WAN_EGRESS(TM)

                          1 Reply Last reply Reply Quote 0
                          • stephenw10S
                            stephenw10 Netgate Administrator
                            last edited by

                            I'll just add that your LAN firewall rule is set to allow only IPv4 TCP/UDP traffic which doesn't include ICMP (ping). You need to add a further rules to allow ICMP or change the existing rule to any IPv4 protocol.

                            Steve

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