The RT-N12 has a 100mbit switch so it's BCM5325 not BCM53115. From the driver code BCM5325 only has 16 total VLAN's so the modified switch-robo may crash it. _________________ Read the forum announcements thoroughly! Be cautious if you're inexperienced.
Available for paid consulting. (Don't PM about complicated setups otherwise)
Looking for bricks and spare routers to expand my collection. (not interested in G spec models)
I just tried it on my wrt300n v1.1 with a BCM5325E switch and it seems to work alright as long as I don't exceed the 16 VLAN limit. I didn't test too thoroughly though so there could still be problems. When I exceeded the 16 VLAN limit nothing happened right away and cat'ing the /proc/switch entries showed the port configs all being there, but a few minutes later after doing some stuff with vconfig all the port configs were wiped, the switch was unresponsive, but I still had access through wireless which is how you should connect when playing with VLAN's.
#startup script example
rmmod switch-robo
insmod /jffs/switch-robo.ko
echo "3 2 5*" > /proc/switch/eth0/vlan/0/ports
echo "" > /proc/switch/eth0/vlan/1/ports
echo "4t 5" > /proc/switch/eth0/vlan/100/ports
echo "4t 0 5" > /proc/switch/eth0/vlan/101/ports
echo "4t 1 5" > /proc/switch/eth0/vlan/105/ports
vconfig add eth0 100
vconfig add eth0 101
vconfig add eth0 105
ifconfig eth0.100 up
ifconfig eth0.101 up
ifconfig eth0.105 up
nvram set wan_ifname=eth0.100
startservice wan
Try it all through telnet/ssh first so that you can reboot if anything fails. The script should tag your WAN port (4) with VID 100/101/105, change your WAN port to be the VLAN 100 interface, put LAN port 4 (0) into VLAN 101, and put LAN port 3 (1) into VLAN 105.
Edit: I forgot the vconfig commands. _________________ Read the forum announcements thoroughly! Be cautious if you're inexperienced.
Available for paid consulting. (Don't PM about complicated setups otherwise)
Looking for bricks and spare routers to expand my collection. (not interested in G spec models)
Last edited by phuzi0n on Thu Mar 03, 2011 9:59; edited 3 times in total
Hi! i too have VF PT, and although i've been able to configure 3play on may draytek 2130Vn, i had to bridge one port to vlan 105 so to have IPTV, and leave the other router ports bridged on vlan 100 so to have Internet.
As some of you know, VF PT uses some sort of "magic" which allows the Thomson TG lan ports to work with different vlans at the same time (port trunking ?), switching them based on the type of device that is plugged in.
Now, the VF config file is hard to understand and draw visually, so i'm having a hard time to recreate it on my draytek (which uses linux - busybox 1.11.2). Some things that i've understood is that if you bridge the vlan 105 to one port, the STBs get a 10.x.x.x IP, but if you use VF TG router+config, you get a 192.168.x.x IP...another thing that i've noticed is that there are some DHCP options being used so to identify if it's a STB by using dhcp option 125 (need to read more about that one).
anyway...fggs, i've noticed that you're installing a module called switch-robo.ko...why...? for switching the vlans on a specific port when diff. devices are plugged in? or is it because your router can't support more then 16 vlans? making it simple: what is switch-robo for?
About my router:
- My draytek supports up to VLAN 4096 on WAN and 99 on LAN (that's the limit via config webpage, but not via busybox from what draytek informed me)
- My draytek cpu is a ARM926EJ-S based on Vitesse WebRocX
Okey...since you, fggs, seem to understand (at least partially...) what VF has done, could you please help me out with a diagram and/or tell me what i will need to make this work on draytek's busybox?
The switch-robo.ko is a patched module of Broadcom switch which allows routers with some broadcom switches to use vlans >16.
This is how TG784 from Vodafone works:
WAN port is tagged to all vlans (100, 101 and 105)
All lan ports are bridged like a normal router, so it gives internet only per default.
For IPTV to work, you will need to run a dhcp client on your vlan105 (or eth0.105, I don't how your interfaces are called) to get ip 10.x.y.z and then use a multicast proxy, like igmpproxy. Upstream would be vlan105 and Downstream would be br0 (lan bridge).
If configured properly, your tvbox will get an ip in "internet range" (192.168.1.X for example) but TV will work.
For Voip, I moved one of the ports to vlan101 and plug TG784 router there, so I can take advantage of RJ11 port.
I have also VF PT fiber ISP, and have a linksys wrt320n working with the 3 vlans (100,101,105) on the wan port, and the internal ips (192.168.1.0) making nat to those vlans.