GL-X750V2 (Spitz) Router - Public IP Won't Change via Software Commands, Only with Power Cycle

Hi everyone,
I am using OpenWrt 22.03.4, r20123-38ccc47687
I'm having a bit of a challenge with my GL-X750V2 (Spitz) router, and I'm hoping someone here might have some insights.

The Problem:

Whenever I physically unplug and replug the router, it gets assigned a new public IP address by my ISP. However, when I try to achieve the same result using software commands via SSH, the public IP remains unchanged.

What I've Tried:

  1. Simple Reboot:
  • I've used the reboot command via SSH, but the public IP doesn't change.
  1. Bringing Down and Up the WAN Interface:
  • I've tried using ifdown wan followed by ifup wan, but the IP remains the same.
  1. Full Interface Down and Up:
  • Ran ifdown -a to bring down all interfaces, waited for 120 seconds, and then rebooted the router. Still, the public IP stays the same.
  1. Deleting DHCP Lease Files:
  • I deleted /tmp/dhcp.leases and /tmp/hosts/odhcpd before bringing down and up the WAN interface. No change in the public IP.

I am using tmux to ensure that all commands (bringing down interfaces, waiting, rebooting) run uninterrupted even if the SSH session disconnects. Still no success.

  • Has anyone else had this issue with the GL-X750V2 or similar devices?
  • Could there be something specific about how this router or its 4G LTE modem interacts with the ISP’s DHCP server?
  • Are there any other commands or scripts that have worked for you to change the public IP via software?

Any Help or Insights Would Be Greatly Appreciated!

Thanks in advance for your help!

So, the latest version of 22.03 is 22.03.7:
https://openwrt.org/releases/22.03/notes-22.03.7

I do not understand why you are using 22.03.4, as Openwrt 22.03 is EOL, you should be using 23.05 as a minimum.

Sounds like your MAC address changes due to sume bug. Can you check over one reboot?

Stock GL.iNet firmware uses Openwrt 22.03.4 as the base for the GL-X750V2, the OP may need to go to the GL.iNet forums.

It appears you are using firmware that is not from the official OpenWrt project.

When using forks/offshoots/vendor-specific builds that are "based on OpenWrt", there may be many differences compared to the official versions (hosted by OpenWrt.org). Some of these customizations may fundamentally change the way that OpenWrt works. You might need help from people with specific/specialized knowledge about the firmware you are using, so it is possible that advice you get here may not be useful.

You may find that the best options are:

  1. Install an official version of OpenWrt, if your device is supported (see https://firmware-selector.openwrt.org).
  2. Ask for help from the maintainer(s) or user community of the specific firmware that you are using.
  3. Provide the source code for the firmware so that users on this forum can understand how your firmware works (OpenWrt forum users are volunteers, so somebody might look at the code if they have time and are interested in your issue).

If you believe that this specific issue is common to generic/official OpenWrt and/or the maintainers of your build have indicated as such, please feel free to clarify.

2 Likes