GLX3000 and Visible Issues

GL-X3000 running firmware 0409release3 (which is the latest) and also flashed my modem firmware to RM520NGLAAR03A03M4G_01.201.01.201. Currently running Visible+ (2.0) and can't get the SIM to connect for data. Sometimes it will connect for about 30-60 seconds and then it fails again.

Have tried using the Auto Setup and the VZWINTERNET APN

Currently near Salt Lake City but was in Idaho a few days ago and it was working fine (and it has worked fine for the last 200+ days using the autosetup at locations around the US). If I take the SIM out and put in iPhone I can hotspot fine without issue. I have spoofed the IMEI to match the iPhone. I am not sure if this is something with local towers or something that Visible has changed.

I can text from the web interface back and forth so I have connectivity to a tower, etc. just no data that I can get.

I wish there was a separate log for modem activity, but I think this is the relevant log info:

Sat Aug 31 22:31:16 2024 daemon.notice netifd: modem_1_1_2 (13088): Request timed out
Sat Aug 31 22:31:46 2024 user.notice mwan3[14837]: Execute ifdown event on interface modem_0001 (rmnet_mhi0)
Sat Aug 31 22:31:46 2024 user.notice firewall: Reloading firewall due to ifdown of modem_0001 (rmnet_mhi0)
Sat Aug 31 22:31:46 2024 authpriv.notice sudo:     root : PWD=/ ; USER=root ; GROUP=nonevpn ; COMMAND=/usr/lib/gl_ddns/dynamic_dns_updater.sh -- stop
Sat Aug 31 22:31:47 2024 daemon.notice netifd: modem_1_1_2 (13088): Failed to connect to service
Sat Aug 31 22:31:47 2024 daemon.notice netifd: Interface 'modem_1_1_2' is now down
Sat Aug 31 22:31:47 2024 daemon.notice netifd: Interface 'modem_1_1_2' is setting up now
Sat Aug 31 22:31:48 2024 user.notice ddns-scripts[11634]: glddns: PID '11634' terminated by 'SIGTERM' at 2024-08-31 22:31
Sat Aug 31 22:31:49 2024 authpriv.notice sudo:     root : PWD=/ ; USER=root ; GROUP=nonevpn ; COMMAND=/usr/lib/gl_ddns/dynamic_dns_updater.sh -- start
Sat Aug 31 22:31:49 2024 user.info mwan3track[9371]: Detect ifdown event on interface modem_0001 (rmnet_mhi0)
Sat Aug 31 22:31:49 2024 user.notice ddns-scripts[15510]: ddns: PID '15510' started at 2024-08-31 22:31
Sat Aug 31 22:31:49 2024 user.warn ddns-scripts[15510]: ddns: Service section disabled! - TERMINATE
Sat Aug 31 22:31:49 2024 user.notice ddns-scripts[15513]: glddns: PID '15513' started at 2024-08-31 22:31
Sat Aug 31 22:31:49 2024 user.warn ddns-scripts[15510]: ddns: PID '15510' exit WITH ERROR '1' at 2024-08-31 22:31
Sat Aug 31 22:31:50 2024 user.warn ddns-scripts[15513]: glddns: NO valid IP found
Sat Aug 31 22:31:51 2024 daemon.notice netifd: modem_1_1_2 (15222):
Sat Aug 31 22:31:51 2024 daemon.notice netifd: modem_1_1_2 (15222):
Sat Aug 31 22:31:51 2024 daemon.notice netifd: modem_1_1_2 (15222): OK
Sat Aug 31 22:31:51 2024 daemon.notice netifd: modem_1_1_2 (15222):
Sat Aug 31 22:31:51 2024 daemon.notice netifd: modem_1_1_2 (15222):
Sat Aug 31 22:31:51 2024 daemon.notice netifd: modem_1_1_2 (15222): OK
Sat Aug 31 22:31:51 2024 daemon.notice netifd: modem_1_1_2 (15222):
Sat Aug 31 22:31:51 2024 daemon.notice netifd: modem_1_1_2 (15222):
Sat Aug 31 22:31:51 2024 daemon.notice netifd: modem_1_1_2 (15222): ERROR
Sat Aug 31 22:31:51 2024 daemon.notice netifd: modem_1_1_2 (15222): Failed to parse message data
Sat Aug 31 22:31:51 2024 daemon.notice netifd: modem_1_1_2 (15222):
Sat Aug 31 22:31:51 2024 daemon.notice netifd: modem_1_1_2 (15222):
Sat Aug 31 22:31:51 2024 daemon.notice netifd: modem_1_1_2 (15222): OK
Sat Aug 31 22:31:51 2024 daemon.notice netifd: modem_1_1_2 (15222):
Sat Aug 31 22:31:51 2024 daemon.notice netifd: modem_1_1_2 (15222):
Sat Aug 31 22:31:51 2024 daemon.notice netifd: modem_1_1_2 (15222): ERROR
Sat Aug 31 22:31:51 2024 daemon.notice netifd: modem_1_1_2 (15222):
Sat Aug 31 22:31:51 2024 daemon.notice netifd: modem_1_1_2 (15222):
Sat Aug 31 22:31:51 2024 daemon.notice netifd: modem_1_1_2 (15222): OK
Sat Aug 31 22:31:51 2024 daemon.notice netifd: modem_1_1_2 (15222):
Sat Aug 31 22:31:51 2024 daemon.notice netifd: modem_1_1_2 (15222):
Sat Aug 31 22:31:51 2024 daemon.notice netifd: modem_1_1_2 (15222): ERROR
Sat Aug 31 22:31:51 2024 daemon.notice netifd: modem_1_1_2 (15222):
Sat Aug 31 22:31:51 2024 daemon.notice netifd: modem_1_1_2 (15222):
Sat Aug 31 22:31:51 2024 daemon.notice netifd: modem_1_1_2 (15222): OK
Sat Aug 31 22:31:51 2024 daemon.notice netifd: modem_1_1_2 (15222):
Sat Aug 31 22:31:51 2024 daemon.notice netifd: modem_1_1_2 (15222):
Sat Aug 31 22:31:51 2024 daemon.notice netifd: modem_1_1_2 (15222): OK
Sat Aug 31 22:31:52 2024 daemon.notice netifd: modem_1_1_2 (15222): ls: /sys/devices/platform/11200000.xhci/usb1/1-1/1-1.2/1-1.2:1.3/net: No such file or directory
Sat Aug 31 22:31:54 2024 user.notice mwan3track[9371]: Interface modem_0001 (rmnet_mhi0) is offline
Sat Aug 31 22:31:55 2024 daemon.notice netifd: modem_1_1_2 (15222): Request timed out

Yes this is known issue and being investigated by GL. Downgrade to 4.4.8.

Can I see it remotely?
Technical Support via GoodCloud.tar (192 KB)

Yes depending on when you want to look. I am leaving this location for another tomorrow am. So if you want to look in the next few hours yes. If it doesn’t work at my next location we can look there as well (there for 6 days)

How do I setup the remote support?

Right now
image
This document has detailed steps

I believe it is all setup properly; let me know next steps.. Thanks!!!

Please text me your mac address and password
Personal letter

FYI here, support helped me by modifying the APN to VZWINTERNET but today arrived at new location in Utah and that APN no longer worked. Did the auto setup and it is now working..

I guess each location I get to just need to try a few different options. Figured I would update in case others are having issues.

Hasn't worked since support originally got it working have moved to a handful of locations (currently in Arizona now). VZWINTERNET will connect (i get an IP address and it shows online) about a minute later it just disconnects and won't connect again.

Getting pretty frustrated with this and not sure if it is a GL issue, Visible issue or a me issue.

Open goodcloud again?

I turned goodcloud back online - let me know if you can see it