still having issues. I actually purchased a separate Asus n14 router to play with Openwrt, trying to figure out WHY your systems does not consistently re-acquire the client wifi connection.
this POST having the video stream up and running from post
1- comfortable with default 'out of the box' setup on the pod here. (re-imaging is a no brainer these days)
2- Power up the pod wait about 3 minutes before doing anything
3- Windows10 PC- using a wifi dongle I connect my desktop PC to FlytPOD_wifi network
4- on screen in firefox it accesses flytpod/flytconsole/ without issue
5- in the console I go to wifi and select client
6 - a scan does indeed see my home router wifi - I select it and wait for the screen prompt to say it's done
7- I wait an 3 minutes and press and hold the POD button for 2-2.5 second till the led blinks differently then let off.
8- I wait about 40 seconds then switch off power to the pod
9- upon turning on the pod, the flytPOD_wifi is still there and there is no connection from the pc/desktop router network.
10- SO.... I repeat 1 through 9 above BUT using a separate laptop and the new Asus n14 router
still no disconnect of the pod wifi nor connection to the home router wifi.
11- I repeat #10 with s third laptop (internal wifi) and tested with my Iphone as hot spots to connect the pod client to
12- still no connection. (as in 9 above)
13- I have tried this repeatedly at least three times each (with variations) the pod wifi never goes away, nor does it connect with any network I select via the flytpod console. I can connect without issue from any pc (or laptop) or network to the flytpod as a AP spot. All will see the pod via wifi.
14- Using the sudo mini terminal, as well as running tests logging in as SSH firstname.lastname@example.org directly on the pod, both bring up the OpenWrt terminal. Doing a firstboot && reboot from either terminal interface does not change the situation.
15- I went as far as to examine the /etc/config/networki and etc/config/system and etc/configwireless files on the pod router and there does not seem to be anything odd there with what all the openwrt documentation states. BUT I never see connect info for what was set via the flytconsole.
QUESTION.... is this a possible issue with the 'load' v1.10 currently on my pod? how can I force an update? re-imaging did not change the issue before this last round of tests.
If there was some consistency to all this I could trouble shoot. but these procedures, that were even re-iterated to me and I followed carefully (and even repeated the boot sequences on my odroid...both auto login, both drop when the button is pushed within roughly 20 seconds. but simply the 'client' connect stuff is NOT working
...I need some ideas of what to look at