-
|
Hi @rubenbe, thanks for this great project! I somehow managed to set up OpenWISP, but it’s just too complex and resource hungry. So I was very happy to see this alternative 🙂 One thing that was really annoying for me with OpenWISP: My hostnames contain underscores for legacy reasons. (Yes, this is technically not legal, but it does work). However, OpenWISP does not accept such hostnames. OTOH it always overwrites device hostnames on device reboot, so manual configuration is not possible either. My configuration is also kind of non standard in general. WireGuard on the router, FreiFunk client WiFi on a certain VLAN and Batman mesh on some devices (not all). Also usually WAN added to LAN bridge, but not always. (On on some devices, extra config workarounds for the WAN interface conduit). So I would like to keep my manual configuration and only use OpenSOHO for monitoring. I think I can „disable“ a host, but does that really prevent all configuration changes? And can I enable this globally, so that it also applies to new hosts on the first join? |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
|
Hi @jpf91! You're welcome! Indeed, it's a massive thing to set up and run. I tried to slim it down, but failed, so I started OpenSOHO as it is ;)
|
Beta Was this translation helpful? Give feedback.
-
|
Great, that works fine and new hosts indeed show up as disabled, thanks! I'll have to play around with OpenSOHO a bit to see what it can do :-) |
Beta Was this translation helpful? Give feedback.
Hi @jpf91!
You're welcome! Indeed, it's a massive thing to set up and run. I tried to slim it down, but failed, so I started OpenSOHO as it is ;)
disabled, that's indeed fully safe, since OpenSOHO will simply refuse the to give the host its config (error 404). The only detail is that this adds an innocent error message …