This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revision | |||
| md:openwrt-meshdesk_17 [2021/11/20 18:15] – admin | md:openwrt-meshdesk_17 [2021/11/20 18:18] (current) – [captive_portal.json] admin | ||
|---|---|---|---|
| Line 296: | Line 296: | ||
| * The radio number for the 2.4G band. | * The radio number for the 2.4G band. | ||
| * The **ifname** for the **lan** interface (We use the WAN port in out implementation) | * The **ifname** for the **lan** interface (We use the WAN port in out implementation) | ||
| - | * With the **Xiaomi 4A 100M Edition** radio0 is the 2.4G radio so no need to tweak that item. (If the hardware has radio1 as the 2.4G band simply look for all the references to **radio0** and make them radio1) | + | * With the **OM2P** radio0 is the 2.4G radio so no need to tweak that item. (If the hardware has radio1 as the 2.4G band simply look for all the references to **radio0** and make them radio1) |
| * See this snippet of a device which has radio1 using the 2.4G band | * See this snippet of a device which has radio1 using the 2.4G band | ||
| <code javascript> | <code javascript> | ||
| Line 339: | Line 339: | ||
| ], | ], | ||
| </ | </ | ||
| - | * With the **Xiaomi 4A 100M Edition** the **ifname** we use is **eth0.1** for the **lan** interface definition. | + | * With the **OM2P** the **ifname** we use is **eth0** for the **lan** interface definition. |
| <code javascript> | <code javascript> | ||
| { | { | ||
| " | " | ||
| " | " | ||
| - | " | + | " |
| - | " | + | |
| - | " | + | |
| - | " | + | |
| - | " | + | |
| - | } | + | |
| - | }, | + | |
| - | </ | + | |
| - | * With the **Xiaomi 4A Gigabit Edition** it will look like this | + | |
| - | < | + | |
| - | { | + | |
| - | " | + | |
| - | " | + | |
| - | " | + | |
| " | " | ||
| " | " | ||
| Line 366: | Line 353: | ||
| </ | </ | ||
| * Once the tweaks are completed we can test everything out. | * Once the tweaks are completed we can test everything out. | ||
| - | * The following link shows how to point the device to the controller using the GUI | + | * The following link shows how to point the device to the controller using the GUI. |
| - | * [[2021: | + | * [[2021: |
| * Point the device to your controller and reboot it. | * Point the device to your controller and reboot it. | ||
| * If all goes well it will show up in **Unknown Nodes** | * If all goes well it will show up in **Unknown Nodes** | ||