Hi there. I just wanted to point out/ask about vlan performance on latest shibby. I have noticed that my gigabit lan speeds drop to 125 mbit/s (in my case, on WNR3500Lv2), form the expected usual ~930 mbit/s. I assume(d) this is due to it being handled by the cpu, in the ip stack, as opposed to the layer 3. Losing 85+% efficiency is a drag, making it rather pointless with vlans for all gigabit scenarios. I just wanted ot doublecheck or have it confirmed this is the reason and not just my model, or implementation issues? I guess I can try to disable some ip filtering on the bridge or so, (like in xen), but not sure if this will make the system insecure/pointless. Haven't tested yet so this is just thrown out here. On a positive side, I started with xen and am amazed (a xen setup will take over the router's job). However, I still wished to vlan a domain guest private server with the router (which will function as 2nd firewall => LAN + wifi), alternatively adding the wifi to a forward bridge (on the xen machine, in front of the router). I guess none of those will work, apart from the vlan, but which will most likely create the same cpu overload/slowdown as mentioned above, right? :/ Would love to have someone join in a bit on the vlan testing, just in case, it *could* be resolved (disabling bridge netfilter, issues... other ideas). Finally, I will use virtual bridges in xen to do tagged vlans possibly and thus, would perhaps think of trunking to the tomato... Again, on the WNR3500Lv2, this is *experimental* by victek is it? However, when I try to load a kernel module 8021q, it does not exist on the router... so just how does that work on tomato then? Cheers, lolziecat (PS. I think the same issues happened on locally compiled tomato + victek version so it's not just shibby but our kernel overall etc).