QUOTE(soonwai @ Oct 28 2019, 12:59 PM)
Yeah, damn TM support is always like that. They always blame the customer first. Real stupid. I guess it works with laypeople.
But back to the 3hr DC issue, this is definitely a TM problem. It sounds like someone at TM accidentally configured 3hours for the pppoe lease time. If you were connected before they configured it and you don't disconnect then you'll be fine but as soon as you disconnect and reconnect, the new lease time comes into effect.
I haven't seen it myself yet and neither has my neighbours so it's limited to affected pppoe concentrators. Maybe post your location or, if possible, pppoe server id if it's happening to you.
For example, mine is ibse01.bgi which is Bangi. You may see this in your router logs. On Mikrotik routers, it's in PPPoE status.
QUOTE(Schadenfreude @ Oct 28 2019, 01:14 PM)
I'm in Kelana Jaya, for the record. Can't seem to find the pppoe server id in my ASUS router logs though, although maybe I'm not looking in the right spots...
Yeah, my friends in the area have not disconnected and I have warned them not to disconnect until the problem is solved.
I can't find the pppoe ID entry in my logs either. But like Schadenfreude, I'm in Kelana Jaya.
QUOTE(Buffalo Soldier @ Oct 28 2019, 01:26 PM)
https://www.linuxbabe.com/ubuntu/ubuntu-stubby-dns-over-tlsI have not been affected yet... But I have been using DOT since I visited this thread as extra safety/privacy precaution. So far seems OK.
If for Ubuntu got, for sure other OS mesti ada.
Thanks. I did try to use Cloudflare DNS which has DNS over https and DNS over TLS to no avail.
I don't think you need to worry as long as your pppoe stays connected. If you've restarted your network equipment in the past few days and are unaffected, then you're safe.