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

    SG 5100 WAN IP no Internet

    Scheduled Pinned Locked Moved General pfSense Questions
    9 Posts 2 Posters 760 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.
    • H
      HeyNetgate
      last edited by

      I have a Netgate SG 5100 on 22.05. The WAN port gets a public IP via an ISP provided cable modem over DHCP. I can see the public IP and can ping into the service provider network. However, my internet is down. I cannot communicate beyond the ISP default gateway on their public IP.

      However, I can plug in a tablet to the cable modem and that works. I have a spare router I'm going to setup and I guess that will work too.

      Any ideas on what is going on the the Netgate 5100? This happened right after an upgrade from 22.01. I'm thinking about reinstalling 22.01 to see if that works.

      What are some good troubleshooting steps to take? I'm mostly familiar with the GUI but I will get into the CLI if necessary.

      1 Reply Last reply Reply Quote 0
      • G
        gabacho4 Rebel Alliance
        last edited by

        can you router ping the internet. If you go to Diagnostics -> Ping, and then put like google.com or something else does it respond?

        H 1 Reply Last reply Reply Quote 0
        • H
          HeyNetgate @gabacho4
          last edited by

          @gabacho4 No, I cannot ping via DNS name or IP address. I can traceroute something 8.8.8.8 and get to the ISP public default gateway and then it dies.

          G 1 Reply Last reply Reply Quote 0
          • G
            gabacho4 Rebel Alliance @HeyNetgate
            last edited by

            @heynetgate is the dns resolver service running? Have you tried to restart the router since this began just to see if it's a gremlin?

            H 1 Reply Last reply Reply Quote 0
            • H
              HeyNetgate @gabacho4
              last edited by

              @gabacho4 DNS services are running. They aren't a factor when pinging by IP 8.8.8.8. Reboots do not resolve the problem.

              G 1 Reply Last reply Reply Quote 0
              • G
                gabacho4 Rebel Alliance @HeyNetgate
                last edited by

                @heynetgate what are the DNS servers that the router is set to use. As you said, a device plugged into the ISP router/modem has connectivity so that works. So then it has to be something that pfSense is/is not doing, especially since the router itself can't reach the world.

                H 1 Reply Last reply Reply Quote 0
                • H
                  HeyNetgate @gabacho4
                  last edited by

                  @gabacho4 I agree that it has to be something the PFSense is doing/not doing. I don't agree that it's DNS. DNS is not a factor when pinging by IP address.

                  But let's look at this because I'm curious how do I find the DNS servers the ISP provides on the WAN interface?

                  G 1 Reply Last reply Reply Quote 0
                  • G
                    gabacho4 Rebel Alliance @HeyNetgate
                    last edited by

                    @heynetgate I agree 100% with you on the ip address ping. The problem is that there are number of places to check. I'd recommend that you use:

                    https://docs.netgate.com/pfsense/en/latest/troubleshooting/connectivity.html

                    and go through that as a checklist. Would be hard to explain why it was working just fine pre-upgrade and then not working post-upgrade.

                    H 1 Reply Last reply Reply Quote 0
                    • H
                      HeyNetgate @gabacho4
                      last edited by

                      @gabacho4 said in SG 5100 WAN IP no Internet:

                      https://docs.netgate.com/pfsense/en/latest/troubleshooting/connectivity.html

                      Those docs are good. But in my case not too fruitful.

                      The WAN IP addressing and DNS is under Status>Interfaces. My WAN is clearly labeled as "WAN Interface (wan igb0)" Those labels help a lot!

                      I had configured my PFSense as a client to ExpressVPN a month or two back. I didn't get the full config they way I wanted and decided to come back to that project later. Well the service started up again on reboot and that kicked me off the network. It's not supposed to work that way, but it does right now. So stopping that service gives me the desired result. I think I may just clear that config and come back and do the whole thing when I can get it done.

                      Anyway, I think that resolved it. I can ping public IP addresses now and google.com.

                      Thanks!

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