QUOTE(tertiary @ Jan 15 2017, 09:50 PM)
Did you get a 404 error when trying to get to the web interface? I had that in Chrome although it had worked fine until the latest flash. Changed to Firefox and I could log in as usual.
Nope, it just never connected to the router in the first place. I decided not to try Shibby and go with Toastman and it worked fine. Setting VID 500 and tagging WAN was working perfectly fine. So for anyone with the RT-N18U, give Toastman a try.
QUOTE(lamode @ Jan 18 2017, 07:58 PM)
hmmm.... could it be some config issue with VID offset?
when the VLAN2 with VID500, did you use 496 VID offset?
i think it's worth to try set VLAN2 with VID500, and disable the VID offset...
I actually don't know what it could be as I tried doing various things to fix it. Even tried doing a full NVRAM wipe, and then setting VID offset but still my router was inaccessible. Did the same thing and just set VID straight to 500 and no connection. I gave up and tried Toastman's build and it worked perfectly fine so the problem is probably in Shibby's build.
QUOTE(jio @ Jan 19 2017, 03:09 PM)
I can confirm Shibby build don't have the 4K VLAN properly supported for BCM53115. Toastman build works till RT-VLAN 7508.2 & RT-N-VLAN 0508.2. 7509/0509 onwards had Shibby code base merged to it & 4K VLAN for BCM53115 no longer working. You can try to submit bug or contact toastman or shibby to fix it. The code file bcmrobo.c.
So probably time to say goodbye to tomato firmware. I don't recommend tomato for anything other than Broadcom MIPS platform anyway. No point supporting newer hardware (issues with hardware accelerations, wifi power amp, etc) if it is poorly supported.
Yea, I wen't with Toastman's build and now things are working fine. I wouldn't say Tomato firmware doesn't work well with our ARM devices. Just have to find the right build I guess.
But oddly enough, I tried DD-WRT and the same issues were happening