Router: D-Link DIR-825 revb
Firmware DD-WRT v3.0-r33525 std (10/17/17)
Kernel: Linux 3.10.107 #41504 Tue Oct 17 01:59:12 CEST 2017 mips
Status: OK
Reset: No
Upgrade from r32170. Two identical routers (AP and Client Bridge).
Router: TP-Link TL-WR841ND v11
Firmware DD-WRT v3.0-r33375 std (09/19/17)
Kernel: Linux 3.18.71 #10485 Tue Sep 19 03:12:51 CEST 2017 mips
Status: No Upgrade
Reset: No
Errors: It says Upgrade Successfully, reboots, and shows r33375 std (09/19/17)
Same here. The upgrade also is done in 3 seconds or so before going to reboot step. Have not done a reset yet as I am dabbling with this remotely (not my main router so not stressed over this either).
Joined: 16 Nov 2015 Posts: 6447 Location: UK, London, just across the river..
Posted: Wed Oct 18, 2017 11:16 Post subject:
xKingx wrote:
Lusitano wrote:
Router: TP-Link TL-WR841ND v11
Firmware DD-WRT v3.0-r33375 std (09/19/17)
Kernel: Linux 3.18.71 #10485 Tue Sep 19 03:12:51 CEST 2017 mips
Status: No Upgrade
Reset: No
Errors: It says Upgrade Successfully, reboots, and shows r33375 std (09/19/17)
Same here. The upgrade also is done in 3 seconds or so before going to reboot step. Have not done a reset yet as I am dabbling with this remotely (not my main router so not stressed over this either).
Same happens with Linksys WRT320n.
can you read in English ??? do you wear an optics ???
http://www.dd-wrt.com/phpBB2/viewtopic.php?t=311642 _________________ Atheros
TP-Link WR740Nv1 ---DD-WRT 55630 WAP
TP-Link WR1043NDv2 -DD-WRT 55723 Gateway/DoT,Forced DNS,Ad-Block,Firewall,x4VLAN,VPN
TP-Link WR1043NDv2 -Gargoyle OS 1.15.x AP,DNS,QoS,Quotas
Qualcomm-Atheros
Netgear XR500 --DD-WRT 55779 Gateway/DoH,Forced DNS,AP Isolation,4VLAN,Ad-Block,Firewall,Vanilla
Netgear R7800 --DD-WRT 55819 Gateway/DoT,AD-Block,Forced DNS,AP&Net Isolation,x3VLAN,Firewall,Vanilla
Netgear R9000 --DD-WRT 55779 Gateway/DoT,AD-Block,AP Isolation,Firewall,Forced DNS,x2VLAN,Vanilla
Broadcom
Netgear R7000 --DD-WRT 55460 Gateway/SmartDNS/DoH,AD-Block,Firewall,Forced DNS,x3VLAN,VPN
NOT USING 5Ghz ANYWHERE
------------------------------------------------------
Stubby DNS over TLS I DNSCrypt v2 by mac913
Router: TP-Link TL-WR841ND v11
Firmware DD-WRT v3.0-r33375 std (09/19/17)
Kernel: Linux 3.18.71 #10485 Tue Sep 19 03:12:51 CEST 2017 mips
Status: No Upgrade
Reset: No
Errors: It says Upgrade Successfully, reboots, and shows r33375 std (09/19/17)
Same here. The upgrade also is done in 3 seconds or so before going to reboot step. Have not done a reset yet as I am dabbling with this remotely (not my main router so not stressed over this either).
Thanks for pointing that out. I wasn't and am not on version 33375 (versions used in my signature), but symptoms were the same. So I did not check that thread before. _________________ - Netgear R7000 / Firmware version: DD-WRT v3.0-r39855M kongac (05/25/19)
- TP-Link TL-WR1043ND v1.8 / Firmware version: DD-WRT v3.0-r33525 std (10/17/17)
- TP-Link TL-WR1043ND v3 / Firmware version: DD-WRT v3.0-r40854 std (08/29/19)
- Linksys WRT320N / Firmware version: DD-WRT v3.0-r40559 mini (08/06/19)
From what can be seen in the timeline a lot of other fixes related to the krack attack have been added after 33525. Does anyone know if these are for routers that have not been patched yet or further fixes are to be expected in the new builds for all routers?
Upgrade from build 33492 fails on TP-Link TL-WR1043ND v1.
Unit reboots, but build 33492 is still present when the unit is up again.
Yes, I can confirm this. It means that for WR1043ND V1 the previous version r33492 still has the same issue as r33375 and r33413 and cannot be upgraded via web.
Thanks for replying Vico56.
Is there any solution to this? I really think 33525 is a need-to-have version because of the KRACK fixes. I tried to update again after performing a factory reset. Also reverting to older DD-WRT versions or stock firmware fails. Did you manage to update in another way? Is there any guide on how to do that?
I was able to go over the stock firmware with the FTPT method. These instructions worked fine with my WR1043ND v1 device.
Posted: Wed Oct 18, 2017 22:26 Post subject: Re: WNDR3700v2
Mile-Lile wrote:
bdg2 wrote:
Also note weird 1 hour inconsistancy in the times in the syslog.
I asked BS about this a time ago... and he told me:
Quote:
the syslog time and local systime has no daylight saving. thats correct and usefull. remember you have a database indexed by date. now daylight saving changes, so the order in your database would get confused
So, it is not going to be "fixed" because there are thing that we don't know about... I use remote logging it is much better (especially when unit reboots) the only my concern is that syslod and klogd ddwrt uses has no encryption...
I meant the way that as you go through the log the time jumps back 1 hour for a couple of entries then forward again!
TFTP upgrade from Buffalo Pro (ddwrt based) firmware rev 30355.
Notes:
Installed on my WDS station slaved router over the 5ghz band. It's basically acting as a wifi adapter for a VOIP phone. However, I did test the wireless networking through the WDS bridge, and all is well there.
Unrelated to this specific build, I had a HELL OF A TIME getting community ddwrt to flash from the buffalo branded crap. In the end, I tftp'd openwrt, then lede, and finally to this. TFTP seems to fail more often than succeed, especially with the rather large ddwrt builds.
BTW, neither openwrt nor lede has the wpa2 patch in place yet. Openwrt seems to be abandoned, while lede has it in their nightlies only. LEDE nightly installed as pure CLI. Since I had no internet access before configuring the WDS bridge, I could not install their GUI packages. I didn't want to bother to learn the text config for all that and am happy to be back on DD-WRT which I've used for probably over 10 years now. Setting up a WDS bridge on DD-WRT is so much simpler than with OpenWRT's GUI.
