5.12.9 TIME problem
5.12.9 TIME problem
Hi! is there anyone here with a fix on the new update of the oc200 5.12. specially with the time settings? because everytime theres a powercut or a fluctuate on the electrity or anything that even shuts the oc200 down even for just a minute. our HOTSPOT (VOUCHER) system time changes. many of our clients goes way past their intended time. like if we don't unauthorize them in the HOTSPOT setup, there's no limit as to when they are connected. we have tried going AUTO in the time settings and also going manual but none of them works its quite a hassle that we have to refresh our timezone from one place to the other just so we can keep our clients not going way past their intended time. one more is the NTP server. which we don't know how it works. any solution to this is greatly appreciated. and i have posted a picture and as you can see there is a mix of date between oct7 and oct 10.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
@Eisen Did this problem occur after updating to 5.12? Also, I can’t see the pictures you uploaded.
- Copy Link
- Report Inappropriate Content
@Eisen You can refer to https://community.tp-link.com/en/business/forum/topic/273926
- Copy Link
- Report Inappropriate Content
@dulu yes, and many are having the same issue as me. since I am from the philippines electricity is not so constant so there will blackout from time to time and next thing we know our client who is just authorize for an 1hr goes way beyond their time limit. like for days. many of my fellow collegues went to downgrade their oc200 because of the latest update
- Copy Link
- Report Inappropriate Content
Hotspot feature needs the Controller to keep running constantly, I don't think the issue you input is adapt to the common scenario. Just like me, hasn't a similar issue so far.
- Copy Link
- Report Inappropriate Content
@Eisen same problem in my network
- Copy Link
- Report Inappropriate Content
TP-Link needs to sort this problem out, it is ridiculous that a critical network controller only validatyes its time and date once in a 24hour period and doesnt make any attempt to retry. this fundamental system need should be validating or synching on a regular schedule of at least hourly, or be able to set this in the controller settings from a minimum of 15 minutes. Other common routers allow for synch calls as frequently as needed. People using the OC200's or 300's are not dummies, so sort this critical problem out TP Link!
- Copy Link
- Report Inappropriate Content
@Eisen et al
First, I acknowledge that this is a real problem and should be fixed ASAP.
There are some temporary workarounds, ie migrate your hardware controller to the TPlink cloud controller, or a software controller running in a VM, container, Pi or laptop/server until the hardware controller firmware is tweaked to include an ntpd (NTP daemon) for the underlying OS.
In fact, this is precisely why my OC200 is in a drawer and I'm using a $35 Pi Clone to run my 5.13 controller in a Docker container, as well as containers for Wireguard and PiHole to cover up deficiencies in the ER605v1...oh, and it also runs a crond job to cover up ongoing deficiencies in TPlink routers limited and buggy support for Dynamic DDNS. At other sites the patch functionality is implemented on Synology NAS using the same Docker container stack.
LINK to my Pi solution build/how-to https://community.tp-link.com/en/business/forum/topic/606692?replyId=1203918
Keep reading that thread for the final result:
-heatsink mandatory
-added Portainer for container control
-added Wireguard (with good throughput results)
-added DDNS via container but later deleted this and replaced with a single crontab line for my DDNS provider
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
With all due respect, I don't understand why you guys think this is a bug in this product, very obvious hints here "Controller Online Required."
No offense, but am I misunderstand?
- Copy Link
- Report Inappropriate Content
Actually this is the main problem. "Controller Online Required" indicates that the controller for the site needs to be online at all times when using a portal. It doesn't mean you need the "Online Controller", a hardware OC200/300 is just as good. As many people do not want to be held captive with online pricing and licenses that can get a bit expensive when managing a larger site, or we just want to have management control over the site when there is no internet connectivity, the hardware controller is an important part. Some of the work arounds are good, but they ignore the problem, which is that TP Link have created a major bug in its firmware and need to fix it.
This time problem renders the Hardware Controller completely useless in an operational situation as everything goes wrong - Logs, access time control and as many of us require, the portal. It seems quite strange that a company like TP Link would be ignoring this fundamental bug whilst rolling out updates for the Omada Devices, not the controller.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 3
Views: 765
Replies: 12
Voters 1
