topic Re: GigaHub 2.0 - Traffic on non-standard ports stops after a few hours in Internet

GigaHub 2.0 - Traffic on non-standard ports stops after a few hours

MrLim — Fri, 10 Oct 2025 18:16:34 GMT

I recently had Bell Fibe internet installed, with a GigaHub 2.0.

When the GigaHub is first turned on, everything works fine.

After a few hours, all of our services that use non-standard web traffic ports (i.e. private DNS on 853, SIP on 5060, and more...) suddenly stop working. We also seem to lose access to external DNS servers, like 8.8.8.8. When this happens, standard web traffic seems to work fine, but everything on the other ports stops working.

When we reset the GigaHub, everything starts working again - no changes to the configuration.

Has anyone else experienced this? Aware of solutions?

One thing we noticed is in the GigaHub logs, there are "TR-069" remote configuration messages, and "ACSD" events that happen approximately at the same frequency/timing as this problem occurs (once/twice a day).

For now, we're just restarting the GigaHub every day as a temporary work-around, but the problem happens at least once a day.

Re: GigaHub 2.0 - Traffic on non-standard ports stops after a few hours

Vanadiel — Sat, 11 Oct 2025 20:53:21 GMT

What do you mean with private DNS on port 853?

Re: GigaHub 2.0 - Traffic on non-standard ports stops after a few hours

MrLim — Sat, 11 Oct 2025 21:26:59 GMT

Android phones have a private DNS feature that uses port 853. When this problem occurs, those phones get an error that the private DNS service is unreachable.

Re: GigaHub 2.0 - Traffic on non-standard ports stops after a few hours

Vanadiel — Sat, 11 Oct 2025 22:01:02 GMT

Ah, yes you are using TLS to establish an encrypted connection with the remote DNS server.

I thought you were running your own private DNS server.

Did you configure the client to use 8.8.8.8 in strict mode, or opportunistic mode?

I am thinking you loose connectivity overall because you loose the connection to 8.8.8.8, meaning you loose all DNS abilities.

If you have not already tried this, try to set the client to opportunistic mode. This way if the TLS connection fails for some reason, it will switch to regular non-TLS mode and you should be able to keep a working 8.8.8.8 connection.