I purchased the Spitz x3000 AX 5g NR last week to replace a T-Mobile Home Internet Gateway in hopes of a stronger, better connection. The gateway being replaced is the Arcadyan KVD21. Lack of configuration and buffer bloat being the main reasoning.
The Spitz consistently has worse latency than the carrier gateway. Running a ping from cmd to 1.1.1.1 would yield 38-55ms on average with the KVD21. The Spitz is consistently 55-80 with an occasional 38-55 in there. Very rare.
The IMEI is that of the carrier Gateway. I have tried upgrading and downgrading both GL firmware and modem firmware, setting DNS, turned on/off hard/software acceleration, packet steering.. I have checked I am using the correct T Mobile APN and MBB. I have tried every possible LTE/NR5g/SA combo possible the KVD21 would be using. I am at a loss as to why my device is basically double the latency. I love the functionality of the Spitz but this has been a nightmare trying to get working correctly.
In Luci interfaces shows rmnet_mhi0. Should this be using WWAN?
Also ran ifconfig and show my br-lan has a lot of drops.
RX packets:72666 errors:0 dropped:4571 overruns:0 frame:0
Beginning to feel this thing shipped with a wonky configuration from the start.
Any help would be amazing and greatly appreciated. Thanks!
PS: I am currently on firmware version 4.0, 0412release3, 2024-09-25 04:14:18 with
modem firmware RM520NGLAAR03A04M4G, 2024-08-12 16:27:10.
PSS: This is with all traffic. Not just a cmd ping to cloudflare. Gaming has taken a terrible hit because of this, which was the soul purpose of purchasing the device.
I consistently get 20-30ms ping with this device to an Ookla Speedtest server I test with hourly in pass through mode, and utilizing band preferences to disable 5GSA. I'm using a TMHI SIM with cloned IMEI from the Sercomm G4SE. I'm using fbb.home as my APN and set the MTU to 1420. I'm connecting to B66/N41 which are close to me and my speeds average 250-400 down and 15-40 up.
Very nice. Those are nice numbers. How is your loaded latency?
I'm around a mile from my tower. Signals are great. I just wish I could figure out where my additional latency is coming from.
Thanks for the reply. I have covered everything in that thread. Connecting to either apn has not been an issue and the latency is the same with both. Mine was defaulted to the TMO MBB and connected fine. Tried the Generic's with no improvement. Despite having AutoSel off, it would eventually change back to Commercial-TMO.
I have now updated to the posted beta firmware and the R03A04 modem firmware.
Still same behavior. Consistently higher latency in both LTE+NR5g(66+41) and SA5g(41+41 and 41+25)
Vanilla OWRT has snapshot-firmwares for the X3000. So means any next stable (major) release will very likely have firmwares for the X3000 (and XE3000).
Snapshot-firmwares are however really base-firmwares, so you need to install luci and such very wanted packages yourself (from SSH).
It’s fairly straight forward I’d say. The guide is pretty well written. Vanilla is indeed vanilla but seems to just run better. I have not found details as for a simple way to execute AT commands yet. Nor band lock or verify CA. This is actually just as much of a headache for someone just wanting it to work.
You are conflating router firmware and modem firmware I think. They are two separate things. Downgrading or upgrading router firmware will not upgrade or downgrade modem firmware.
0412_3 did not fix the problem and modem firmware R1A08 doesn't CA correctly..
What is this in my logs?
Sat Nov 2 01:03:01 2024 daemon.notice netifd: modem_0001 (20807): Device only supports raw-ip mode but is missing this required driver attribute: /sys/class/net/rmnet_mhi0/qmi/raw_ip
Sat Nov 2 01:07:57 2024 daemon.notice netifd: modem_0001 (3220): ERROR
Sat Nov 2 01:10:32 2024 daemon.err modprobe: failed to find a module named act_ipt
2024/11/02 09:17:41 [error] 6420#0: *12406 open() "/www/luci-static/resources/protocol/3g.js" failed (2: No such file or directory), client: 192.168.8.155, server: , request: "GET /luci-static/resources/protocol/3g.js?v=git-22.245.77575-63bfee6 HTTP/1.1", host: "192.168.8.1", referrer: "http://192.168.8.1/cgi-bin/luci/"
2024/11/02 09:17:41 [error] 6421#0: *12343 open() "/www/luci-static/resources/protocol/directip.js" failed (2: No such file or directory), client: 192.168.8.155, server: , request: "GET /luci-static/resources/protocol/directip.js?v=git-22.245.77575-63bfee6 HTTP/1.1", host: "192.168.8.1", referrer: "http://192.168.8.1/cgi-bin/luci/"
2024/11/02 09:17:41 [error] 6421#0: *12343 open() "/www/luci-static/resources/protocol/relay.js" failed (2: No such file or directory), client: 192.168.8.155, server: , request: "GET /luci-static/resources/protocol/relay.js?v=git-22.245.77575-63bfee6 HTTP/1.1", host: "192.168.8.1", referrer: "http://192.168.8.1/cgi-bin/luci/"
It seems the Web UI Luci request the http server via the API, and the log prints the API error, but have not these js scripts. May I know it is the GL firmware or vanilla OpenWRT?
Regarding the latency, may try testing the plugin 'SQM QOS' to probably optimize the latency time.
Stock firmware. QoS did not help. This device has just not been right. And the whole flash this flash that back and forth as the community has recommended so fast and often I fear for the worst even more now.
Please don't worry about syslog errors, because these belong to the Luci interface, not GL WEBUI. All functions of the device are mainly based on GL WEBUI.
Regarding the issue of latency, I have discussed it with the modem team, if the latency is less than 200ms, it is within the acceptable with normal range.
If two KVD21 or two X3000 are put together, there may be a little difference.
Because of differences in antenna direction, network environment, base station data packet processing, etc., differences within 50ms are normal.