From 10a44d60c0633106cf0a7f49ae42b50dba35f4fb Mon Sep 17 00:00:00 2001 From: Christine Zak <92458803+czakfb@users.noreply.github.com> Date: Tue, 28 Jun 2022 18:58:01 -0700 Subject: [PATCH] updates for 2.6 release integrations file fix added correct path in toc minor edits "TIP OpenWiFi" --- SUMMARY.md | 2 +- about/about-openwifi.md | 4 ++-- {about-openwifi => about}/integrations.md | 0 getting-started/access-points.md | 13 ++++++------- 4 files changed, 9 insertions(+), 10 deletions(-) rename {about-openwifi => about}/integrations.md (100%) diff --git a/SUMMARY.md b/SUMMARY.md index 5882425..60bf4e3 100644 --- a/SUMMARY.md +++ b/SUMMARY.md @@ -7,7 +7,7 @@ * [About OpenWifi](about/about-openwifi.md) * [Open WiFi First](about/contribute.md) * [Supported Hardware](about/supported-hardware.md) -* [Integrations](openwifi-stack/openwifi-stack.md) +* [Integrations](about/integrations.md) * [Device Partner Information](about/device-partner-information.md) * [Cloud Partner Information](about/cloud-partner-information.md) * [Ordering OpenWiFi APs](about/ordering-open-wi-fi-aps.md) diff --git a/about/about-openwifi.md b/about/about-openwifi.md index 6466edb..f537f4d 100644 --- a/about/about-openwifi.md +++ b/about/about-openwifi.md @@ -1,6 +1,6 @@ -# About OpenWifi +# About TIP OpenWifi -## About TIP OpenWifi +## Moving OpenWifi. Further. Meta Connectivity provides solutions leveraging the Telecom Infra Project (TIP) OpenWiFi ecosystem—as part of the TIP Open Converged Wireless Project Group. diff --git a/about-openwifi/integrations.md b/about/integrations.md similarity index 100% rename from about-openwifi/integrations.md rename to about/integrations.md diff --git a/getting-started/access-points.md b/getting-started/access-points.md index c5d79d6..b099321 100644 --- a/getting-started/access-points.md +++ b/getting-started/access-points.md @@ -1,9 +1,9 @@ # Access Points -TIP OpenWiFi devices are available from many hardware partners. All TIP OpenWiFi devices have the same standard image of open source software. +TIP OpenWiFi devices are available from many hardware partners. All TIP OpenWiFi devices have the same standard image of open source software. TIP OpenWiFi 1.0 devices run OpenWrt operating system with OpenSync as a management stack. -The use of OpenWrt is largely upstream based on OpenWrt 19.07 in Open WiFi 1.0. +The use of OpenWrt is largely upstream based on OpenWrt 19.07 in Open WiFi 1.0. When a TIP firmware image is created, the system will merge TIP specific patches, kernel specific patches, and build this with the target OpenWrt 19.07 operating system as one complete firmware image. From this process a TIP OpenWiFi standard firmware results with the following settings. @@ -17,9 +17,9 @@ When a TIP firmware image is created, the system will merge TIP specific patches ### Unable to Connect to WAN or Controller -If the OpenWiFi device has been unable to reach the internet or the assigned controller, the 'Maverick' SSID will appear. Joining this Wi-Fi network will join the local management interface to help onboard the device to the internet and controller. +If the OpenWiFi device has been unable to reach the internet or the assigned controller, the 'Maverick' SSID will appear. Joining this Wi-Fi network will join the local management interface to help onboard the device to the internet and controller. -After joining Maverick SSID, opening a web browser to the address 192.168.1.1 where the following login displays. Enter root login and password. +After joining Maverick SSID, opening a web browser to the address 192.168.1.1 where the following login displays. Enter root login and password. ![Maverick Local Web Page](../.gitbook/assets/image%20%2811%29.png) @@ -35,9 +35,8 @@ It is possible to apply a firmware update from the Maverick interface. This oper ![Maverick based firmware upgrade](../.gitbook/assets/image%20%289%29.png) -Manually setting the cloud location may be done using its Fully Qualified Domain Name \(FQDN\) in the Redirector field. Device certificates are unique per TIP Open WiFi access point or switch. It should not be required to change these values at any time. Please exercise caution if replacing certificates manually. +Manually setting the cloud location may be done using its Fully Qualified Domain Name \(FQDN\) in the Redirector field. Device certificates are unique per TIP OpenWiFi access point or switch. It should not be required to change these values at any time. Please exercise caution if replacing certificates manually. ![Maverick set Cloud 'Redirector'](../.gitbook/assets/image%20%2817%29.png) -### - +###