What's new
  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

380.57 - Turning on IP Traffic soft-bricks AC56U?

apf888

New Around Here
Has anyone gotten IP Traffic working on the AC56U (HW A1) using 380.57? The minute I turned on the setting in the UI, all the front LEDs turned off except for the power LED and it literally played dead (and stayed that way) even after power cycle or holding down reset for 5s. (this seems to happen regardless of whether the clear IP Traffic data flag is set or not).

The only way I got it back up was by following these instructions here and reloading the TRX file via TFTP (though I suspect it might've been just that it forced the NVRAM to clear somehow).

So after turning on IP Traffic three times and having to reload the firmware three times (with the last time literally happening after a reload, factory reset from the menu, then going straight to the IP Traffic setting), I ended up having to leave it off turned off... (since this needed to be up and running today) o_O

Meanwhile, I have a bunch of AC66Us with IP Traffic enabled, all of which are working fine (though only one of them is actually at 380.57). Maybe it's an ARM thing? (since AC56U and AC68U are ARM units and there's something already known going on with the AC68U and its wireless?)
 
Has anyone gotten IP Traffic working on the AC56U (HW A1) using 380.57? The minute I turned on the setting in the UI, all the front LEDs turned off except for the power LED and it literally played dead (and stayed that way) even after power cycle or holding down reset for 5s.

Once the router crashed. It's auto reboot could end up in a funky state as you described. I don't exactly know why but maybe if I had left it alone for half hour it would sort out by itself. Anyway I never have that patience or in the first few times when it happened, panic mode urged me into rescue mode to flash a good firmware.

Back to your crash. I think I saw from some users log that 380.57 for ac56u has new Ethernet driver but old wireless driver. This mix and match probably yields to more scary symptom than ac68 with both new drivers and only losing 2.4ghz.

One thing you can try if haven't is to manually disable HW NAT. Reboot and then turn on IP Traffic.

You may have luck and lose nothing. Since Ip traffic will disable HW NAT anyway.

Or else I'm afraid you need to revert back to a prior version. BTW 378.55 is rock solid for me. You may consider .56 if it has a new feature that you need there.
 

Similar threads

Latest threads

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!

Members online

Back
Top