Is there any timeline on when this will be a generally available feature?
ok, I just realized that this case is not handled at all by the GL-iNet firmware. In my case I just lose connectivity to the router when my ISP changes the IP.
My wild guess: there is no reaction upon IP change from the WAN DHCP. It’s very likely that the router IP is changing but the dnsmasq configuration is not changed or, if changed, dnsmasq is not restarted and therefore it simply stops replying to DHCP REQUESTs from the LAN side.
The FW should react to every WAN lease and check if anything has changed. If so, should just re-run the enable procedure and let dnsmasq get the new network.
@lizh @yuxin.zou is this the right place to report this bug? If not, where could I open a ticket? Thanks!
I have some logs retrieved at the time of the issue. But I Cannot add more replies to this topic.
Logs are here: https://pastebin.com/J0sYpwrA
Please let me know if I should open a bug somewhere else.
Thanks!
Interested in getting this working.
I am using a TP ER605 load balancer, so it looks like all I need to do run the command below via SSH.
curl -k http://127.0.0.1/rpc -H ‘glinet: 1’ -d ‘{“jsonrpc”:“2.0”,“method”:“call”,“params”:[“”,“netmode”,“set_mode”,{“mode”:“passthrough”,“mask”:“auto”}],“id”:1}’
Then just restart it and connect it to my TP Link switch, do I need a static IP or it? Is it PPPOE? That’s the correct option on the other end?
Thanks for your feedback, we have fixed it.
The next version of the firmware will resolve this issue.
great to hear that! Looking forward to upgrading to the new version!
For your information, I have shared my logs also with your support contact. Therefore there might be a ticket opened there.
@yuxin.zou is thee any way to be informed when a new firmware is out? some specific webpage or anything else?
The device’s admin panel will pop up with a prompt.
It will also be updated here: GL.iNet download center (gl-inet.com)
Thanks a lot @yuxin.zou . If you build a RC release with bug fixes only, I could give it a go and report back.
there is a new version available (4.0-0405release1), but it seems to be compiled on January 3rd, therefore I presume this is not the one I am waiting for. Right?
Thanks a lot
1 Like
Hi
@yuxin.zou thank you for sharing this workaround! It’s very useful!
Although I can’t wait to have it as final released software.
I’ve a couple of questions:
-
I noticed that I get a NATed IP. Not the real public IP provided by my ISP. Is this normal ? Can it be disabled?
-
I noticed that load balance feature is not available. Is it considered in the future release? Here I believe the NAT would be useful, but please consider using both ethernet ports individually for load balancing between each SIM. I mean SIM1 IP Passthrough to WAN port and SIM2 IP Passthrough to LAN port. And another option to use load balacing between SIMs with only WAN port as it is 2,5Gbps either with NAT or without NAT.
Thank you!
Hi @ordex you managed to get the public internet IP passed through instead of a private one ?
This device doesn’t have the Bridge option, it works as a Router, therefore, there will always be NAT between the public WAN and the private LAN, until, the Bridge capability will be implemented.
1 Like
I get the IP assigned by the ISP. If the ISP assigns a private IP, then you’ll see a private IP on your device. Viceversa for a public IP.
I just enabled passthrough as explained at the beginning of this thread.
@logi it is not bridge mode, but you still get the WAN IP Passed through.
I know, I have used the same, it is bridge, but it is experimental, and wasn’t stable enough for my usage
YES, it(4.0-0405release1) hasn’t update.
@lizh do you have any ETA for the firmware with the fix for this bug?
Even having a beta or rc release to test would be great. Unfortunately this bug is quite annoying as it requires rebooting the device almost every day.
Thanks!
Hi @lizh @yuxin.zou
I am testing the beta firmware which includes the fix.
However something is not quite right. It’s possible it worked once, but today, upon IP change, my X3000 got stuck again.
This time this is what happened:
Wed Jan 31 09:27:06 2024 daemon.notice netifd: modem_0001 (18002): [01-30_09:27:45:593] requestGetSIMStatus SIMStatus: SIM_READY
Wed Jan 31 09:27:06 2024 daemon.notice netifd: modem_0001 (18002): [01-30_09:27:45:597] requestGetProfile[1] myinternet.wind///0/IPV4V6
Wed Jan 31 09:27:06 2024 daemon.notice netifd: modem_0001 (18002): [01-30_09:27:45:597] requestSetProfile[1] myinternet.wind///0/IPV4V6
Wed Jan 31 09:27:06 2024 daemon.notice netifd: modem_0001 (18002): [01-30_09:27:45:598] no need to set skip the rest
Wed Jan 31 09:27:06 2024 daemon.notice netifd: modem_0001 (18002): [01-30_09:27:45:600] requestRegistrationState2 MCC: 222, MNC: 88, PS: Attached, DataCap: 5G_NSA
Wed Jan 31 09:27:06 2024 daemon.notice netifd: modem_0001 (18002): [01-30_09:27:45:604] requestQueryDataCall IPv4ConnectionStatus: DISCONNECTED
Wed Jan 31 09:27:06 2024 daemon.notice netifd: modem_0001 (18002): [01-30_09:27:45:607] requestQueryDataCall IPv6ConnectionStatus: DISCONNECTED
Wed Jan 31 09:27:06 2024 daemon.notice netifd: modem_0001 (18002): [01-30_09:27:45:619] requestSetupDataCall WdsConnectionIPv4Handle: 0xe8b9ebc0
Wed Jan 31 09:27:06 2024 daemon.notice netifd: modem_0001 (18002): [01-30_09:27:45:631] requestSetupDataCall WdsConnectionIPv6Handle: 0xe8bae3c0
Wed Jan 31 09:27:06 2024 daemon.notice netifd: modem_0001 (18002): [01-31_09:27:05:458] requestQueryDataCall IPv4ConnectionStatus: DISCONNECTED
Wed Jan 31 09:27:06 2024 daemon.notice netifd: modem_0001 (18002): [01-31_09:27:05:460] requestQueryDataCall IPv6ConnectionStatus: DISCONNECTED
Wed Jan 31 09:27:06 2024 daemon.notice netifd: modem_0001 (18002): [01-31_09:27:06:461] requestRegistrationState2 MCC: 222, MNC: 88, PS: Attached, DataCap: 5G_NSA
Wed Jan 31 09:27:06 2024 daemon.notice netifd: modem_0001 (18002): [01-31_09:27:06:475] requestSetupDataCall WdsConnectionIPv4Handle: 0xe8b9ebc0
Wed Jan 31 09:27:13 2024 daemon.info dnsmasq-dhcp[20087]: DHCPREQUEST(br-lan) 151.59.109.151 00:02:c9:de:40:6c
Wed Jan 31 09:27:13 2024 daemon.info dnsmasq-dhcp[20087]: DHCPACK(br-lan) 151.59.109.151 00:02:c9:de:40:6c edge1-it
Wed Jan 31 09:27:35 2024 daemon.info dnsmasq-dhcp[20087]: DHCPREQUEST(br-lan) 151.59.109.151 00:02:c9:de:40:6c
Wed Jan 31 09:27:35 2024 daemon.info dnsmasq-dhcp[20087]: DHCPACK(br-lan) 151.59.109.151 00:02:c9:de:40:6c edge1-it
Wed Jan 31 09:27:40 2024 user.notice mwan3[12801]: Execute ifdown event on interface modem_0001 (rmnet_mhi0)
Wed Jan 31 09:27:40 2024 user.notice firewall: Reloading firewall due to ifdown of modem_0001 (rmnet_mhi0)
Wed Jan 31 09:27:40 2024 user.notice root: modem ip different, now regain ip ...
Wed Jan 31 09:27:41 2024 daemon.info avahi-daemon[5500]: Withdrawing address record for 151.59.109.152 on br-lan.
Wed Jan 31 09:27:41 2024 daemon.info avahi-daemon[5500]: Leaving mDNS multicast group on interface br-lan.IPv4 with address 151.59.109.152.
Wed Jan 31 09:27:41 2024 daemon.info avahi-daemon[5500]: Interface br-lan.IPv4 no longer relevant for mDNS.
Wed Jan 31 09:27:41 2024 daemon.info avahi-daemon[5500]: Joining mDNS multicast group on interface br-lan.IPv4 with address 192.168.8.1.
Wed Jan 31 09:27:41 2024 daemon.info avahi-daemon[5500]: New relevant interface br-lan.IPv4 for mDNS.
Wed Jan 31 09:27:41 2024 daemon.info avahi-daemon[5500]: Registering new address record for 192.168.8.1 on br-lan.IPv4.
Wed Jan 31 09:27:41 2024 kern.info kernel: [172892.719603] mtk_soc_eth 15100000.ethernet eth1: Link is Down
Wed Jan 31 09:27:41 2024 kern.info kernel: [172892.725726] br-lan: port 1(eth1) entered disabled state
Wed Jan 31 09:27:41 2024 daemon.notice netifd: Network device 'eth1' link is down
Wed Jan 31 09:27:41 2024 daemon.notice netifd: bridge 'br-lan' link is down
Wed Jan 31 09:27:41 2024 daemon.notice netifd: Interface 'lan' has link connectivity loss
Wed Jan 31 09:27:41 2024 daemon.info dnsmasq[20087]: exiting on receipt of SIGTERM
Wed Jan 31 09:27:41 2024 daemon.info dnsmasq[13623]: Connected to system UBus
Wed Jan 31 09:27:41 2024 daemon.info dnsmasq[13623]: started, version 2.85 cachesize 150
Wed Jan 31 09:27:41 2024 daemon.info dnsmasq[13623]: DNS service limited to local subnets
Wed Jan 31 09:27:41 2024 daemon.info dnsmasq[13623]: compile time options: IPv6 GNU-getopt no-DBus UBus no-i18n no-IDN DHCP DHCPv6 no-Lua TFTP conntrack ipset auth cryptohash DNSSEC no-ID loop-detect inotify dumpfile
Wed Jan 31 09:27:41 2024 daemon.info dnsmasq[13623]: UBus support enabled: connected to system bus
Wed Jan 31 09:27:41 2024 daemon.info dnsmasq-dhcp[13623]: DHCP, IP range 192.168.8.100 -- 192.168.8.249, lease time 12h
Wed Jan 31 09:27:41 2024 daemon.info dnsmasq[13623]: using only locally-known addresses for domain test
Wed Jan 31 09:27:41 2024 daemon.info dnsmasq[13623]: using only locally-known addresses for domain onion
Wed Jan 31 09:27:41 2024 daemon.info dnsmasq[13623]: using only locally-known addresses for domain localhost
Wed Jan 31 09:27:41 2024 daemon.info dnsmasq[13623]: using only locally-known addresses for domain local
Wed Jan 31 09:27:41 2024 daemon.info dnsmasq[13623]: using only locally-known addresses for domain invalid
Wed Jan 31 09:27:41 2024 daemon.info dnsmasq[13623]: using only locally-known addresses for domain bind
Wed Jan 31 09:27:41 2024 daemon.info dnsmasq[13623]: using only locally-known addresses for domain lan
Wed Jan 31 09:27:41 2024 daemon.info dnsmasq[13623]: reading /tmp/resolv.conf.d/resolv.conf.auto
Wed Jan 31 09:27:41 2024 daemon.info dnsmasq[13623]: using only locally-known addresses for domain test
Wed Jan 31 09:27:41 2024 daemon.info dnsmasq[13623]: using only locally-known addresses for domain onion
Wed Jan 31 09:27:41 2024 daemon.info dnsmasq[13623]: using only locally-known addresses for domain localhost
Wed Jan 31 09:27:41 2024 daemon.info dnsmasq[13623]: using only locally-known addresses for domain local
Wed Jan 31 09:27:41 2024 daemon.info dnsmasq[13623]: using only locally-known addresses for domain invalid
Wed Jan 31 09:27:41 2024 daemon.info dnsmasq[13623]: using only locally-known addresses for domain bind
Wed Jan 31 09:27:41 2024 daemon.info dnsmasq[13623]: using only locally-known addresses for domain lan
Wed Jan 31 09:27:41 2024 daemon.info dnsmasq[13623]: using nameserver 151.5.216.25#53
Wed Jan 31 09:27:41 2024 daemon.info dnsmasq[13623]: using nameserver 151.5.216.225#53
Wed Jan 31 09:27:41 2024 daemon.info dnsmasq[13623]: read /etc/hosts - 4 addresses
Wed Jan 31 09:27:41 2024 daemon.info dnsmasq[13623]: read /tmp/hosts/dhcp.cfg01411c - 3 addresses
Wed Jan 31 09:27:41 2024 daemon.info dnsmasq-dhcp[13623]: read /etc/ethers - 0 addresses
Wed Jan 31 09:27:42 2024 kern.info kernel: [172893.748244] MediaTek MT7981 PHY mdio-bus:00: TX-VCM SW cal result: 0x1
Wed Jan 31 09:27:42 2024 kern.info kernel: [172893.755717] mtk_soc_eth 15100000.ethernet eth1: PHY [mdio-bus:00] driver [MediaTek MT7981 PHY]
Wed Jan 31 09:27:42 2024 kern.info kernel: [172893.764426] mtk_soc_eth 15100000.ethernet eth1: configuring for phy/gmii link mode
Wed Jan 31 09:27:42 2024 daemon.info dnsmasq[13623]: exiting on receipt of SIGTERM
Wed Jan 31 09:27:42 2024 daemon.info dnsmasq[13823]: Connected to system UBus
Wed Jan 31 09:27:42 2024 daemon.info dnsmasq[13823]: started, version 2.85 cachesize 150
Wed Jan 31 09:27:42 2024 daemon.info dnsmasq[13823]: DNS service limited to local subnets
Wed Jan 31 09:27:42 2024 daemon.info dnsmasq[13823]: compile time options: IPv6 GNU-getopt no-DBus UBus no-i18n no-IDN DHCP DHCPv6 no-Lua TFTP conntrack ipset auth cryptohash DNSSEC no-ID loop-detect inotify dumpfile
Wed Jan 31 09:27:42 2024 daemon.info dnsmasq[13823]: UBus support enabled: connected to system bus
Wed Jan 31 09:27:42 2024 daemon.info dnsmasq-dhcp[13823]: DHCP, IP range 192.168.8.100 -- 192.168.8.249, lease time 12h
Wed Jan 31 09:27:42 2024 daemon.info dnsmasq[13823]: using only locally-known addresses for domain test
Wed Jan 31 09:27:42 2024 daemon.info dnsmasq[13823]: using only locally-known addresses for domain onion
Wed Jan 31 09:27:42 2024 daemon.info dnsmasq[13823]: using only locally-known addresses for domain localhost
Wed Jan 31 09:27:42 2024 daemon.info dnsmasq[13823]: using only locally-known addresses for domain local
Wed Jan 31 09:27:42 2024 daemon.info dnsmasq[13823]: using only locally-known addresses for domain invalid
Wed Jan 31 09:27:42 2024 daemon.info dnsmasq[13823]: using only locally-known addresses for domain bind
Wed Jan 31 09:27:42 2024 daemon.info dnsmasq[13823]: using only locally-known addresses for domain lan
Wed Jan 31 09:27:42 2024 daemon.info dnsmasq[13823]: reading /tmp/resolv.conf.d/resolv.conf.auto
Wed Jan 31 09:27:42 2024 daemon.info dnsmasq[13823]: using only locally-known addresses for domain test
Wed Jan 31 09:27:42 2024 daemon.info dnsmasq[13823]: using only locally-known addresses for domain onion
Wed Jan 31 09:27:42 2024 daemon.info dnsmasq[13823]: using only locally-known addresses for domain localhost
Wed Jan 31 09:27:42 2024 daemon.info dnsmasq[13823]: using only locally-known addresses for domain local
Wed Jan 31 09:27:42 2024 daemon.info dnsmasq[13823]: using only locally-known addresses for domain invalid
Wed Jan 31 09:27:42 2024 daemon.info dnsmasq[13823]: using only locally-known addresses for domain bind
Wed Jan 31 09:27:42 2024 daemon.info dnsmasq[13823]: using only locally-known addresses for domain lan
Wed Jan 31 09:27:42 2024 daemon.info dnsmasq[13823]: using nameserver 151.5.216.25#53
Wed Jan 31 09:27:42 2024 daemon.info dnsmasq[13823]: using nameserver 151.5.216.225#53
Wed Jan 31 09:27:42 2024 daemon.info dnsmasq[13823]: read /etc/hosts - 4 addresses
Wed Jan 31 09:27:42 2024 daemon.info dnsmasq[13823]: read /tmp/hosts/dhcp.cfg01411c - 3 addresses
Wed Jan 31 09:27:42 2024 daemon.info dnsmasq-dhcp[13823]: read /etc/ethers - 0 addresses
Wed Jan 31 09:27:42 2024 user.info mwan3track[18474]: Detect ifdown event on interface modem_0001 (rmnet_mhi0)
Wed Jan 31 09:27:45 2024 kern.info kernel: [172896.828226] mtk_soc_eth 15100000.ethernet eth1: Link is Up - 1Gbps/Full - flow control off
Wed Jan 31 09:27:45 2024 kern.info kernel: [172896.836634] br-lan: port 1(eth1) entered blocking state
Wed Jan 31 09:27:45 2024 kern.info kernel: [172896.841978] br-lan: port 1(eth1) entered forwarding state
Wed Jan 31 09:27:45 2024 daemon.notice netifd: Network device 'eth1' link is up
Wed Jan 31 09:27:45 2024 daemon.notice netifd: bridge 'br-lan' link is up
Wed Jan 31 09:27:45 2024 daemon.notice netifd: Interface 'lan' has link connectivity
Wed Jan 31 09:27:47 2024 user.notice mwan3track[18474]: Interface modem_0001 (rmnet_mhi0) is offline
Wed Jan 31 09:27:52 2024 daemon.notice netifd: modem_0001_4 (18709): udhcpc: sending renew to 151.59.109.152
Wed Jan 31 09:27:52 2024 daemon.notice netifd: modem_0001_4 (18709): udhcpc: bind(UDP): Address not available
Wed Jan 31 09:27:52 2024 daemon.notice netifd: modem_0001_4 (18709): udhcpc: sending renew to 0.0.0.0
Wed Jan 31 09:28:15 2024 user.notice root: modem ip different, now regain ip ...
Wed Jan 31 09:28:45 2024 user.notice root: modem ip different, now regain ip ...
Wed Jan 31 09:29:15 2024 user.notice root: modem ip different, now regain ip ...
Wed Jan 31 09:29:45 2024 user.notice root: modem ip different, now regain ip ...
So the LAN is back on 192.168.8.0/24, but the modem interface is unable to obtain a new IP and thus the router won’t recover from this situation.
This is how udhcpc was running:
udhcpc -p/var/run/udhcpc-rmnet_mhi0.pid -s/lib/netifd/dhcp.script -f -t0 -irmnet_mhi0 -x
hostname:GL-X3000-C-R-O121
I can’t figure out why it hit the ‘Address not available’ error. Maybe because rmnet_mhi0 was not yet up when udhcpc was started?
I then tried manually to kill the udhcpc process and everything got stuck (I had to reboot the X3000).
I guess that udhcpc was then able to obtain an IP and the network stack reacted to that, but due to the inconsistent state it did not recover properly.
I hope this is helpful to further debug the
If this situation occurs again, please help to execute the following instructions：
ifconfig
gl_modem -B 0001:01:00.0 AT AT+CGPADDR
1 Like
Hi @lizh , here is the requested output + some other commands I executed.
It seems the problem happens reliably the second time my ISP changes the IP. The first time it goes through properly.
Let me know if you need any extra data. Thanks!
root@GL-X3000:~# ifconfig
br-lan Link encap:Ethernet HWaddr 94:83:C4:A0:09:0D
inet addr:151.59.136.33 Bcast:151.59.136.63 Mask:25
5.255.255.192
inet6 addr: fe80::9683:c4ff:fea0:90d/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:10249389 errors:0 dropped:83362 overruns:0
frame:0
TX packets:20207551 errors:0 dropped:0 overruns:0 car
rier:0
collisions:0 txqueuelen:1000
RX bytes:5647696680 (5.2 GiB) TX bytes:21613813133 (
20.1 GiB)
eth0 Link encap:Ethernet HWaddr 94:83:C4:A0:09:0C
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Interrupt:76
eth1 Link encap:Ethernet HWaddr 94:83:C4:A0:09:0D
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:10417984 errors:0 dropped:0 overruns:0 fra
me:0
TX packets:20208999 errors:0 dropped:0 overruns:0 car
rier:0
collisions:0 txqueuelen:1000
RX bytes:5801725931 (5.4 GiB) TX bytes:21698872221 (
20.2 GiB)
Interrupt:76
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:1024825 errors:0 dropped:0 overruns:0 fram
e:0
TX packets:1024825 errors:0 dropped:0 overruns:0 carr
ier:0
collisions:0 txqueuelen:1000
RX bytes:85764286 (81.7 MiB) TX bytes:85764286 (81.7
MiB)
rmnet_mhi0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00
-00-00-00-00-00-00-00
inet addr:192.168.8.245 Mask:255.255.255.0
inet6 addr: fe80::8369:c231:8a4e:2ef6/64 Scope:Link
UP RUNNING NOARP MTU:1500 Metric:1
RX packets:4797112 errors:0 dropped:0 overruns:0 fram
e:0
TX packets:10184004 errors:0 dropped:0 overruns:0 car
rier:0
collisions:0 txqueuelen:1000
RX bytes:21494350112 (20.0 GiB) TX bytes:5635367038
(5.2 GiB)
root@GL-X3000:~# gl_modem -B 0001:01:00.0 AT AT+CGPADDR
+CGPADDR: 1,"151.59.136.32","42.2.176.33.0.0.0.61.157.140.106.3
9.217.148.115.152"
+CGPADDR: 2,"0.0.0.0","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0"
+CGPADDR: 3,"0.0.0.0","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0"
OK
root@GL-X3000:~#
root@GL-X3000:~# ip r
151.59.136.32 dev br-lan proto kernel scope link
root@GL-X3000:~# ip l
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNK
NOWN mode DEFAULT group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_
codel state DOWN mode DEFAULT group default qlen 1000
link/ether 94:83:c4:a0:09:0c brd ff:ff:ff:ff:ff:ff
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_co
del master br-lan state UP mode DEFAULT group default qlen 1000
link/ether 94:83:c4:a0:09:0d brd ff:ff:ff:ff:ff:ff
4: ra0: <BROADCAST,MULTICAST> mtu 1500 qdisc fq_codel state DOW
N mode DEFAULT group default qlen 1000
link/ether 94:83:c4:a0:09:0e brd ff:ff:ff:ff:ff:ff
5: rmnet_mhi0: <NOARP,UP,LOWER_UP> mtu 1500 qdisc fq_codel stat
e UP mode DEFAULT group default qlen 1000
link/none
6: br-lan: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noq
ueue state UP mode DEFAULT group default qlen 1000
link/ether 94:83:c4:a0:09:0d brd ff:ff:ff:ff:ff:ff
7: ra1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mo
de DEFAULT group default qlen 1000
link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
8: rax0: <BROADCAST,MULTICAST> mtu 1500 qdisc fq_codel state DO
WN mode DEFAULT group default qlen 1000
link/ether 94:83:c4:a0:09:0f brd ff:ff:ff:ff:ff:ff
9: rax1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN m
ode DEFAULT group default qlen 1000
link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
10: apcli0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOW
N mode DEFAULT group default qlen 1000
link/ether 92:83:c4:a0:09:0e brd ff:ff:ff:ff:ff:ff
11: apclix0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DO
WN mode DEFAULT group default qlen 1000
link/ether 9e:83:c4:a0:09:0e brd ff:ff:ff:ff:ff:ff
root@GL-X3000:~# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNK
NOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_
codel state DOWN group default qlen 1000
link/ether 94:83:c4:a0:09:0c brd ff:ff:ff:ff:ff:ff
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_co
del master br-lan state UP group default qlen 1000
link/ether 94:83:c4:a0:09:0d brd ff:ff:ff:ff:ff:ff
4: ra0: <BROADCAST,MULTICAST> mtu 1500 qdisc fq_codel state DOW
N group default qlen 1000
link/ether 94:83:c4:a0:09:0e brd ff:ff:ff:ff:ff:ff
5: rmnet_mhi0: <NOARP,UP,LOWER_UP> mtu 1500 qdisc fq_codel stat
e UP group default qlen 1000
link/none
inet 192.168.8.245/24 scope global rmnet_mhi0
valid_lft forever preferred_lft forever
inet 151.59.136.32/26 brd 151.59.136.63 scope global rmnet_
mhi0
valid_lft forever preferred_lft forever
inet6 fe80::8369:c231:8a4e:2ef6/64 scope link stable-privac
y
valid_lft forever preferred_lft forever
6: br-lan: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noq
ueue state UP group default qlen 1000
link/ether 94:83:c4:a0:09:0d brd ff:ff:ff:ff:ff:ff
inet 151.59.136.33/26 brd 151.59.136.63 scope global br-lan
valid_lft forever preferred_lft forever
inet6 fe80::9683:c4ff:fea0:90d/64 scope link
valid_lft forever preferred_lft forever
7: ra1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN gr
oup default qlen 1000
link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
8: rax0: <BROADCAST,MULTICAST> mtu 1500 qdisc fq_codel state DO
WN group default qlen 1000
link/ether 94:83:c4:a0:09:0f brd ff:ff:ff:ff:ff:ff
9: rax1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN g
roup default qlen 1000
link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
10: apcli0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOW
N group default qlen 1000
link/ether 92:83:c4:a0:09:0e brd ff:ff:ff:ff:ff:ff
11: apclix0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DO
WN group default qlen 1000
link/ether 9e:83:c4:a0:09:0e brd ff:ff:ff:ff:ff:ff
root@GL-X3000:~#
in my case i was using a SIM card as the incoming connection(WAN - public facing IP).
The SIM APN has to be set manually before the connection can be initiated.
I think that the modem(SIM) doesn’t search for available/possible subdomains to automatically connect to.
so in other words:
The SIM automatically connects to ISP APN “Second-level domain”(a1.net.) and does not check(resolve) to see if there are any available subdomains(fixedip.a1.net.).
after manually setting the APN inclusive of the subdomain it worked.
my Problem now is that as soon as I restart the device it looses the manually configured APN?
Only when I restart the router can I access the router GUI via internal address of 192.168.8.1, but the i loose the APN config.
I had to disable “Auto SIM Switching” as it tries to initiate a connection on the second card as soon as the first one fails(this causes a loop of connect attempts and disconnects)