The connectionlist is a great part. this means i can add the "most used" networks to the list.
the part with the hotspot is better then nothing. however not perfect.
This means i need to set my phone to an hotspot, get my wifes phone and connect to the "lan" wifi. to change the configuration.
otherwise we need to allow configuration from the wan interface.....from an untrusted network. (wich is disabled by default)
Yes, unfortunately so far you need two devices (one as AP, and one as client) to be able to connect and modify.
I have my 7" tablet and my smartphone. The laptop would be no problem as this one has ethernet. But I travel light.
Even opening the WAN WLAN interface will not help. The WLAN stays down until connected, once any AP is connected both are open.
You could swap the functions AP-bridge and station-bridge between the physical and the virtual WLAN interface. But then only AP's at the same frequency are connectable.
I had no success in trying to use the little push-button to start a special configuration on the press of that button.
That's why I included my Woobm and my RBMQS as AP's in the list, two interesting Mikrotik tools, smaller and almost as small as the mAP Lite.
for the connection list, is it possible to re-order them?
and when i add a profile without an ssid and security to none. will it connect to any network without encryption?
The connection list can be sorted by dragging the items in Winbox. Something similar must be there in Webfig, but I use Winbox or the Mikrotik APP in Android.
Never tried "without SSID" what that one does. In the log with /system/logging set with Topics=wireless it gives the impression it could work. Interesting thought.
last question for today,
i was planning to ad the eth1 device to a bridge called wan.
however i think that isn't the correct methode.
What is the best option to make ETH1 also availible as wan interface (when connected to this interface the wireless interface should not connect to an upstream wifi. but make the "lan" wifi availible.
I'm afraid this won't work as intended. It is not having an active ethernet interface ported to the bridge that will activate the WLAN interface. It is the connection to the physical WLAN that activates that master WLAN and all the virtual slave WLAN's.
Again many thanks for all the effort to learn this mikrotik-noob that the product isn't as bad as it looked the first day ;)
On my todo list ... as I stumbled upon this one in the wiki ....(@strods says it's only for X86 for ethernet ports, but hey this is in the wiki at the wireless page)
disable-running-check (yes | no; Default: no)
When set to yes interface will always have running flag. If value is set to no', the router determines whether the card is up and running - for AP one or more clients have to be registered to it, for station, it should be connected to an AP.