admin
-
Posts
305 -
Joined
-
Last visited
-
Days Won
108
Community Answers
-
admin's post in Keenetic Segmentation behind another ADSL Provider router was marked as the answer
Keenetic has necessary firewall rules enabled by default so that you don't need to duplicate them manually, and therefore, it's secure by default. The provider's router does not add any extra isolation, nor does it break any existing Keenetic isolation. The provider's router is simply a part "provider" for Keenetic, which is, by default, an untrusted (public) network. Keenetic permits no incoming connections from the outside.
Keenetic segmentation adds security to your network so that if your IoT device is compromised, it will not allow access to other devices on another segment as long as they are isolated. And the ISP router in no way reduces security in this scenario.
-
admin's post in How to remotely connect to KeeneticOS GUI using public iPv6 address? was marked as the answer
The current implementation of KeenDNS does not support direct IPv6. It resolves your KeenDNS name into the cloud IPv6 addresses only. The only option is to connect to the IPv6 address directly without HTTPS. The Web interface is accessible by IPv6 in version 4.0 only, so please upgrade your device to 4.0 (Preview).
-
admin's post in 3.9 beta 0.5 - Service: "Link-layer discovery observer": unexpectedly stopped - unknown option "a". was marked as the answer
The initial error (unknown option "a") is hotfixed in 3.09 Beta 0.6.
The @r13's one cannot be easily reproduced. We'll leave it until next time 💤
-
admin's post in Modifying schedule in startup-config was marked as the answer
Yes, it will. The device will automatically reboot as soon as you upload the file. The startup-config only applies when the device starts up.
-
admin's post in Disable or enable access to the KeenDNS Web configurator was marked as the answer
To enable public access:
ip http security-level public ssl To disable public access:
ip http security-level private