New Build - 03/05/2018 - r35244

Post new topic   Reply to topic    DD-WRT Forum Forum Index -> Atheros WiSOC based Hardware
Goto page Previous  1, 2, 3, 4, 5, 6  Next
Author Message
ilmagico
DD-WRT Novice


Joined: 18 Jun 2014
Posts: 29

PostPosted: Thu Mar 08, 2018 8:42    Post subject: Reply with quote
Router Model TPLINK WR1043ND V2
Firmware: DD-WRT v3.0-r35244 std (03/05/18 )
Time: 09:12:05 up 21:57, load average: 0.03, 0.02, 0.0

Status: OK
Reset: No . It keeps all my settings.

Updated from 02-17-2018-r35034 using web GUI.

I have VPN server set, dnsmasq, 2 wifi networks

I have in syslog some strange lines .

ar 7 13:30:57 DD-WRT_g daemon.err httpd[4694]: Request Error Code 408: No request appeared within a reasonable time period.
Mar 7 13:30:57 DD-WRT_g daemon.err httpd[4694]: Request Error Code 408: No request appeared within a reasonable time period.
Mar 7 13:30:57 DD-WRT_g daemon.err httpd[4694]: Request Error Code 408: No request appeared within a reasonable time period.
Mar 7 13:30:57 DD-WRT_g daemon.err httpd[4694]: Request Error Code 408: No request appeared within a reasonable time period.
Mar 7 13:30:57 DD-WRT_g daemon.err httpd[4694]: Request Error Code 408: No request appeared within a reasonable time period.
Mar 7 13:30:57 DD-WRT_g daemon.err httpd[4694]: Request Error Code 408: No request appeared within a reasonable time period.
Mar 7 13:30:57 DD-WRT_g daemon.err httpd[4694]: Request Error Code 408: No request appeared within a reasonable time period.
Mar 7 13:30:57 DD-WRT_g daemon.err httpd[4694]: Request Error Code 408: No request appeared within a reasonable time period.
Mar 7 13:30:57 DD-WRT_g daemon.err httpd[4694]: Request Error Code 408: No request appeared within a reasonable time period.
Mar 7 13:30:58 DD-WRT_g daemon.err httpd[4694]: Request Error Code 408: No request appeared within a reasonable time period.
Mar 7 13:30:58 DD-WRT_g daemon.err httpd[4694]: Request Error Code 408: No request appeared within a reasonable time period.
Mar 7 13:31:27 DD-WRT_g daemon.err httpd[4694]: Request Error Code 408: No request appeared within a reasonable time period.
Mar 7 13:31:31 DD-WRT_g daemon.err httpd[4694]: Request Error Code 408: No request appeared within a reasonable time period.
Mar 7 13:31:31 DD-WRT_g daemon.err httpd[4694]: Request Error Code 408: No request appeared within a reasonable time period.
Mar 7 13:31:31 DD-WRT_g daemon.err httpd[4694]: Request Error Code 408: No request appeared within a reasonable time period.
Mar 7 13:31:31 DD-WRT_g daemon.err httpd[4694]: Request Error Code 408: No request appeared within a reasonable time period.
Mar 7 13:31:31 DD-WRT_g daemon.err httpd[4694]: Request Error Code 408: No request appeared within a reasonable time period.
....
Sponsor
dasnick
DD-WRT User


Joined: 23 Jul 2009
Posts: 69

PostPosted: Thu Mar 08, 2018 13:36    Post subject: Reply with quote
Has anyone of you guys running the 1043nd had issues with the wifi going down and not coming back up in the last releases? I'm still using the r34311 (I tried other versions but given the ntp issue, this one seemed the most stable and without that problem), but sometimes I loose the wifi with no computer finding it. The light goes dark, and I have to reboot the router.

I never experienced it before as I usually turn off the router during the night but I wanted to change places with my main router and this one and decided to let it on for a few weeks and check the stability. The first time this happened, the 1043 was up for about 8 days. The last time was a couple of days ago, when I formatted one of my laptops and had to synchronise google drive again (580gb) when I used the wired connection for about 300gb and then decided to use the wifi connection just as a brute force test, and after probably 200GB download the wifi connection was down.

We are not heavy users (just 2 with about 8/9 wifi devices: laptops, ipads smartphones) but I really wanted stability for not having my wife asking me all the time why the internet is down!!! I hardly use wired connections. The router is connected via powerline to my ISP router, which distributes ip addresses.
Alozaros
DD-WRT Guru


Joined: 16 Nov 2015
Posts: 4113
Location: UK, London, just across the river..

PostPosted: Thu Mar 08, 2018 15:26    Post subject: Reply with quote
my 1043ndv2 has no issues with WiFi and never had so far its rock solid...
but 1043nd v1.x has a lot of issues and its generally belied, its a crap unit, so consider replacing it or your
wife will get mad on you Razz Razz Razz

_________________
Atheros
TP-Link WR740Nv1 -----DD-WRT 44538 BS AP,NAT
TP-Link WR740Nv4 -----DD-WRT 44251 BS WAP/Switch
TP-Link WR1043NDv2 ---DD-WRT 45229 BS AP,NAT,AP Isolation,Firewall,Local DNS,Forced DNS,DoT,VPN,VLAN
TP-Link WR1043NDv2 ---DD-WRT 45493 BS AP,NAT,AD Block,Firewall,Local DNS,Forced DNS,DoT,VPN,VLAN
TP-Link WR1043NDv2 ---Gargoyle OS 1.12.0 AP,NAT,QoS,Quotas
Qualcomm/IPQ8065
Netgear R7800 -----DD-WRT 45563 BS AP,NAT,AD-Block,AP&Net Isolation,VLAN's,Firewall,Local DNS,DoT
Broadcom
Netgear R7000 -----DD-WRT 45563 BS AP,Wi-Fi OFF,NAT,AD-Block,Firewall,Local DNS,Forced DNS,DoT,VPN
-----------------------------------------------------------------------------------------------
Stubby for DNS over TLS I DNSCrypt v2 by mac913
Frakko
DD-WRT User


Joined: 06 May 2016
Posts: 402

PostPosted: Thu Mar 08, 2018 15:49    Post subject: Reply with quote
Router Model TP-Link 841ND V9
Firmware Version DD-WRT v3.0-r35244 std (03/05/2018 )
Kernel Version Linux 3.18.98 #8777 Mon Mar 5 04:44:06 CET 2018 mipsmips
Status - Ok
Reset - No
Errors - YES

SES / AOSS / EZ-SETUP / WPS Button ->

Turning off radio -> Enable
Turn radio off at boot -> Enable

After loading the new firmware the wifi networks become active and the devices connect to the wifi (!) at start. The LED dedicated to making visible that the wifi networks are active remains off but that of the connection flashes as the devices are connected. I tried to restart the router but the problem remains.Up to now with the other firmware the problem was not present.
Even if I press the appropriate button, the wifi networks remain active regardless of whether the dedicated LED is on or off.

--> Downgrade previous stable version.


Last edited by Frakko on Fri Mar 09, 2018 16:13; edited 1 time in total
dasnick
DD-WRT User


Joined: 23 Jul 2009
Posts: 69

PostPosted: Thu Mar 08, 2018 16:38    Post subject: Reply with quote
Alozaros wrote:
my 1043ndv2 has no issues with WiFi and never had so far its rock solid...
but 1043nd v1.x has a lot of issues and its generally belied, its a crap unit, so consider replacing it or your
wife will get mad on you Razz Razz Razz

mine is a v3... I have a v1 but its not in use...
Alozaros
DD-WRT Guru


Joined: 16 Nov 2015
Posts: 4113
Location: UK, London, just across the river..

PostPosted: Thu Mar 08, 2018 18:26    Post subject: Reply with quote
dasnick wrote:
Alozaros wrote:
my 1043ndv2 has no issues with WiFi and never had so far its rock solid...
but 1043nd v1.x has a lot of issues and its generally belied, its a crap unit, so consider replacing it or your
wife will get mad on you Razz Razz Razz

mine is a v3... I have a v1 but its not in use...


well v3 has a regular and US version i guess yours is US version and if im not wrong, they are country domain/TX power fixed, so not much to do...
anyway if its not due to bad WiFi settings than its something either on client side or something like a bad radio hardware, stick to the build that's ok....

_________________
Atheros
TP-Link WR740Nv1 -----DD-WRT 44538 BS AP,NAT
TP-Link WR740Nv4 -----DD-WRT 44251 BS WAP/Switch
TP-Link WR1043NDv2 ---DD-WRT 45229 BS AP,NAT,AP Isolation,Firewall,Local DNS,Forced DNS,DoT,VPN,VLAN
TP-Link WR1043NDv2 ---DD-WRT 45493 BS AP,NAT,AD Block,Firewall,Local DNS,Forced DNS,DoT,VPN,VLAN
TP-Link WR1043NDv2 ---Gargoyle OS 1.12.0 AP,NAT,QoS,Quotas
Qualcomm/IPQ8065
Netgear R7800 -----DD-WRT 45563 BS AP,NAT,AD-Block,AP&Net Isolation,VLAN's,Firewall,Local DNS,DoT
Broadcom
Netgear R7000 -----DD-WRT 45563 BS AP,Wi-Fi OFF,NAT,AD-Block,Firewall,Local DNS,Forced DNS,DoT,VPN
-----------------------------------------------------------------------------------------------
Stubby for DNS over TLS I DNSCrypt v2 by mac913
kroolas
DD-WRT Novice


Joined: 07 Apr 2014
Posts: 42

PostPosted: Thu Mar 08, 2018 21:56    Post subject: Reply with quote
PistolLoca wrote:
Ok, so I've been lurking around here for ages and following the discussions. I was using a very old dd-wrt version on my TPLINK TL-WDR3600 v1 and updated because of the one big bug. Since then I couldn't get my router to run smoothly anymore. I'm now on version 33986, and though some people have reported this version do be good for my model, I only get good performance after a restart, but soon after that my connection starts getting slower and slower until I finally have to reboot after just about 1 hour. So, the question of them all: can anybody recommend a firmware version which will work well with my old router? I still kind of like it, and don't want to change it. Thanks a lot!!


I skipped 33986. 33772 was a good build, but now I'm on 35034 and it works smoothly. What do you use on your WDR3600?

_________________
TP-Link TL-WDR3600 v1
DD-WRT v3.0-r42366 std (02/14/20)
Linux 3.10.108-d10 #38381
Wildlion
DD-WRT Guru


Joined: 24 May 2016
Posts: 991

PostPosted: Thu Mar 08, 2018 22:37    Post subject: Reply with quote
kroolas wrote:
PistolLoca wrote:
Ok, so I've been lurking around here for ages and following the discussions. I was using a very old dd-wrt version on my TPLINK TL-WDR3600 v1 and updated because of the one big bug. Since then I couldn't get my router to run smoothly anymore. I'm now on version 33986, and though some people have reported this version do be good for my model, I only get good performance after a restart, but soon after that my connection starts getting slower and slower until I finally have to reboot after just about 1 hour. So, the question of them all: can anybody recommend a firmware version which will work well with my old router? I still kind of like it, and don't want to change it. Thanks a lot!!


I skipped 33986. 33772 was a good build, but now I'm on 35034 and it works smoothly. What do you use on your WDR3600?


I probably do not use mine like kroolas does, I use mine as a utility router and mostly as a wireless client for other computers. It is not on all the time but it works with this firmware thread, standard errors (such as the httpd login error, ntp logged as error when it is success)
mrjcd
DD-WRT Guru


Joined: 31 Jan 2015
Posts: 5386
Location: Texas

PostPosted: Fri Mar 09, 2018 13:29    Post subject: Reply with quote
EA8500
k4.9 working ... just barely Smile
holding steady here

root@--:~# dmesg | tail -10
[ 45.969068] br1: port 3(vlan4) entered blocking state
[ 45.972648] br1: port 3(vlan4) entered listening state
[ 48.014496] br1: port 3(vlan4) entered learning state
[ 50.094502] br1: port 3(vlan4) entered forwarding state
[ 50.094549] br1: topology change detected, propagating
[ 63.079228] Ebtables v2.0 registered
[46852.774759] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
[46852.833480] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
[163717.541725] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
[163717.577427] ath10k_pci 0000:01:00.0: Unknown eventid: 36925

root@--:~# nvram get DD_BOARD
Linksys EA8500

root@--:~# cat /tmp/loginprompt
DD-WRT v3.0-r35244 std (c) 2018 NewMedia-NET GmbH
Release: 03/05/18

root@--:~# uptime
07:04:42 up 2 days, 11:33, load average: 0.19, 0.12, 0.09

root@--:~# date
Fri Mar 9 07:04:43 CST 2018


root@--:~# cat /tmp/var/log/messages | grep err
Mar 9 08:33:23 -- daemon.err process_monitor[2968]: cyclic NTP Update success (servers 2.pool.ntp.org 212.18.3.19 88.99.174.22)
Mar 9 09:33:24 -- daemon.err process_monitor[2968]: cyclic NTP Update success (servers 2.pool.ntp.org 212.18.3.19 88.99.174.22)
Mar 9 10:33:25 -- daemon.err process_monitor[2968]: cyclic NTP Update success (servers 2.pool.ntp.org 212.18.3.19 88.99.174.22)
Mar 9 11:33:26 -- daemon.err process_monitor[2968]: cyclic NTP Update success (servers 2.pool.ntp.org 212.18.3.19 88.99.174.22)
Mar 9 12:33:26 -- daemon.err process_monitor[2968]: cyclic NTP Update success (servers 2.pool.ntp.org 212.18.3.19 88.99.174.22)


root@--:~# cat /tmp/var/log/messages.0 | grep err
Jan 1 00:00:39 -- kern.info kernel: [ 0.250478] qcom_rpm 108000.rpm: could not find pctldev for node /soc/pinmux@800000/i2c4_pinmux, deferring probe
Jan 1 00:00:39 -- kern.err kernel: [ 0.301274] msm_bus_fabric_init_driver
Jan 1 00:00:40 -- kern.err kernel: [ 2.846101] Calibration not found.
Jan 1 00:00:40 -- kern.err kernel: [ 2.848604] qcom-tsens 900000.thermal-sensor: tsens calibration failed
Jan 1 00:00:40 -- kern.err kernel: [ 2.863448] CPUidle arm: CPU 0 failed to init idle CPU ops
Jan 1 00:00:40 -- kern.err kernel: [ 3.003065] of: dev_pm_opp_of_cpumask_add_table: couldn't find opp table for cpu:0, -19
Jan 1 00:00:40 -- kern.err kernel: [ 3.008061] of: dev_pm_opp_of_cpumask_add_table: couldn't find opp table for cpu:1, -19
Jan 1 00:00:40 -- kern.warn kernel: [ 8.387001] ath10k_pci 0000:01:00.0: Direct firmware load for ath10k/pre-cal-pci-0000:01:00.0.bin failed with error -2
Jan 1 00:00:40 -- kern.warn kernel: [ 8.399382] ath10k_pci 0000:01:00.0: Direct firmware load for ath10k/QCA99X0/hw2.0/firmware-6.bin failed with error -2
Jan 1 00:00:40 -- kern.err kernel: [ 11.191319] ath10k_pci 0000:01:00.0: failed to fetch board data for bus=pci,vendor=168c,device=0040,subsystem-vendor=168c,subsystem-device=0002 from ath10k/QCA99X0/hw2.0/board-2.bin
Jan 1 00:00:40 -- kern.warn kernel: [ 12.696847] ath10k_pci 0001:01:00.0: Direct firmware load for ath10k/pre-cal-pci-0001:01:00.0.bin failed with error -2
Jan 1 00:00:40 -- kern.warn kernel: [ 12.708700] ath10k_pci 0001:01:00.0: Direct firmware load for ath10k/QCA99X0/hw2.0/firmware-6.bin failed with error -2
Jan 1 00:00:40 -- kern.err kernel: [ 15.042338] ath10k_pci 0001:01:00.0: failed to fetch board data for bus=pci,vendor=168c,device=0040,subsystem-vendor=168c,subsystem-device=0002 from ath10k/QCA99X0/hw2.0/board-2.bin
Jan 1 00:00:40 -- kern.err kernel: [ 18.452362] qcom-dwc3-usb-phy 100f8830.phy: cannot get HSIO settings from device node, using default values
Jan 1 00:00:40 -- kern.err kernel: [ 18.453190] qcom-dwc3-usb-phy 110f8830.phy: cannot get HSIO settings from device node, using default values
Jan 1 00:00:40 -- kern.err kernel: [ 25.726289] sd 0:0:0:0: [sda] Asking for cache data failed
Jan 1 00:00:40 -- kern.err kernel: [ 25.729949] sd 0:0:0:0: [sda] Assuming drive cache: write through
Jan 1 00:00:50 -- daemon.err ntpclient[2012]: Failed resolving address to hostname 2.pool.ntp.org: Try again
Jan 1 00:00:50 -- daemon.err ntpclient[2012]: Failed resolving server 2.pool.ntp.org: Network is down
Mar 7 01:32:21 -- daemon.err process_monitor[2008]: cyclic NTP Update success (servers 2.pool.ntp.org 212.18.3.19 88.99.174.22)
Mar 7 01:32:27 -- daemon.err process_monitor[2968]: cyclic NTP Update success (servers 2.pool.ntp.org 212.18.3.19 88.99.174.22)
Mar 7 01:32:33 -- daemon.err openvpn[2823]: event_wait : Interrupted system call (code=4)
Mar 7 01:37:24 -- daemon.err httpd[1489]: Request Error Code 401: Authorization required. please note that the default username is "root" in all newer releases
Mar 7 02:32:28 -- daemon.err process_monitor[2968]: cyclic NTP Update success (servers 2.pool.ntp.org 212.18.3.19 88.99.174.22)
Mar 7 03:32:29 -- daemon.err process_monitor[2968]: cyclic NTP Update success (servers 2.pool.ntp.org 212.18.3.19 88.99.174.22)
Mar 7 04:32:29 -- daemon.err process_monitor[2968]: cyclic NTP Update success (servers 2.pool.ntp.org 212.18.3.19 88.99.174.22)
Mar 7 05:32:30 -- daemon.err process_monitor[2968]: cyclic NTP Update success (servers 2.pool.ntp.org 212.18.3.19 88.99.174.22)
Mar 7 06:32:31 -- daemon.err process_monitor[2968]: cyclic NTP Update success (servers 2.pool.ntp.org 212.18.3.19 88.99.174.22)
Mar 7 07:32:33 -- daemon.err process_monitor[2968]: cyclic NTP Update success (servers 2.pool.ntp.org 212.18.3.19 88.99.174.22)
Mar 7 08:32:33 -- daemon.err process_monitor[2968]: cyclic NTP Update success (servers 2.pool.ntp.org 212.18.3.19 88.99.174.22)
Mar 7 09:32:34 -- daemon.err process_monitor[2968]: cyclic NTP Update success (servers 2.pool.ntp.org 212.18.3.19 88.99.174.22)
Mar 7 10:32:35 -- daemon.err process_monitor[2968]: cyclic NTP Update success (servers 2.pool.ntp.org 212.18.3.19 88.99.174.22)
Mar 7 11:32:36 -- daemon.err process_monitor[2968]: cyclic NTP Update success (servers 2.pool.ntp.org 212.18.3.19 88.99.174.22)
Mar 7 12:32:27 -- daemon.err httpd[1489]: Request Error Code 401: Authorization required. please note that the default username is "root" in all newer releases
Mar 7 12:32:37 -- daemon.err process_monitor[2968]: cyclic NTP Update success (servers 2.pool.ntp.org 212.18.3.19 88.99.174.22)
Mar 7 13:32:38 -- daemon.err process_monitor[2968]: cyclic NTP Update success (servers 2.pool.ntp.org 212.18.3.19 88.99.174.22)
Mar 7 14:32:39 -- daemon.err process_monitor[2968]: cyclic NTP Update success (servers 2.pool.ntp.org 212.18.3.19 88.99.174.22)
Mar 7 15:32:40 -- daemon.err process_monitor[2968]: cyclic NTP Update success (servers 2.pool.ntp.org 212.18.3.19 88.99.174.22)
Mar 7 16:32:41 -- daemon.err process_monitor[2968]: cyclic NTP Update success (servers 2.pool.ntp.org 212.18.3.19 88.99.174.22)
Mar 7 17:32:42 -- daemon.err process_monitor[2968]: cyclic NTP Update success (servers 2.pool.ntp.org 212.18.3.19 88.99.174.22)
Mar 7 18:32:43 -- daemon.err process_monitor[2968]: cyclic NTP Update success (servers 2.pool.ntp.org 212.18.3.19 88.99.174.22)
Mar 7 19:32:44 -- daemon.err process_monitor[2968]: cyclic NTP Update success (servers 2.pool.ntp.org 212.18.3.19 88.99.174.22)
Mar 7 20:32:45 -- daemon.err process_monitor[2968]: cyclic NTP Update success (servers 2.pool.ntp.org 212.18.3.19 88.99.174.22)
Mar 7 21:32:49 -- daemon.err process_monitor[2968]: cyclic NTP Update success (servers 2.pool.ntp.org 212.18.3.19 88.99.174.22)
Mar 7 22:32:50 -- daemon.err process_monitor[2968]: cyclic NTP Update success (servers 2.pool.ntp.org 212.18.3.19 88.99.174.22)
Mar 7 23:32:51 -- daemon.err process_monitor[2968]: cyclic NTP Update success (servers 2.pool.ntp.org 212.18.3.19 88.99.174.22)
Mar 8 00:32:52 -- daemon.err process_monitor[2968]: cyclic NTP Update success (servers 2.pool.ntp.org 212.18.3.19 88.99.174.22)
Mar 8 01:32:53 -- daemon.err process_monitor[2968]: cyclic NTP Update success (servers 2.pool.ntp.org 212.18.3.19 88.99.174.22)
Mar 8 02:32:54 -- daemon.err process_monitor[2968]: cyclic NTP Update success (servers 2.pool.ntp.org 212.18.3.19 88.99.174.22)
Mar 8 03:32:55 -- daemon.err process_monitor[2968]: cyclic NTP Update success (servers 2.pool.ntp.org 212.18.3.19 88.99.174.22)
Mar 8 04:32:56 -- daemon.err process_monitor[2968]: cyclic NTP Update success (servers 2.pool.ntp.org 212.18.3.19 88.99.174.22)
Mar 8 05:33:00 -- daemon.err process_monitor[2968]: cyclic NTP Update success (servers 2.pool.ntp.org 212.18.3.19 88.99.174.22)
Mar 8 06:33:00 -- daemon.err process_monitor[2968]: cyclic NTP Update success (servers 2.pool.ntp.org 212.18.3.19 88.99.174.22)
Mar 8 07:33:01 -- daemon.err process_monitor[2968]: cyclic NTP Update success (servers 2.pool.ntp.org 212.18.3.19 88.99.174.22)
Mar 8 08:33:02 -- daemon.err process_monitor[2968]: cyclic NTP Update success (servers 2.pool.ntp.org 212.18.3.19 88.99.174.22)
Mar 8 09:33:03 -- daemon.err process_monitor[2968]: cyclic NTP Update success (servers 2.pool.ntp.org 212.18.3.19 88.99.174.22)
Mar 8 10:33:04 -- daemon.err process_monitor[2968]: cyclic NTP Update success (servers 2.pool.ntp.org 212.18.3.19 88.99.174.22)
Mar 8 11:33:04 -- daemon.err process_monitor[2968]: cyclic NTP Update success (servers 2.pool.ntp.org 212.18.3.19 88.99.174.22)
Mar 8 12:33:05 -- daemon.err process_monitor[2968]: cyclic NTP Update success (servers 2.pool.ntp.org 212.18.3.19 88.99.174.22)
Mar 8 13:33:06 -- daemon.err process_monitor[2968]: cyclic NTP Update success (servers 2.pool.ntp.org 212.18.3.19 88.99.174.22)
Mar 8 14:33:07 -- daemon.err process_monitor[2968]: cyclic NTP Update success (servers 2.pool.ntp.org 212.18.3.19 88.99.174.22)
Mar 8 15:33:08 -- daemon.err process_monitor[2968]: cyclic NTP Update success (servers 2.pool.ntp.org 212.18.3.19 88.99.174.22)
Mar 8 16:33:09 -- daemon.err process_monitor[2968]: cyclic NTP Update success (servers 2.pool.ntp.org 212.18.3.19 88.99.174.22)
Mar 8 17:33:10 -- daemon.err process_monitor[2968]: cyclic NTP Update success (servers 2.pool.ntp.org 212.18.3.19 88.99.174.22)
Mar 8 18:33:11 -- daemon.err process_monitor[2968]: cyclic NTP Update success (servers 2.pool.ntp.org 212.18.3.19 88.99.174.22)
Mar 8 19:33:12 -- daemon.err process_monitor[2968]: cyclic NTP Update success (servers 2.pool.ntp.org 212.18.3.19 88.99.174.22)
Mar 8 20:33:13 -- daemon.err process_monitor[2968]: cyclic NTP Update success (servers 2.pool.ntp.org 212.18.3.19 88.99.174.22)
Mar 8 21:33:13 -- daemon.err process_monitor[2968]: cyclic NTP Update success (servers 2.pool.ntp.org 212.18.3.19 88.99.174.22)
Mar 8 22:33:14 -- daemon.err process_monitor[2968]: cyclic NTP Update success (servers 2.pool.ntp.org 212.18.3.19 88.99.174.22)
Mar 8 23:33:15 -- daemon.err process_monitor[2968]: cyclic NTP Update success (servers 2.pool.ntp.org 212.18.3.19 88.99.174.22)
Mar 9 00:33:16 -- daemon.err process_monitor[2968]: cyclic NTP Update success (servers 2.pool.ntp.org 212.18.3.19 88.99.174.22)
Mar 9 01:33:17 -- daemon.err process_monitor[2968]: cyclic NTP Update success (servers 2.pool.ntp.org 212.18.3.19 88.99.174.22)
Mar 9 02:33:18 -- daemon.err process_monitor[2968]: cyclic NTP Update success (servers 2.pool.ntp.org 212.18.3.19 88.99.174.22)
Mar 9 03:33:19 -- daemon.err process_monitor[2968]: cyclic NTP Update success (servers 2.pool.ntp.org 212.18.3.19 88.99.174.22)
Mar 9 04:33:19 -- daemon.err process_monitor[2968]: cyclic NTP Update success (servers 2.pool.ntp.org 212.18.3.19 88.99.174.22)
Mar 9 05:33:20 -- daemon.err process_monitor[2968]: cyclic NTP Update success (servers 2.pool.ntp.org 212.18.3.19 88.99.174.22)
Mar 9 06:33:21 -- daemon.err process_monitor[2968]: cyclic NTP Update success (servers 2.pool.ntp.org 212.18.3.19 88.99.174.22)
Mar 9 07:33:22 -- daemon.err process_monitor[2968]: cyclic NTP Update success (servers 2.pool.ntp.org 212.18.3.19 88.99.174.22)
root@--:~#

http://www.dslreports.com/speedtest/30697259

http://www.dslreports.com/speedtest/30697641

http://www.dslreports.com/speedtest/30697679
Heracles87
DD-WRT User


Joined: 04 Feb 2017
Posts: 55

PostPosted: Fri Mar 09, 2018 19:52    Post subject: Reply with quote
dasnick wrote:
Has anyone of you guys running the 1043nd had issues with the wifi going down and not coming back up in the last releases? I'm still using the r34311 (I tried other versions but given the ntp issue, this one seemed the most stable and without that problem), but sometimes I loose the wifi with no computer finding it. The light goes dark, and I have to reboot the router.

I never experienced it before as I usually turn off the router during the night but I wanted to change places with my main router and this one and decided to let it on for a few weeks and check the stability. The first time this happened, the 1043 was up for about 8 days. The last time was a couple of days ago, when I formatted one of my laptops and had to synchronise google drive again (580gb) when I used the wired connection for about 300gb and then decided to use the wifi connection just as a brute force test, and after probably 200GB download the wifi connection was down.

We are not heavy users (just 2 with about 8/9 wifi devices: laptops, ipads smartphones) but I really wanted stability for not having my wife asking me all the time why the internet is down!!! I hardly use wired connections. The router is connected via powerline to my ISP router, which distributes ip addresses.

If you own a 1043ND V3, build r34929 is very solid Very Happy
nahnaush
DD-WRT Novice


Joined: 25 Oct 2016
Posts: 7

PostPosted: Sat Mar 10, 2018 1:21    Post subject: DD-WRT Build v3.0-r35244 std on TP-Link TL-WR842ND v1 Reply with quote
ftp://ftp.dd-wrt.com/betas/2018/03-05-2018-r35244/

Router: TP-Link TL-WR842ND v1
CPU Model: Atheros AR7241 ver 1 rev 1.1 (0x0101)
Firmware: DD-WRT v3.0-r35244 std (03/05/18)
Kernel: Linux 3.10.108-dd #50328 Mon Mar 5 04:25:04 CET 2018 mips
Status: Operational
Reset: Yes
Errors: None observed
jmfolcik
DD-WRT User


Joined: 06 Nov 2010
Posts: 125

PostPosted: Sat Mar 10, 2018 2:12    Post subject: TL841 v9 good Reply with quote
Two of the TL841 v9's run my home network and are working fine after about an hour so far. One of them is just an additional wired AP located a floor up. Still feel limited with cpu for NAT, with SFE enabled I still only get 60-70megabit maxes on a 100meg service. Anyone found a trick to squeeze more out of this model? Disabling the wan traffic counter seems to help by about 10megabit.
dasnick
DD-WRT User


Joined: 23 Jul 2009
Posts: 69

PostPosted: Sat Mar 10, 2018 9:37    Post subject: Reply with quote
Heracles87 wrote:
dasnick wrote:
Has anyone of you guys running the 1043nd had issues with the wifi going down and not coming back up in the last releases? I'm still using the r34311 (I tried other versions but given the ntp issue, this one seemed the most stable and without that problem), but sometimes I loose the wifi with no computer finding it. The light goes dark, and I have to reboot the router.

I never experienced it before as I usually turn off the router during the night but I wanted to change places with my main router and this one and decided to let it on for a few weeks and check the stability. The first time this happened, the 1043 was up for about 8 days. The last time was a couple of days ago, when I formatted one of my laptops and had to synchronise google drive again (580gb) when I used the wired connection for about 300gb and then decided to use the wifi connection just as a brute force test, and after probably 200GB download the wifi connection was down.

We are not heavy users (just 2 with about 8/9 wifi devices: laptops, ipads smartphones) but I really wanted stability for not having my wife asking me all the time why the internet is down!!! I hardly use wired connections. The router is connected via powerline to my ISP router, which distributes ip addresses.

If you own a 1043ND V3, build r34929 is very solid Very Happy


Does that version have the NTP issue?
Wildlion
DD-WRT Guru


Joined: 24 May 2016
Posts: 991

PostPosted: Sat Mar 10, 2018 15:09    Post subject: Reply with quote
dasnick wrote:
Heracles87 wrote:
dasnick wrote:
Has anyone of you guys running the 1043nd had issues with the wifi going down and not coming back up in the last releases? I'm still using the r34311 (I tried other versions but given the ntp issue, this one seemed the most stable and without that problem), but sometimes I loose the wifi with no computer finding it. The light goes dark, and I have to reboot the router.

I never experienced it before as I usually turn off the router during the night but I wanted to change places with my main router and this one and decided to let it on for a few weeks and check the stability. The first time this happened, the 1043 was up for about 8 days. The last time was a couple of days ago, when I formatted one of my laptops and had to synchronise google drive again (580gb) when I used the wired connection for about 300gb and then decided to use the wifi connection just as a brute force test, and after probably 200GB download the wifi connection was down.

We are not heavy users (just 2 with about 8/9 wifi devices: laptops, ipads smartphones) but I really wanted stability for not having my wife asking me all the time why the internet is down!!! I hardly use wired connections. The router is connected via powerline to my ISP router, which distributes ip addresses.

If you own a 1043ND V3, build r34929 is very solid Very Happy


Does that version have the NTP issue?


What do you consider the NTP issue? Brainslayer fixed the ipv4 vs ipv6 issue, so ntp works fine now. NTP does give an error every hour, when it actually synced and is a success (wrong log stream in code)
Lusitano
DD-WRT User


Joined: 25 Jun 2014
Posts: 125
Location: São Paulo - Brazil

PostPosted: Sun Mar 11, 2018 15:41    Post subject: Reply with quote
TP-Link TL-WR841ND v11
DD-WRT v3.0-r35244 std (03/05/18 )
Linux 3.18.98 #8767 Mon Mar 5 04:32:43 CET 2018 mips

Status: OK
Reset: NO
Errors: NTP in Client Bridge (Routed) not working and Request Error Code 401: Authorization required. please note that the default username is "root" in all newer releases (Spam)
Goto page Previous  1, 2, 3, 4, 5, 6  Next Display posts from previous:    Page 4 of 6
Post new topic   Reply to topic    DD-WRT Forum Forum Index -> Atheros WiSOC based Hardware All times are GMT

Navigation

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You cannot download files in this forum