GL-X750 - Manual setup options on admin panel?

I am using my router for AT&T broadband. Earlier today I couldn’t get it to connect. This evening I fiddled with the “Manual setup”. One of these worked but now I’m curious what those are for and what they mean. Specifically I’m asking about the drop down for “device”.

For instance:

/dev/cdc-wdm0

What are all of these for? Which one should I be using for 4g lte?

which device worked?

cdc-wdm0 is the modem device used for QMI protocol.

ttyUSB is modem device using in serial mode.

Modems could work in both mode. Generally ttyUSB mode has less problems but qmi mode may have more speed.

I don’t recall. A couple worked. It was definitely one of the ttyUSB ones. However overnight, the internet seems to have stopped working even though the router says it has internet. All lights are lit up, but all connected devices seem to have no internet. I have using firmware 3.108. I upgraded from 3.028 last night.

How do I fix that?

Any ideas? It drops out a few hours after connecting and never recovers.

Is there a setting somewhere on the new software that fixes this???

When you say it drops out, does the Control Panel Internet screen show you are still connected or does it say SIM Not Registered?

It won’t let me upload photos. However, YES…

1.) The admin screen shows that I am connected to the internet and the icons on the router panel indicate that I am connected to the internet.
2.) No devices connected to the router whether via WIFI or ETHERNET cable have seem to have internet access.
3.) However, with a command prompt I can PING GOOGLE AND YAHOO. Even so, a browser will not pull up their associated websites.

This is bizarre. I feel like this is a stupid easy problem to solve based on what seems to be quite specific issues.

What am I missing here?

EDIT: Just like that, everything seems to have reconnected after I disconnected my wifi on the pc and reconnected it. Its like everything woke up.

What is going on?

Wed Sep 2 05:24:01 2020 daemon.info dnsmasq-dhcp[10538]: DHCPACK(br-lan) 192.168.8.73 00:d0:2d:91:59:3a Gateway91593A
Wed Sep 2 05:27:11 2020 daemon.notice netifd: Network device ‘eth0’ link is down
Wed Sep 2 05:27:11 2020 kern.info kernel: [83349.421332] eth0: link down
Wed Sep 2 05:27:11 2020 kern.info kernel: [83349.421761] br-lan: port 2(eth0) entered disabled state
Wed Sep 2 05:27:13 2020 daemon.notice netifd: Network device ‘eth0’ link is up
Wed Sep 2 05:27:13 2020 kern.info kernel: [83351.502830] eth0: link up (100Mbps/Full duplex)
Wed Sep 2 05:27:13 2020 kern.info kernel: [83351.502946] br-lan: port 2(eth0) entered blocking state
Wed Sep 2 05:27:13 2020 kern.info kernel: [83351.502961] br-lan: port 2(eth0) entered forwarding state
Wed Sep 2 05:27:16 2020 daemon.notice netifd: Network device ‘eth0’ link is down
Wed Sep 2 05:27:16 2020 kern.info kernel: [83353.581932] eth0: link down
Wed Sep 2 05:27:16 2020 kern.info kernel: [83353.582323] br-lan: port 2(eth0) entered disabled state
Wed Sep 2 05:27:21 2020 daemon.notice netifd: Network device ‘eth0’ link is up
Wed Sep 2 05:27:21 2020 kern.info kernel: [83358.782823] eth0: link up (100Mbps/Full duplex)
Wed Sep 2 05:27:21 2020 kern.info kernel: [83358.782890] br-lan: port 2(eth0) entered blocking state
Wed Sep 2 05:27:21 2020 kern.info kernel: [83358.782902] br-lan: port 2(eth0) entered forwarding state
Wed Sep 2 05:27:22 2020 daemon.info dnsmasq-dhcp[10538]: DHCPDISCOVER(br-lan) 00:d0:2d:91:59:3a
Wed Sep 2 05:27:22 2020 daemon.info dnsmasq-dhcp[10538]: DHCPOFFER(br-lan) 192.168.8.73 00:d0:2d:91:59:3a
Wed Sep 2 05:27:22 2020 daemon.info dnsmasq-dhcp[10538]: DHCPREQUEST(br-lan) 192.168.8.73 00:d0:2d:91:59:3a
Wed Sep 2 05:27:22 2020 daemon.info dnsmasq-dhcp[10538]: DHCPACK(br-lan) 192.168.8.73 00:d0:2d:91:59:3a Gateway91593A
Wed Sep 2 05:31:11 2020 daemon.info dnsmasq-dhcp[10538]: DHCPDISCOVER(br-lan) 00:d0:2d:91:59:3a
Wed Sep 2 05:31:11 2020 daemon.info dnsmasq-dhcp[10538]: DHCPOFFER(br-lan) 192.168.8.73 00:d0:2d:91:59:3a
Wed Sep 2 05:31:11 2020 daemon.info dnsmasq-dhcp[10538]: DHCPREQUEST(br-lan) 192.168.8.73 00:d0:2d:91:59:3a
Wed Sep 2 05:31:11 2020 daemon.info dnsmasq-dhcp[10538]: DHCPACK(br-lan) 192.168.8.73 00:d0:2d:91:59:3a Gateway91593A
Wed Sep 2 05:35:01 2020 daemon.info dnsmasq-dhcp[10538]: DHCPDISCOVER(br-lan) 00:d0:2d:91:59:3a
Wed Sep 2 05:35:01 2020 daemon.info dnsmasq-dhcp[10538]: DHCPOFFER(br-lan) 192.168.8.73 00:d0:2d:91:59:3a
Wed Sep 2 05:35:01 2020 daemon.info dnsmasq-dhcp[10538]: DHCPREQUEST(br-lan) 192.168.8.73 00:d0:2d:91:59:3a
Wed Sep 2 05:35:01 2020 daemon.info dnsmasq-dhcp[10538]: DHCPACK(br-lan) 192.168.8.73 00:d0:2d:91:59:3a Gateway91593A
Wed Sep 2 05:38:51 2020 daemon.info dnsmasq-dhcp[10538]: DHCPDISCOVER(br-lan) 00:d0:2d:91:59:3a
Wed Sep 2 05:38:51 2020 daemon.info dnsmasq-dhcp[10538]: DHCPOFFER(br-lan) 192.168.8.73 00:d0:2d:91:59:3a
Wed Sep 2 05:38:51 2020 daemon.info dnsmasq-dhcp[10538]: DHCPREQUEST(br-lan) 192.168.8.73 00:d0:2d:91:59:3a
Wed Sep 2 05:38:51 2020 daemon.info dnsmasq-dhcp[10538]: DHCPACK(br-lan) 192.168.8.73 00:d0:2d:91:59:3a Gateway91593A
Wed Sep 2 05:42:41 2020 daemon.info dnsmasq-dhcp[10538]: DHCPDISCOVER(br-lan) 00:d0:2d:91:59:3a
Wed Sep 2 05:42:41 2020 daemon.info dnsmasq-dhcp[10538]: DHCPOFFER(br-lan) 192.168.8.73 00:d0:2d:91:59:3a
Wed Sep 2 05:42:41 2020 daemon.info dnsmasq-dhcp[10538]: DHCPREQUEST(br-lan) 192.168.8.73 00:d0:2d:91:59:3a
Wed Sep 2 05:42:41 2020 daemon.info dnsmasq-dhcp[10538]: DHCPACK(br-lan) 192.168.8.73 00:d0:2d:91:59:3a Gateway91593A
Wed Sep 2 05:46:31 2020 daemon.info dnsmasq-dhcp[10538]: DHCPDISCOVER(br-lan) 00:d0:2d:91:59:3a
Wed Sep 2 05:46:31 2020 daemon.info dnsmasq-dhcp[10538]: DHCPOFFER(br-lan) 192.168.8.73 00:d0:2d:91:59:3a
Wed Sep 2 05:46:31 2020 daemon.info dnsmasq-dhcp[10538]: DHCPREQUEST(br-lan) 192.168.8.73 00:d0:2d:91:59:3a
Wed Sep 2 05:46:31 2020 daemon.info dnsmasq-dhcp[10538]: DHCPACK(br-lan) 192.168.8.73 00:d0:2d:91:59:3a Gateway91593A
Wed Sep 2 05:50:21 2020 daemon.info dnsmasq-dhcp[10538]: DHCPDISCOVER(br-lan) 00:d0:2d:91:59:3a
Wed Sep 2 05:50:21 2020 daemon.info dnsmasq-dhcp[10538]: DHCPOFFER(br-lan) 192.168.8.73 00:d0:2d:91:59:3a
Wed Sep 2 05:50:21 2020 daemon.info dnsmasq-dhcp[10538]: DHCPREQUEST(br-lan) 192.168.8.73 00:d0:2d:91:59:3a
Wed Sep 2 05:50:21 2020 daemon.info dnsmasq-dhcp[10538]: DHCPACK(br-lan) 192.168.8.73 00:d0:2d:91:59:3a Gateway91593A
Wed Sep 2 05:54:11 2020 daemon.info dnsmasq-dhcp[10538]: DHCPDISCOVER(br-lan) 00:d0:2d:91:59:3a
Wed Sep 2 05:54:11 2020 daemon.info dnsmasq-dhcp[10538]: DHCPOFFER(br-lan) 192.168.8.73 00:d0:2d:91:59:3a
Wed Sep 2 05:54:11 2020 daemon.info dnsmasq-dhcp[10538]: DHCPREQUEST(br-lan) 192.168.8.73 00:d0:2d:91:59:3a
Wed Sep 2 05:54:11 2020 daemon.info dnsmasq-dhcp[10538]: DHCPACK(br-lan) 192.168.8.73 00:d0:2d:91:59:3a Gateway91593A
Wed Sep 2 05:57:15 2020 daemon.notice netifd: Network device ‘eth0’ link is down
Wed Sep 2 05:57:15 2020 kern.info kernel: [85152.773275] eth0: link down
Wed Sep 2 05:57:15 2020 kern.info kernel: [85152.773653] br-lan: port 2(eth0) entered disabled state
Wed Sep 2 05:57:17 2020 daemon.notice netifd: Network device ‘eth0’ link is up
Wed Sep 2 05:57:17 2020 kern.info kernel: [85154.854662] eth0: link up (100Mbps/Full duplex)
Wed Sep 2 05:57:17 2020 kern.info kernel: [85154.854731] br-lan: port 2(eth0) entered blocking state
Wed Sep 2 05:57:17 2020 kern.info kernel: [85154.854745] br-lan: port 2(eth0) entered forwarding state
Wed Sep 2 05:57:19 2020 daemon.notice netifd: Network device ‘eth0’ link is down
Wed Sep 2 05:57:19 2020 kern.info kernel: [85156.933756] eth0: link down
Wed Sep 2 05:57:19 2020 kern.info kernel: [85156.934145] br-lan: port 2(eth0) entered disabled state
Wed Sep 2 05:57:20 2020 daemon.notice netifd: Network device ‘eth0’ link is up
Wed Sep 2 05:57:20 2020 kern.info kernel: [85157.974677] eth0: link up (100Mbps/Full duplex)
Wed Sep 2 05:57:20 2020 kern.info kernel: [85157.974746] br-lan: port 2(eth0) entered blocking state
Wed Sep 2 05:57:20 2020 kern.info kernel: [85157.974758] br-lan: port 2(eth0) entered forwarding state
Wed Sep 2 05:57:20 2020 daemon.info dnsmasq-dhcp[10538]: DHCPDISCOVER(br-lan) 00:d0:2d:91:59:3a
Wed Sep 2 05:57:20 2020 daemon.info dnsmasq-dhcp[10538]: DHCPOFFER(br-lan) 192.168.8.73 00:d0:2d:91:59:3a
Wed Sep 2 05:57:20 2020 daemon.info dnsmasq-dhcp[10538]: DHCPREQUEST(br-lan) 192.168.8.73 00:d0:2d:91:59:3a
Wed Sep 2 05:57:20 2020 daemon.info dnsmasq-dhcp[10538]: DHCPACK(br-lan) 192.168.8.73 00:d0:2d:91:59:3a Gateway91593A
Wed Sep 2 06:00:05 2020 daemon.info hostapd: wlan1: STA e4:2b:34:5a:9d:1b IEEE 802.11: authenticated
Wed Sep 2 06:00:05 2020 daemon.info hostapd: wlan1: STA e4:2b:34:5a:9d:1b IEEE 802.11: associated (aid 2)
Wed Sep 2 06:00:05 2020 daemon.notice hostapd: wlan1: AP-STA-CONNECTED e4:2b:34:5a:9d:1b
Wed Sep 2 06:00:05 2020 daemon.info hostapd: wlan1: STA e4:2b:34:5a:9d:1b RADIUS: starting accounting session 8531800656511CCC
Wed Sep 2 06:00:05 2020 daemon.info hostapd: wlan1: STA e4:2b:34:5a:9d:1b WPA: pairwise key handshake completed (RSN)
Wed Sep 2 06:00:05 2020 daemon.info dnsmasq-dhcp[10538]: DHCPREQUEST(br-lan) 192.168.8.223 e4:2b:34:5a:9d:1b
Wed Sep 2 06:00:05 2020 daemon.info dnsmasq-dhcp[10538]: DHCPNAK(br-lan) 192.168.8.223 e4:2b:34:5a:9d:1b address not available
Wed Sep 2 06:00:08 2020 daemon.info dnsmasq-dhcp[10538]: DHCPDISCOVER(br-lan) e4:2b:34:5a:9d:1b
Wed Sep 2 06:00:08 2020 daemon.info dnsmasq-dhcp[10538]: DHCPOFFER(br-lan) 192.168.8.63 e4:2b:34:5a:9d:1b
Wed Sep 2 06:00:08 2020 daemon.info dnsmasq-dhcp[10538]: DHCPDISCOVER(br-lan) e4:2b:34:5a:9d:1b
Wed Sep 2 06:00:08 2020 daemon.info dnsmasq-dhcp[10538]: DHCPOFFER(br-lan) 192.168.8.63 e4:2b:34:5a:9d:1b
Wed Sep 2 06:00:08 2020 daemon.info dnsmasq-dhcp[10538]: DHCPDISCOVER(br-lan) e4:2b:34:5a:9d:1b
Wed Sep 2 06:00:08 2020 daemon.info dnsmasq-dhcp[10538]: DHCPOFFER(br-lan) 192.168.8.63 e4:2b:34:5a:9d:1b
Wed Sep 2 06:00:09 2020 daemon.info dnsmasq-dhcp[10538]: DHCPREQUEST(br-lan) 192.168.8.63 e4:2b:34:5a:9d:1b
Wed Sep 2 06:00:09 2020 daemon.info dnsmasq-dhcp[10538]: DHCPACK(br-lan) 192.168.8.63 e4:2b:34:5a:9d:1b iPhone
Wed Sep 2 06:01:08 2020 daemon.info dnsmasq-dhcp[10538]: DHCPDISCOVER(br-lan) 00:d0:2d:91:59:3a
Wed Sep 2 06:01:08 2020 daemon.info dnsmasq-dhcp[10538]: DHCPOFFER(br-lan) 192.168.8.73 00:d0:2d:91:59:3a
Wed Sep 2 06:01:08 2020 daemon.info dnsmasq-dhcp[10538]: DHCPREQUEST(br-lan) 192.168.8.73 00:d0:2d:91:59:3a
Wed Sep 2 06:01:08 2020 daemon.info dnsmasq-dhcp[10538]: DHCPACK(br-lan) 192.168.8.73 00:d0:2d:91:59:3a Gateway91593A
Wed Sep 2 06:04:58 2020 daemon.info dnsmasq-dhcp[10538]: DHCPDISCOVER(br-lan) 00:d0:2d:91:59:3a
Wed Sep 2 06:04:58 2020 daemon.info dnsmasq-dhcp[10538]: DHCPOFFER(br-lan) 192.168.8.73 00:d0:2d:91:59:3a
Wed Sep 2 06:04:58 2020 daemon.info dnsmasq-dhcp[10538]: DHCPREQUEST(br-lan) 192.168.8.73 00:d0:2d:91:59:3a
Wed Sep 2 06:04:58 2020 daemon.info dnsmasq-dhcp[10538]: DHCPACK(br-lan) 192.168.8.73 00:d0:2d:91:59:3a Gateway91593A
Wed Sep 2 06:08:48 2020 daemon.info dnsmasq-dhcp[10538]: DHCPDISCOVER(br-lan) 00:d0:2d:91:59:3a
Wed Sep 2 06:08:48 2020 daemon.info dnsmasq-dhcp[10538]: DHCPOFFER(br-lan) 192.168.8.73 00:d0:2d:91:59:3a
Wed Sep 2 06:08:48 2020 daemon.info dnsmasq-dhcp[10538]: DHCPREQUEST(br-lan) 192.168.8.73 00:d0:2d:91:59:3a
Wed Sep 2 06:08:48 2020 daemon.info dnsmasq-dhcp[10538]: DHCPACK(br-lan) 192.168.8.73 00:d0:2d:91:59:3a Gateway91593A
Wed Sep 2 06:12:38 2020 daemon.info dnsmasq-dhcp[10538]: DHCPDISCOVER(br-lan) 00:d0:2d:91:59:3a
Wed Sep 2 06:12:38 2020 daemon.info dnsmasq-dhcp[10538]: DHCPOFFER(br-lan) 192.168.8.73 00:d0:2d:91:59:3a
Wed Sep 2 06:12:38 2020 daemon.info dnsmasq-dhcp[10538]: DHCPREQUEST(br-lan) 192.168.8.73 00:d0:2d:91:59:3a
Wed Sep 2 06:12:38 2020 daemon.info dnsmasq-dhcp[10538]: DHCPACK(br-lan) 192.168.8.73 00:d0:2d:91:59:3a Gateway91593A
Wed Sep 2 06:16:28 2020 daemon.info dnsmasq-dhcp[10538]: DHCPDISCOVER(br-lan) 00:d0:2d:91:59:3a
Wed Sep 2 06:16:28 2020 daemon.info dnsmasq-dhcp[10538]: DHCPOFFER(br-lan) 192.168.8.73 00:d0:2d:91:59:3a
Wed Sep 2 06:16:28 2020 daemon.info dnsmasq-dhcp[10538]: DHCPREQUEST(br-lan) 192.168.8.73 00:d0:2d:91:59:3a
Wed Sep 2 06:16:28 2020 daemon.info dnsmasq-dhcp[10538]: DHCPACK(br-lan) 192.168.8.73 00:d0:2d:91:59:3a Gateway91593A
Wed Sep 2 06:18:13 2020 daemon.notice hostapd: wlan1: AP-STA-DISCONNECTED e4:2b:34:5a:9d:1b
Wed Sep 2 06:18:13 2020 daemon.info hostapd: wlan1: STA e4:2b:34:5a:9d:1b IEEE 802.11: disassociated
Wed Sep 2 06:18:14 2020 daemon.info hostapd: wlan1: STA e4:2b:34:5a:9d:1b IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Wed Sep 2 06:20:18 2020 daemon.info dnsmasq-dhcp[10538]: DHCPDISCOVER(br-lan) 00:d0:2d:91:59:3a
Wed Sep 2 06:20:18 2020 daemon.info dnsmasq-dhcp[10538]: DHCPOFFER(br-lan) 192.168.8.73 00:d0:2d:91:59:3a
Wed Sep 2 06:20:18 2020 daemon.info dnsmasq-dhcp[10538]: DHCPREQUEST(br-lan) 192.168.8.73 00:d0:2d:91:59:3a
Wed Sep 2 06:20:18 2020 daemon.info dnsmasq-dhcp[10538]: DHCPACK(br-lan) 192.168.8.73 00:d0:2d:91:59:3a Gateway91593A
Wed Sep 2 06:22:42 2020 daemon.notice netifd: modem_1_1_2_4 (10155): udhcpc: sending renew to 10.142.200.208
Wed Sep 2 06:22:42 2020 daemon.notice netifd: modem_1_1_2_4 (10155): udhcpc: lease of 10.142.200.207 obtained, lease time 7200
Wed Sep 2 06:24:08 2020 daemon.info dnsmasq-dhcp[10538]: DHCPDISCOVER(br-lan) 00:d0:2d:91:59:3a
Wed Sep 2 06:24:08 2020 daemon.info dnsmasq-dhcp[10538]: DHCPOFFER(br-lan) 192.168.8.73 00:d0:2d:91:59:3a
Wed Sep 2 06:24:08 2020 daemon.info dnsmasq-dhcp[10538]: DHCPREQUEST(br-lan) 192.168.8.73 00:d0:2d:91:59:3a
Wed Sep 2 06:24:08 2020 daemon.info dnsmasq-dhcp[10538]: DHCPACK(br-lan) 192.168.8.73 00:d0:2d:91:59:3a Gateway91593A
Wed Sep 2 06:27:18 2020 daemon.notice netifd: Network device ‘eth0’ link is down
Wed Sep 2 06:27:18 2020 kern.info kernel: [86956.122553] eth0: link down
Wed Sep 2 06:27:18 2020 kern.info kernel: [86956.123135] br-lan: port 2(eth0) entered disabled state
Wed Sep 2 06:27:20 2020 daemon.notice netifd: Network device ‘eth0’ link is up
Wed Sep 2 06:27:20 2020 kern.info kernel: [86958.203815] eth0: link up (100Mbps/Full duplex)
Wed Sep 2 06:27:20 2020 kern.info kernel: [86958.203880] br-lan: port 2(eth0) entered blocking state
Wed Sep 2 06:27:20 2020 kern.info kernel: [86958.203891] br-lan: port 2(eth0) entered forwarding state
Wed Sep 2 06:27:22 2020 daemon.notice netifd: Network device ‘eth0’ link is down
Wed Sep 2 06:27:22 2020 kern.info kernel: [86960.282582] eth0: link down
Wed Sep 2 06:27:22 2020 kern.info kernel: [86960.283015] br-lan: port 2(eth0) entered disabled state
Wed Sep 2 06:27:23 2020 daemon.notice netifd: Network device ‘eth0’ link is up
Wed Sep 2 06:27:23 2020 kern.info kernel: [86961.323808] eth0: link up (100Mbps/Full duplex)
Wed Sep 2 06:27:23 2020 kern.info kernel: [86961.323871] br-lan: port 2(eth0) entered blocking state
Wed Sep 2 06:27:23 2020 kern.info kernel: [86961.323882] br-lan: port 2(eth0) entered forwarding state
Wed Sep 2 06:27:24 2020 daemon.info dnsmasq-dhcp[10538]: DHCPDISCOVER(br-lan) 00:d0:2d:91:59:3a
Wed Sep 2 06:27:24 2020 daemon.info dnsmasq-dhcp[10538]: DHCPOFFER(br-lan) 192.168.8.73 00:d0:2d:91:59:3a
Wed Sep 2 06:27:24 2020 daemon.info dnsmasq-dhcp[10538]: DHCPREQUEST(br-lan) 192.168.8.73 00:d0:2d:91:59:3a
Wed Sep 2 06:27:24 2020 daemon.info dnsmasq-dhcp[10538]: DHCPACK(br-lan) 192.168.8.73 00:d0:2d:91:59:3a Gateway91593A

Which ATT service plan do you have?

For your client devices, have you tried both Ethernet and Wifi?

Any difference if you run a VPN Client from the router?

Have you tried setting TTL to 65 or 66?

Advanced - Firewall - Custom Rules
#ipv6ttlfix
ip6tables -t mangle -I POSTROUTING -o wwan0 -j HL --hl-set 65
ip6tables -t mangle -I PREROUTING -i wwan0 -j HL --hl-set 65
#startTTL
iptables -t mangle -I POSTROUTING -o wwan0 -j TTL --ttl-set 65
iptables -t mangle -I PREROUTING -i wwan0 -j TTL --ttl-set 65
#endTTL

It does not matter if it is wifi or Ethernet.

When client devices can not connect to the internet, the router still indicates that it has internet. Also the computer while unable to load a webpage can ping websites. I do not know what all of those commands are or why I need them. I don’t understand why this device all of a sudden has ceased to function flawlessly. I have had no issues whatsoever in four months since it was brand new and now all of a sudden it’s doing this.

This has been factory reset 5 times, updated to latest firmware, downgraded to previous firmware — TWICE…and still it does not work. This device was working absolutely flawlessly for 7 months on the AT&T network and NOW all of a sudden it stops working reliably.

It is an unlimited AT&T plan from a third party provider. I do not have any VPN stuff. I have not tried the TTL but I will try it out and let you know.

No luck. TTL changes did not solve the problem.

Where is the manufacturer support on this? This feels like it should be a throwdown easy fix for someone familiar with this router.

Router says everything is connected.
Computer can ping websites but not load them
All other devices that are connected to router complain of ‘no internet connection’.
As long as I’m USING the internet, it seems to be fine. When the router is idle and not doing much is when it seems to make devices drop.

What do we need to do to get this escalated and solved?

This seems a DNS problem. Can you post your main panel screenshot? Just to understand the current IP and DNS etc.

Are you saying that you have internet when you reconnect wifi? Or whatever it cannot connect after this happen? I wonder if you can get into the device and get the log.

Do not downgrade firmware. Just use the latest one and we start from here .

I will have to host the image somewhere. I have upgraded again to the latest firmware.

I’m saying that the router is currently connected to the LTE network. My computer is connected via WiFi. A camera system is connected via lan.

Right now, the router is connected to the lte network according to the router.

The computer will not load any pages and seems to have no internet access. HOWEVER, at the same time, I can ping google.com with Cmd prompt and get low latency and no errors.

The camera system currently complains of no internet access.

If I go the the admin page of the router and disconnect and then auto setup to reconnect, then everything works for a few minutes until it stops again.

I can get to logs. One is posted in this thread.

Remove the camera system from the lan for now.

Assuming that your X750 is 192.168.8.1, can you tell us what your computer shows for IP, Gateway & DNS

Also, you have any DNS options set on the X750?
These are my working settings (but they may not work for you).

It kind of sounds like Port 80/443 traffic is being blocked.

Do you have any firewall policies in place?

You can get a VPN with Mullvad for about $6 for 1 month if you want to try and see if Port 80/443 traffic flows through the VPN https://mullvad.net/en/

Looks like Windscribe will let you do a computer based VPN with 2-10GB of data for free, this would be enough for you to test: https://windscribe.com/

If it works with a VPN, then ATT might be blocking http(s) traffic on that sim/account.

Alright, I found some new info.

First, YES…I can use your settings, and I will test those out for custom DNS.

Second…can you check this link:

Does this mean anything to you? I basically suspect maybe this is my problem, and this is why I’m asking about VPN stuff. I want to try the VPN, but I want it to be router based, not computer based. I need every device to be protected.

What do I need to do?

Setup the free computer based VPN with 2-10GB of data: https://windscribe.com/ . This would be enough for you to test to see if VPN solves your problem as it did for most of those people in the thread you linked to.

If the VPN test works, you can get a paid VPN services with WindScribe, MullVad or any of the other VPNs that offer Wireguard for routers.

Thanks! I went ahead and paid for NordVPN. There is a 30 day money back guarantee if it doesn’t work for any reason. Honestly, this is probably something I should have been using anyway.

Since you seem versed in this topic, can you explain to me WHY this solution seems to be working? Don’t they all go through AT&T for service? How does VPN avoid the problematic proxy server issue that seems to be the problem? I don’t fully understand. I know enough about networking to get in trouble.

If you are able to make a successful connection to a VPN server, all of your traffic routes through that connection and avoids any ATT proxies(where they might be doing stuff to your port 80/443 traffic). ATT doesn’t see your individual port traffic when using a VPN.

Been reading this thread, and @RichP is helpfully offering me advice on similar problems in my own, other thread (Thanks Rich.:slight_smile: ) . @Agdodge4x4 - did your problem go away by adjusting the TTL and/or going through a proxy? I’d like to avoid running all my data through a proxy. But perhaps if I want to avoid anybody sniffing I should anyway. I wary of the performance cost and debugging complexity if I go through a VPN for all my traffic…