Posted: Wed Aug 15, 2018 7:23 Post subject: Re: Netgear R6400 v2
kernel-panic69 wrote:
I'll be the heckler here. "Don't be skurred!". After I bricked my E4200 v1 several builds ago and have been running with serial console, and I kinda laugh at it now. All part of the fun... "Flash it 'til it bricks!"
Hehehehe.
I can see it your way. Unfortunately, I have too many things on my mind right now. With tools (serial cable etc) and time, I would love to do that coz that's what I like doing.
I'll probably sit this one out till someone else has done it and confirmed ... or till the next long weekend comes along.
Joined: 24 Feb 2013 Posts: 1634 Location: Belgrade
Posted: Wed Aug 15, 2018 8:32 Post subject:
Router Model Netgear R6250
Firmware Version DD-WRT v3.0-r36596 std (08/14/1
Kernel Version Linux 4.4.147 #3670 SMP Mon Aug 13 16:34:44 CEST 2018 armv7l
Status: Rock solid (Unbound, QoS, Speedchecker, Softether)
reset: No
Errors: None
Router Model: Buffalo WZR-1750DHP
Firmware: DD-WRT v3.0-r36596 std (08/14/18)
Kernel: Linux 4.4.147 #3670 SMP Mon Aug 13 16:34:44 CEST 2018 armv7l
Previous: DD-WRT v3.0-r36440M kongac (07/30/18)
Mode: AP / Local DNS / QoS HFSC - FQ-CODEL/ Static DHCP x 15
Reset: GUI before and after Flash
Status: Local DNS doesn't appear to respond (GRC bench). Not sure if it's a build or setup problem yet. Backup AP so not a major issue for me.
Router Model: Linksys EA6400
Firmware: DD-WRT v3.0-r36596 std (08/14/18)
Kernel: Linux 4.4.147 #3670 SMP Mon Aug 13 16:34:44 CEST 2018 armv7l
Mode: VPN AP / Switch
Previous: DD-WRT v3.0-r36330 std (07/16/18)
Reset: GUI before flash
Status: Working as expected
Router Model: Linksys E3000
Firmware: DD-WRT v3.0-r36596 mega (08/14/18)
Kernel: Linux 3.10.108-d5 #20484 Tue Aug 14 13:50:51 CEST 2018 mips
Mode: AP / Switch
Previous: DD-WRT v3.0-r36330 mega (07/16/18)
Reset: GUI before flash
Errors: Working as expected
[quote="nodnarb91"]What vpn is that? Quite the decrease in speed. Anonymity/encryption over speed.
Bernadoe wrote:
Router: Netgear R7000
Firmware: DD-WRT v3.0-r36596 std (08/14/2018)
Kernel: Linux 4.4.147 #3670 SMP Mon Aug 13 16:34:44 CEST 2018 armv7l
Status: Working
Reset: No
Previous: 36440M
Errors: No
CPU Temperature : CPU 55.8 °C / WL0 48.3 °C / WL1 50.4 °C
Working very well :
Router mode : DHCP
SFE Enable STP Enable
DNSMasq
Encrypt DNS
Cache DNSSEC data
Validate DNS Replies (DNSSEC)
Local DNS
No DNS Rebind
Query DNS in Strict Order
Usb
Nas, Samba, JFFS2, MiniDLNA
wl0, wl1
Vpn (OpenVPN Client)
Just to be sure, I tested 36596 micro_generic on the WRT54GSv6, and it still bricks. TFTP back to 36242, after reset, works fine.
WRT54Gv2.2
Linksys WRT54G/GL/GS
DD-WRT v3.0-r36596 mini (08/14/18
Linux 2.4.37 #50191 Tue Aug 14 06:22:35 CEST 2018 mips
[dd-wrt.v24_mini_generic.bin]
dd-wrt.v24_micro_generic.bin
Like previous builds --- Will not work
Done the reset button but could not TFTP a dd-wrt firmware.
Lucky I had WRT54GV4.0_4.21.1_US_code.bin so it TFTP ok but could not log on till done the reset button again.
GUI install r36104_micro_generic.bin from Linksys firmware all ok.
GUI install the r36104 dd-wrt.v24_mini_generic.bin and he's still good.
Router/Version: RT-AC87U A1
File: asus_rt-ac87u-firmware.trx
Firmware: DD-WRT v3.0-r36596 std (08/14/18 )
Kernel: Linux 4.4.147 #3677 SMP Tue Aug 14 08:50:36 CEST 2018 armv7l
Previous: DD-WRT v3.0-r36247 std (06/29/18 )
Mode/Status: Gateway/Ok
Reset: Yes, reset factory default both prior to install and after install, and WebGUI reboot
Setup Using: IPv4, DNSMasq, Port & Port Range Forwarding, USB, NAS, VAP, and NTP TimeSync
Issues/Errors: No, after reboot necessary to hit the APPLY SETTINGS button to enable VAP
Router/Version: RT-AC68R A1
File: asus_rt-ac68u-firmware.trx
Firmware: DD-WRT v3.0-r36596 std (08/14/18 )
Kernel: Linux 4.4.147 #3670 SMP Mon Aug 13 16:34:44 CEST 2018 armv7l
Previous: DD-WRT v3.0-r36410 std (07/28/18 )
Mode/Status: Repeater Bridge 5Ghz (AC Only)/Ok
Reset: No
Issues/Errors: OK
Router/Version: RT-AC66U A1
File: dd-wrt-36596-Asus_RT-AC66U.trx
Firmware: DD-WRT v3.0-r36596 giga (08/14/18 )
Kernel: Linux 3.10.108-d5 #20468 Tue Aug 14 13:28:43 CEST 2018 mips
Previous: DD-WRT v3.0-r36247 giga (06/29/18 )
Mode/Status: Repeater Bridge 5Ghz (AC Only)/Ok
Reset: Yes, reset factory default both prior to install and after install, and WebGUI reboot
Issues/Errors: Yes, but after some time devices start dropping
Router/Version: E4200 V1
File: dd-wrt.v24-36596_NEWD-2_K3.x_mega-e4200.bin
Firmware: DD-WRT v3.0-r36596 mega (08/14/18 )
Kernel: Linux 3.10.108-d5 #20484 Tue Aug 14 13:50:51 CEST 2018 mips
Previous: DD-WRT v3.0-r36410 mega (07/28/18 )
Mode/Status: Repeater Bridge 5Ghz (N-Only 5 GHz) /OK
Reset: Yes, reset factory default both prior to install and after install, and WebGUI reboot
Issues/Errors: Connection painfully slow. _________________ Netgear XR500, R7800
Asus AC87Ua1
Repeater Bridge
Netgear R6400v2otp
I tried making a repeater, and it displayed the VAP name, but even with the right password, I couldn't connect. Even with no password I couldn't connect. 31899 is the latest I found that you can use to make a repeater and connect to the VAP to use it.
My 2 cents.
How about 33986? _________________ R7500v2 - 38150M
RT-AC68U - stock
Wifi settings:
ac/n-ng-mixed, noise immunity, short preamble (2.4g), short gi, rts/cts+threshold, ack timing 1350, hfsc-fq_codel
*spectrum cable 100/10Mbps ipv4
*Things I shared here is for reference only, ie. it works for me does not mean it will work for you. And yes apparently such disclaimer is needed around here
Posted: Wed Aug 15, 2018 18:03 Post subject: dd-wrt 36596 feedback
I just installed build 36596 on my RTN66u rev. b1. Previously I had 35531 build. I am atempting to get reliable multiple vaps going. I have reset the router both before and after the flash.
Previously, the 2.4GHZ vap would be up for a moment or so then either disappear or the primary 2.4GHZ would go. So far that is not the case, the issue now is one of authentication.
I created two vaps, one on wl0.1, the other on wl1.1. All four networks, primary 2.4, primary 5, vap 2.4, and vap 5, all have different SSIDs. They do for testing purposes have the same password.
I have created two additional bridges br1 which got wl0.1 assigned to it, and br2 which got wl1.1 assigned to it. The primary 2.4 and 5GHZ networks are in a single 192.168.4.x/255.255.255.0 segment. The 2.4 vap is on the 192.168.7.0/255.255.255.0 and the second vap is on 192.168.9.0/255.255.255.0.
I have created two additional dhcp server assignments, dhcp1 goes for br1 and dhcp2 goes for br2.
I have applied settings throughout the process and rebooted the router when done.
Connecting to the primary 2.4 and 5GHZ networks works fine. The problem comes when atempting to authenticate to either the 2.4 or 5GHZ guest vaps, neither connects, I don't get an authentication error just an atempt at connection (this is on my android tablet), then reconnects up to my primary network.
The mode of the router is AP. The wl0 and wl0.1 are set to NG-mixed. The wl1 and wl1.1 are set to mixed.
I've got an ethernet connection computer to router while I do this and from the computer I can ping all three network address spaces. I can also still see all four networks via the phone.
Both the 2.4 and 5GHZ vap have ap isolation and net isolation enabled.
I am not running any IPv6.
That's my feedback, any input appreciated.
Joined: 08 May 2018 Posts: 14223 Location: Texas, USA
Posted: Wed Aug 15, 2018 19:24 Post subject: Re: dd-wrt 36596 feedback
dmehler wrote:
I just installed build 36596 on my RTN66u rev. b1. Previously I had 35531 build. I am atempting to get reliable multiple vaps going. I have reset the router both before and after the flash.
Previously, the 2.4GHZ vap would be up for a moment or so then either disappear or the primary 2.4GHZ would go. So far that is not the case, the issue now is one of authentication.
I created two vaps, one on wl0.1, the other on wl1.1. All four networks, primary 2.4, primary 5, vap 2.4, and vap 5, all have different SSIDs. They do for testing purposes have the same password.
I have created two additional bridges br1 which got wl0.1 assigned to it, and br2 which got wl1.1 assigned to it. The primary 2.4 and 5GHZ networks are in a single 192.168.4.x/255.255.255.0 segment. The 2.4 vap is on the 192.168.7.0/255.255.255.0 and the second vap is on 192.168.9.0/255.255.255.0.
I have created two additional dhcp server assignments, dhcp1 goes for br1 and dhcp2 goes for br2.
I have applied settings throughout the process and rebooted the router when done.
Connecting to the primary 2.4 and 5GHZ networks works fine. The problem comes when atempting to authenticate to either the 2.4 or 5GHZ guest vaps, neither connects, I don't get an authentication error just an atempt at connection (this is on my android tablet), then reconnects up to my primary network.
The mode of the router is AP. The wl0 and wl0.1 are set to NG-mixed. The wl1 and wl1.1 are set to mixed.
I've got an ethernet connection computer to router while I do this and from the computer I can ping all three network address spaces. I can also still see all four networks via the phone.
Both the 2.4 and 5GHZ vap have ap isolation and net isolation enabled.
I am not running any IPv6.
That's my feedback, any input appreciated.
I would try setting both your 5GHz APs, primary and VAP to NA-Mixed. Plain 'Mixed' for either band is broken AFAIK. Your authentication should be set to Auto for all 4 APs if you are using WPA2. I remember someone saying that switching to WPA and back to WPA2 with saving / applying seems to fix things (in 36410):
I have noticed in standard gateway/AP mode there are a few little tricky things to add to default configs to make things work (dnsmasq, especially!), but that's the nature of the beast. I'm guessing something in soft resets doesn't help the VAP situation, and I don't think you want to do a 30/30/30 reset on the RT-N66U:
Posted: Wed Aug 15, 2018 19:58 Post subject: Re: dd-wrt 36596 feedback
kernel-panic69 wrote:
dmehler wrote:
I just installed build 36596 on my RTN66u rev. b1. Previously I had 35531 build. I am atempting to get reliable multiple vaps going. I have reset the router both before and after the flash.
Previously, the 2.4GHZ vap would be up for a moment or so then either disappear or the primary 2.4GHZ would go. So far that is not the case, the issue now is one of authentication.
I created two vaps, one on wl0.1, the other on wl1.1. All four networks, primary 2.4, primary 5, vap 2.4, and vap 5, all have different SSIDs. They do for testing purposes have the same password.
I have created two additional bridges br1 which got wl0.1 assigned to it, and br2 which got wl1.1 assigned to it. The primary 2.4 and 5GHZ networks are in a single 192.168.4.x/255.255.255.0 segment. The 2.4 vap is on the 192.168.7.0/255.255.255.0 and the second vap is on 192.168.9.0/255.255.255.0.
I have created two additional dhcp server assignments, dhcp1 goes for br1 and dhcp2 goes for br2.
I have applied settings throughout the process and rebooted the router when done.
Connecting to the primary 2.4 and 5GHZ networks works fine. The problem comes when atempting to authenticate to either the 2.4 or 5GHZ guest vaps, neither connects, I don't get an authentication error just an atempt at connection (this is on my android tablet), then reconnects up to my primary network.
The mode of the router is AP. The wl0 and wl0.1 are set to NG-mixed. The wl1 and wl1.1 are set to mixed.
I've got an ethernet connection computer to router while I do this and from the computer I can ping all three network address spaces. I can also still see all four networks via the phone.
Both the 2.4 and 5GHZ vap have ap isolation and net isolation enabled.
I am not running any IPv6.
That's my feedback, any input appreciated.
I would try setting both your 5GHz APs, primary and VAP to NA-Mixed. Plain 'Mixed' for either band is broken AFAIK. Your authentication should be set to Auto for all 4 APs if you are using WPA2. I remember someone saying that switching to WPA and back to WPA2 with saving / applying seems to fix things (in 36410):
I have noticed in standard gateway/AP mode there are a few little tricky things to add to default configs to make things work (dnsmasq, especially!), but that's the nature of the beast. I'm guessing something in soft resets doesn't help the VAP situation, and I don't think you want to do a 30/30/30 reset on the RT-N66U:
That is my input which I might get chastised for later.
@kernel-panic69 thank you. My 2.4 vap and primary are set to NG-mixed, my 5GHZ's are now set to NA-mixed, and I did reboot the router after applying the change. I am using WPA2-PSK for authentication on all four networks. I'm not sure what your refering to when you say authentication set to auto, I didn't see anything regarding that, I just saw the WPA, WPA2, radius, and I think wep options.
In any event that change did not solve the issue, the behavior is the same.
Joined: 08 May 2018 Posts: 14223 Location: Texas, USA
Posted: Wed Aug 15, 2018 20:11 Post subject: Re: dd-wrt 36596 feedback
dmehler wrote:
@kernel-panic69 thank you. My 2.4 vap and primary are set to NG-mixed, my 5GHZ's are now set to NA-mixed, and I did reboot the router after applying the change. I am using WPA2-PSK for authentication on all four networks. I'm not sure what your refering to when you say authentication set to auto, I didn't see anything regarding that, I just saw the WPA, WPA2, radius, and I think wep options.
In any event that change did not solve the issue, the behavior is the same.
The "Auto" I am referring to is under "Advanced" for wl0, wl1, etc. If you set PSK on that page, it will ONLY work with WEP encryption configured. Found that out the hard way
The only other option I can think of is erasing nvram and starting from scratch.
I tried to upgrade from 36154 to 36596 with no reset to factory defaults. The upgrade completed, but on restart there was no VAP on 2.4 (don't have a 5ghz VAP). I restarted the R7000 several times. Some of the times, it would not show the 2.4 base or VAP networks. Other times, it did show the base 2.4 network. I only tried once to connect to the base 2.4 and it did work. The issue was the 2.4 VAP.
The times it did show up, I could see one other device on the wireless page, but it would have NA on tx and either NA or 1M for RX which meant that it wasn't going to work. I confirmed that by trying with my phone to connect to the 2.4 VAP and it would give me an incorrect password issue which is not what is causing this issue.
I went back to 36154 thinking all was well, but then the 2.4 VAP was not working on that. I did a factory reset and tried to restore the settings, but it did not fix the VAP.
I then downgraded to 35452 to get things working again. After that, I went ahead and tried to go back to 36596 which did complete, but the VAP problem remained.
Finally, I had to go back to Netgear firmware and reload 35452 and restore the settings. Now the 2.4 VAP works.
I would like to get back to a higher build number so it will be more up to date. I understand that I may have to reconfigure from scratch, but am hoping to find an easier way.
Is there a thread that covers most if not all these tricks? I have not found one over the last several weeks while this VAP issue has been ongoing. _________________ -----------------------------------
Netgear R7000
Joined: 09 Nov 2014 Posts: 314 Location: Bakersfield, CA
Posted: Thu Aug 16, 2018 0:00 Post subject:
jerrytouille wrote:
SinCalChewy wrote:
I tried making a repeater, and it displayed the VAP name, but even with the right password, I couldn't connect. Even with no password I couldn't connect. 31899 is the latest I found that you can use to make a repeater and connect to the VAP to use it.
My 2 cents.
How about 33986?
I pretty much stared from this build and went backwards through the builds (that work, none of the bugged builds), all with the same settings, and none of them would let me connect to the VAP, even without a password. Maybe I missed it, not sure, but it's a "Guest Router" though, and we don't have many guests at all, so it's not that big of a deal for me.
I might try it later tonight and see if I can get it working. It's a Xbox 360 Client Bride that I setup for like $20, and the "WiFi Addon" made by Microsoft for the 360 is like $100. So it's definitely an awesome set of software. I won't run a router that doesn't support DD-WRT. Stock firmware doesn't have my features, and there's not all the options DD-WRT has. Not even close _________________ Deployed Routers:
Netgear R7800 - 1x build 46979
- Gateway (USB /w Entware, CAKE QoS)
Netgear R7000 - 3x build 46979
