The content of this topic has been archived between 29 Mar 2018 and 22 Apr 2018. There are no obvious gaps in this topic, but there may still be some posts missing at the end.
Update:
Openwrt development pretty much stopped in April/May 2016 when practically all active core developers left for LEDE - best is to head over to LEDE, stable release 17.01 or current LEDE snapshots.
The active travelmate LEDE-forum thread with download links can be found here
Have fun!
Dirk
(Last edited by dibdot on 29 Jul 2017, 17:37)
i sen't you an email, please respond
i sen't you an email, please respond
Up to now I've answered all queries ... please try again (I've tagged my email in the first post) - thanks.
travelmate is now in trunk - see first post!
Dirk, please correct me if I'm wrong -- does it search available networks with iw/iwinfo to scan for nearby SSIDs and if it matches one of the SSIDs defined as STA in the wireless interfaces, only then it attempts to enable STA interface and connect?
Is there any AP downtime for when it's trying to connect to STA?
What if the SSIDs match, but the key is incorrect, is there any AP downtime?
What if the higher priority STA can't connect, would it automatically jump to the next STA?
Finally, have you talked to hnyman about luci app for travelmate yet?
Dirk, please correct me if I'm wrong -- does it search available networks with iw/iwinfo to scan for nearby SSIDs and if it matches one of the SSIDs defined as STA in the wireless interfaces, only then it attempts to enable STA interface and connect?
that's correct, even the "up" sta interface appears down, cause all changes are uncommitted (in uci terms) and will be reverted directly after a successful connect.
Is there any AP downtime for when it's trying to connect to STA?
there is a single, really small ap outage during >network reload<, nothing more.
What if the SSIDs match, but the key is incorrect, is there any AP downtime?
same applies to this situation (for multiple times). Therefore you can set "trm_maxretry" (default 3) to configure how many times should travelmate try to connect to a certain uplink.
What if the higher priority STA can't connect, would it automatically jump to the next STA?
yes, travelmate goes sequentially through the configured wireless stations.
Finally, have you talked to hnyman about luci app for travelmate yet?
no, not yet. travelmate is really an early bird for further testing ... 
Thank you Dirk, fantastic work!
Thank you Dirk, fantastic work!
Thanks, you're welcome! Meanwhile Hannu provided a luci frontend for travelmate, many, many thanks for that! 
Dirk,
I have a few follow up questions.
1. The fact that I add wwan to the wan firewall zone would not mess up anything when I'd want to use my router with travelmate disabled in a proper router mode, would it?
2. For the proper Wireless Repeater mode to work I also used to create stabridge interface, run relayd and have a hotplug script which would update stabridge ip address with the wwan ip address. Is that something that travelmate does automatically or do I still need to do all that before running travelmate?
Thanks again!
(Last edited by stangri on 28 Nov 2016, 04:49)
1. The fact that I add wwan to the wan firewall zone would not mess up anything when I'd want to use my router with travelmate disabled in a proper router mode, would it?
a disabled/not used wan interface should make no harm
2. For the proper Wireless Repeater mode to work I also used to create stabridge interface, run relayd and have a hotplug script which would update stabridge ip address with the wwan ip address. Is that something that travelmate does automatically or do I still need to do all that before running travelmate?
I don't fully understand your setup (never used relayd so far) ... travelmate only works with an existing wireless config, no interface creation or other magic changes in network config.
So I have two APs and two STAs defined in wireless config and yet travelmate complains:
Thu Dec 1 11:38:23 2016 user.notice travelmate-0.2.6[2852] error: no usable AP configuration found, please add an 'ifname' entry in '/etc/config/wireless'So I have two APs and two STAs defined in wireless config and yet travelmate complains:
Thu Dec 1 11:38:23 2016 user.notice travelmate-0.2.6[2852] error: no usable AP configuration found, please add an 'ifname' entry in '/etc/config/wireless'
Hi Stan,
please post your wireless config ... or send it by email - thanks!
Dirk,
Thanks for your prompt reply! Here it is (sanitized):
wireless.radio0=wifi-device
wireless.radio0.type='mac80211'
wireless.radio0.hwmode='11g'
wireless.radio0.path='platform/10180000.wmac'
wireless.radio0.htmode='HT20'
wireless.radio0.country='US'
wireless.radio0.txpower='16'
wireless.radio0.channel='auto'
wireless.default_radio0=wifi-iface
wireless.default_radio0.device='radio0'
wireless.default_radio0.network='lan'
wireless.default_radio0.mode='ap'
wireless.default_radio0.ssid='************'
wireless.default_radio0.key='************'
wireless.default_radio0.encryption='psk2+ccmp'
wireless.default_radio0.wps_pushbutton='0'
wireless.default_radio0.wpa_group_rekey='3600'
wireless.@wifi-iface[1]=wifi-iface
wireless.@wifi-iface[1].device='radio0'
wireless.@wifi-iface[1].network='guest'
wireless.@wifi-iface[1].mode='ap'
wireless.@wifi-iface[1].ssid='************'
wireless.@wifi-iface[1].encryption='psk2'
wireless.@wifi-iface[1].key='************'
wireless.@wifi-iface[1].isolate='1'
wireless.@wifi-iface[2]=wifi-iface
wireless.@wifi-iface[2].device='radio0'
wireless.@wifi-iface[2].network='lan'
wireless.@wifi-iface[2].ssid='************'
wireless.@wifi-iface[2].mode='sta'
wireless.@wifi-iface[2].key='************'
wireless.@wifi-iface[2].encryption='psk2+ccmp'
wireless.@wifi-iface[2].wps_pushbutton='0'
wireless.@wifi-iface[2].disabled='1'
wireless.@wifi-iface[3]=wifi-iface
wireless.@wifi-iface[3].device='radio0'
wireless.@wifi-iface[3].network='lan'
wireless.@wifi-iface[3].ssid='STA-WiFi'
wireless.@wifi-iface[3].mode='sta'
wireless.@wifi-iface[3].encryption='none'
wireless.@wifi-iface[3].wps_pushbutton='0'
wireless.@wifi-iface[3].disabled='1'PS. Despite the first iface being shown as wireless.default_radio0 it is addressable as wireless.@wifi-iface[0].
So I have two APs and two STAs defined in wireless config and yet travelmate complains:
Thu Dec 1 11:38:23 2016 user.notice travelmate-0.2.6[2852] error: no usable AP configuration found, please add an 'ifname' entry in '/etc/config/wireless'
Please try travelmate 0.2.7, this version no longer relies on static ifnames in wireless config.
stangri wrote:So I have two APs and two STAs defined in wireless config and yet travelmate complains:
Thu Dec 1 11:38:23 2016 user.notice travelmate-0.2.6[2852] error: no usable AP configuration found, please add an 'ifname' entry in '/etc/config/wireless'Please try travelmate 0.2.7, this version no longer relies on static ifnames in wireless config.
Dirk,
As I didn't find the prebuilt 0.2.7 package, I just updated the /usr/bin/travelmate.sh file with the 0.2.7 from github and it doesn't error out anymore, however it doesn't bring up STA either. The connection defined in the first (disabled) STA iface in my config matches existing/available WiFi network (from my main router), however I don't see the script trying to bring it up.
Fri Dec 2 16:15:23 2016 user.notice slider: Switching to Wireless Repeater mode
Fri Dec 2 16:15:23 2016 daemon.info dnsmasq[2870]: exiting on receipt of SIGTERM
Fri Dec 2 16:15:30 2016 daemon.info dnsmasq[3113]: started, version 2.76 cachesize 5000
Fri Dec 2 16:15:30 2016 daemon.info dnsmasq[3113]: compile time options: IPv6 GNU-getopt no-DBus no-i18n no-IDN DHCP DHCPv6 no-Lua TFTP conntrack ipset auth DNSSEC no-ID loop-detect inotify
Fri Dec 2 16:15:30 2016 daemon.info dnsmasq[3113]: DNS service limited to local subnets
Fri Dec 2 16:15:30 2016 daemon.info dnsmasq-dhcp[3113]: DHCP, IP range 10.0.0.100 -- 10.0.0.249, lease time 1h
Fri Dec 2 16:15:30 2016 daemon.info dnsmasq-dhcp[3113]: DHCP, IP range 192.168.8.100 -- 192.168.8.249, lease time 12h
Fri Dec 2 16:15:30 2016 daemon.info dnsmasq[3113]: using local addresses only for domain local
Fri Dec 2 16:15:30 2016 daemon.warn dnsmasq[3113]: no servers found in /tmp/resolv.conf.auto, will retry
Fri Dec 2 16:15:30 2016 daemon.info dnsmasq[3113]: read /etc/hosts - 4 addresses
Fri Dec 2 16:15:30 2016 daemon.info dnsmasq[3113]: read /tmp/hosts/dhcp.cfg02411c - 19 addresses
Fri Dec 2 16:15:30 2016 daemon.info dnsmasq-dhcp[3113]: read /etc/ethers - 0 addresses
Fri Dec 2 16:15:30 2016 user.notice button: BTN_0 is pressed for 345 seconds
Fri Dec 2 16:15:31 2016 kern.info kernel: [ 613.644109] device wlan0 left promiscuous mode
Fri Dec 2 16:15:31 2016 kern.info kernel: [ 613.648857] br-lan: port 2(wlan0) entered disabled state
Fri Dec 2 16:15:31 2016 daemon.notice netifd: Interface 'guest' is now down
Fri Dec 2 16:15:31 2016 daemon.notice netifd: Interface 'guest' is disabled
Fri Dec 2 16:15:31 2016 daemon.notice netifd: Interface 'guest' has link connectivity loss
Fri Dec 2 16:15:32 2016 daemon.notice netifd: radio0 (3227): command failed: Not supported (-122)
Fri Dec 2 16:15:32 2016 daemon.notice netifd: radio0 (3227): Configuration file: /var/run/hostapd-phy0.conf
Fri Dec 2 16:15:32 2016 kern.info kernel: [ 614.739432] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Fri Dec 2 16:15:32 2016 kern.info kernel: [ 614.761512] device wlan0 entered promiscuous mode
Fri Dec 2 16:15:32 2016 kern.info kernel: [ 614.766506] br-lan: port 2(wlan0) entered forwarding state
Fri Dec 2 16:15:32 2016 kern.info kernel: [ 614.772218] br-lan: port 2(wlan0) entered forwarding state
Fri Dec 2 16:15:32 2016 daemon.notice netifd: radio0 (3227): wlan0: interface state UNINITIALIZED->COUNTRY_UPDATE
Fri Dec 2 16:15:32 2016 daemon.notice netifd: radio0 (3227): ACS: Automatic channel selection started, this may take a bit
Fri Dec 2 16:15:32 2016 daemon.notice netifd: radio0 (3227): wlan0: interface state COUNTRY_UPDATE->ACS
Fri Dec 2 16:15:32 2016 daemon.notice netifd: radio0 (3227): wlan0: ACS-STARTED
Fri Dec 2 16:15:32 2016 kern.info kernel: [ 615.047066] br-lan: port 2(wlan0) entered disabled state
Fri Dec 2 16:15:34 2016 daemon.info dnsmasq[3113]: exiting on receipt of SIGTERM
Fri Dec 2 16:15:34 2016 daemon.info dnsmasq[3350]: started, version 2.76 cachesize 5000
Fri Dec 2 16:15:34 2016 daemon.info dnsmasq[3350]: compile time options: IPv6 GNU-getopt no-DBus no-i18n no-IDN DHCP DHCPv6 no-Lua TFTP conntrack ipset auth DNSSEC no-ID loop-detect inotify
Fri Dec 2 16:15:34 2016 daemon.info dnsmasq[3350]: DNS service limited to local subnets
Fri Dec 2 16:15:34 2016 daemon.info dnsmasq-dhcp[3350]: DHCP, IP range 192.168.8.100 -- 192.168.8.249, lease time 12h
Fri Dec 2 16:15:34 2016 daemon.info dnsmasq[3350]: using local addresses only for domain local
Fri Dec 2 16:15:34 2016 daemon.warn dnsmasq[3350]: no servers found in /tmp/resolv.conf.auto, will retry
Fri Dec 2 16:15:34 2016 daemon.info dnsmasq[3350]: read /etc/hosts - 4 addresses
Fri Dec 2 16:15:34 2016 daemon.info dnsmasq[3350]: read /tmp/hosts/dhcp.cfg02411c - 19 addresses
Fri Dec 2 16:15:34 2016 daemon.info dnsmasq-dhcp[3350]: read /etc/ethers - 0 addresses
Fri Dec 2 16:15:39 2016 daemon.notice netifd: radio0 (3227): ACS: Survey is missing noise floor
Fri Dec 2 16:15:39 2016 daemon.notice netifd: radio0 (3227): ACS: Survey is missing noise floor
Fri Dec 2 16:15:39 2016 daemon.notice netifd: radio0 (3227): ACS: Survey is missing noise floor
Fri Dec 2 16:15:39 2016 daemon.notice netifd: radio0 (3227): ACS: Survey is missing noise floor
Fri Dec 2 16:15:39 2016 daemon.notice netifd: radio0 (3227): ACS: Survey is missing noise floor
Fri Dec 2 16:15:39 2016 daemon.notice netifd: radio0 (3227): ACS: Survey is missing noise floor
Fri Dec 2 16:15:39 2016 daemon.notice netifd: radio0 (3227): ACS: Survey is missing noise floor
Fri Dec 2 16:15:39 2016 daemon.notice netifd: radio0 (3227): ACS: Survey is missing noise floor
Fri Dec 2 16:15:39 2016 daemon.notice netifd: radio0 (3227): ACS: Survey is missing noise floor
Fri Dec 2 16:15:39 2016 daemon.notice netifd: radio0 (3227): ACS: Survey is missing noise floor
Fri Dec 2 16:15:39 2016 daemon.notice netifd: radio0 (3227): ACS: Survey is missing noise floor
Fri Dec 2 16:15:39 2016 daemon.notice netifd: radio0 (3227): wlan0: ACS-COMPLETED freq=2412 channel=1
Fri Dec 2 16:15:39 2016 daemon.notice netifd: radio0 (3227): Using interface wlan0 with hwaddr e4:95:6e:40:e0:bc and ssid "********************"
Fri Dec 2 16:15:40 2016 kern.info kernel: [ 618.953663] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Fri Dec 2 16:15:40 2016 kern.info kernel: [ 618.960344] br-lan: port 2(wlan0) entered forwarding state
Fri Dec 2 16:15:40 2016 kern.info kernel: [ 618.966059] br-lan: port 2(wlan0) entered forwarding state
Fri Dec 2 16:15:40 2016 kern.info kernel: [ 618.996005] IPv6: ADDRCONF(NETDEV_UP): wlan0-1: link is not ready
Fri Dec 2 16:15:40 2016 daemon.notice netifd: radio0 (3227): Using interface wlan0-1 with hwaddr e4:95:6e:40:e0:bd and ssid "********************"
Fri Dec 2 16:15:40 2016 daemon.notice netifd: radio0 (3227): wlan0: interface state ACS->ENABLED
Fri Dec 2 16:15:40 2016 daemon.notice netifd: radio0 (3227): wlan0: AP-ENABLED
Fri Dec 2 16:15:40 2016 kern.info kernel: [ 619.549148] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0-1: link becomes ready
Fri Dec 2 16:15:41 2016 daemon.notice netifd: Network device 'wlan0' link is up
Fri Dec 2 16:15:41 2016 daemon.notice netifd: Network device 'wlan0-1' link is up
Fri Dec 2 16:15:41 2016 daemon.notice netifd: Interface 'guest' is enabled
Fri Dec 2 16:15:41 2016 daemon.notice netifd: Interface 'guest' is setting up now
Fri Dec 2 16:15:41 2016 daemon.notice netifd: Interface 'guest' is now up
Fri Dec 2 16:15:41 2016 daemon.notice netifd: Interface 'guest' has link connectivity
Fri Dec 2 16:15:41 2016 user.notice firewall: Reloading firewall due to ifup of guest (wlan0-1)
Fri Dec 2 16:15:42 2016 kern.info kernel: [ 620.791900] br-lan: port 2(wlan0) entered forwarding state
Fri Dec 2 16:15:43 2016 user.notice travelmate-0.2.7[3132] info: wwan interface connected to uplink "net.melmac.van"
Fri Dec 2 16:15:43 2016 daemon.notice netifd: Network device 'wlan0-1' link is down
Fri Dec 2 16:15:43 2016 daemon.notice netifd: Interface 'guest' has link connectivity loss
Fri Dec 2 16:15:43 2016 daemon.notice netifd: Interface 'guest' is now down
Fri Dec 2 16:15:43 2016 daemon.notice netifd: Interface 'guest' is disabled
Fri Dec 2 16:15:43 2016 kern.info kernel: [ 621.746105] device wlan0 left promiscuous mode
Fri Dec 2 16:15:43 2016 kern.info kernel: [ 621.750834] br-lan: port 2(wlan0) entered disabled state
Fri Dec 2 16:15:43 2016 daemon.notice netifd: Network device 'wlan0' link is down
Fri Dec 2 16:15:44 2016 daemon.notice netifd: radio0 (3543): command failed: Not supported (-122)
Fri Dec 2 16:15:45 2016 daemon.notice netifd: radio0 (3543): Configuration file: /var/run/hostapd-phy0.conf
Fri Dec 2 16:15:45 2016 kern.info kernel: [ 623.332502] IPv6: ADDRCONF(NETDEV_UP): wlan0-1: link is not ready
Fri Dec 2 16:15:45 2016 kern.info kernel: [ 623.353819] device wlan0-1 entered promiscuous mode
Fri Dec 2 16:15:45 2016 kern.info kernel: [ 623.359008] br-lan: port 2(wlan0-1) entered forwarding state
Fri Dec 2 16:15:45 2016 kern.info kernel: [ 623.364887] br-lan: port 2(wlan0-1) entered forwarding state
Fri Dec 2 16:15:45 2016 daemon.notice netifd: radio0 (3543): wlan0-1: interface state UNINITIALIZED->COUNTRY_UPDATE
Fri Dec 2 16:15:45 2016 daemon.notice netifd: radio0 (3543): ACS: Automatic channel selection started, this may take a bit
Fri Dec 2 16:15:45 2016 daemon.notice netifd: radio0 (3543): wlan0-1: interface state COUNTRY_UPDATE->ACS
Fri Dec 2 16:15:45 2016 daemon.notice netifd: radio0 (3543): wlan0-1: ACS-STARTED
Fri Dec 2 16:15:45 2016 kern.info kernel: [ 623.730202] br-lan: port 2(wlan0-1) entered disabled state
Fri Dec 2 16:15:50 2016 daemon.notice netifd: radio0 (3543): handle_probe_req: send failed
Fri Dec 2 16:15:50 2016 daemon.notice netifd: radio0 (3543): handle_probe_req: send failed
Fri Dec 2 16:15:50 2016 daemon.notice netifd: radio0 (3543): handle_probe_req: send failed
Fri Dec 2 16:15:50 2016 daemon.notice netifd: radio0 (3543): handle_probe_req: send failed
Fri Dec 2 16:15:50 2016 daemon.notice netifd: radio0 (3543): handle_probe_req: send failed
Fri Dec 2 16:15:50 2016 daemon.notice netifd: radio0 (3543): handle_probe_req: send failed
Fri Dec 2 16:15:50 2016 daemon.notice netifd: radio0 (3543): handle_probe_req: send failed
Fri Dec 2 16:15:50 2016 daemon.notice netifd: radio0 (3543): handle_probe_req: send failed
Fri Dec 2 16:15:50 2016 daemon.notice netifd: radio0 (3543): handle_probe_req: send failed
Fri Dec 2 16:15:50 2016 daemon.notice netifd: radio0 (3543): handle_probe_req: send failed
Fri Dec 2 16:15:52 2016 daemon.notice netifd: radio0 (3543): ACS: Survey is missing noise floor
Fri Dec 2 16:15:52 2016 daemon.notice netifd: radio0 (3543): ACS: Survey is missing noise floor
Fri Dec 2 16:15:52 2016 daemon.notice netifd: radio0 (3543): ACS: Survey is missing noise floor
Fri Dec 2 16:15:52 2016 daemon.notice netifd: radio0 (3543): ACS: Survey is missing noise floor
Fri Dec 2 16:15:52 2016 daemon.notice netifd: radio0 (3543): ACS: Survey is missing noise floor
Fri Dec 2 16:15:52 2016 daemon.notice netifd: radio0 (3543): ACS: Survey is missing noise floor
Fri Dec 2 16:15:52 2016 daemon.notice netifd: radio0 (3543): ACS: Survey is missing noise floor
Fri Dec 2 16:15:52 2016 daemon.notice netifd: radio0 (3543): ACS: Survey is missing noise floor
Fri Dec 2 16:15:52 2016 daemon.notice netifd: radio0 (3543): ACS: Survey is missing noise floor
Fri Dec 2 16:15:52 2016 daemon.notice netifd: radio0 (3543): ACS: Survey is missing noise floor
Fri Dec 2 16:15:52 2016 daemon.notice netifd: radio0 (3543): ACS: Survey is missing noise floor
Fri Dec 2 16:15:52 2016 daemon.notice netifd: radio0 (3543): wlan0-1: ACS-COMPLETED freq=2412 channel=1
Fri Dec 2 16:15:52 2016 daemon.notice netifd: radio0 (3543): Using interface wlan0-1 with hwaddr e4:95:6e:40:e0:bd and ssid "********************"
Fri Dec 2 16:15:53 2016 kern.info kernel: [ 627.466611] IPv6: ADDRCONF(NETDEV_UP): wlan0-2: link is not ready
Fri Dec 2 16:15:53 2016 daemon.notice netifd: radio0 (3543): Using interface wlan0-2 with hwaddr e4:95:6e:40:e0:be and ssid "********************"
Fri Dec 2 16:15:53 2016 daemon.notice netifd: radio0 (3543): wlan0-1: interface state ACS->ENABLED
Fri Dec 2 16:15:53 2016 daemon.notice netifd: radio0 (3543): wlan0-1: AP-ENABLED
Fri Dec 2 16:15:53 2016 kern.info kernel: [ 628.202803] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Fri Dec 2 16:15:53 2016 daemon.notice netifd: radio0 (3543): Interface 2 setup failed: BRIDGE_NOT_ALLOWED
Fri Dec 2 16:15:53 2016 daemon.notice netifd: Interface 'guest' is enabled
Fri Dec 2 16:15:53 2016 daemon.notice netifd: Interface 'guest' is setting up now
Fri Dec 2 16:15:53 2016 daemon.notice netifd: Interface 'guest' is now up
Fri Dec 2 16:15:54 2016 user.notice firewall: Reloading firewall due to ifup of guest (wlan0-2)Could it be because of the guest wlan?
(Last edited by stangri on 3 Dec 2016, 01:30)
As I didn't find the prebuilt 0.2.7 package, I just updated the /usr/bin/travelmate.sh file with the 0.2.7 from github and it doesn't error out anymore, however it doesn't bring up STA either. The connection defined in the first (disabled) STA iface in my config matches existing/available WiFi network (from my main router), however I don't see the script trying to bring it up.
[...]
Fri Dec 2 16:15:42 2016 kern.info kernel: [ 620.791900] br-lan: port 2(wlan0) entered forwarding state
Fri Dec 2 16:15:43 2016 user.notice travelmate-0.2.7[3132] info: wwan interface connected to uplink "net.melmac.van"
[...]Looks OK for me ...
Could it be because of the guest wlan?
a guest wlan on a travel router, really!?
If it still not working please send your sanitized network & wireless config via email and I'll try to reproduce that. BTW you could set 'trm_debug' '1' in travelmate config to enable script debugging ...
[...] Fri Dec 2 16:15:42 2016 kern.info kernel: [ 620.791900] br-lan: port 2(wlan0) entered forwarding state Fri Dec 2 16:15:43 2016 user.notice travelmate-0.2.7[3132] info: wwan interface connected to uplink "net.melmac.van" [...]Looks OK for me ...
Khm, dunno how I missed that line. However that STA iface showed up as disconnected in Luci, so I didn't check it it worked or not. I'll do some more testing and let you know.
Hehe, guess what, I've had my STAs assigned to lan interface rather than wwan. I'll try again and post back.
Still no cigar. If I'm watching the Network/Interfaces page in Luci I believe I can see WWAN going up and showing the mac address and uptime very briefly, and then it disconnects. Let me know if you prefer to switch to e-mail or continue here.
root@MT300N-E0BC:~# logread | grep travelmate
Mon Dec 5 11:45:01 2016 user.notice travelmate-0.2.7[5807] error: no usable AP configuration found, please check '/etc/config/wireless'
Mon Dec 5 11:52:04 2016 user.notice travelmate-0.2.7[7004] error: no usable AP configuration found, please check '/etc/config/wireless'
Mon Dec 5 11:53:02 2016 user.notice travelmate-0.2.7[7415] debug: set ::: change: commit, config: , interface: , command: , checklist: , uci-changes:
Mon Dec 5 11:53:03 2016 user.notice travelmate-0.2.7[7415] debug: main ::: scan-tool: /usr/sbin/iw, aplist: wlan0, ssidlist: "WallerHome-2.4G" "SHAW-9E21A3" "MB" "COOLKIDS-2.4G" "SHAW-9FE72A" "HP-Print-F7-Officejet Pro 8610" "SHAW-D56C31" "YoungKimmyChimneyy" "ArlenX-2" "PingChin" "SHAW-663AC6" "SHAW-E658B0" "***********" "TT" "***********" "RecamaraGR" "ArlenX" "TELUS3002-2.4G"
Mon Dec 5 11:53:03 2016 user.notice travelmate-0.2.7[7415] debug: set ::: change: partial, config: cfg043579, interface: wwan, command: up, checklist: wwan, uci-changes: wireless.cfg043579.disabled='0'
Mon Dec 5 11:57:14 2016 user.notice travelmate-0.2.7[8964] debug: set ::: change: commit, config: , interface: , command: , checklist: , uci-changes:
Mon Dec 5 11:57:15 2016 user.notice travelmate-0.2.7[8964] debug: main ::: scan-tool: /usr/sbin/iw, aplist: wlan0, ssidlist: "HP-Print-F7-Officejet Pro 8610" "SHAW-9FE72A" "SHAW-9E21A3" "TELUS3242-LIVINGROOM-2.4G" "SHAW-D56C31" "HP-Print-0B-Photosmart 6520" "lsys" "ChoobNet3" "***********" "TT" "***********" "Susie_teal" "SHAW-05EAA0" "WallerHome" "2girls1wifi" "1guest1wifi" "ArlenX_RPT"
Mon Dec 5 11:57:15 2016 user.notice travelmate-0.2.7[8964] debug: set ::: change: partial, config: cfg043579, interface: wwan, command: up, checklist: wwan, uci-changes: wireless.cfg043579.disabled='0'
Mon Dec 5 11:57:31 2016 user.notice travelmate-0.2.7[8964] debug: set ::: change: revert, config: , interface: , command: , checklist: , uci-changes: wireless.cfg043579.disabled='0'
Mon Dec 5 11:57:37 2016 user.notice travelmate-0.2.7[8964] debug: set ::: change: commit, config: , interface: , command: , checklist: , uci-changes:
Mon Dec 5 11:57:37 2016 user.notice travelmate-0.2.7[8964] error: no usable AP configuration found, please check '/etc/config/wireless'BTW, it shows it tried to change disabled=0, however in uci show wireless both STAs are still disabled=1.
(Last edited by stangri on 5 Dec 2016, 21:27)
Still no cigar. If I'm watching the Network/Interfaces page in Luci I believe I can see WWAN going up and showing the mac address and uptime very briefly, and then it disconnects. Let me know if you prefer to switch to e-mail or continue here.
Hi Stan,
I can reproduce those issues and will fix that with the next 0.3.x update - I'll send you a pre-release via email for further testing (but this will take some time!).
br
dirk
Hi Dirk.
I wanted to know if I should use the travelmate package in STA+AP only. Because when I used it on my my Linkit 7688 module in its STA mode the device started.
Hi Dirk.
I wanted to know if I should use the travelmate package in STA+AP only. Because when I used it on my my Linkit 7688 module in its STA mode the device started.
STA mode only? Did you use a wired connection to access your router?
Anyway, I have to rework travelmate a bit ... please wait for the next 0.3.x release.
Thanks for your patience!
Dirk
My bad. I meant the device started hanging in STA mode
On new years eve I've released 0.3.0 ... the AP/STA detection troubles should have been fixed. Also travelmate switched to procd interface triggers and no longer polls in the background.
(Last edited by dibdot on 8 Jan 2017, 15:51)
I keep seeing a message in LuCi which says "your hardware does not support multi-SSID". Does this mean i will not be able to use travelmate?
I'm a beginner at this.