Erik, I went down the Rabbit hole over the past week... First and foremost, 384.9 is awesome and very stable in my use when removing variables that I personally inject. I have about 35 clients connecting across a client (media) bridge with an AP to repeat on non-conflicting channels. With DD-WRT this is perfectly stable 100% of the time, but as I've mentioned, with limited functionality as DD-WRT client bridge is not a true transparent bridge, meaning clients connecting to the AP show as the same mac address as the MB in the middle and that confuses some of the enhanced functionality.
I mentioned in the Beta post that I was so pleased with the stability of 384.9 that I may try resetting the MB (AC68P) to it in order to see if stability existed there as well... it doesn't. Within 12 hours, DHCP requests still fail, which I've gone as far as capturing logs from router, MB, and AP elsewhere in this forum, but without the expertise to come to any root cause. I then loaded John's fork, which surprisingly was more stable on the MB sandwiched between a router and AP running 384.9 (AC86U and AC3200 respectively). I would start to see drops after 12 hours though on random clients where DHCP would not be able to obtain an IP address. This was most obvious on a mobile client exiting and entering WiFi range.
Then came Tomato and ultimately back to DD-WRT. Though functionality is reduced as the mac address of AP connected clients are rewritten to that of the MB, this firmware has been rock solid. Take heart in the crazy amount of RTFM you see and know that this is a great go to build that I recommend. DCD errors are not your problem and a workaround to scrub them exists. Non-reproducible errors are expected, but I believe they are less this time around than with other builds. Anyway, great work and thank you and also this whole community.
I mentioned in the Beta post that I was so pleased with the stability of 384.9 that I may try resetting the MB (AC68P) to it in order to see if stability existed there as well... it doesn't. Within 12 hours, DHCP requests still fail, which I've gone as far as capturing logs from router, MB, and AP elsewhere in this forum, but without the expertise to come to any root cause. I then loaded John's fork, which surprisingly was more stable on the MB sandwiched between a router and AP running 384.9 (AC86U and AC3200 respectively). I would start to see drops after 12 hours though on random clients where DHCP would not be able to obtain an IP address. This was most obvious on a mobile client exiting and entering WiFi range.
Then came Tomato and ultimately back to DD-WRT. Though functionality is reduced as the mac address of AP connected clients are rewritten to that of the MB, this firmware has been rock solid. Take heart in the crazy amount of RTFM you see and know that this is a great go to build that I recommend. DCD errors are not your problem and a workaround to scrub them exists. Non-reproducible errors are expected, but I believe they are less this time around than with other builds. Anyway, great work and thank you and also this whole community.