Unifi unifi & tomato firmware -- possible?
|
|
 Jan 15 2017, 06:01 PM
Return to original view | Post
#1
|
 
Junior Member
137 posts Joined: Dec 2008 From: Somewhere between my chair and computer  
|
So I have been trying to get tomato or DD wrt to work on my Asus RT N18U with Unifi but no luck. I used to use it with TIME without a problem but now with this VLAN tagging stuff, I just can't get it to connect to WAN. I have created a VLAN2 with VID as 500 and set it to the WAN port and still nothing. I have double checked my Unifi login credentials and everything is correct. The stock firmware works fine but tomato doesn't. Any ideas?
|
|
|
|
|
|
Jan 15 2017, 08:05 PM
Return to original view | Post
#2
|
|
Junior Member
137 posts Joined: Dec 2008 From: Somewhere between my chair and computer
|
QUOTE(tertiary @ Jan 15 2017, 07:04 PM) Which Tomato build number are you trying, and which flavour - Shibby or Toastman? I am running Shibby build 138. |
|
|
Jan 15 2017, 08:35 PM
Return to original view | Post
#3
|
|
Junior Member
137 posts Joined: Dec 2008 From: Somewhere between my chair and computer
|
QUOTE(tertiary @ Jan 15 2017, 08:31 PM) I tried that build on my Netgear router and couldn't get Unifi to work. Maybe there's a VLAN problem with that build (and 137 also didn't work). I tried the same thing. Reverted to build 132 and do VID offset but my router wouldn't boot to the admin interface anymore. The LEDs turn on but I couldn't actually access anything.I reverted to build 132 and used the VLAN ID offset method detailed above and internet works (but not HyppTV). I am gonna try Toastman's build to see if it works. Will report back if all goes well. |
|
|
Jan 21 2017, 01:41 PM
Return to original view | Post
#4
|
|
Junior Member
137 posts Joined: Dec 2008 From: Somewhere between my chair and computer
|
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? 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.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... 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. 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.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. But oddly enough, I tried DD-WRT and the same issues were happening |
| Change to: |  0.0166sec
 0.22
 7 queries
 GZIP Disabled
Time is now: 7th December 2025 - 07:18 PM |
Quote