But I don't know how to troubleshoot such things. This all seems to point to some kind of communication problem between my win10 DHCP client my DD-WRT DHCP server. The win10 devices can connect to DD-WRT when using a static IP. The win10 devices have no problems connecting to other routers / AP's / hotspots.ģ. Every other, non win10 device can connect to DD-WRT both on wired and wireless.Ģ. I would try turning off the Windows firewall completely and testing, but I am really scratching my head on this one, unless your network adapters' configs are screwy. You could try that reset first to see if it will work, but at this point, I am at a total loss, because I haven't had issues of this magnitude with DD-WRT and Win10 at all. If neither wireless nor wired can connect on Win10, then the problem may not be DD-WRT, you may need to do a complete network reset in Win10. You can try to roll back to the suggested Kong build, and do an nvram reset to defaults before and after flashing, and again just to be sure and start with the default settings, changing only the wireless settings. If everything but Windows is connecting fine, I also wouldn't suspect hardware failure in the router. I see no reason for this to be so broken, considering people have reported successful flashes to R7000 in the forums. I think maybe for giggles, I would try turning off the Windows firewall completely and testing, but I am really scratching my head on this one, unless your network adapters' configs are screwy. So now router 1 will always remain up and if router 2 loses its upstream link then ,since the bug only affects wireless, you will still be able to connect to router 2 by connecting wirelessly to router 1 and putting router 2's IP address into a browser.Wired -and- wireless, Windows 10 won't connect? Now that is odd. Wireless/wireless mode = AP access point or Client+AP, with SSID name/password/security etc as you wish The important thing is that y is different from the other 2 subnets on the upstream router and router 1 Local network/LAN router IP = .1 (or other appropriate setting). Wireless/wireless mode = AP access point, with SSID name/password/security etc as you wishĬonnect a cable between the WAN port of router 1 and a LAN port of router 2Ĭonfigure router 2 as a client or client /AP depending what router you want to use for your wifi clients to connect to, i.e in the configuration settings The important thing is that x is different from the other 2 subnets on the upstream router and router 2 The workaround is to use two routers next to each other connected via a cable, we'll call them router 1 and router 2.Ĭonfigure router 1 as a wireless AP only, i.e in the configuration settings Since there is no wifi you then have to connect to it via a cable to see what is going on, fine if you can get to it, but if it is installed high up somewhere not always very practical So the problem is a bug/feature in Gargoyle means that when using the router downstream configured as a gateway in client/AP mode, and using the router to wirelessly connect to an upstream router to get internet and having the downstream router then act as a wireless AP for clients, the downstream router will drop its wifi if/when the connection to the upstream router goes down for any reason. But one could be that old slow router you have lying around with no other use I guess OK, worked out a workaround to do this if anyone else needs it
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |