Hello!
Thanks so much for this thread! I thought i was going mildly crazy before I found it! I've been encountering very similar issues resulting in Skype apparently overloading the Superhub and stopping it processing all traffic for 1-2 minutes, resulting in a brief internet outage. Very frustrating after initially being super excited about Virgin Media rolling out faster broadband in our area, then discovering that actually my previous fibre service appeared far more reliable. (Uno, Plusnet never had these issues).
I couldn't replicate the exact symptoms that caused Skype to do this, but while investigating this one thing I did find I could replicate 100% of the time is making the superhub become unresponsive at 192.168.100.1, and 192.168.0.1 (Running in modem only mode) by sending many DNS requests.
To replicate:
- Open a terminal window and ping the superhub, ping 192.168.100.1 (keep it open!)
- Launch a loop of constant DNS requests, in unix: while ( true ) do host www.google.co.uk 1.1.1.1; done
- Boom - the first terminal window will stop responding to ICMP pings within a few seconds.
Note: Thanks & Apologies to Cloudflare for the DNS spam during my testing (owners of 1.1.1.1) but I think you can take it! 😉
Make sure you cancel the loop of DNS requests - your modem will recover but most of the time not immediately, it seems to take it a good while to 'get over' having a high number of UDP packets thrown through it. During this time the modem management page will be intermittent or unavailable.
I managed to escalate this to VM, and one of their clever folks has replicated this in the lab, and so will log it with the Superhub vendor. It appears to affect Superhub3 and Superhub 4 (I've tried both). VM are sending me a Superhub 2 AC, so I'm hopeful I'll then get stable connectivity for a while until a new firmware is released!
I'm hoping this issue, and the poor UDP handling issue / Skype dropouts are linked, and so both get fixed! 🙂