Hi folks,
I love my GL-X3000, but ran into an unexpected problem with its cellular connection - likely due to the speed of the router relative to the network.
Given that my GL-X3000 does very well in my car, it felt logical that it should work in a (low-flying) aircraft as well. The aircraft is equipped with an external antenna (a RAMI AV-289) that feeds into the main radio. The performance of this setup is superb while on the ground, but when airborne the modems start to trip in relatively quick succession - too quick to have meaningful service between reconnects as it would take fairly long for a modem to restart. I tried using two SIMs and have the router switch automatically, but that did not help the situation.
From what I understand from the logs a modem would trip (not sure over what) and then encounters an issue trying to come up again (which one, I have no idea). I have attached a excerpt from the system.log at the end of this message.
The router’s firmware is current (0405release1) and the power supply suffices on the ground and in my car (I am using an 100W Anker power bank and a 12V USB-C trigger). The aircraft is fairly slow, for an aircraft. I can about track a fast moving car on a highway here (in Germany). From experience I can say that cell coverage in these type of aircraft is not an issue with speed per se. My regular cell phone quite often works just fine. However, due to the dampening factor of the hull (it is made out of carbon-fiber reinforced polymers) coverage is rather limited - hence the need for this setup.
Going through old posts I found a similar issue that T-Mobile subscribers had last year. However, that issue has been fixed already from what I understand.
Can anyone point me to a solution or even just a meaningful way to debug this?
------ system.log --------
Sun Jan 28 14:42:00 2024 daemon.notice netifd: modem_0001 (8727): [01-28_14:41:21:254] requestRegistrationState2 MCC: 204, MNC: 8, PS: Detached, DataCap: UNKNOW
Sun Jan 28 14:42:00 2024 daemon.notice netifd: modem_0001 (8727): [01-28_14:41:28:926] requestRegistrationState2 MCC: 262, MNC: 3, PS: Detached, DataCap: UNKNOW
Sun Jan 28 14:42:00 2024 daemon.notice netifd: modem_0001 (8727): [01-28_14:41:42:846] requestRegistrationState2 MCC: 262, MNC: 1, PS: Detached, DataCap: UNKNOW
Sun Jan 28 14:42:00 2024 daemon.notice netifd: modem_0001 (8727): [01-28_14:41:55:616] requestRegistrationState2 MCC: 0, MNC: 0, PS: Detached, DataCap: UNKNOW
Sun Jan 28 14:42:00 2024 daemon.notice netifd: modem_0001 (8727): [01-28_14:41:55:804] requestRegistrationState2 MCC: 0, MNC: 0, PS: Detached, DataCap: UNKNOW
Sun Jan 28 14:42:00 2024 daemon.notice netifd: modem_0001 (8727): [01-28_14:41:56:396] requestRegistrationState2 MCC: 262, MNC: 1, PS: Detached, DataCap: UNKNOW
Sun Jan 28 14:42:00 2024 daemon.notice netifd: modem_0001 (8727): [01-28_14:41:56:400] requestRegistrationState2 MCC: 262, MNC: 1, PS: Detached, DataCap: UNKNOW
Sun Jan 28 14:42:00 2024 daemon.notice netifd: modem_0001 (8727): [01-28_14:42:00:432] QmiWwanThread exit
Sun Jan 28 14:42:00 2024 daemon.notice netifd: modem_0001 (8727): [01-28_14:42:00:433] qmi_main exit
Sun Jan 28 14:42:00 2024 daemon.notice netifd: Interface ‘modem_0001’ is now down
Sun Jan 28 14:42:00 2024 user.notice mwan3[14759]: Execute ifdown event on interface modem_0001 (unknown)
Sun Jan 28 14:42:00 2024 user.info mwan3track[9090]: Detect ifdown event on interface modem_0001 (rmnet_mhi0)
Sun Jan 28 14:42:02 2024 daemon.notice netifd: Interface ‘modem_0001’ is setting up now
Sun Jan 28 14:42:05 2024 daemon.notice netifd: modem_0001 (15164):
Sun Jan 28 14:42:05 2024 daemon.notice netifd: modem_0001 (15164):
Sun Jan 28 14:42:05 2024 daemon.notice netifd: modem_0001 (15164): OK
Sun Jan 28 14:42:05 2024 daemon.notice netifd: modem_0001 (15164):
Sun Jan 28 14:42:05 2024 daemon.notice netifd: modem_0001 (15164):
Sun Jan 28 14:42:05 2024 daemon.notice netifd: modem_0001 (15164): OK
Sun Jan 28 14:42:05 2024 daemon.notice netifd: modem_0001 (15164):
Sun Jan 28 14:42:05 2024 daemon.notice netifd: modem_0001 (15164):
Sun Jan 28 14:42:05 2024 daemon.notice netifd: modem_0001 (15164): ERROR
Sun Jan 28 14:42:05 2024 daemon.notice netifd: modem_0001 (15164): Failed to parse message data
Sun Jan 28 14:42:05 2024 user.notice mwan3track[9090]: Interface modem_0001 (rmnet_mhi0) is offline