Where can you see this in the logs/see this makes a difference?
More:
I don’t know how to change the TTL. I could figure out how to do it, but that’s a link to a command without context for me. I’ve not had to SSH in yet. I run a command? Shouldn’t I edit a file to change a config? I find if I click on the wrong thing (like Auto to connect) it undoes my AT commands and config changes.
If you’re telling me to change TTL, what should I change it to? And why? Can I see in the logs what you think is happening and how this fixes it?
I appreciate advice, but I’ve been “trying stuff” for a week and it’s really not the correct way to diagnose and fix a problem.
I’ve read a few threads… It looks like people are changing TTL because they are having trouble with tethered phones, which is not my setup. And their problem is speeds, which isn’t my problem… ?
I’ve read up and now understand that carriers use the TTL value to determine if there are additional devices ‘behind’ the device connecting to them, and that command will adjust the TTL so that everything looks like it originates at the x750.
Can you point me to where you found that this is the cause of the problem? I’m trying to find the resource that links my problem to TTL values.
I also tried a NETGEAR lb1120 and have the same symptoms… after a while, able to ping, but not able to get any traffic higher up the stack… So it is something happening upstream that’s not just the device.
@DanDan I think you saw the other thread where some people are having “proxy” issues on Port 80/443 traffic. The only solution I have seen, that you can implement outside of ATT fixing it, is running a VPN.
I am testing Mullvad, Windscrbe and StrongVPN via Wireguard protocol now.
I am leaning towards Windscribe because they have Ad Blocking and a few other controls, but need to do more back-to-back speed tests early in the morning (off-peak)
You tried to help when I ran into the issues I had. I sent several long emails explaining the issues, and recommendations for how to improve the product.
It needed to have better transparency about errors and configuration- it is too much of a black box in that the logging wasn’t clear and complete. The ability to configure it through the UI was a bit buggy and confusing.
Why were connections dropping?
What configurations lasted across rebooting? The device didn’t work, and it wasn’t clear why it wasn’t working.
I know it worked for some people, not me. I spent enough time trying it and really trying to work with support (with you, actually).
Your team has made updates? Good for you.
But- like I said- I returned this product months ago- ultimately I could not get it to work as needed. Good luck.
What does this really mean? Is this for any X750? Or newly sold ones? Does it apply a firmware upgrade to the modem? If so, which models? Or change the IMEI using the AT command? Or just use a different APN and that accepts the std IMEI?
