Notes: 3. Bridge modes on k4.4 devices may sometimes work in some configurations in certain builds but are not supported by the bcmdhd driver. Use client or repeater instead as WDS doesn't work with Broadcom ARM either (see Issues below).
And I just realized I need to edit below to read above.....
I've been using Client bridge with every build without issue on my 87u until this build.
Now, no matter what build I load nothing but AP mode seems to work. All client modes show no TX, will not connect. However if I do a site survey it shows the network I'm trying to connect to as a client.
Something strange going on here. _________________ Location (urban) - 1x Linksys EA8500 (AP wlan0 & wlan1 enabled)
1x Asus 68u (Repeater Bridge w/VAP) - wl0 disabled
1x Asus 87u (Client Bridge) - wl1 disabled
Joined: 08 May 2018 Posts: 14217 Location: Texas, USA
Posted: Wed Mar 11, 2020 4:22 Post subject:
Possibly linked to things still in development, I can't say for sure. I just know that it either works or it doesn't work and that is the way it's been since before I got here. _________________ "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
Joined: 26 Mar 2013 Posts: 1856 Location: Hung Hom, Hong Kong
Posted: Wed Mar 11, 2020 4:32 Post subject:
stephensuley wrote:
Now, no matter what build I load nothing but AP mode seems to work. All client modes show no TX, will not connect. However if I do a site survey it shows the network I'm trying to connect to as a client.
Would you wanna try a factory reset when re-installing a build? Anyway, you have never needed that.
_________________ Router: Asus RT-N18U (rev. A1)
Drink, Blink, Stretch! Live long and prosper! May the Force and farces be with you!
I've tried that. After upgrading all network modes except AP will not work.
I even reverted back to ASus stock firmware and then back to an older firmware of dd-wrt, same result.......only AP gets the radio to transmit. All other network modes no longer try to connect.
Has anyone ever seen this? I'm at a loss. _________________ Location (urban) - 1x Linksys EA8500 (AP wlan0 & wlan1 enabled)
1x Asus 68u (Repeater Bridge w/VAP) - wl0 disabled
1x Asus 87u (Client Bridge) - wl1 disabled
Joined: 08 May 2018 Posts: 14217 Location: Texas, USA
Posted: Wed Mar 11, 2020 15:01 Post subject:
It was probably a matter of it was working with whatever configuration you had at one point without reset during upgrades and then it finally decided it didn't want to work anymore. That is the reasoning behind the annotations in the build threads, I presume. It either works, or it doesn't. There has been no desire to fix it, or all attempts to fix it have been in vain. _________________ "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
This has been working as client bridge device for years...it must be something recent.
I'll update my 4500v2 Client Mode router tonight and see what happens. It is k3.10 though, in case it is kernel-related.
Are you using any VAPs?
no VAPs.
It's a super basic setup on this device....
From defaults;
[BASIC]
I change the hostname, LAN IP/mask and GW. Click Save.
[WIRELESS]
Switch wireless network mode to Client bridge on wl0. Click Save.
Enable WPA2 w/AES and set the psk on wl0. Click Save.
[SECURITY]
Disable the firewall. Click Save.
Then I reboot.
I'm going to try loading the asus firmware again, and this time I'll do a hard reset with the asus firmware loaded, and then load dd-wrt back on......hard reset and upgrade to the latest dd-wrt.
I'm not going to give up. I'll update the group shortly. _________________ Location (urban) - 1x Linksys EA8500 (AP wlan0 & wlan1 enabled)
1x Asus 68u (Repeater Bridge w/VAP) - wl0 disabled
1x Asus 87u (Client Bridge) - wl1 disabled
There's certain other things, like setting it in router mode from gateway and certain steps before disabling the firewall.
It's up and running! Man that was a strange one. By reverting to the stock firmware and then hard reset and then put dd-wrt back and it was working as before.
Hey KP, Thanks for the reminder.
However I've never had to change that setting from gateway to router for proper operation.
The WAN interface is disabled and no NAT is being applied. So there's no need to change the mode to router. Those instructions you linked to are a little stale and I believe they're attempting to cover the most use cases possible.
For my network, I do a back2back with the 87u in CB to a 68u with dd-wrt also with WAN disabled. My clients connect to that 68u. It's all in my signature.
Anyways all is good now. It's been many years since I had to roll up my sleeves and bring a router back from the brink. _________________ Location (urban) - 1x Linksys EA8500 (AP wlan0 & wlan1 enabled)
1x Asus 68u (Repeater Bridge w/VAP) - wl0 disabled
1x Asus 87u (Client Bridge) - wl1 disabled
Joined: 08 May 2018 Posts: 14217 Location: Texas, USA
Posted: Wed Mar 11, 2020 18:54 Post subject:
Glad you got it working. Although the wiki is stale, perhaps it was last checked and edited....
Quote:
This page was last modified 15:39, 21 January 2020
, and every time I've set up CB or attempted to, that has been what I followed. Maybe I need to attempt a more simpler approach like yours on my R7000P and see if I can't make it work in CB mode instead.... then I could get rid of the powerline adapters or use them as a backup.... _________________ "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
Router/Version: ASUS RT-N12D1
Mode: Wireless and "test it before you destroy your main devices"
File: dd-wrt.v24-42617_NEWD-2_K3.x_mega_RT-N12, dd-wrt.v24-42617_NEWD-2_K3.x_mega_RT-N12B1 and dd-wrt.v24-42617_NEWD-2_K3.x_mega
Kernel: Linux 3.10.108-d10 #2784 Thu Mar 5 13:17:43 +04 2020 mips
Status: up 21 min, seems stable (connected 4 devices wireless and this PC wired)
As always: D1 revision needs either B1 or generic N12 release, NOT C1!
Netgear R6700v3 router, flashed with netgear-r6700v3-webflash.bin to DD-WRT r42617.
Installed without apparent incident and initially appeared to work OK. However it turns out the dnsmasq DHCP server stops working after running for several hours to a day. Rebooting is required to get dnsmasq working again. (Restarting the service by disabling/re-enabling DHCP server does not work.)
I know that latest is not necessarily greatest with DD-WRT releases. I figured I'd try the latest one first though. Is there a recommended stable release for this router? Don't need the fancier features like VPN or even NAS, just stable routing and DHCP.
Those instructions you linked to are a little stale and I believe they're attempting to cover the most use cases possible.
What does that mean exactly?
I did finally update my 4500v2 client mode to alpha build r42681 this morning, with no problems. I've always had client mode and bridge devices set to Router mode.
cbraxton wrote:
Is there a recommended stable release for this router?
This one would be as good as any. Latest should be greatest...it just often isn't.
Builds after this will be -O3 compiler performance config enabled for k4.4+, which would include the R6700v3. _________________ #NAT/SFE/CTF: limited speed w/ DD#Repeater issues#DD-WRT info: FAQ, Builds, Types, Modes, Changes, Demo#
OPNsense x64 5050e ITX|DD: DIR-810L, 2*EA6900@1GHz, R6300v1, RT-N66U@663, WNDR4000@533, E1500@353,
WRT54G{Lv1.1,Sv6}@250|FreshTomato: F7D8302@532|OpenWRT: F9K1119v1, RT-ACRH13, R6220, WNDR3700v4
Looks like the problem I was experiencing on that Netgear R6700V3 router was due to bad hardware. Since posting about the problem it has gotten progressively worse until the thing would barely run for more than an hour at a time.
I've used build r42617 on other routers and it has not skipped a beat at least for the basics, but with differing hardware it can be tough to predict what release will work best on what model. Of course that's all part of the fun!
Router/Version: Netgear R7000P Mode: AP, USB, Samba, FTP, Privoxy File: factory-to-dd-wrt.chk for Netgear R7000P Kernel: Linux 4.4.215 #1057 SMP Thu Mar 5 08:05:50 +04 2020 armv7l Status: working with errors, 9 days uptime, 5GHz channel cannot be set manually
upgraded without reset from build 41686 (power cycle only), only channel selection options for 5GHz VHT80 are Auto and current channel in the drop down menu. Anyone else with this issue?
