Posted: Sun Jan 10, 2016 10:58 Post subject: DD-WRT v3.0-r28493 (12/10/15) - TP-Link TL-WR841ND v9
Hi there,
I can confirm this issue in all builds I ever tested on my router.
And can also confirm that the above two lines are fixing the communication issues between LAN ports, BUT is generating other issues: like open your LAN to WAN completely, that's a big security risk for me!!
So this is NOT a solution, from my point of view.
If someone has some idea on how to fix the communication issues between LAN ports please post it here.
Someone had an interesting comment on facebook about this issue:
"by default it bridges the ETH and WLAN ports. But if you check AP insulation or guest mode - then you will have this situation."
Posted: Wed Jan 20, 2016 16:39 Post subject: DD-WRT v3.0-r28882 std (01/19/16) on TL-WR841N-v9
Hi,
I can cornfirm this issue on my router.
The lines that have solved the problem in my router are as follows:
Code:
swconfig dev switch0 set enable_vlan 1
swconfig dev switch0 set apply
The difference with the above is replacing eth1 by switch0, and I think that is the source of the bug.
I have left as a startup script and everything ok.
I seem to have found some solution and I sent it to BrainSlayer for testing and deployment if it is stable enough. For those of you who don't bother trying, do execute on a telnet or ssh console the following and share experience. For me it does work.
Code:
swconfig dev eth1 set enable_vlan 1
swconfig dev eth1 set apply
Thanks for this! It didn't quite work as-is for me, but with some sleuthing it set me on the right track! For anyone else who's having this issue (specifically for me on a TP-Link WDR3500) and tries the above solution only to get an error about being unable to connect to switch, try running ifconfig to see if there's more than one ethernet device on the router, and try a different one. For me, I had to do:
Code:
swconfig dev eth0 set enable_vlan 1
swconfig dev eth0 set apply
And now it works after I've added it to startup!
Thanks! I switched the code from eth0 to eth1 on my Tl-841n and started to work immediately!
This is still a bug on tplink 841NDv9 running 12/15/2016 firmware.
Adding this to startup fixed it. Was tearing apart a windows 7 computer thinking it was the built-in firewall or something.
swconfig dev eth0 set enable_vlan 1
swconfig dev eth0 set apply
Posted: Sat Apr 28, 2018 12:18 Post subject: problem still, build 35831
Problem still exists for build 35831. I flashed that version, then reset to defaults, and then noticed no LAN-to-LAN traffic. Only after I telnetted into the router and pinged the devices successfully did I realize this.
Can confirm this is still an issue, what's worse, any build newer than 36247 won't let you apply those commands (it'll fail on the apply, and the device will no longer be reachable).
The issue is still there in the latest builds. In fact, it seems to be worse. When I enter the 3 commands just above, the switch ports forward packets to one another but one cannot administer the router from them anymore! It's unclear why the "eth0" port ("port 5" on the switch) loses contact with the switch after these commands, but it does. What to do?
Last edited by Brett Glass on Thu Mar 19, 2020 23:38; edited 2 times in total
P.S. - After several hours of experimentation, I thought I'd finally found a series of commands - a combination of the ones above - which, when run as a startup script, seems to work. After I ran these commands, the switch behaved like a proper switch on a router, whose ports communicate with one another and are bridged to the CPU and Wi-Fi! But my success was short-lived. I walked away from the bench, and when I came back the switch had stopped forwarding packets between ports again.
Developers, please make the router work properly!
Last edited by Brett Glass on Fri Mar 20, 2020 0:48; edited 5 times in total
Joined: 08 May 2018 Posts: 14249 Location: Texas, USA
Posted: Thu Mar 19, 2020 23:44 Post subject:
Brett Glass wrote:
P.S. - After several hours of experimentation, I finally found a series of commands which, when run as a startup script, seems to work. It's a combination of commands listed earlier in this thread:
swconfig dev switch0 set reset 1
swconfig dev switch0 set enable_vlan 1
swconfig dev switch0 set apply
swconfig dev eth0 set enable_vlan 1
swconfig dev eth0 set apply
Apparently, ALL of these commands are necessary, in this order, to make the switch behave like a proper switch, whose ports communicate with one another and are bridged to the CPU and Wi-Fi! Developers, please make the router work properly without these commands.
