MarvinAndro
Occasional Visitor
Christmas started with flashing 380.57 on my RT-AC68U and that killed all of my 2.4 clients. I reverted back to 378.56_2 and didn't have time to touch it until after the new year. Flashed again to 380.57 a couple of weeks ago and saw others also having issues on the 2.4 channel when IPTraffic was enabled. I can confirm that if I lose the ability to track device usage by IP, things work but that's not what I want.
About a month since 380.57 came out I though I'd ask if anyone found, and potentially fixed, the issue with IPTraffic - sorry if I didn't hit the post if one had already answered this.
I'm back to 378.56_2 because I also have the VoIP issues reported - multiple ATA devices, Android native SIP in the Dialer, Obi on voip.ms, GV, Fongo, GrooveIP.
Thanks! M
About a month since 380.57 came out I though I'd ask if anyone found, and potentially fixed, the issue with IPTraffic - sorry if I didn't hit the post if one had already answered this.
I'm back to 378.56_2 because I also have the VoIP issues reported - multiple ATA devices, Android native SIP in the Dialer, Obi on voip.ms, GV, Fongo, GrooveIP.
Thanks! M