Hello,
We have two AC-RT68U routers with the most recent released Merlin firmware (380.65) and have been having some consistent issues with WDS. This may or may not be an issue with the firmware, per se, but perhaps some changes to the firmware could help with it.
The problem is periodic disconnects, typically about twice a day or so, of the link between the two routers. All of the normal setup recommendations have been followed, and WDS generally works very well, except that it will randomly disconnect. It will always reconnect, but it always takes 8-10 minutes to do so. This was measured by writing a shell script on one of the client machines to monitor the connection and determine the frequency and length of the outages. The link is on 5GHz, and I've tried various bandwidths (40 and 80MHz), and both upper- and lower-band channels, and the result is the same - one or two disconnects per day which take 8-10 minutes to reconnect on their own. I have not tried putting the link on 2.4GHz, as 2.4GHz is far too crowded in this location.
I'm currently running some experiments with router placement to see if the disconnects are related to interference or to something in the internal implementation. In either case, however, while occasional disconnects can occur in the real world, the real problem is that it is taking 8-10 minutes for the routers to notice that the connection is down and reconnect. Generally, if a laptop or other client disconnects for some reason, the driver or firmware notices immediately and attempts to reconnect.
So here's the feature request part. There appears to be some process or loop in the router that eventually notices that the WDS link has gone down and reconnects it, but would it be possible to pull this checking in from ~10 minutes to something at least in the order of a few seconds, similar to what occurs on most clients when they lose a connection. I don't know if the detection of the link being down is handled in the firmware or in the hardware, so there may not be anything that can be done, but I thought I would throw it out there and ask.
Thanks..
We have two AC-RT68U routers with the most recent released Merlin firmware (380.65) and have been having some consistent issues with WDS. This may or may not be an issue with the firmware, per se, but perhaps some changes to the firmware could help with it.
The problem is periodic disconnects, typically about twice a day or so, of the link between the two routers. All of the normal setup recommendations have been followed, and WDS generally works very well, except that it will randomly disconnect. It will always reconnect, but it always takes 8-10 minutes to do so. This was measured by writing a shell script on one of the client machines to monitor the connection and determine the frequency and length of the outages. The link is on 5GHz, and I've tried various bandwidths (40 and 80MHz), and both upper- and lower-band channels, and the result is the same - one or two disconnects per day which take 8-10 minutes to reconnect on their own. I have not tried putting the link on 2.4GHz, as 2.4GHz is far too crowded in this location.
I'm currently running some experiments with router placement to see if the disconnects are related to interference or to something in the internal implementation. In either case, however, while occasional disconnects can occur in the real world, the real problem is that it is taking 8-10 minutes for the routers to notice that the connection is down and reconnect. Generally, if a laptop or other client disconnects for some reason, the driver or firmware notices immediately and attempts to reconnect.
So here's the feature request part. There appears to be some process or loop in the router that eventually notices that the WDS link has gone down and reconnects it, but would it be possible to pull this checking in from ~10 minutes to something at least in the order of a few seconds, similar to what occurs on most clients when they lose a connection. I don't know if the detection of the link being down is handled in the firmware or in the hardware, so there may not be anything that can be done, but I thought I would throw it out there and ask.
Thanks..