Problem is similar: on the following router, wired LAN devices cannot see each other, port forwarding works to one LAN device (a desktop PC), does not work to another LAN device (a Raspberry Pi server), meanwhile wireless LAN devices can see all wired LAN devices.
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
same issue as op, this solution worked for me! thanks
TP-Link WR841N v9
DDWRT v24160 & 24461
It resolved my issue as well. Thanks!
For those that claim this fix doesn't work be sure to look under Setup > Networking to see what interface your switched ports are on. I have a WR841N v8 that has the wan on eth0 and the switch on eth1. My v9 lan switch uses eth0.
Any plans for BS to implement a permanent fix in the f/w for this issue in upcoming builds?
This problem persists in BrainSlayer (and other beta) builds for wr841n/nd in at least v7, v8 and v9, in my experience. Holds true for recent 2015 builds, too. This was especially an issue for me with client bridge mode where I had several clients on the LAN. Each could see the internet and ping clients on the AP Router, but could not ping each other on the client bridge. The start-up code fixed that issue and now everyone is pings. Looks like this is a long-running and as-yet unfixed issue.
Posted: Sun Apr 05, 2015 17:44 Post subject: OMG IT WORKED THANK YOU!!!
I registered just to say THANK YOU SO MUCH for those two simple lines of code. I am using node.js / websockets on my arduino hosting it from my home server and could not for the life of me get it to work. I thought I was doing something wrong and spent THREE WEEKS chasing problems down rabbit holes. One after another.
I was starting to question my understanding of computer networking all together! I'm no expert but Jesus, I knew my network SHOULD have been working. I thought the problem was the linux setup but after three weeks I realized it was only a problem on WIRED ports. Then found this page and the vlan thing worked.
I did have to use eth0 though, not eth1 but I realized that quickly.
Anyways, that's my ramble. I'm just so excited my websockets are working now.
THANK YOU THANK YOU THANK YOU!!!
EDIT:
Just for other's information, I am using a TP-LINK WDR3500 V 1.2 (but used the v1 firmware) with the DD-WRT v24-sp2 (05/27/14) std - build 24160
I had this issue with multiple builds of this firmware.
Hi, just wanted to dump some info when I found this thread.
I was having all kinds of WAN / LAN issues on my router (TP-Link TL-WR941ND v3), sometimes WAN did not even get DHCP and I could never get LAN computers to ping successfully. The only firmware I could get to work normally was DD-WRT v24-sp2 (02/11/13) std - build 20675. I tried around 10-15 different ones 3-4 mounts back, non worked except for 20675, I also tried the newest one there was back then, unsure what version it could have been.
Now today just out of pure curiosity I tried DD-WRT v24-sp2 (04/09/15) std - build 26653, and so far everything is working. So maybe people with LAN issues could give that one a try. Not saying it will help but reading this thread reminded me a lot of the issues I was having.
*EDIT*
Things that I know are working at 26653 that I previously had major issues with are
DHCP on WAN
LAN <---> LAN Communication
WiFi <---> LAN Communication
Port forwarding
