Forums › Forums › CQ Forums › CQ troubleshooting › Disconnecting on ethernet
- This topic has 3 replies, 2 voices, and was last updated 3 months ago by Mark.
-
AuthorPosts
-
2024/08/23 at 10:49 pm #124990MarkParticipant
Using the Ethernet cable with a switch cq20b. DHCP provided by TPLink AX3000 range extender. We just started using using this wifi6 extender over the TPLink AC model. We disconnect sometimes within seconds, but always within just a few minutes.
After playing around some found that connecting to a different network (dhcp provided by a different router) the problem did not happen. Connecting back to the switch with the AX300 providing dhcp, the problem occurs again. When we assign a static IP address, there is no issue.
Would prefer not to be using a static address as sometimes we do want to attach to other networks.
2024/08/25 at 3:08 am #125008MarkParticipantUPDATE: I found that these devices have a dhcp lease time of 1 minute. So it would disconnect each time the lease is renewed. Obviously that is a ridiculous lease time. I increased it to 2 days and no more disconnections.
However I don’t think the app should disconnect when the lease is renewed. Smallish issue but you might wanna check it. Could add to people perceptions of disconnections if a lease time is short.
2024/08/26 at 1:30 pm #125045BrianParticipantI think you have a misunderstanding of how DHCP leases work. When the time expires, the connected device can no longer use that IP address and has to renegotiate with the DHCP server to get a “new” IP address – even if it end up being the same address it was previously assigned. Of course the device is going to loose connection to the console during this process. A&H has long felt that when a device looses it’s connection with the console, that it should reload ALL of the data and not make assumptions about what might have changed or not changed. It’s really the only way to handle it.
Furthermore, the lease time is set on the DHCP server, so that setting isn’t something related to the A&H system. It was a network setting out of their control that was giving you problems.
2024/09/03 at 5:19 pm #125252MarkParticipantI noted in my post that the lease time was ridiculous. Of course the short lease time is not within Allan and heath control and that with an appropriate lease time this is a small issue.
However, the mixer is very aware of the lease. Its up to the mixer to handle its lease. And it does this fine at least to the point it requests a new one as expected. But when the renewal is requested and granted at 50% or even 87.5% of the lease expiration time and the new lease is granted with the same IP address why would there ever be a disconnection? The lease did not expire and was never released.
You may need to read up on dhcp. Tcpip can perform this seamlessly so that we do not experience disconnection. I believe even if the address changes there is no reason to disconnect. This would be very annoying in every dhcp network if things just disconnected.
Mark
-
AuthorPosts
- You must be logged in to reply to this topic.