Internal clock or RTC (Realtime Clock) for GL-MT6000 Flint 2?

Technical Support for Routers
1

I just bought a GL-MT6000 Flint 2 AX6000 Wireless router. I am wondering if it has an internal clock or hardware clock in it so it can know the proper time when not connected to the internet. Does anyone know if it has a RTC in it?

If it doesn't have one, is there any way to buy a RTC and install it on my Flint 2? Please let me know, and share some recommendations of RTC's that I can install and that will work with this router.

Thanks

2

Why do you want RTC?

The device uses NTP by default which is precise and does not cause any issues. I doubt there is a RTC embedded - there is no battery inside the device.

1 Like
3

I like having an internal RTC to prevent time based hacks or attacks, ensuring that my routers clock is crosschecked with the internets clock. This helps in preventing time-based attacks.

4

If you are that worried about being attacked or hacked, you shouldn't be using consumer grade products. I highly suggest you open your wallet and get your self a CISCO firewall.

1 Like
5

If you unplug the WAN, you're safe. Trust me. I only post from 5G LTE :eyes::grin:

(JK) :eyes::eyes:

1 Like
6

RTC won't help against this.

7

If the time tampering is concern, why not have cheap or free VPS nodes as remote observers? Geographically distributed nodes with highly secured encryption protocol would very trustful in your case. GPS would be cheaper, but theoretically GPS could also be compromised.

Me? Of course I'm just using public NTP. I thought about build my own time server that receives PPS signal, but that was solely for accuracy, not concerned any attacks.

But if I have a critical mission to defend against time attacks, I'll keep the time with one cesium clock, three rubidium clocks, five military-grade GNSS, and fifteen internationally distributed cellular observers. - The most important thing is, issuing the bloated invoice every month!

Thanks, it was fun to imagine for few minutes. :smiley:

8

I am not sure how this should help in any way.

The RTC will be overwritten by the NTP. So "time tampering protection" is just a useless wish since NTP will be always the "main" clock.

The trustworthiness is NTP > RTC, not the other way around.

9

Based on the above, of course I assumed that OP is using or would code some specially tailored program that compares the drift with current system time. I wouldn't say how it's realistic. Was I bad?