woutgg
commented
10 years ago This gist connects both to an existing network and sets up an AP.
It does not forward traffic however. In case we want that too we should probably set up a NAT. The alternative would be to make the AP part of the sta subnet and forward dhcp as well, but this makes configuration more complex/confusing because if no existing network is available the box would need to re-enable dhcp again. And apart from that, it would make the wireless device<->box connection depend again on the box<->existing-net connection, which should be avoided.
peteruithoven
You can configure the original TP-link box to be an access point that itself, which connects to another access point for internet (WISP). http://doodle3d.com/help/wiki/configuring-wisp-router Doing something like this would enable us to enable a access point out of the box and then add a client mode connection.
Currently when users get the box, it's in access point mode (because we don't know anything about their network). The user then connects to the WiFi hotspot of the box and then tries to connect the box to their own (home) network. When they do this they lose connection and there is no way for us to communicate whether connecting succeeded or failed. When it failed it's troublesome because they can now only connect to the box using an ethernet cable. When we could keep the access point in the air we can just communicate the status and let them retry. This is even more important when users use devices that don't have an ethernet port.
If this is possible it might be a better solution for the problem behind issue #209.