you tell you put a switch between and it works. so you still have the tagged / untagged thing. or do you let do the switch the tagging thing?
i have vlan7 tag and vlan8 tag same time on wan port.
you can use both dd-wrt routers. so one will do the iptv thing and the second does the internet traffic. i am doing this like the same way. _________________ RT-N66U @ Build 25697M K3.10.63
TL-WR842ND v1 @ BS-build 23919 WDS AP
TL-WR841ND @ BS-build 23919 WDS Client
TL-WR841ND @ BS-build 23919 Client Bridge ( Routed )
you tell you put a switch between and it works. so you still have the tagged / untagged thing. or do you let do the switch the tagging thing?
Yes, it works, because ISP cable goes to the switch, from the switch one cable goes to WAN and second to tagged vlan 6 port 3. Port 3 act like a tagged dd-wrt switch port. Then i can connect to port 1 or port 2 IPTV box for TV or computer and watch channels...
Putting switch between ISP and DD-WRT is only workaround... I want to do right.
I hope, you understand me
BasCom wrote:
i have vlan7 tag and vlan8 tag same time on wan port.
you can use both dd-wrt routers. so one will do the iptv thing and the second does the internet traffic. i am doing this like the same way.
As I said, I want to do it right...
From that, what I have tried, if I make WAN port tagged - WAN port cannot get internet IP address... As I understand dd-wrt cannot work as tagged port with untagged traffic...
so, if you have a solution, and dd-wrt cant handle what you want, what will be left? : live with the solution.
you can check your vlan config with
cat /proc/switch/eth0/vlan/2/ports
in telnet
you may also add * to the 5 in vlan2. that means: default vlan for untagged packets. but that means no untagged traffic will go through your default (main) vlan. making your network beeing alive you need to use tags for all clients. _________________ RT-N66U @ Build 25697M K3.10.63
TL-WR842ND v1 @ BS-build 23919 WDS AP
TL-WR841ND @ BS-build 23919 WDS Client
TL-WR841ND @ BS-build 23919 Client Bridge ( Routed )
so, if you have a solution, and dd-wrt cant handle what you want, what will be left? : live with the solution.
maybe...
BasCom wrote:
you can check your vlan config with
cat /proc/switch/eth0/vlan/2/ports
in telnet
In E900 router there is no such directory /proc/switch ...
Code:
root@DD-WRT:~# cat /proc/s
self/ slabinfo stat swaps sys/ sysvipc/
BasCom wrote:
you may also add * to the 5 in vlan2. that means: default vlan for untagged packets. but that means no untagged traffic will go through your default (main) vlan. making your network beeing alive you need to use tags for all clients.
try with your second dd-wrt router.
maybe your managed switch can do port mirroring? so you can connect a pc to that mirrored port and do some sniffing with wireshark. you can watch the vlanid´s in ethernet frames. then you´re not longer guessing _________________ RT-N66U @ Build 25697M K3.10.63
TL-WR842ND v1 @ BS-build 23919 WDS AP
TL-WR841ND @ BS-build 23919 WDS Client
TL-WR841ND @ BS-build 23919 Client Bridge ( Routed )
try with your second dd-wrt router.
maybe your managed switch can do port mirroring? so you can connect a pc to that mirrored port and do some sniffing with wireshark. you can watch the vlanid´s in ethernet frames. then you´re not longer guessing
yes, lastest...
I will try both your suggestions...
I'm think, I'm not guessing, because if I tag traffic on my managed switch for vlan2 and vlan6, router WAN port get's IP address of tagged vlan2 traffic and computers on ports 1, 2 and 3 get's IP adresses from vlan6 tagged traffic. So as I said - dd-wrt cannot work with untagged traffic... Or I missing something... I don't know...
And on my second router (610nv2) there is cat /proc/switch/eth0/vlan/2/ports, but empty. Somewhere I have read, that on gigabit routers, these files are empty or showing as empty...
because if I tag traffic on my managed switch for vlan2 and vlan6, router WAN port get's IP address of tagged vlan2 traffic
so, your internet traffic is tagged , too ? you told, it is not
confused.
/proc/switch/eth0/vlan/2/ports in wrt610 should contain the wan port and cpu (guess 0 and 8 )
and there you can recheck for nvram vlan config normally
your case vlan6 dir should contain 4t 1t 2t 3t 5 like it is set in nvram _________________ RT-N66U @ Build 25697M K3.10.63
TL-WR842ND v1 @ BS-build 23919 WDS AP
TL-WR841ND @ BS-build 23919 WDS Client
TL-WR841ND @ BS-build 23919 Client Bridge ( Routed )
because if I tag traffic on my managed switch for vlan2 and vlan6, router WAN port get's IP address of tagged vlan2 traffic
so, your internet traffic is tagged , too ? you told, it is not
confused.
No, my internet traffic is not tagged. I have managed switch for testing purposes. And I test router functionality with that switch. I can't leave my family without internet and IPTV in time when I'm testing
And as I said, when testing with managed switch if I tag vlan2 traffic, then WAN port get's IP address, if I leave it untagged, then WAN doesn't get IP....
BasCom wrote:
/proc/switch/eth0/vlan/2/ports in wrt610 should contain the wan port and cpu (guess 0 and 8 )
and there you can recheck for nvram vlan config normally
your case vlan6 dir should contain 4t 1t 2t 3t 5 like it is set in nvram
As I said in my last post, I have read somewhere, that on gigabit routers(as my 610nv2), these files(i.e. /proc/switch/eth0/vlan/2/ports) are empty or showing as empty...
And as I said, when testing with managed switch if I tag vlan2 traffic, then WAN port get's IP address, if I leave it untagged, then WAN doesn't get IP....
i do not understand at all.
obviously you need vlan2 to be tagged for ISP internet WAN address, but you wrote it need to be untagged ? _________________ RT-N66U @ Build 25697M K3.10.63
TL-WR842ND v1 @ BS-build 23919 WDS AP
TL-WR841ND @ BS-build 23919 WDS Client
TL-WR841ND @ BS-build 23919 Client Bridge ( Routed )
