Posted: Sun Jul 19, 2020 18:16 Post subject: upgrading to beat the perma wireless isolation bug
per the wiki, i flashed dd-wrt.v24-33772_NEWD-2_K2.6_mini-WNDR3700v3 then dd-wrt.v24-33772_NEWD-2_K3.x_mega-nv64k onto my netgear wndr3700v3 a couple years ago only to learn of a bug where wireless isolation stays on pretty much full time regardless of the settings. this has been a major pita, but dd-wrt allowed me to get around my crappy isp's restrictions. but i really, really need a fully functioning wireless network. so im hoping the issue has been fixed in one of the subsequent releases.
after going through all the required contradictory reading again, i believe ive distilled what i should do down to:
a.Set your computer to a static IP of 192.168.1.8. (or to whatever subnet the router is on) Disable all firewalls and security. Disable wireless on your computer and only have the router connected to the flashing computer by the ethernet cable between the two.
b. Hard reset prior to flashing. Wait. Check for password page on re-login and change password.
c. Flash dd-wrt.v24-43845_NEWD-2_K3.x_mega-nv64k.bin via the dd-wrt webgui upgrade page
d. Wait...at least three minutes. Lights should return to normal.
e. Do a power cycle of the router.
f. Wait for the lights to return to normal.
g. HARD reset again. Wait. Check for the password page and set the password. Then you can reconfigure your settings manually.
h. Once configured set your computer back to autoIP and autoDNS.
my questions are 1) is the above procedure, including chosen build, accurate for my application and 2) should flashing to this build resolve the permanent wireless isolation bug?
Posted: Tue Jul 21, 2020 18:49 Post subject: Re: upgrading to beat the perma wireless isolation bug
crpngdth wrote:
my questions are 1) is the above procedure, including chosen build, accurate for my application and 2) should flashing to this build resolve the permanent wireless isolation bug?
also, there's no use in backing up the cfe again, right?
yes, maybe, and correct.
There is a new build out today; check the build thread before flashing it (or anything, for the respective build thread). I seem to recall the isolation stuff finally getting fixed earlier this year, but I've not tested it.
Doing a GUI reset will suffice before the flash (really only needed if you've got a bunch of non-default services enabled). And after flashing, you should probably do a `nvram erase && reboot` from telnet and manually set up. You could skip the latter reset, but if you have issues, definitely do that before reporting issues. Good luck! _________________ #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
Joined: 08 May 2018 Posts: 14246 Location: Texas, USA
Posted: Tue Jul 21, 2020 20:09 Post subject:
Some folks need to look through recent posts. I do not recommend 'nvram erase'. If anything, use the webUI Administration->Factory Defaults, unless you wish to risk bricking or dubious outcome. _________________ "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
made it to DD-WRT v3.0-r43845 mega (07/18/20) without a hitch.
manually restored the config. always a party.
but the openvpn client doesnt appear to be connecting and webui>status>openvpn isnt much help as the log is blank (attached). i copied all the settings over from a text file and the screenshots i took previously, save for the following newly appeared configuration items:
it would appear the issue was with copying the cert/key text into gedit, then copying it back from gedit into the router after flashing...though i suppose its possible i could have initially hosed the copy operation into gedit. the problem persisted after removing the additional config details, and re-copying everything from my backup text file. it was only resolved after digging out the original cert/key files and copying them into the router.
now im just left with a lone error in the log that wasnt there before:
Code:
W WARNING: Using --management on a TCP port WITHOUT passwords is STRONGLY discouraged and considered insecure
from my reading this appears to be a harmless warning about webui>services>VPN not having its own needless password protection in this context?
