Hub 3.0 crashes when using specific software - nothing in network log

[SmartyUK]

Hi, 

I have for the past 7 months been frustratingly trying to use Ableton on my computer whilst connected to my home network.

When I boot it up, the Hub completely crashes after a few seconds. Every time. WiFi drops out for all devices in the household and I then have to use the software with my WiFi off on my machine.

There is nothing in the network log on the router itself to suggest what the issue might be. I thought it was my MacBook itself causing it, or network flooding etc.. but I've used the same MacBook and the same software on other networks and it runs perfectly elsewhere. 

I have been in comms with Ableton support also on this back and forth for months and the issue is not theirs to solve. I've turned off auto updating and everything to reduce the network load from the application. 

Q's

1 - has anyone else experienced this? With any software, not just Ableton?

2 - if yes.. how did you solve it? Is it an IPv4 vs IPv6 problem maybe? or something more intricate? 

Any help much appreciated. 

Edit: Yes -  I have performed the pin hole reset a number of times to no avail 

[SmartyUK]

Network log attached - I last made it crash at 20:35 tonight and as can be seen, there is no network log of the activity.

Time Priority Description

22/07/2024 20:30:40	Warning!	LAN login FAILED : Incorrect Username / Password / ConnectionType;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
22/07/2024 02:44:34	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
21/07/2024 19:36:23	Error	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
19/07/2024 02:23:7	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/07/2024 07:36:23	Error	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
16/07/2024 07:53:39	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
14/07/2024 19:36:23	Error	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
11/07/2024 23:24:20	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
11/07/2024 07:36:23	Error	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/07/2024 00:01:28	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
07/07/2024 19:36:23	Error	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
04/07/2024 20:36:31	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
04/07/2024 17:15:7	Error	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/07/2024 01:31:7	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/07/2024 01:20:38	critical	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/07/2024 01:19:4	Warning!	Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/07/2024 01:18:59	Warning!	RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/07/2024 01:18:59	critical	SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/07/2024 01:18:59	Warning!	RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/07/2024 01:18:58	critical	SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

[Sephiroth]

When you boot what up?  The Hub (which model?) or the Mac?

[Client62]

It is a Hub 3, perhaps using it in Modem mode with an external Wi-Fi Router would help.

[Sephiroth]

We still don't know what the OP is actually reporting.  I'll ask again:

The Hub (which model?) crashes when what is booted?  The Hub or the MacBook?  And what does "completel crashes" mean?  We understand that there is loss of WiFi; are the SSIDs still advertised?  If a USB adapter to RJ45 is used, and the MacBook connected to the Hub by Ethernet, does the connection work?

What is the "Ableton" connection with all this?  Does the crash occur only when Ableton is loaded in the MacBook?

[Sephiroth]

Ah - the OP has posted this elsewhere n the forum:

"I have a similar issue whereby a piece of music software I have (Ableton) nukes my network as soon as it’s loaded - moments after I quit the program, the network recovers. 

I can happily use the program online via my phones hotspot so it’s not a data/bandwidth challenge as far as I can see but I’m yet to find a solution that points to a router setting that’s causing this. 
edit: yes I’ve spoken to Ableton support and have turned off all automatic updates and sending of data usage etc to see if this solves it however it’s still an issue "

So, my principal question has been answered.  The Hub doesn't actually crash; when Ableton is loaded things go wrong (need to go into this); when Ableton is closed on the MacBook, the "network recovers".

The OP should note that the Forum Team won't be able to resolve this because third party equipment and software seems to be at the root of this.  So it will be down to the Community to try and assist with the problem.

In that case, information is everything because we are remote and the OP knows what's going on.  Perhaps we can start with a full description of "nukes my network" etc.  Does "recover" mean that the Hub does not need rebooting? etc.