This shows you the differences between two versions of the page.
| easymesh:tplink [2023/12/18 22:10] – created olaf | easymesh:tplink [2023/12/18 23:01] (current) – created olaf | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== EasyMesh with TP-Link AX55====== | + | ===== EasyMesh with TP-Link AX55 ===== |
| + | <WRAP column> | ||
| + | <WRAP column> | ||
| + | <WRAP round notice>// | ||
| + | For ethernet backhaul to work Beta firmware 1.2.6 is required.\\ | ||
| + | It can be found at https:// | ||
| + | </ | ||
| + | <WRAP clear></ | ||
| + | |||
| + | ==== Setup ===== | ||
| + | |||
| + | Step 1 ... | ||
| + | |||
| + | Step 2 ... | ||
| + | |||
| + | Step x ... | ||
| + | |||
| + | |||
| + | ==== Ethernet backhaul ==== | ||
| + | |||
| + | With firmware 1.2.6 installed, there is not much more to do than to connect the second AX55 to the Mesh Master.\\ | ||
| + | But, when the Mesh Master is configuring the mesh with ethernet backhaul, it creates a loop for about 1 to 2 seconds. | ||
| + | This is a problem if there are switches in the network that have loop protection (some devices have STP) enabled. | ||
| + | Therefore, it is important to disable loop protection. | ||
| + | |||
| + | Once the secondary mesh node is connected and recognized, it will switch to wired mode and reboot. | ||
| + | The Mesh Master node will reboot too. | ||
| - | This is related to hardware version v1.0 | ||
| - | For ethernet backhaul to work Beta firmware 1.2.6 is required. It can be found at https:// | ||