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

    WAN seems to be getting next hop IP address, not public IP address

    Scheduled Pinned Locked Moved DHCP and DNS
    7 Posts 3 Posters 95 Views 3 Watching
    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.
    • T Offline
      TonyB972 0
      last edited by

      Hello,

      The issue I am having is that when I connect my pfSense router to the fiber modem the WAN IP seems to be the next hop IP address of my ISP, 192.83.xxx.xxx.
      When I connect a different router or laptop to the fiber modem, I get a publicly routable IP address, 208.93.xxx.xxx.
      WAN interface is set to DHCP.
      I tried setting net.inet.ip.redirect to 0, but it did not fix the issue.

      Any insight would be appreciated, thank you

      chpalmerC 1 Reply Last reply Reply Quote 0
      • chpalmerC Offline
        chpalmer @TonyB972 0
        last edited by chpalmer

        @TonyB972-0 192.83.0.0/18 is definitely a range of public IP addresses.. Finland ISP. You could try cloning the MAC address of your other device on the WAN page of your PFsense.. if you want the other address .

        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
        • T Offline
          TonyB972 0
          last edited by

          Cloning the MAC address worked, I'm not sure why, but it did.

          chpalmerC johnpozJ 2 Replies Last reply Reply Quote 0
          • chpalmerC Offline
            chpalmer @TonyB972 0
            last edited by

            @TonyB972-0 said in WAN seems to be getting next hop IP address, not public IP address:

            Cloning the MAC address worked, I'm not sure why, but it did.

            Magic.. ๐Ÿ˜๐Ÿ˜

            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
            • johnpozJ Offline
              johnpoz LAYER 8 Global Moderator @TonyB972 0
              last edited by

              @TonyB972-0 said in WAN seems to be getting next hop IP address, not public IP address:

              I'm not sure why, but it did.

              Because your isp runs a dhcp server, and that server had an old lease with your mac in it.

              Also to you getting an IP in a different range - many isp run multiple layer 3 on the same L2.. So getting an IP from a different range is not all that uncommon.

              You can see this quite often when you just sniff for arps on your wan.

              06:59:37.727960 ARP, Request who-has 209.122.60.47 tell 209.122.48.1, length 46
              06:59:37.729849 ARP, Request who-has 209.122.35.23 tell 209.122.32.1, length 46
              06:59:37.978289 ARP, Request who-has 216.80.19.171 tell 216.80.19.161, length 46
              06:59:38.052330 ARP, Request who-has 208.59.70.155 tell 208.59.70.153, length 46
              06:59:38.058422 ARP, Request who-has 216.80.109.46 tell 216.80.109.33, length 46
              06:59:38.595241 ARP, Request who-has 207.181.199.99 tell 207.181.199.97, length 46
              06:59:39.352258 ARP, Request who-has 131.106.219.205 tell 131.106.219.201, length 46
              

              These are different L3 networks, that seeing arp on my wan.. Clearly many of them are not the same network.

              Its quite possible you could get an IP from your isp in any of those networks.

              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 25.07.1 | Lab VMs 2.8.1, 25.07.1

              1 Reply Last reply Reply Quote 0
              • T Offline
                TonyB972 0
                last edited by

                That makes sense, I appreciate the explanation.
                Strange that ever other device I connected to the modem got a DHCP address in the 208.93.xxx.xxx that was publicly routable, and the pfSense always got the 192.83.xxx.1 address that was not. Though this ISP is small, as in just my town small. I'm not surprised that when I did not use their equipment, I did not get the results either party would expect.
                Thank you for the time taken for the knowledge share.

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

                  @TonyB972-0 said in WAN seems to be getting next hop IP address, not public IP address:

                  192.83.xxx.1 address that was not.

                  192.83 is public IP. Your maybe thinking of 192.168 which is rfc1918

                  btw - not sure where your using some 208.93.xxx.xxx, because your not talking to pfsense with that IP, nor does your history ever show you connecting with an IP that starts with those 2 octets.

                  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 25.07.1 | Lab VMs 2.8.1, 25.07.1

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