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

    WAN DHCP, pfsense don't take new IP

    Routing and Multi WAN
    2
    6
    658
    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.
    • W
      whitewater
      last edited by

      Hello,
      I do not know if I'm in the right place, here is my problem.

      I have a dlink modem dwr 921, 4G modem on a dedicated interface on pfsense, in bridge. it's private IP is 192.168.0.1

      pfsense, in DHCP, retrieves the public IP.
      As it is a SIM card, the public IP changes,
      but pfsense does not get the new address.

      here are the DHCP logs on pfsense :

      Oct 26 10:28:08	dhclient	44737	bound to <new ip public adress> -- renewal in 150 seconds.
Oct 26 10:28:08	dhclient		Creating resolv.conf
Oct 26 10:28:08	dhclient		RENEW
Oct 26 10:28:08	dhclient	44737	DHCPACK from 192.168.0.1
Oct 26 10:28:08	dhclient	44737	DHCPREQUEST on vtnet11 to 192.168.0.1 port 67

      <new ip public adress> : it's the new public IP address sended by the dlink dwr 921.
      On pfSense, the corresponding interface keeps the old public IP.

      thank you

      1 Reply Last reply Reply Quote 0
      • W
        whitewater
        last edited by whitewater

        Here i am again.
        The interface take a new public IP address.

        Oct 26 10:38:31	dhclient	44737	bound to <new public ip - 2nd> -- renewal in 43200 seconds.
Oct 26 10:38:31	dhclient		Creating resolv.conf
Oct 26 10:38:31	dhclient		Adding new routes to interface: vtnet11
Oct 26 10:38:31	dhclient		New Routers (vtnet11): <new public ip - 2nd>
Oct 26 10:38:31	dhclient		New Broadcast Address (vtnet11): <new public ip - 2nd.XXX>
Oct 26 10:38:31	dhclient		New Subnet Mask (vtnet11): 255.255.255.248
Oct 26 10:38:31	dhclient		New IP Address (vtnet11): <new public ip - 2nd>
Oct 26 10:38:31	dhclient		ifconfig vtnet11 inet <new public ip - 2nd> netmask 255.255.255.248 broadcast <new public ip - 2nd.XXX>
Oct 26 10:38:31	dhclient		Starting add_new_address()
Oct 26 10:38:31	dhclient		BOUND

        <new public ip - 2nd> : new IP, different of <new ip public adress>

        But it will certainly lost it when IP public address will change.

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

          What do you think should happen if your ISP issues you a new address?

          What address they give you is up to them.

          Maybe post the Status > Interfaces output in conjunction with the DHCP logs showing the addresses received via DHCP and the addresses actually placed on the interfaces.

          Obfuscating the public addresses is not helping one bit.

          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
          • W
            whitewater
            last edited by whitewater

            @derelict said in WAN DHCP, pfsense don't take new IP:

            What do you think should happen if your ISP issues you a new address?

            For me, pfsense retreive new address from the modem and replace its interface IP.
            Maybie i I say something very wrong

            What address they give you is up to them.
            Maybe post the Status > Interfaces output in conjunction with the DHCP logs showing the addresses received via DHCP and the addresses actually placed on the interfaces.

            Here image.
            https://ibb.co/eMPqA0

            Now, I realize that IP show is a private IP :
            10.68.239.86

            Real public IP is 37.171.149.228 for exemple (see with monip.org).

            So, it's normal gateway is down.

            Modem d-link dwr 921 show me connected with 10.68.239.86 and not show real public IP 37.171.149.228

            So, the d-link don't send real IP, also in bridge mode.

            Maybie, if someone know, a parameters ?
            with openwrt or dd-wrt firmware better ?

            Is LTE modem able to do full bridge ?
            Thank you.

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

              Probably a question for D-Link. Sorry. Unless someone around here happens to have one.

              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
              • W
                whitewater
                last edited by

                I found why.
                My mobile operator don't send public IP to their client.
                A NAT is used between a public IP and the terminal.
                So, modem retreive a private IP from this NAT operator.

                Thank anyway Derelict.

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