Your reports for Qualcomm/Atheros units are greatly appreciated !
Router:
Firmware:
Kernel:
Status:
Reset:
Errors: _________________ THERE ARE NO STRANGERS HERE; ONLY FRIENDS YOU HAVEN'T YET MET.
________________________________________________________________________________________________________
DD-WRT CHANGELOG | DEVICES | DD-WRT BUILDS | KONG BUILDS | UNOFFICIAL BUILDS | DD-WRT in VIRTUALBOX
Last edited by KrypteX on Sat Dec 12, 2015 8:16; edited 1 time in total
WNDR3700 V4
DD-WRT v3.0-r28493 std (12/10/15)
Linux 3.10.94 #13436 Thu Dec 10 05:19:58 CET 2015 mips
No Reset - GUI install live over r28444
main router
2.4 & 5 GHz ok
ath0.1 as br1 restricted guest ok
MAC clone ok
samba share ok
I need more horsepower -- can't move GB+ files to/from USB and also run QOS
ssh ok
remote ssh ok
VPN passthru ok
29 static leases
Recursive DNS Resolving -- must 'Apply Settings' after reboot for local DNS to work
Working OK -
uptime 1:12
---
WRT160NL x3
DD-WRT v3.0-r28493 std (12/10/15)
Linux 3.10.94 #13374 Thu Dec 10 03:52:25 CET 2015 mips
No Reset -- previous r28444
The WAP + guest install good live from GUI.
The WDS-Station install good live from GUI.
WDS-AP went into brick mode w/flashy power light after try live install from GUI.
Had to pull it out of network and TFTP. It also has a samba share drive attached but that really shouldn't
have upset the install ... I TFTP 28493 and never touched the USB drive. TFTP, put back in network, it linked
to station and samba share is all there working good.
All are working very well... so far.
uptime WAP 57 min / WDS-Sta 46 min / WDS-AP 28 min
Joined: 24 Feb 2013 Posts: 1634 Location: Belgrade
Posted: Thu Dec 10, 2015 19:39 Post subject:
Router ModelTPLINK WR1043ND V2
Firmware Version DD-WRT v3.0-r28493 std (12/10/15)
Kernel VersionLinux 3.18.24 #6977 Thu Dec 10 04:59:17 CET 2015 mips
Status: working
Reset: no
Errors: still testing. GUI visuals look very good on all browsers - thx KONG
Router ModelTP-Link TL-WR740N v4
Firmware Version DD-WRT v3.0-r28493 std (12/10/15)
Kernel VersionLinux 3.10.94 #13412 Thu Dec 10 04:34:21 CET 2015 mips
Status: working
Reset: no
Errors: none
Thx devs. 6in4 HE tunnel with DNSMasq works very fast. DNS-O-MATIC update works, FireSSH on Chrome with Dropbear SSH works great, Syslog on Remote server works, telnet works, VPN didn't tried - will tomorrow from work...
Thank you, thank you, thank you:)
p.s. Noticed for a few builds that firewall works different. Does not log IP of brute force attacker on 1723 and block it for some time...
Joined: 09 Jul 2009 Posts: 11 Location: Eugene, Oregon, USA
Posted: Fri Dec 11, 2015 0:19 Post subject:
Router Model: TP-Link Archer C7 v2
Status: OK
Reset: no
I only upgraded the repeater so far (base AP is still on 28444). But it appears to work now with ath10k repeater mode. I did see the incorrect reporting of rate, and not using correct extension channels, as noted in bugs above. But, basically, it works.
Router Name: WRZ-600DHP
Router Model: Buffalo WZR-HP-AG300H
Firmware: DD-WRT v3.0-r28493 (12/10/15)
Time: 19:43:52 up 27 min, load average: 0.00, 0.04, 0.12
Reset: 30/30/30 after flash via telnet
Error: IPv6 shows in the console but no ipv6 address and even disabled the ipv6 still show in the console.
Joined: 24 Feb 2013 Posts: 1634 Location: Belgrade
Posted: Fri Dec 11, 2015 7:47 Post subject:
DeathReaper wrote:
Error: IPv6 shows in the console but no ipv6 address and even disabled the ipv6 still show in the console
It works for me. So, if you want help we need more details. Post some more details about your IPv6 configuration such as:
Do you use:
6in4 tunnel, native IPv6, IPv6 with prefix delagation?
Do you use:
DHCP6s, Radvd or DNSMasq for advertising and handing out addresses?
Do u have custom or default configuration?
Give us output of:
cat /tmp/radvd.conf
Remember that radvd does not advertise ipv6 dns servers to windows clients via RDNSS. Linux and ios devices work just fine. Radvd provides stateless configuration for ipv6 clients.
My suggestion to you: disable radvd, dhcpv6s, dhcpv6c and try to USE DNSMASQ custom settings for IPv6.
Running dd-wrt from a few months back on a TL-WDR4300 here. Having a lot of issues with 5Ghz and want to try the latest version. Just one question. I frequently read about resetting the device before and after flash and have no problem doing so, but lately also read a lot about erasing nvram to rule out even more issues.
Keeping both in mind, what are the recommended steps in flashing these days (30-30-30, nvram, ...)? And how do i perform those additional steps like NVRAM?
Last edited by siroj on Fri Dec 11, 2015 12:28; edited 1 time in total
Running dd-wrt from a few months back on a TL-WDR4300 here. Having a lot of issues with 5Ghz and want to try the latest version. Just one question. I frequently read about resetting the device before and after flash and have no problem doing so, but lately also read a lot about erasing nvram to rule out even more issues.
Keeping both in mind, what are the recommended steps in flashing these days (30-30-30, nvram, ...)?
Siroj, a 30/30/30 reset does clear the NVRAM on some models, and on others it doesn't or only partially clears it. Another way to do this is by running either of these commands over Telnet or via the CLI:
Code:
erase nvram && reboot
or
Code:
mtd erase nvram
There are many reports of 30/30/30 resets working on older router models but not newer ones. The 30/30/30 reset was originally for the WRT54G series routers, but these days in my eyes it's pretty much old news. That's not to say that there are some models out there which still respond to 30/30/30. There are also many reports about resetting to factory defaults in the web GUI not completely clearing out the NVRAM. The trick is finding which method works for your router.
Code:
mtd erase nvram
is a backup method if the first code snippet I posted doesn't work.
Be sure to always clear the NVRAM before you flash to a newer build of DD-WRT. I also recommend doing so afterwards, although it isn't as important as doing it before a flash. Many of the bricked routers you hear about are due to people who don't know what they're doing; they flash via wireless and/or aren't clearing the NVRAM.
Last edited by teslacoil on Fri Dec 11, 2015 12:56; edited 2 times in total
I did see the incorrect reporting of rate, and not using correct extension channels, as noted in bugs above. But, basically, it works.