Posted: Sat Mar 25, 2023 20:19 Post subject: Repeater (not repeater bridge) issue - E2000
I've followed the directions for the WLAN Repeater and I do see the WAN address being the main router's assigned DHCP address. I am running DD-WRT v3.0-r44715 mega (11/03/20) - directions being here:
When I connect a WIRED client into the E2000, I do get the new IP range-assigned DHCP address, and I can access the internet. This is successful 100% of time.
When I try to access the internet via a WIRELESS client, 99 times out of 100 I get no connection (there is no security set up for the primary router or the repeater) and once I got connected with about half speed (about right), and following that, I rebooted the router, connected wirelessly again but now the speed was about 1Mbps and another reboot had me with no connection again.
I'll be glad to post screenprints to assist with my problem... but any outstanding "gotchas" that jump out?
Use the broadcom_K26 or broadcom_K3X folder, you'll want K3X as repeater modes may still be broken in K26 builds. Also, keep in mind, a lot of wikis have not been curated and kept up to date. _________________ "Life is but a fleeting moment, a vapor that vanishes quickly; All is vanity"
Contribute To DD-WRT Pogo - A minimal level of ability is expected and needed... DD-WRT Releases 2023 (PolitePol)
DD-WRT Releases 2023 (RSS Everything)
----------------------
Linux User #377467 counter.li.org / linuxcounter.net
No luck - downgraded and have the same problem, so it's not a version issue.
Since the wired clients work perfectly, am I missing some static route or other configuration item? I'm connecting via a Win10 laptop, and I get the message "Open, No Internet" as the connection information when I can connect or "Cannot Connect to This Network"
Joined: 06 Jun 2006 Posts: 3763 Location: I'm the one on the plate.
Posted: Mon Mar 27, 2023 2:56 Post subject:
texnnyc wrote:
"Cannot Connect to This Network"
I've had Windows 10 freak out with that error on perfectly good and functional WiFi access points. Restarting the Windows computer usually fixes it and allows it to connect.
Another avenue of trouble shooting the WiFi connection is to set a static IP address in the client computer. DHCP confusion in DD-WRT repeater configurations has been a common bug for about the last 17 years. Also try connecting with something other than just one finicky Windows 10 box. _________________ http://69.175.13.131:8015 Streaming Week-End Disco. Station Ripper V 1.1 will do.
Posted: Sat Apr 01, 2023 23:55 Post subject: Success!
Latest K3x build worked like a charm!
Didn't like encryption, but that's something I can figure out (seemed on the passphrase it wanted it in hex, not the actual phrase)
Connected without encryption with no problems the first time, and after several reboots and power downs, still connected! (This is where the earlier builds seem to fail)
Joined: 08 May 2018 Posts: 14125 Location: Texas, USA
Posted: Sun Apr 02, 2023 11:16 Post subject:
The webUI doesn't ask for hex, it asks for plain text. In fact, the pass for wifi is stored in nvram in plain text last I knew. Perhaps it was invalid characters. _________________ "Life is but a fleeting moment, a vapor that vanishes quickly; All is vanity"
Contribute To DD-WRT Pogo - A minimal level of ability is expected and needed... DD-WRT Releases 2023 (PolitePol)
DD-WRT Releases 2023 (RSS Everything)
----------------------
Linux User #377467 counter.li.org / linuxcounter.net