Travelmate support thread


Never seen such error. Please provide the output of

/etc/init.d/travelmate status

and your travelmate config. Thanks!


Reported problems seems to be unrelated to travelmate. Why do you use this unknown fork? The GL-AR750S is officially supported by OpenWrt (NOR-flash).


I got it to work eventually, all is well again!

I'm using their fork because (apparently...) I'm supposed to then be able to create Nand firmware, which as I understand it is better because then I'm also updating kernel drivers. Still learning... Little info on this device.


Dear all, I am using travelmate (newest version) on an GL-MT300A. I would like to change my Mac-address. When travelmate is not running I can do so using macchanger but as soon as I turn travelmate back on the Mac-address changes back to its original state.

Can you give me a clue how to proceed? (Actually what I want to achieve is to use a random Mac-address everytime the device starts - that is the ultimate goal.



I installed travelmate (both 1.2.2 and 1.3.1) on a GL-AR750 on 18.06.1, and it refused to connect to any of the wireless networks I specified. After debugging the code, I found that the wifi-iface section names (in /etc/config/wireless) cannot contain underscores (_).

I had added wifi-iface sections manually, and copying the existing config, I had specified section names like:

config wifi-iface 'trm_wwan_home'
config wifi-iface 'trm_wwan_work'

Looking at /usr/bin/, in f_main(), section names and radios are retrieved from the keys of trm_stalist:


If the section name contains underscores, then config would hold only the first part of the section name (before the first underscore).

I believe changing the config line to


(removing the shortest matching pattern instead of the longest) should work, but I haven't tested it.

(I believe radio device names can also contain underscores, but I haven't tested this either.)

It would be great if the code can be modified to accommodate underscores in section names. At the very least, it would help if this limitation was documented in the readme.



Nice finding! :+1:
I'll change that with the next update.


@jefferyto I've pushed a PR regarding named 'wifi-iface' sections (see Would be nice, if you could test that ... thanks!


I did a quick test and it seems to be working - thanks!


Also, it would be nice to have a way to disable an interface so that travelmate doesn’t try to connect to it at all (e.g. after the time limit of a preferred wifi network is over, can disable it and fallback to a less preferred network).

Normally I would manually comment out the config entry, but travelmate (through uci) has a habit of removing all comments when saving.


Just prioritize the configured stations as you like via "UP"/"DOWN" in Wireless Stations tab, e.g.


In this example travelmate will switch to my mobile AP (meinIO) as soon as I enable this functionality on my mobile ... and fall back to lower prioritized whenever I disable this AP.


Oops, somehow I thought travelmate decides which network to connect to based on signal strength. (Even on this LuCI screen, it's not clear to me that travelmate will try to connect in top-to-bottom order. I thought the ordering was only for my visual preference.)

I still think a clear "disabled" setting would be useful though. In my case, the signal for the less-preferred network is weak. No matter how many disconnections I experience, I still wouldn't want travelmate to give up and try the other (time-limited, now expired) network.

And now that I know travelmate tries networks in order, I would also suggest adding a "priority" option instead of relying on config section order. I guess because I prefer manually editing config files, I want to order/group my sections in a way that makes sense to me. (And because the order of connection is an actual setting, having it set explicitly as an option makes me feel better :joy:)

(A thought I had after posting:) If you keep a list of opt-in wifi interfaces (a bit like mwan3 policies):

config travelmate 'global'
    list trm_interfaces 'networkA'
    list trm_interfaces 'networkB'

then it can support disabled networks (by not including in the list) and connection ordering (using list order).

These are not deal-breakers though - thanks again for this package!