698622495c
**Description** <!-- Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change. --> ⚒️ Fixes # <!--(issue)--> **⚙️ Type of change** - [ ] ⚙️ Feature/App addition - [ ] 🪛 Bugfix - [ ] ⚠️ Breaking change (fix or feature that would cause existing functionality to not work as expected) - [ ] 🔃 Refactor of current code **🧪 How Has This Been Tested?** <!-- Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration --> **📃 Notes:** <!-- Please enter any other relevant information here --> **✔️ Checklist:** - [ ] ⚖️ My code follows the style guidelines of this project - [ ] 👀 I have performed a self-review of my own code - [ ] #️⃣ I have commented my code, particularly in hard-to-understand areas - [ ] 📄 I have made corresponding changes to the documentation - [ ] ⚠️ My changes generate no new warnings - [ ] 🧪 I have added tests to this description that prove my fix is effective or that my feature works - [ ] ⬆️ I increased versions for any altered app according to semantic versioning **➕ App addition** If this PR is an app addition please make sure you have done the following. - [ ] 🪞 I have opened a PR on [truecharts/containers](https://github.com/truecharts/containers) adding the container to TrueCharts mirror repo. - [ ] 🖼️ I have added an icon in the Chart's root directory called `icon.png` --- _Please don't blindly check all the boxes. Read them and only check those that apply. Those checkboxes are there for the reviewer to see what is this all about and the status of this PR with a quick glance._
1.7 KiB
1.7 KiB
title
| title |
|---|
| Installation Notes |
Our chart by default runs on internal port 443 however those not running Ingress may run into issues with other processes requesting port 443.
The Solution
- Click
Advanced Settings - Change
Target Portto 8043 to match theexternalport as below
Finding APs / Omada Discovery Utility
By default the omada-controller chart doesn't support discovery by APs on the same network.
The solution
- One must use the
Omada Discovery Utilityand point APs to youromada-controller. - Please follow the directions on the TP-Link Website to download and use this utility. They have a nice FAQ that may be of use.
DHCP Option 138
As well, the Omada-Controller supports using DHCP to inform your APs of the location of the controller. This can be done using the Omada software or another DHCP server such as OPNsense. This has been tested by users (see TP-Link Reddit for more info) but there's a reference guide available in the official Omada SDN Software Controller users guide.
