Very slow LTE

[itimo01]

Do you use a vpn or a proxy?

Here Google Chrome uses proxy settings, and Firefox does not.
But I wonder why this matters for login to the MikroTik Web GUI.

As long as you don’t have an exception for the Address it will try accessing the MT WebGUI through the proxy.
Which I guess the proxy doesn’t like to do.

[mutluit]

@mutluit

ii firefox-esr 115.14.0esr-1~deb11u1 amd64 Mozilla Firefox web browser - Extended Support Release (ESR)

I just tried it on an old(er) ESR Version and yes the menu doesn’t appear.

Not sure if the current ESR (115.20) fixes that. Probably not.

Thanks for confirmation.
I’m updating my software from the Debian stable repository.
So, if they don’t have a version that works with the said ROS version, then I cannot do anything else.
But I would have guessed that such a big company like MikroTik would have some inhouse test people who test the software with all the major webbrowser versions.
A good part-time job for students for example, IMO.

[itimo01]

@mutluit

But I would have guessed that such a big company like MikroTik would have some inhouse test people who test the software with all the major webbrowser versions.

Yes, but 115.14 has been out of date for a long time (common Debian LTS thing, but we’re not starting this discussion here on MT Forums )
115.15 has been released in September 2024.

And the current ESR Version 128 works great
ESR 115.20 doesn’t work, but support for it will end in MARCH 2025

[holvoetn]

Plenty of sites not working with Internet Explorer anymore.
Why would it be different with other old browser versions ?

[KiwiBloke]

Why not just use Winbox? No need for a browser of any type. v3 works fine using wine in Linux and v4 works natively in Linux.

[holvoetn]

Plus added benefit of MAC access when IP is failing.

[mutluit]

I need to create a wireless cellular (ie. LTE) solution with these requirements:

1. Wireless-only solution (ie. 4G/LTE is sufficient for my needs).
2. Use of 2 (or even 3) wireless WAN uplinks to the Internet (ie. 2 or 3 SIMs).
3. The main traffic is routed depending on time of the day (for example SIM1 for the 1st 8 hours of the day, SIM2 the next 8 hours, and SIM3 the final 8 hours)
4. All SIMs always on (for redundancy).
5. The wireless components need literally to be mobile (ie. not a fixed antenna above the roof or so).
6. Distribution (routing) of the traffic is done locally in LAN via simple “metric” settings for multiple routes
   (or by using individual route tables as is possible in advanced routing under Linux)

For this I of course need multiple LTE routers (or a router that can house more than 1 SIM cards).
I recently tried it with LTE USB sticks, but had no luck with the sticks as they did not work (seems they are SIMlocked for Indonesia as “Telkomsel” is written on them).
This is a home/business use-case, and I’m after a budget solution.
So, my wireless adventure continues…

I now have made this working with 3 LTE routers (1 “MT hAP ax lite LTE6” and 2 of the said cheap CPE LTE4 routers).
As said, the hAP did cause some speed problems, but if one finds a “sweet spot” in the room then that router becomes usable also w/o extending it with an external LTE antenna…
If anybody interested, I can post my Linux config (entry in /etc/network/interfaces and a bash script gateway-select.sh that acccepts the params R1, R2, R3; this of course can also be called via cron job…)
Each PC can chose itself the (wireless) WAN gateway it wants to use (prioritization via “metric” settings) .
Ie. this is a simple solution for only a few PCs in LAN, not for a company or so.