====== captive_portal.json file ====== * Edit the file ///etc/MESHdesk/configs/captive_config.json//. * This file is a JSON structure that the device uses as a reference to configure itself with a special captive portal when it is not yet managed by the controller. * There are only two items that might need to be tweaked * The radio number for the 2.4G band. * The **ports** for the **br-lan** device (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) * See this snippet of a device which has radio1 using the 2.4G band "wireless": [ { "wifi-device": "radio1", "options": { "channel": 1, "disabled": 0, "hwmode": "11g", "htmode": "HT20" } }, { "wifi-iface": "two", "options": { "device": "radio1", "ifname": "two0", "mode": "ap", "network": "ex_two", "encryption": "none", "ssid": "_Replace_", "key": "", "hidden": false, "isolate": false, "auth_server": "", "auth_secret": "" } }, { "wifi-iface": "web_by_w", "options": { "device": "radio1", "mode": "sta", "network": "web_by_w", "encryption": "psk2", "key": "radiusdesk", "ssid": "meshdesk_config", "disabled": "1" } } ], * With the **Xiaomi 4A 100M Edition** the **port** we use is **eth0.1** for the **br-lan** device definition. { "device": "br-lan", "options": { "name": "br-lan", "type": "bridge" }, "lists": { "ports": [ "eth0.1" ] } }, * With the **Xiaomi 4A Gigabit Edition** it will look like this { "device": "br-lan", "options": { "name": "br-lan", "type": "bridge" }, "lists": { "ports": [ "wan" ] } }, * Once the tweaks are completed we can test everything out.