I have a RT-AC66U setup as a media bridge between my Google Fiber router and my firewall. This is a temp setup while I have construction going on in the basement.
I set this up back in I think August running Merlin 380.65_2...I think. All was working great for a few months. Then came along KRACK which I wanted to mitigate so I went back to Asus-WRT 380_8120 to get the latest fix since it wasn't yet ported over to Merlin. That went off without a hitch on my N66U and my AC66U.
Jump forward a couple of weeks later and my AC66U now has developed a once a week issue where it just stops forwarding traffic across the bridge. Link shows up, Google shows the client connection, but no traffic is being forwarded without a reboot of the AC66 which restores service for a week or so.
I can't say that a MUST have the KRACK fixes on my AC66 since it services outside the firewall which in theory is already encrypted via TLS or IPSEC. I just generally try to run my N66 and AC66 on the same code and the N66 needs the updates since it sits inside the firewall with internal protocols exposed that are not natively encrypted.
I am getting ready to update to Merlin 380.68 which should include the KRACK fixes for *66U devices. Hoping the bridge stability returns as well. Any ideas and/or suggestions on what may have introduced the instability to a previously stable environment within that last update?
I set this up back in I think August running Merlin 380.65_2...I think. All was working great for a few months. Then came along KRACK which I wanted to mitigate so I went back to Asus-WRT 380_8120 to get the latest fix since it wasn't yet ported over to Merlin. That went off without a hitch on my N66U and my AC66U.
Jump forward a couple of weeks later and my AC66U now has developed a once a week issue where it just stops forwarding traffic across the bridge. Link shows up, Google shows the client connection, but no traffic is being forwarded without a reboot of the AC66 which restores service for a week or so.
I can't say that a MUST have the KRACK fixes on my AC66 since it services outside the firewall which in theory is already encrypted via TLS or IPSEC. I just generally try to run my N66 and AC66 on the same code and the N66 needs the updates since it sits inside the firewall with internal protocols exposed that are not natively encrypted.
I am getting ready to update to Merlin 380.68 which should include the KRACK fixes for *66U devices. Hoping the bridge stability returns as well. Any ideas and/or suggestions on what may have introduced the instability to a previously stable environment within that last update?
