GL-X3000 Spritz AX - WAN interface going up and down constantly

Technical Support for Routers
1

I just received my GL-X3000 Spitz AX this a.m. from DHL. Super-fast shipping from Gl.inet - much appreciated. I unboxed the unit, installed my T-Mobile SIM, used the auto SIM/WAN configurator and upgraded the firmware. I rebooted the unit set the time zone and setup my Wi-Fi.

At first things were good. Did some testing and noticed some lagging and weird behavior. I checked the log to find the unit has been losing wan connection. I think this is due to the X3000 seeing a WAN IP change?, but I am double NAT with T-Mobile so I am not sure what it is looking at.

Here as an excerpt from the log. I notice my clock is off by 15 mins as well. My time zone is set correctly. Any help appreciated.

p.s. I really like this device. The Wi-Fi is well done and performs well.

Log info
Mon Jun 12 13:54:24 2023 user.info mwan3rtmon[8913]: Detect rtchange event.
Mon Jun 12 13:54:24 2023 user.notice firewall: Reloading firewall due to ifup of modem_0001_4 (rmnet_mhi0)
Mon Jun 12 13:54:31 2023 user.notice root: modem ip different, now regain ip …
Mon Jun 12 13:54:31 2023 daemon.notice netifd: Interface ‘modem_0001_4’ has lost the connection
Mon Jun 12 13:54:31 2023 daemon.notice netifd: Interface ‘modem_0001_4’ is now down
Mon Jun 12 13:54:31 2023 daemon.notice netifd: Interface ‘modem_0001_4’ is disabled
Mon Jun 12 13:54:31 2023 daemon.notice netifd: Interface ‘modem_0001_4’ is enabled
Mon Jun 12 13:54:31 2023 daemon.notice netifd: Interface ‘modem_0001_4’ is setting up now
Mon Jun 12 13:54:31 2023 daemon.notice netifd: modem_0001_4 (24619): udhcpc: started, v1.33.2
Mon Jun 12 13:54:31 2023 daemon.notice netifd: modem_0001_4 (24619): udhcpc: sending discover
Mon Jun 12 13:54:31 2023 daemon.notice netifd: modem_0001_4 (24619): udhcpc: sending select for 192.0.0.2
Mon Jun 12 13:54:31 2023 daemon.notice netifd: modem_0001_4 (24619): udhcpc: lease of 192.0.0.2 obtained, lease time 7200
Mon Jun 12 13:54:31 2023 daemon.notice netifd: Interface ‘modem_0001_4’ is now up
Mon Jun 12 13:54:31 2023 user.notice mwan3[24591]: Execute ifdown event on interface modem_0001_4 (unknown)
Mon Jun 12 13:54:31 2023 user.notice firewall: Reloading firewall due to ifdown of modem_0001_4 ()
Mon Jun 12 13:54:32 2023 user.notice mwan3[24906]: Execute ifup event on interface modem_0001_4 (rmnet_mhi0)
Mon Jun 12 13:54:32 2023 user.notice mwan3[24906]: Starting tracker on interface modem_0001_4 (rmnet_mhi0)
Mon Jun 12 13:54:34 2023 user.info mwan3rtmon[8913]: Detect rtchange event.
Mon Jun 12 13:54:34 2023 user.notice firewall: Reloading firewall due to ifup of modem_0001_4 (rmnet_mhi0)
Mon Jun 12 13:54:41 2023 user.notice root: modem ip different, now regain ip …
Mon Jun 12 13:54:41 2023 daemon.notice netifd: Interface ‘modem_0001_4’ has lost the connection
Mon Jun 12 13:54:41 2023 daemon.notice netifd: Interface ‘modem_0001_4’ is now down
Mon Jun 12 13:54:41 2023 daemon.notice netifd: Interface ‘modem_0001_4’ is disabled
Mon Jun 12 13:54:41 2023 daemon.notice netifd: Interface ‘modem_0001_4’ is enabled
Mon Jun 12 13:54:41 2023 daemon.notice netifd: Interface ‘modem_0001_4’ is setting up now
Mon Jun 12 13:54:41 2023 daemon.notice netifd: modem_0001_4 (25834): udhcpc: started, v1.33.2
Mon Jun 12 13:54:41 2023 daemon.notice netifd: modem_0001_4 (25834): udhcpc: sending discover
Mon Jun 12 13:54:41 2023 daemon.notice netifd: modem_0001_4 (25834): udhcpc: sending select for 192.0.0.2
Mon Jun 12 13:54:41 2023 daemon.notice netifd: modem_0001_4 (25834): udhcpc: lease of 192.0.0.2 obtained, lease time 7200
Mon Jun 12 13:54:41 2023 daemon.notice netifd: Interface ‘modem_0001_4’ is now up
Mon Jun 12 13:54:41 2023 user.notice mwan3[25811]: Execute ifdown event on interface modem_0001_4 (unknown)
Mon Jun 12 13:54:42 2023 user.notice firewall: Reloading firewall due to ifdown of modem_0001_4 ()
Mon Jun 12 13:54:42 2023 user.notice mwan3[26126]: Execute ifup event on interface modem_0001_4 (rmnet_mhi0)
Mon Jun 12 13:54:42 2023 user.notice mwan3[26126]: Starting tracker on interface modem_0001_4 (rmnet_mhi0)
Mon Jun 12 13:54:45 2023 user.info mwan3rtmon[8913]: Detect rtchange event.
Mon Jun 12 13:54:45 2023 user.notice firewall: Reloading firewall due to ifup of modem_0001_4 (rmnet_mhi0)
Mon Jun 12 13:54:51 2023 user.notice root: modem ip different, now regain ip …
Mon Jun 12 13:54:51 2023 daemon.notice netifd: Interface ‘modem_0001_4’ has lost the connection
Mon Jun 12 13:54:51 2023 daemon.notice netifd: Interface ‘modem_0001_4’ is now down
Mon Jun 12 13:54:51 2023 daemon.notice netifd: Interface ‘modem_0001_4’ is disabled
Mon Jun 12 13:54:51 2023 daemon.notice netifd: Interface ‘modem_0001_4’ is enabled
Mon Jun 12 13:54:51 2023 daemon.notice netifd: Interface ‘modem_0001_4’ is setting up now
Mon Jun 12 13:54:51 2023 daemon.notice netifd: modem_0001_4 (27059): udhcpc: started, v1.33.2
Mon Jun 12 13:54:51 2023 daemon.notice netifd: modem_0001_4 (27059): udhcpc: sending discover
Mon Jun 12 13:54:51 2023 daemon.notice netifd: modem_0001_4 (27059): udhcpc: sending select for 192.0.0.2
Mon Jun 12 13:54:52 2023 daemon.notice netifd: modem_0001_4 (27059): udhcpc: lease of 192.0.0.2 obtained, lease time 7200
Mon Jun 12 13:54:52 2023 daemon.notice netifd: Interface ‘modem_0001_4’ is now up
Mon Jun 12 13:54:52 2023 user.notice mwan3[27032]: Execute ifdown event on interface modem_0001_4 (unknown)
Mon Jun 12 13:54:52 2023 user.notice firewall: Reloading firewall due to ifdown of modem_0001_4 ()
Mon Jun 12 13:54:52 2023 user.notice mwan3[27347]: Execute ifup event on interface modem_0001_4 (rmnet_mhi0)
Mon Jun 12 13:54:53 2023 user.notice mwan3[27347]: Starting tracker on interface modem_0001_4 (rmnet_mhi0)
Mon Jun 12 13:54:55 2023 user.info mwan3rtmon[8913]: Detect rtchange event.
Mon Jun 12 13:54:55 2023 user.notice firewall: Reloading firewall due to ifup of modem_0001_4 (rmnet_mhi0)
Mon Jun 12 13:55:02 2023 user.notice root: modem ip different, now regain ip …
Mon Jun 12 13:55:02 2023 daemon.notice netifd: Interface ‘modem_0001_4’ has lost the connection
Mon Jun 12 13:55:02 2023 daemon.notice netifd: Interface ‘modem_0001_4’ is now down
Mon Jun 12 13:55:02 2023 daemon.notice netifd: Interface ‘modem_0001_4’ is disabled
Mon Jun 12 13:55:02 2023 daemon.notice netifd: Interface ‘modem_0001_4’ is enabled
Mon Jun 12 13:55:02 2023 daemon.notice netifd: Interface ‘modem_0001_4’ is setting up now
Mon Jun 12 13:55:02 2023 daemon.notice netifd: modem_0001_4 (28275): udhcpc: started, v1.33.2
Mon Jun 12 13:55:02 2023 daemon.notice netifd: modem_0001_4 (28275): udhcpc: sending discover
Mon Jun 12 13:55:02 2023 daemon.notice netifd: modem_0001_4 (28275): udhcpc: sending select for 192.0.0.2
Mon Jun 12 13:55:02 2023 daemon.notice netifd: modem_0001_4 (28275): udhcpc: lease of 192.0.0.2 obtained, lease time 7200
Mon Jun 12 13:55:02 2023 daemon.notice netifd: Interface ‘modem_0001_4’ is now up
Mon Jun 12 13:55:02 2023 user.notice mwan3[28252]: Execute ifdown event on interface modem_0001_4 (unknown)
Mon Jun 12 13:55:02 2023 user.notice firewall: Reloading firewall due to ifdown of modem_0001_4 ()
Mon Jun 12 13:55:03 2023 user.notice mwan3[28567]: Execute ifup event on interface modem_0001_4 (rmnet_mhi0)
Mon Jun 12 13:55:03 2023 user.notice mwan3[28567]: Starting tracker on interface modem_0001_4 (rmnet_mhi0)
Mon Jun 12 13:55:05 2023 user.info mwan3rtmon[8913]: Detect rtchange event.
Mon Jun 12 13:55:05 2023 user.notice firewall: Reloading firewall due to ifup of modem_0001_4 (rmnet_mhi0)
Mon Jun 12 13:55:12 2023 user.notice root: modem ip different, now regain ip …
Mon Jun 12 13:55:12 2023 daemon.notice netifd: Interface ‘modem_0001_4’ has lost the connection
Mon Jun 12 13:55:12 2023 daemon.notice netifd: Interface ‘modem_0001_4’ is now down
Mon Jun 12 13:55:12 2023 daemon.notice netifd: Interface ‘modem_0001_4’ is disabled
Mon Jun 12 13:55:12 2023 daemon.notice netifd: Interface ‘modem_0001_4’ is enabled
Mon Jun 12 13:55:12 2023 daemon.notice netifd: Interface ‘modem_0001_4’ is setting up now
Mon Jun 12 13:55:12 2023 daemon.notice netifd: modem_0001_4 (29500): udhcpc: started, v1.33.2
Mon Jun 12 13:55:12 2023 daemon.notice netifd: modem_0001_4 (29500): udhcpc: sending discover
Mon Jun 12 13:55:12 2023 daemon.notice netifd: modem_0001_4 (29500): udhcpc: sending select for 192.0.0.2
Mon Jun 12 13:55:12 2023 daemon.notice netifd: modem_0001_4 (29500): udhcpc: lease of 192.0.0.2 obtained, lease time 7200
Mon Jun 12 13:55:12 2023 daemon.notice netifd: Interface ‘modem_0001_4’ is now up
Mon Jun 12 13:55:12 2023 user.notice mwan3[29477]: Execute ifdown event on interface modem_0001_4 (unknown)
Mon Jun 12 13:55:13 2023 user.notice firewall: Reloading firewall due to ifdown of modem_0001_4 ()
Mon Jun 12 13:55:13 2023 user.notice mwan3[29792]: Execute ifup event on interface modem_0001_4 (rmnet_mhi0)
Mon Jun 12 13:55:13 2023 user.notice mwan3[29792]: Starting tracker on interface modem_0001_4 (rmnet_mhi0)
Mon Jun 12 13:55:15 2023 user.info mwan3rtmon[8913]: Detect rtchange event.
Mon Jun 12 13:55:16 2023 user.notice firewall: Reloading firewall due to ifup of modem_0001_4 (rmnet_mhi0)
Mon Jun 12 13:55:22 2023 user.notice root: modem ip different, now regain ip …
Mon Jun 12 13:55:22 2023 daemon.notice netifd: Interface ‘modem_0001_4’ has lost the connection
Mon Jun 12 13:55:22 2023 daemon.notice netifd: Interface ‘modem_0001_4’ is now down
Mon Jun 12 13:55:22 2023 daemon.notice netifd: Interface ‘modem_0001_4’ is disabled
Mon Jun 12 13:55:22 2023 daemon.notice netifd: Interface ‘modem_0001_4’ is enabled
Mon Jun 12 13:55:22 2023 daemon.notice netifd: Interface ‘modem_0001_4’ is setting up now
Mon Jun 12 13:55:22 2023 daemon.notice netifd: modem_0001_4 (30727): udhcpc: started, v1.33.2
Mon Jun 12 13:55:22 2023 daemon.notice netifd: modem_0001_4 (30727): udhcpc: sending discover
Mon Jun 12 13:55:22 2023 daemon.notice netifd: modem_0001_4 (30727): udhcpc: sending select for 192.0.0.2
Mon Jun 12 13:55:23 2023 daemon.notice netifd: modem_0001_4 (30727): udhcpc: lease of 192.0.0.2 obtained, lease time 7200
Mon Jun 12 13:55:23 2023 daemon.notice netifd: Interface ‘modem_0001_4’ is now up
Mon Jun 12 13:55:23 2023 user.notice mwan3[30704]: Execute ifdown event on interface modem_0001_4 (unknown)
Mon Jun 12 13:55:23 2023 user.notice firewall: Reloading firewall due to ifdown of modem_0001_4 ()
Mon Jun 12 13:55:23 2023 user.notice mwan3[31040]: Execute ifup event on interface modem_0001_4 (rmnet_mhi0)
Mon Jun 12 13:55:24 2023 user.notice mwan3[31040]: Starting tracker on interface modem_0001_4 (rmnet_mhi0)
Mon Jun 12 13:55:26 2023 user.info mwan3rtmon[8913]: Detect rtchange event.
Mon Jun 12 13:55:26 2023 user.notice firewall: Reloading firewall due to ifup of modem_0001_4 (rmnet_mhi0)

2

I discovered this post. We have identical equipment and provider. Downgrading now and will report back after some testing.

GL-X3000 Extremely Unstable Modem - Technical Support for Routers - GL.iNet (gl-inet.com)

3

I may be having the same issue. Just received the router today and ran some testing noticing dropped connections. I did change the APN to match for T-Mobile. Also I tried setting the TTL but not sure it sticks in the config.

Will report back in this thread.

1 Like
4

Thanks for this - I would check out the other thread as well. We all seem to be having the same issue. I am in the US using T-Mobile business service. The “Auto Setup” button worked for me, but would you mind sharing the APN info you are using?

I have been testing 4.3.0 for about 2 hours and have had no drops. I will run this overnight and report back. I hope someone from Gl.iNet is following these forums.

Let us know how you get along and thanks for your feedback!

5

So I updated to 4.3.3 beta. I ran it for about 20 minutes without issues, then needed the sim back in my phone.
Can check again tomorrow.

As for APN. I used manual setup: fast.tmobile.com with TTL 65.

Edited: Issues are happening with 4.3.3. Also, I am roaming with T-Mobile sim.

1 Like
6

Thanks for the feedback and info. Maybe I will give 4.3.3 a try.

7

Negative for me on beta 4.3.3 - same behavior as 4.3.1. Started right away for me after flash and reboot.

Going back to 4.3.0.

8

Yeah 4.3.3 keeps stopping also

1 Like
9

Hi T480s:

Can I check this issue remotely?

Thanks!

10

Thank you for reaching out - please PM me directly on this.

11

I have run 4.3.0 overnight with no issues. @lizh thank you for joining the discussion. I am happy to troubleshoot this with you or provide whatever logs you need.

12

Hi T480s:

When the above issue occurs, help to execute the AT instructions: AT+CGPADDR.

Then help to check ip obtained:

image
image748×569 15.6 KB

Thanks!

13

Would like to say I’m having the same issue. Using T-Mobile SIM with V4.3.0 working flawlessly until I go V4.3.1 or newer.

Here’s my post: X3000 Spitz 4G Issues?

1 Like
14

Please tell me what to expect when I enter this command. Do you want me to issue this SSH or via terminal in the LuCI?

The T-Mobile service is CGNAT - I am essentially double NAT. The first time I use “auto setup” is used I get a WAN IP similar to what you have above. After a reboot and all other subsequent reboots my device is behind their CGNAT and provides me an address of 192.0.0.2.

T-Mobile will not hand out static IP address to consumers or business accounts with a FEIN number. Mine is a business postpaid account with out FEIN as I am a sole proprietor in effect. I hope this helps.

Again 4.3.0 has been working perfectly - anything newer generates the log info provided above.

15

Thank you - my experience as well. 4.3.0 is stable. Anything newer is not.

1 Like
16

Thank you very much.

Please help verify the firmware:
https://dl.gl-inet.com/?model=x3000&type=beta

17

@lizh if you go up about 7 or 8 posts, you will see that both myself and @Dominion7574 have tried 4.3.3 without success. It exhibits the same result as what is posted above.

4.3.0 has been working perfectly - anything newer 4.3.1 and 4.3.3 fails and generates log entries as in my 1st post.

18

Hi T480s

image
image1046×496 25.8 KB

This is a new firmware.

Thanks!

19

So far so good. Ill let you know tomorrow after more testing.

20

Thank you very much.