TomatoUSB

Hi:

I am in need of VLAN tagging so replaced my Tomato 1.28 image with Shibby's tomato-ND-1.28.5x-102-VPN.trx image (K24 folder). I picked a 2.4 image as I wasn't sure that my WRT54GSv2 would support a 2.6 kernel and didn't want to risk bricking my router (thought I read that on a DD-WRT forum).

Anyway, on the VLAN page, the 'Tagged' check boxes are disabled. Is this a limitation with my chosen image or a hardware limitation? Am I safe to go ahead and install tomato-K26USB-1.28.RT-MIPSR2-102-AIO.trx (even though my router doesn't have a USB port)?

Thanks,
Pab

Hi:

Just following up to provide a word of warning. Based on the statement "Older MIPSR1 routers are also supported" I read on shibby's top download directory (under the K26 heading) in combination with my router's entry on the router list, I thought I understood that the WRT54GSv2 was supported by the K26 builds. I decided to upgrade to tomato-K26-1.28.RT-MIPSR2-102-Max.trx. Bad move… as this bricked my router. Maybe it seems like an obvious mistake now, but anyway…

I tried a number of the recovery methods documented around the net (though no JTAG or pin shorting), but have had no luck in recovering. Again, just a friendly warning.

Pab

Well, I got lucky. I tried pin shorting and managed to revive the router and flashed it with a basic Tomato 1.28 so I'm sort of back to where I started. Given that I'm trying to get VLAN tagging working, which build should I use? Is there a good K26 option for me? Or should I only use a K24 build (as before) and try and sort out the missing 802.1q module manually? Any help would be very much appreciated.

Thanks,
Pab

I've now successfully upgrade to tomato-K26-1.28.RT-MIPSR1-101-Max.trx build (so why no MIPSR1 102 builds?), but the VLAN tagging check boxes are still disabled. Running a 'modprobe 8021q' from the command line is still reporting 'module not found in modules.dep'. Any suggestions what to do next? Pretty please, with sugar on top! :)

In my ongoing quest, I viewed the source for page advanced-vlan.asp and notice that the trunk_vlan_supported javascript variable is the key here. It is only set to true for the following hardware:
case '0x0467': // WRT54GL 1.x, WRT54GS 3.x/4.x
case '0x048e': // WL-520GU, WL-500G Premium v2
case '0x04ef': // WRT320N/E2000
case '0x04cf': // WRT610Nv2/E3000, RT-N16
case '0xf52c': // E4200v1

So then I ran 'nvram get boardtype' on the router and got back '0x0318'. More googling and I came across the dd-wrt's VLAN page where it claims VLAN tagging is indeed supported by the WRT54GS V2 (I'd post the link, but I am denied from doing so). So, I was tempted to go ahead and do a little hacking to try this out, but it looks like the page is in a read-only filesystem. Of course, even if I hack the web page to force this through, will that be enough?

Just documenting things as I discover them.

Pab