Travelmate support thread

[slh]

It is a hardware restriction, a hard one. And yes, it also applies to the WLAN chipsets used in your garden variety smartphone.

Yes, you can cheat around it -that's exactly what travelmate is doing- but that doesn't change the underlying limitations.

Yes, an android device with with >4x 2 GHz cores, 4++ GB RAM and >32 GB eMMC flash can put more lipstick on that pig than OpenWrt, which still needs to keep working on a 400 MHz single core mips 24Kc SOC, 128 MB RAM and 16 MB spi-nor flash. News at Eleven.

It's fine if you aren't happy with OpenWrt (or travelmate), your options include not using it or helping to improve it.
Conceptually, OpenWrt expects/ requires ethernet access for basic configurations, strictly that could (technically) be 'improved', but there are many corner cases making this not as easy across the board of all supported devices, to make this not an attractive choice for the developers, after all OpenWrt developers are not designing the hardware and have to make do with what the users have sourced elsewhere. If you don't have ethernet connectivity (not every day, but at least whenever you need it), OpenWrt isn't the right choice for you.

[pwildi]

Sorry to bring up this old issue. But I ran into a related issue. I renamed my radios from radio0/1 to radio2g/radio5g so I can easy tell which one is what band.

That broke the ACL. I locally changed it to :"/etc/init.d/travelmate scan radio*" : [ "exec" ]

Any reason the ACL has to be that strict on naming?

[Falco]

Hi,

I installed TravelMate on a GL-MT3000 and it's working fine.

However, on the Travelmate overview page, I do not see information about the active connection and also on the Wireless stations the active connection is not blue.

I used to have this available on my TR3000, and it's rather convenient.

Is there a reason why these things are not available on my GL-MT3000, or is there a way to fix it?

[dibdot]

@Falco

Is there a reason why these things are not available on my GL-MT3000, or is there a way to fix it?

Provide your travelmate config and the output of:

/etc/init.d/travelmate enabled; echo $?
/etc/init.d/travelmate status
cat /etc/openwrt_release

Thanks!

[Falco]

Thanks for your help!

Not sure how to share the config, but it's a standard install?

root@GL-MT3000:~# /etc/init.d/travelmate enabled; echo $?
1
root@GL-MT3000:~# /etc/init.d/travelmate status
::: no travelmate runtime information available
root@GL-MT3000:~# cat /etc/openwrt_release
DISTRIB_ID='OpenWrt'
DISTRIB_RELEASE='25.12.2'
DISTRIB_REVISION='r32802-f505120278'
DISTRIB_TARGET='mediatek/filogic'
DISTRIB_ARCH='aarch64_cortex-a53'
DISTRIB_DESCRIPTION='OpenWrt 25.12.2 r32802-f505120278'
DISTRIB_TAINTS=''
root@GL-MT3000:~# 

[dibdot]

The travelmate service is disabled in your setup, just enable it:

/etc/init.d/travelmate enable

[Falco]

By the way, another thing I noticed is that Travelmate was not activated after running the interface wizard. I needed to activate Travelmate first and then run the interface wizard, otherwise the needed interfaces (trm_wwan, etc) were not created.

[Falco]

Check, with this command I know see the info and also the active connection is blue again.

[dibdot]

FYI, in master and 25.12.-branch is a new travelmate release. It mainly contains numerous backend fixes (adapted to the Adblock/BanIP codebase) as well as a few new features; see ...

travelmate: release 2.4.5-1