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

    Static IP not working

    Scheduled Pinned Locked Moved General pfSense Questions
    7 Posts 4 Posters 1.6k 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.
    • K
      Knaik
      last edited by

      I'm having some issues with setting my WAN as a static IP, everything on the LAN won't connect to the internet. All LAN computers can get to the pfSense box and get an IP.

      My ISP gives me the following as static:

      IP: 192.168.99.196
      Subnet: 255.255.255.248 (Which is /29, I think..)
      Gateway: 192.168.99.193

      I have my LAN IP as: 10.10.100.1 with DHCP from 10.10.100.25-50

      From what I gather, it might be a DNS issue, every time I do a test DNS lookup on pfSense it comes back with 127.0.0.1 no response and 8.8.8.8 says 0 as the response. If I ping an IP, it times out.

      What I've checked:
      -Setting gateway on general setup
      -DNS servers are specified as 8.8.8.8 and 8.8.4.4
      -No rules setup on the firewall
      -No packages installed

      Any help would be appreciated, as I'm stumped!  >:(

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

        Your isp gives you private address? rfc1918 space?  IP: 192.168.99.196

        You sure about that??  Can you ping your gateway IP on pfsense 192.168.99.193  Did you uncheck the block rfc1918 on your wan?

        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
        • stephenw10S
          stephenw10 Netgate Administrator
          last edited by

          It's probably not a DNS issue if you can't ping IPs either. Blocking private networks on WAN shouldn't stop LAN side clients pinging out.
          I would guess either some upstream problem or maybe a routing problem. Is the system default gateway set correctly? Did you set a gateway on LAN? (a common mistake).

          More info please.  :)

          Steve

          1 Reply Last reply Reply Quote 0
          • K
            Knaik
            last edited by

            Yes, this ISP is in a rural area and it looks like networking designed by a high school kid; they give us a 192.168.99.196 IP address and then port forward across their setup to give me a "static" outside address, which is crazy but that's what I've got.

            I double checked and block rfc1918 is unchecked on WAN and LAN.

            The system default gateway is set to 192.168.99.193 with the LAN gateway set to None.

            Pinging the gateway also times out, so I'm still lost…

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

              Are you pinging from the pfSense diagnostics gui or a client on the LAN?
              Have you tested the wan connection with some other device? Does your ISP do MAC filtering?

              Steve

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

                If pfsense can not talk to its own gateway, not sure how you expect it to get to you to 8.8.8.8, etc  You have a bad cable, you got bad info?  They are going mac filtering - what device are you plugging into?  Did you power cycle it between changing devices connected to it?

                Cable modems for example almost always need to be reset when you change the mac connected to it.

                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
                • chpalmerC
                  chpalmer
                  last edited by

                  with a /29 you would have 192.168.99.192 - 192.168.99.199 available in your subnet.  Try pinging each and every one except the address your WAN is set to.

                  For the rest-  a great number of small rural ISP's use private space on their networks between their routers and customer WAN.

                  Triggering snowflakes one by one..
                  Intel(R) Core(TM) i5-4590T CPU @ 2.00GHz on an M400 WG box.

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