This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revision | |||
| user_guide:wifi_client_support [2016/10/31 09:49] – [Introduction] admin | user_guide:wifi_client_support [2016/10/31 09:54] (current) – [A Catch-22] admin | ||
|---|---|---|---|
| Line 35: | Line 35: | ||
| * Remember that the channel the mesh runs on should be the same as the Access Point it connects to as a client. | * Remember that the channel the mesh runs on should be the same as the Access Point it connects to as a client. | ||
| </ | </ | ||
| + | |||
| + | ---------------- | ||
| + | |||
| + | ===== What's the requirements? | ||
| + | |||
| + | * The good news is that with this solution you do not need any additional hardware, in fact you'll probably use fewer nodes in your mesh. | ||
| + | * All you need is to use the latest SVN code and build the MESHdesk firmware with the relayd package included as specified on this page: http:// | ||
| + | * On the exit points of both **MESHdesk** meshes and **APdesk AP** Profiles you cannot have an exit point that is bridged with Ethernet | ||
| + | * You can have a: | ||
| + | * Captive Portal | ||
| + | * NAT + DHCP | ||
| + | * OpenVPN Bridge | ||
| + | |||