@Thomasinaz thanks for the tip. I still think that GL-iNet should post the change log to the firmware download page. My router is out in the camper and unplugged at the moment hence some effort involved to just see the change log vs pulling up the firmware page on my computer.
@yuxin.zou I upgraded the firmware. For me, it’s still behaving the same. Visible never reliably connects on the first try, either immediately after power on, or after switching SIM slots. Sometimes I have to “Abort” while it is trying to connect. Sometimes it connects but there is no Internet, so I have to “Disconnect” and try “Auto Setup” again. Usually during this process, the Cellular Settings I have saved under the profile (APN VZWINTERNET, TTL 65, MTU 1428) are reset to internet, null, null. At this point, it usually connects to Visible and I am connected to the internet. But then I have to manually change the TTL and MTU again, and then it usually reconnects successfully.
Can you point me to any log files I can monitor (via ssh) during this process, so I can gain some insight into what is happening during the multiple failed attempts to connect to Visible and the internet every time I power on or switch SIMs?
Once I get connected to Visible, the connection remains up and stays stable indefinitely.
@pwyngaard I’ve also saw it reset the APN to internet and then had it connect and work fine. I have my TTL settings in a firewall-start (or a similar file name) file and don’t adjust the MTU so I haven’t experienced those fields resetting.
@doczenith1 Are you also having similar problems with Visible basically never connecting on the first try? When the APN gets reset to internet, do you change it back to VZWINTERNET, or leave it alone? I change it back, at which point the modem tries to reconnect again. Sometimes it reconnects, and sometimes it doesn’t. After a few tries this morning, I was finally able to get a stable Visible connection with VZWINTERNET / 65 TTL / 1428 MTU. But in all, it probably took 10 tries.
Regarding setting the firewall rules, I’ve seen mention of that throughout this forum. Would you be able to direct me as to how and where I set this on the Spitz AX? I’m familiar with ssh and the linux-esque openwrt command line. My assumption is it is a set of iptables commands I need to issue. I’m just not sure exactly what those commands look like. Thank you.
Yes, I am having similar issues but it only seems to take me 2 or 3 tries to get it working. I can’t remember if it’s using the APN internet or VZWINTERNET when it finally connects but probably VZWINTERNET.
The reason I chose to use the firewall-start file is that when I first got my Spitz a few months ago and would enter a TTL value the value didn’t seem to stick. After leaving that screen and coming back the entry box was blank. No need to SSH into the router. You can access the location for the commands via LuCI which you get to under advanced settings in the router GUI. This is what I am using which applies the TTL setting to all interfaces.
iptables -t mangle -I POSTROUTING 1 -j TTL --ttl-set 65
iptables -t mangle -I PREROUTING 1 -j TTL --ttl-set 65
ip6tables -t mangle -I POSTROUTING 1 -j HL --hl-set 65
ip6tables -t mangle -I PREROUTING 1 -j HL --hl-set 65
There should be a dummy file already on the router. I just added these lines after pre populated and commented out lines.
P.S. Can I ask why you are changing the MTU to 1428?
Awesome, thank you @doczenith1, I appreciate it. Question about the iptables command: I often see these commands include the -i or -o command line option, along with a device name. Your commands lack these, so I assume specifying the device is not necesary?
I can’t give you a technical reason why I set the MTU to 1428. I saw it in other posts in this forum. If you search for “1428”, you’ll see several posts. It probably does not make much of a difference…
I’ll paste some verbiage below that was included in the post where I got the iptables commands from. I think it may answer your question regarding the -i or -o.
“… you need the ipv6 rules as visible is over ipv6 even if you only see ipv4 addresses. Specifying 1 instead of -o wwan0 or -i wwan0 makes it the first rule and on any interface. It seems to work better and it sticks. Add it directly on the firewall page.”
From what I could tell by looking at some other examples the -o is used for the POSTROUTING and -i is used for the PREROUTING lines before the interface. On my ASUS router that I use via a USB tethered phone I include “-o usb0” for the interface.
@yuxin.zou It seems we both have problems getting Visible to connect on the first try. In my case, the Visible SIM is in slot 2, and there is an ATT SIM in slot 1. ATT seems to always work fine. How can I debug this problem? What log files should I look at? What can I share with you to get your help resolving the issue? Thanks.
I am using the beta firmware, release40402, and I am using that profile, but I am still unable to ever connect to Visible successfully on the first try. It takes several tries, and in the process, as described above, the SIM settings are completely reset.
How can I debug this problem? I’m very comfortable with ssh and the command line, just don’t know where to look to see where the failure(s) are happening.
I’d like to add that it’s not just settings like APN, TTL, and MTU that are reset in the profile when going through the Disconnect / Abort / Auto Setup cycles needed to finally get Visible to connect. Any Band Masking settings are also lost.
If it is convenient for you,you could share with gl.inet_support via cloud platform.I will check it remotly.
I am having the exact same problems with unreliable connections to celluar data with my GL-X3000. In my case, the device is activated on Verizon directly, not visible.
I reverted to an earlier firmware version, which had previously worked reliably. But that actually has not helped.
Try the APN suggestions from this Reddit post, seems to have resolved problems for many people:
I haven’t been able to connect to Visible either. At best I see it connect for a few minutes, then it disconnects. Have other people been able to resolve this?
My Visible connection has been up for 4 days now using firmware 4.0-release10305. I’m using VZWINTERNET for the APN. I’m not sure if these other settings have any effect on the stability of the connection but I am using automatic for DNS, have modified the TTL per my earlier post and have a WireGuard tunnel running.
1 Like
Thanks! Apparently during some of my earlier testing Visible blocked the SIM card I had been using. I’m waiting to get a replacement and will give it a try again.
I’m having the same issue with Visible sim, unable to get it to connect with my GL-XE3000 . I have the latest firmware. I have tried the above troubleshooting and settings, but still it won’t connect. What can I do to get this working?
My X3000 has worked just fine with the Visible base plan on 4.0-release50402 and now on 4.0-0403release7. The one thing that might be different in my setup vs those having issues is that at some point I changed the IMEI to that of my Pixel 7.
1 Like
What is the reason behind using the TTL of 88?