CCTV suddenly being blocked
My CCTV has run via the Hub 3 on 192.168.0.20 for many years, all of a sudden I can no longer access it locally from by browser whilst connected to my wifi. The app still works on wifi but it no longer lets me connect to the CCTV over mobile data anymore either - it used to previously so guessing something has stopped it in the settings. I remember the CCTV guy saying it was using port forwarding or something. Is there some setting that could be blocking it?
Hub 4 TLS Latency with Firewall Enabled (Firmware 01.04.092.07.16) — Consistent 5s Handshake Delay
Posting to document and seek advice on a consistent issue I’m experiencing with a Virgin Media Hub 4 running firmware 01.04.092.07.16.EURO.PC20. Summary of Fault: When the firewall is enabled on the Hub 4, there is a consistent 5+ second delay during the TLS handshake phase for HTTPS connections. This occurs on all sites and has been replicated using curl, browsers, and diagnostic tools across multiple devices. When the firewall is disabled, TLS handshake times return to normal (100–200 ms), and all delays disappear. This behaviour is identical to the one reported in Community Thread ID 5475086, which attributes the issue to firmware 01.04.092.07.16 and confirms that it is resolved in firmware version 01.04.100.xx.xx.EURO.PC20 or by switching to a Hub 5. Technical Diagnostics (example curl results): With firewall ON: DNS lookup : 0.006204s TCP connect : 0.006792s TLS handshake : 5.094022s Server proc. : 5.152472s With firewall OFF: DNS lookup : 0.010297s TCP connect : 0.011480s TLS handshake : 0.103843s Server proc. : 0.151060s No DNS changes or browser settings affect this. The delay is introduced at the router level and consistently impacts every HTTPS request. Actions Taken: Factory reset of the Hub 4 Wired and wireless testing across multiple machines Replicated issue on different OS and network stacks Rebooted between firewall toggles What I Need Help With: Can anyone confirm the latest firmware version for the Hub 4 and whether they’ve received 01.04.100 or higher? Has anyone else on M350 or below had this resolved via firmware push or Hub 5 swap recently? Can any Virgin Media staff confirm if this fix is being actively rolled out or applied on request? Complaint reference already raised: C-0506256775 Thanks in advance to anyone who can shed more light. Happy to provide additional logs if useful. – K