NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
mansus
Aug 30, 2016Aspirant
R7800 wireless clients cannot connect to lan clients
Hello, I have the latest firmware 1.0.2.04 on R7800 and have an issue where my wifi client cannot access servers on lan on the same router. I found suggestions about firmware resets and turning o...
- Nov 22, 2016
evel I'm using Kong Mod from myopenrouter.com. It's a straightforward process on how to replace the firmware (just look at the latest article). For VLAN tagging, you'll need to create a VLAN on eth0 (default WAN) interface (Setup->Networking) and assign a newly created port as WAN port on the same page. Once you're online - you can easily do the rest (wifi, services, etc). WIFI->LAN works right away.
Thx, Mansus.
evel
Nov 22, 2016Aspirant
JamesGL I have done a factory reset after upgrading to 1.0.2.12. Still not working. I was able to access my ReadyNAS once immediately after reseting but it quickly stopped. My wireshark traces look the same as before. Lots of resets and high RTO.
I may have to go the DD-WRT route as well. I need to have a fix ASAP.
mansus
Nov 22, 2016Aspirant
evel I'm using Kong Mod from myopenrouter.com. It's a straightforward process on how to replace the firmware (just look at the latest article). For VLAN tagging, you'll need to create a VLAN on eth0 (default WAN) interface (Setup->Networking) and assign a newly created port as WAN port on the same page. Once you're online - you can easily do the rest (wifi, services, etc). WIFI->LAN works right away.
Thx, Mansus.
- mansusNov 23, 2016Aspirant
Hello evel,
This is their reply:
"Our higher level of support could not see any issues from the debug logs you provided. They would like to know if you are willing to continue troubleshooting with them."
I mean I give them logs taken simultenously from the router and from the clients yet they see no issues. Even when the client reports "cannot connect, internal error, etc".
That was after 2 months and multiple wireshark/debug logs from both router and end-points. So I just gave up and went with DD-WRT.
Thx, Mansus.
- evelNov 23, 2016Aspirant
Wow. I am by no means a network engineer but even I can see problems in my wireshark traces.
I've had good luck with DD-WRT in the past. I'll give it a go.
- TheEtherNov 23, 2016Guru
Could you post a snippet of the wireshark capture here? Doesn't have to be the raw capture. The decoded capture is fine.
- streiluNov 24, 2016Guide
I may provide you some logs this evening or tomorrow, don't know when I have time to capture some.
- DrCthulhuDec 06, 2016Aspirant
mansus I'm having the same issue with wireless clients not connecting to lan clients... I tried flashing the latest Kong DD-WRT at your suggestion, but I could never get it to connect to Centurylink so I had to go back to the stock FW.
On the setup tab I put in username@qwest.net and my password for PPPoE credentials and then on the networking tab set up the vlan 201 for eth0 and set the wan port to the new eth0.201 port with no luck. Any other suggestions on what I should be doing? I never put in a domain name or hostname on the credentials tab, is that needed?
If there is a good tutorial on this, I would appreciate it. I'm no stranger to running custom router fw or setting it up in general, but this is the first time I've had to worry about PPPoE credentials and vlan tagging (used to have a cable provider).