Router Model: TPLINK 841n V5, V7.1, V7.2
CPU Model: Atheros AR724x
Firmware Version: DD-WRT v3.0-r35034 std
Status: worked
Reset: No
previous:34929
errors: speedtest in wireless mode drops from 55Mbps in 34929 to 39Mbps in this version. wired mode works fine.
Router: TP-Link WDR3600v1
previous FW: r34876
new Firmware: r35034
Status: OK
Reset: No
Problems: low Wifi speed on 2.4 and 5GHz. Same settings, tried multiple restarts, same result on all devices. Went back to r34876 and Wifi speeds are normal again. Wifi speeds were 2/3 the normal and expected results.
No speed issues with wired connections.
Joined: 16 Nov 2015 Posts: 6440 Location: UK, London, just across the river..
Posted: Thu Feb 22, 2018 14:36 Post subject:
Router Model TPLINK WR1043ND V2
Firmware Version DD-WRT v3.0-r35034 std (02/17/1
Kernel Version Linux 3.18.95-rc1 #7835 Sat Feb 17 07:38:13 CET 2018 mips
update: via Web
reset: No
status: operational
errors: NTP time
it does work so far so good...
i was wondering how the fk i got only 9.9.9.9 DNS forced but
i can see my 2 x ISP DNS too i had to ban them with IPtables rules, so with PPPoE is there a DNS leak...??? _________________ 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
Joined: 05 Oct 2016 Posts: 19 Location: Bremen, Germany
Posted: Thu Feb 22, 2018 21:32 Post subject:
Router: TP-Link TL-WDR4900 V1.3
Firmware: 02-17-2018-r35034
Kernel: Linux version 4.4.116-rc1
Status: BRICKED
Reset: No, second try yes
Errors: Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(31,3)
And once again: It is bricked.
Tried update from R33607, webflash and factory-to-ddwrt.
Unbricked via serial connection and kept the output (attached).
Was surprised to find this line:
[ 0.000000] Linux version 4.4.116-rc1 (root@linux) (gcc version 7.1.0 (LEDE GCC 7.1.0 r4634-3542088a3f) ) #657 Sat Feb 17 14:56:23 CET 2018
Router: DIR-615e3
Firmware: dir615e3-firmware.bin (v3.0-r35034 std)
Kernel: Linux 3.10.108-dd #49287 Sat Feb 17 06:42:21 CET 2018 mips
Status: Buggy on gui
Reset: No
Notes on configuration:
DNSMasq
Virtual wireless with bridging x2
multiple DHCP server
QOS
Errors:
1. Apply settings on multiple pages does not work (for example Setup->Basic Setup, Setup->Network and Security->Firewall)
2. Firmware upgrade button does not work (I have had to use command line to upgrade/downgrade)
3. Factory Defaults (reset) does not work (apparently broken after 33006)
4. Firmware restore button broken (apparently broken after 33006)
5. Switch ports can not communicate with each other (see post https://www.dd-wrt.com/phpBB2/viewtopic.php?t=312371 ) [have not tested due to not using]
6. NTP with an address that can be resolved with IPv6 selects v6 when connection is v4 only
7. user.info : Authentication fail after each http login
Router: DIR-825 rev B1
Firmware: dir825-firmware.bin (v3.0-r35034 std)
Kernel: Linux 3.10.108-dd #49269 Sat Feb 17 06:02:45 CET 2018 mips
Status: Working
Reset: No
Notes on configuration:
Media Network
DNSMasq
Port Forwarding
DHCP reservation
Errors:
1. NTP with an address that can be resolved with IPv6 selects v6 when connection is v4 only
2. user.info : Authentication fail after each http login
Joined: 22 Aug 2009 Posts: 267 Location: New York State
Posted: Sat Feb 24, 2018 3:34 Post subject:
Router:TP-Link Archer C7 v4
Firmware:DD-WRT v3.0-r35034 (02/17/18 )
Reset:Yes, before and after
Errors: None
Previous; r34760 01-30-2018
Issues;
From previous F/W, the 5.6GHz Radio LED is on (continuously) when the Radio is disabled! This eventually goes out (at least it did with the last F/W), but this is showing the reverse of what it should.
The 2.4GHz Radio LED continuously flashes with or w/o activity.
Joined: 30 Jan 2015 Posts: 676 Location: Texas, USA
Posted: Sat Feb 24, 2018 19:38 Post subject:
FTP downloads site is up now. _________________ ASUS GT-BE98 PRO Main: Fiber 5gbps up/down
ASUS AXE16000: AI Mesh node
2 X ASUS RT-AX89X: AI Mesh nodes
QNAP QSW-1208-8C 12-Port 10GbE Switch
XS712T ProSafe 12-Port 10GbE Switch
3 X R9000 DD-WRT Mesh
Router: DIR-615e3
Firmware: dir615e3-firmware.bin (v3.0-r35034 std)
Kernel: Linux 3.10.108-dd #49287 Sat Feb 17 06:42:21 CET 2018 mips
Status: Buggy on gui
Reset: No
Notes on configuration:
DNSMasq
Virtual wireless with bridging x2
multiple DHCP server
QOS
Errors:
1. Apply settings on multiple pages does not work (for example Setup->Basic Setup, Setup->Network and Security->Firewall)
2. Firmware upgrade button does not work (I have had to use command line to upgrade/downgrade)
3. Factory Defaults (reset) does not work (apparently broken after 33006)
4. Firmware restore button broken (apparently broken after 33006)
5. Switch ports can not communicate with each other (see post https://www.dd-wrt.com/phpBB2/viewtopic.php?t=312371 ) [have not tested due to not using]
6. NTP with an address that can be resolved with IPv6 selects v6 when connection is v4 only
7. user.info : Authentication fail after each http login
Router: DIR-825 rev B1
Firmware: dir825-firmware.bin (v3.0-r35034 std)
Kernel: Linux 3.10.108-dd #49269 Sat Feb 17 06:02:45 CET 2018 mips
Status: Working
Reset: No
Notes on configuration:
Media Network
DNSMasq
Port Forwarding
DHCP reservation
Errors:
1. NTP with an address that can be resolved with IPv6 selects v6 when connection is v4 only
2. user.info : Authentication fail after each http login
both routers have:
on every hour
daemon.err process_monitor[]: cyclic NTP Update success
Errors:
First 5Ghz Wifi was visible, however, VERY flaky, kept dropping.
Second 5Ghz Wifi wasn't visible and couldn't connect.
2.4Ghz - marginal success in connecting, however, once connected no one could see the device on the network.
