I enabled repeater bridge mode on my R8000 with the most recent kong mod firmware, and its broken my router.
I've tried the resetting procedures but it just keeps bootlooping..
It pings for a few seconds on boot, I hope i can tftp a factory image to reset it, or its time to find the serial cables :(
I couldnt reset it with the button, it was kernel panicing, I needed to use a serial cable to fix it :(
Can I ask what was the fw date you used? I'm about to load the fw into my R8000 becuase I want to use it as a repeater. I saw that there is another version from december on the desipro website. This will be my first time loading a DDWRT fw onto a router.
See the subject of the thread :)
The ident from the router including build#
Firmware: DD-WRT v3.0-r30880M kongac (11/14/16)
Althought i downloaded it from the post titled
https://www.myopenrouter.com/download/dd-wrt-kong-mod-netgear-r8000-2016...
I'd make sure you have a 3.3V Serial Cable working with it before you try bridge mode..
I'm having real problems with it as an AP too, with broken IPv6ND on my wifi.
Thanks and no I don't have a serial cable nor I have used one which is why I want to find a stable fw for repeater mode. Like I said, i have never flashed a router and the only reason I'm considering it is because in the offcial fw the repeater mode option has been disabled. I wanted to upgrade my current repeater to something more powerfull.
in the desipri page there is a december uploaded version but IDK if its a new one or the same november one you used.
I can confirm this also happens (kernel panic) on Repeater mode on the very latest 2017 January release that I tried.
It seemed initially to appear to work but the panic actually happened to me as soon as I set the wifi ssid's to use a password in WPA Personal 2 mode. Having wifi enabled in 'open' mode just isn't going to fly so I had no choice but to recover the R8000 via serial debug cable and then reflash the original Netgear firmware.
If I get some free playtime I may rebuild the entire stack from source-code and debug the problem to see why its crashing. Probably something very stupid...
thanks for letting us know, hope you can find the issue o your free time so we can use this great feature! :)