New Build - 08/22/2020 - r44236

Post new topic   Reply to topic    DD-WRT Forum Index -> Atheros WiSOC based Hardware
Goto page Previous  1, 2
View previous topic :: View next topic  
Author Message
kernel-panic69
DD-WRT Guru


Joined: 08 May 2018
Posts: 14244
Location: Texas, USA
PostPosted: Mon Aug 24, 2020 1:49    Post subject: Reply with quote
^^^^^ serial logs, syslogs, dmesg output? Can't fix broken things without information...
_________________
"Life is but a fleeting moment, a vapor that vanishes quickly; All is vanity"
Contribute To DD-WRT
Pogo - A minimal level of ability is expected and needed...
DD-WRT Releases 2023 (PolitePol)
DD-WRT Releases 2023 (RSS Everything)
----------------------
Linux User #377467 counter.li.org / linuxcounter.net
Back to top View user's profile Send private message Visit poster's website
Sponsor
tatsuya46
DD-WRT Guru


Joined: 03 Jan 2010
Posts: 7568
Location: YWG, Canada
PostPosted: Mon Aug 24, 2020 2:25    Post subject: Reply with quote
Router Model: dir-862L(x2), wndr4300, x86_64(2x qca9984 ,1x qca6174)

Status: it runs
Reset: no
Errors: see tickets below

https://svn.dd-wrt.com/ticket/5225 *
https://svn.dd-wrt.com/ticket/5603 *
https://svn.dd-wrt.com/ticket/5848
https://svn.dd-wrt.com/ticket/5938
https://svn.dd-wrt.com/ticket/6286
https://svn.dd-wrt.com/ticket/6315
https://svn.dd-wrt.com/ticket/6481 *
https://svn.dd-wrt.com/ticket/6495 *
https://svn.dd-wrt.com/ticket/6655
https://svn.dd-wrt.com/ticket/6842
https://svn.dd-wrt.com/ticket/6903 *
https://svn.dd-wrt.com/ticket/6921
https://svn.dd-wrt.com/ticket/7154
https://svn.dd-wrt.com/ticket/7207 *


wds stations connected to qca6174 wds ap transfer no data no ping nothing. remote management does not work on dir-862L, instant error page. works in r44191..
_________________
LATEST FIRMWARE(S)

BrainSlayer wrote:
we just do it since we do not like any restrictions enforced by stupid cocaine snorting managers

[x86_64] Haswell i3-4150/QCA9984/QCA9882 ------> r55797 std
[QUALCOMM] DIR-862L --------------------------------> r55797 std
▲ ACTIVE / INACTIVE ▼
[QUALCOMM] WNDR4300 v1 --------------------------> r50485 std
[BROADCOM] DIR-860L A1 ----------------------------> r50485 std


Sigh.. why do i exist anyway.. | I love you Anthony.. never forget that.. my other 99% that ill never see again..

Back to top View user's profile Send private message
ccbrianf
DD-WRT User


Joined: 10 Jun 2015
Posts: 59
PostPosted: Tue Aug 25, 2020 15:23    Post subject: DIR-862L 2.4ghz Channel Scan broken Reply with quote
Router Model: Dlink DIR862-A1
Firmware Version: DD-WRT v3.0-r44236 std (08/22/20)
Kernel Version: Linux 3.18.140-d5 #88664 Sat Aug 22 04:33:59 +04 2020 mips

Problem: 2.4ghz channel scan causes loss of WIFI and sometimes locks httpd requiring a restart

Thank you for all the work developing this software!
Back to top View user's profile Send private message
shadyjoin
DD-WRT Novice


Joined: 06 Oct 2019
Posts: 11
PostPosted: Wed Aug 26, 2020 15:22    Post subject: Fire TV 1st gen can't connect to WDR4300 running r44236 Reply with quote
<<deleted due to embarrassment>>

Last edited by shadyjoin on Thu Aug 27, 2020 0:09; edited 1 time in total
Back to top View user's profile Send private message
mrjcd
DD-WRT Guru


Joined: 31 Jan 2015
Posts: 6291
Location: Texas
PostPosted: Wed Aug 26, 2020 20:05    Post subject: Reply with quote
still worky ok
same ol unexpected tx_fetch_ind event crap she gets sometimes Twisted Evil
Code:
mrjcd@OMG-Deb:~$ ssh root@citadel-station-homeworld.mrjcd.com
DD-WRT v3.0-r44236 std (c) 2020 NewMedia-NET GmbH
Release: 08/22/20
Board: Linksys EA8500
==========================================================
 
     ___  ___     _      _____  ______       ____  ___
    / _ \/ _ \___| | /| / / _ \/_  __/ _  __|_  / / _ \
   / // / // /___/ |/ |/ / , _/ / /   | |/ //_ <_/ // /
  /____/____/    |__/|__/_/|_| /_/    |___/____(_)___/
                                                     
                       DD-WRT v3.0
                   http://www.dd-wrt.com
 
==========================================================


BusyBox v1.32.0 (2020-08-22 00:26:04 +03) built-in shell (ash)

root@Citadel-Station-Homeworld:~# date
Wed Aug 26 15:00:38 CDT 2020
root@Citadel-Station-Homeworld:~# uptime
 15:00:42 up 4 days, 19:00,  load average: 0.07, 0.05, 0.00
root@Citadel-Station-Homeworld:~# dmesg | tail -80
[   39.296910] br1: port 1(ath0.1) entered learning state
[   41.297082] br1: port 2(ath1.1) entered learning state
[   51.296831] br1: port 3(vlan4) entered learning state
[   54.297272] br1: port 1(ath0.1) entered forwarding state
[   56.297012] br1: port 2(ath1.1) entered forwarding state
[   66.296880] br1: port 3(vlan4) entered forwarding state
[ 7254.875066] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[ 7254.875098] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[ 7254.882303] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[ 7254.890456] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[15215.498791] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[15215.498823] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[15215.505945] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[15215.514187] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[45575.464325] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[45575.464355] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[45575.471568] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[45575.479724] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[70334.926369] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[70334.926410] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[70334.933653] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[70334.941803] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[106385.252886] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[106385.252928] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[106385.260141] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[106385.268359] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[114145.425114] ath10k_pci 0001:01:00.0: received unexpected tx_fetch_ind event: in push mode
[114145.425159] ath10k_pci 0001:01:00.0: received unexpected tx_fetch_ind event: in push mode
[114145.432374] ath10k_pci 0001:01:00.0: received unexpected tx_fetch_ind event: in push mode
[114145.440591] ath10k_pci 0001:01:00.0: received unexpected tx_fetch_ind event: in push mode
[130024.072900] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[130024.072942] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[130024.080205] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[130024.088406] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[130045.081986] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[130045.082027] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[130045.089229] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[130045.097398] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[152847.798127] IMQ driver unloaded successfully.
[152849.161846] IMQ: use 2 as queue number
[152849.175069] IMQ driver loaded successfully. (numdevs = 16, numqueues = 2, imq_dev_accurate_stats = 1)
[152849.175096]    Hooking IMQ after NAT on PREROUTING.
[152849.183384]    Hooking IMQ before NAT on POSTROUTING.
[166935.498085] IMQ driver unloaded successfully.
[166936.806837] IMQ: use 2 as queue number
[166936.819710] IMQ driver loaded successfully. (numdevs = 16, numqueues = 2, imq_dev_accurate_stats = 1)
[166936.819739]    Hooking IMQ after NAT on PREROUTING.
[166936.828021]    Hooking IMQ before NAT on POSTROUTING.
[205028.397953] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[205028.397998] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[205028.405120] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[205028.413448] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[206606.832029] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[206606.832071] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[206606.839297] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[206606.847441] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[245059.556600] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[245059.556641] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[245059.563847] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[245059.572066] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[245146.588953] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[245146.588993] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[245146.596150] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[245146.604478] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[245488.724590] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[245488.724632] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[245488.731844] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[245488.740060] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[245917.898564] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[245917.898608] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[245917.905758] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[245917.914056] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[293909.462501] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[293909.462544] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[293909.469784] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[293909.477997] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[336016.325896] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[336016.325939] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[336016.333173] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[336016.341360] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
root@Citadel-Station-Homeworld:~# exit
Connection to citadel-station-homeworld.mrjcd.com closed.
mrjcd@OMG-Deb:~$
Back to top View user's profile Send private message
evdjj3j
DD-WRT Novice


Joined: 13 Apr 2012
Posts: 33
PostPosted: Fri Aug 28, 2020 2:12    Post subject: Reply with quote
evdjj3j wrote:
TP Link Archer C7 v2 US
DD-WRT v3.0-r44236 std (08/22/20)
GUI install over previous r44191
No Reset


Failed

Cannot access the internet, local network connectivity dropping over and over. Restored back to 43718 and everything is functioning correctly.


Code:

Router Name
ArcherC7v2
Router Model
TP-Link ARCHER-C7 v2
Firmware Version
DD-WRT v3.0-r44236 std (08/22/20)
Kernel Version
Linux 3.18.140-d5 #88648 Sat Aug 22 04:03:56 +04 2020 mips


Dec 31 19:00:13 Voyager syslog.info syslogd started: BusyBox v1.32.0
Dec 31 19:00:13 Voyager user.info : syslogd : daemon successfully started
Dec 31 19:00:13 Voyager user.info : resetbutton : resetbutton daemon successfully started
Dec 31 19:00:13 Voyager user.info : bridge : interface wlan0 successfully deleted from bridge br0
Dec 31 19:00:13 Voyager user.info : bridge : bridge br0 successfully added
Dec 31 19:00:13 Voyager user.info : bridge : interface eth1 successfully added to bridge br0
Dec 31 19:00:16 Voyager user.info : bridge : interface ath0 successfully added to bridge br0
Dec 31 19:00:18 Voyager user.info : bridge : interface ath1 successfully added to bridge br0
Dec 31 19:00:19 Voyager user.info : hwmon : successfully started
Dec 31 19:00:19 Voyager user.info : telnetd : daemon successfully started
Dec 31 19:00:19 Voyager user.info : syslogd : syslog daemon successfully stopped
Dec 31 19:00:19 Voyager user.info : wland : daemon successfully started
Dec 31 19:00:19 Voyager syslog.info syslogd exiting
Dec 31 19:00:20 Voyager syslog.info syslogd started: BusyBox v1.32.0
Dec 31 19:00:20 Voyager user.info : sfe : shortcut forwarding engine successfully stopped
Dec 31 19:00:20 Voyager user.info : dnsmasq : daemon successfully started
Dec 31 19:00:21 Voyager user.info : cron : daemon successfully started
Dec 31 19:00:21 Voyager cron.info cron[967]: (CRON) STARTUP (fork ok)
Dec 31 19:00:22 Voyager daemon.info httpd[973]: httpd : httpd server started at port 80
Dec 31 19:00:22 Voyager user.info : httpd : http daemon successfully started
Dec 31 19:00:23 Voyager user.info : vpn modules : vpn modules successfully unloaded
Dec 31 19:00:23 Voyager user.info : vpn modules : nf_conntrack_proto_gre successfully loaded
Dec 31 19:00:23 Voyager user.info : vpn modules : nf_nat_proto_gre successfully loaded
Dec 31 19:00:23 Voyager user.info : vpn modules : nf_conntrack_pptp successfully loaded
Dec 31 19:00:23 Voyager user.info : vpn modules : nf_nat_pptp successfully loaded
Dec 31 19:00:24 Voyager user.info : ttraff : traffic counter daemon successfully started
Dec 31 19:00:24 Voyager user.info : httpd : daemon successfully stopped
Dec 31 19:00:24 Voyager daemon.info httpd[1021]: httpd : httpd server shutdown
Dec 31 19:00:25 Voyager daemon.info httpd[1208]: httpd : httpd server started at port 80
Dec 31 19:00:25 Voyager user.info : httpd : http daemon successfully started
Dec 31 19:00:25 Voyager user.info : resetbutton : daemon successfully stopped
Dec 31 19:00:25 Voyager user.info : resetbutton : resetbutton daemon successfully started
Dec 31 19:00:30 Voyager user.info : dnsmasq : daemon successfully stopped
Dec 31 19:00:30 Voyager user.info : dnsmasq : daemon successfully started
Dec 31 19:00:30 Voyager user.info : upnp : daemon successfully stopped
Dec 31 19:00:31 Voyager user.info : vpn modules : vpn modules successfully unloaded
Dec 31 19:00:31 Voyager user.info : vpn modules : nf_conntrack_proto_gre successfully loaded
Dec 31 19:00:31 Voyager user.info : vpn modules : nf_nat_proto_gre successfully loaded
Dec 31 19:00:31 Voyager user.info : vpn modules : nf_conntrack_pptp successfully loaded
Dec 31 19:00:31 Voyager user.info : vpn modules : nf_nat_pptp successfully loaded
Dec 31 19:00:31 Voyager user.info : upnp : daemon successfully started
Dec 31 19:00:31 Voyager user.info : wland : daemon successfully stopped
Dec 31 19:00:31 Voyager user.info : wland : daemon successfully started
Dec 31 19:00:31 Voyager user.info : wan : WAN is up. IP: xxx.xxx.xxx.xxx              I changed the IP to x's, it was correct before
Dec 31 19:00:32 Voyager user.info : vpn modules : vpn modules successfully unloaded
Dec 31 19:00:32 Voyager user.info : vpn modules : nf_conntrack_proto_gre successfully loaded
Dec 31 19:00:32 Voyager user.info : vpn modules : nf_nat_proto_gre successfully loaded
Dec 31 19:00:32 Voyager user.info : vpn modules : nf_conntrack_pptp successfully loaded
Dec 31 19:00:32 Voyager user.info : vpn modules : nf_nat_pptp successfully loaded
Dec 31 19:00:32 Voyager user.info : sfe : shortcut forwarding engine successfully stopped
Dec 31 19:00:33 Voyager user.info : process_monitor : successfully started
Dec 31 19:00:33 Voyager user.info : ddns : inadyn daemon successfully started
Dec 31 19:00:34 Voyager daemon.debug ntpclient[1691]: Connecting to pool.ntp.org [64.79.100.196] ...
Aug 27 20:11:42 Voyager daemon.info ntpclient[1691]: Time set from pool.ntp.org [64.79.100.196].
Aug 27 20:11:42 Voyager daemon.info process_monitor[1690]: cyclic NTP Update success (servers pool.ntp.org)
Aug 27 20:11:43 Voyager daemon.debug process_monitor[1690]: Restarting cron (time sync change)
Aug 27 20:11:43 Voyager user.info : cron : daemon successfully stopped
Aug 27 20:11:43 Voyager user.info : cron : daemon successfully started
Aug 27 20:11:43 Voyager cron.info cron[1767]: (CRON) STARTUP (fork ok)
Aug 27 20:11:43 Voyager user.info : process_monitor : daemon successfully stopped
Aug 27 20:11:43 Voyager daemon.info process_monitor[1690]: process_monitor : cleanup timers
Aug 27 20:11:43 Voyager user.info : process_monitor : successfully started
Aug 27 20:11:43 Voyager daemon.debug process_monitor[1772]: We need to re-update after 3600 seconds
Aug 27 20:11:43 Voyager daemon.info process_monitor[1772]: process_monitor : set timer: 3600 seconds, callback: ntp_main()
Aug 27 20:11:48 Voyager user.debug : ttraff: data collection started
Aug 27 20:14:09 Voyager user.info : udhcpc : dhcp lease info hasn't changed, do nothing
Aug 27 20:14:09 Voyager user.info : udhcpc : restart multicast forwarder, in case the peer broke the connection on renew
Back to top View user's profile Send private message
tatsuya46
DD-WRT Guru


Joined: 03 Jan 2010
Posts: 7568
Location: YWG, Canada
PostPosted: Fri Aug 28, 2020 4:43    Post subject: Reply with quote
evdjj3j wrote:
evdjj3j wrote:
TP Link Archer C7 v2 US
DD-WRT v3.0-r44236 std (08/22/20)
GUI install over previous r44191
No Reset


Failed

Cannot access the internet, local network connectivity dropping over and over. Restored back to 43718 and everything is functioning correctly.


Code:

Router Name
ArcherC7v2
Router Model
TP-Link ARCHER-C7 v2
Firmware Version
DD-WRT v3.0-r44236 std (08/22/20)
Kernel Version
Linux 3.18.140-d5 #88648 Sat Aug 22 04:03:56 +04 2020 mips


Dec 31 19:00:13 Voyager syslog.info syslogd started: BusyBox v1.32.0
Dec 31 19:00:13 Voyager user.info : syslogd : daemon successfully started
Dec 31 19:00:13 Voyager user.info : resetbutton : resetbutton daemon successfully started
Dec 31 19:00:13 Voyager user.info : bridge : interface wlan0 successfully deleted from bridge br0
Dec 31 19:00:13 Voyager user.info : bridge : bridge br0 successfully added
Dec 31 19:00:13 Voyager user.info : bridge : interface eth1 successfully added to bridge br0
Dec 31 19:00:16 Voyager user.info : bridge : interface ath0 successfully added to bridge br0
Dec 31 19:00:18 Voyager user.info : bridge : interface ath1 successfully added to bridge br0
Dec 31 19:00:19 Voyager user.info : hwmon : successfully started
Dec 31 19:00:19 Voyager user.info : telnetd : daemon successfully started
Dec 31 19:00:19 Voyager user.info : syslogd : syslog daemon successfully stopped
Dec 31 19:00:19 Voyager user.info : wland : daemon successfully started
Dec 31 19:00:19 Voyager syslog.info syslogd exiting
Dec 31 19:00:20 Voyager syslog.info syslogd started: BusyBox v1.32.0
Dec 31 19:00:20 Voyager user.info : sfe : shortcut forwarding engine successfully stopped
Dec 31 19:00:20 Voyager user.info : dnsmasq : daemon successfully started
Dec 31 19:00:21 Voyager user.info : cron : daemon successfully started
Dec 31 19:00:21 Voyager cron.info cron[967]: (CRON) STARTUP (fork ok)
Dec 31 19:00:22 Voyager daemon.info httpd[973]: httpd : httpd server started at port 80
Dec 31 19:00:22 Voyager user.info : httpd : http daemon successfully started
Dec 31 19:00:23 Voyager user.info : vpn modules : vpn modules successfully unloaded
Dec 31 19:00:23 Voyager user.info : vpn modules : nf_conntrack_proto_gre successfully loaded
Dec 31 19:00:23 Voyager user.info : vpn modules : nf_nat_proto_gre successfully loaded
Dec 31 19:00:23 Voyager user.info : vpn modules : nf_conntrack_pptp successfully loaded
Dec 31 19:00:23 Voyager user.info : vpn modules : nf_nat_pptp successfully loaded
Dec 31 19:00:24 Voyager user.info : ttraff : traffic counter daemon successfully started
Dec 31 19:00:24 Voyager user.info : httpd : daemon successfully stopped
Dec 31 19:00:24 Voyager daemon.info httpd[1021]: httpd : httpd server shutdown
Dec 31 19:00:25 Voyager daemon.info httpd[1208]: httpd : httpd server started at port 80
Dec 31 19:00:25 Voyager user.info : httpd : http daemon successfully started
Dec 31 19:00:25 Voyager user.info : resetbutton : daemon successfully stopped
Dec 31 19:00:25 Voyager user.info : resetbutton : resetbutton daemon successfully started
Dec 31 19:00:30 Voyager user.info : dnsmasq : daemon successfully stopped
Dec 31 19:00:30 Voyager user.info : dnsmasq : daemon successfully started
Dec 31 19:00:30 Voyager user.info : upnp : daemon successfully stopped
Dec 31 19:00:31 Voyager user.info : vpn modules : vpn modules successfully unloaded
Dec 31 19:00:31 Voyager user.info : vpn modules : nf_conntrack_proto_gre successfully loaded
Dec 31 19:00:31 Voyager user.info : vpn modules : nf_nat_proto_gre successfully loaded
Dec 31 19:00:31 Voyager user.info : vpn modules : nf_conntrack_pptp successfully loaded
Dec 31 19:00:31 Voyager user.info : vpn modules : nf_nat_pptp successfully loaded
Dec 31 19:00:31 Voyager user.info : upnp : daemon successfully started
Dec 31 19:00:31 Voyager user.info : wland : daemon successfully stopped
Dec 31 19:00:31 Voyager user.info : wland : daemon successfully started
Dec 31 19:00:31 Voyager user.info : wan : WAN is up. IP: xxx.xxx.xxx.xxx              I changed the IP to x's, it was correct before
Dec 31 19:00:32 Voyager user.info : vpn modules : vpn modules successfully unloaded
Dec 31 19:00:32 Voyager user.info : vpn modules : nf_conntrack_proto_gre successfully loaded
Dec 31 19:00:32 Voyager user.info : vpn modules : nf_nat_proto_gre successfully loaded
Dec 31 19:00:32 Voyager user.info : vpn modules : nf_conntrack_pptp successfully loaded
Dec 31 19:00:32 Voyager user.info : vpn modules : nf_nat_pptp successfully loaded
Dec 31 19:00:32 Voyager user.info : sfe : shortcut forwarding engine successfully stopped
Dec 31 19:00:33 Voyager user.info : process_monitor : successfully started
Dec 31 19:00:33 Voyager user.info : ddns : inadyn daemon successfully started
Dec 31 19:00:34 Voyager daemon.debug ntpclient[1691]: Connecting to pool.ntp.org [64.79.100.196] ...
Aug 27 20:11:42 Voyager daemon.info ntpclient[1691]: Time set from pool.ntp.org [64.79.100.196].
Aug 27 20:11:42 Voyager daemon.info process_monitor[1690]: cyclic NTP Update success (servers pool.ntp.org)
Aug 27 20:11:43 Voyager daemon.debug process_monitor[1690]: Restarting cron (time sync change)
Aug 27 20:11:43 Voyager user.info : cron : daemon successfully stopped
Aug 27 20:11:43 Voyager user.info : cron : daemon successfully started
Aug 27 20:11:43 Voyager cron.info cron[1767]: (CRON) STARTUP (fork ok)
Aug 27 20:11:43 Voyager user.info : process_monitor : daemon successfully stopped
Aug 27 20:11:43 Voyager daemon.info process_monitor[1690]: process_monitor : cleanup timers
Aug 27 20:11:43 Voyager user.info : process_monitor : successfully started
Aug 27 20:11:43 Voyager daemon.debug process_monitor[1772]: We need to re-update after 3600 seconds
Aug 27 20:11:43 Voyager daemon.info process_monitor[1772]: process_monitor : set timer: 3600 seconds, callback: ntp_main()
Aug 27 20:11:48 Voyager user.debug : ttraff: data collection started
Aug 27 20:14:09 Voyager user.info : udhcpc : dhcp lease info hasn't changed, do nothing
Aug 27 20:14:09 Voyager user.info : udhcpc : restart multicast forwarder, in case the peer broke the connection on renew


this is fixed in next release
_________________
LATEST FIRMWARE(S)

BrainSlayer wrote:
we just do it since we do not like any restrictions enforced by stupid cocaine snorting managers

[x86_64] Haswell i3-4150/QCA9984/QCA9882 ------> r55797 std
[QUALCOMM] DIR-862L --------------------------------> r55797 std
▲ ACTIVE / INACTIVE ▼
[QUALCOMM] WNDR4300 v1 --------------------------> r50485 std
[BROADCOM] DIR-860L A1 ----------------------------> r50485 std


Sigh.. why do i exist anyway.. | I love you Anthony.. never forget that.. my other 99% that ill never see again..

Back to top View user's profile Send private message
habeIchVergessen
DD-WRT User


Joined: 04 May 2010
Posts: 431
PostPosted: Sun Aug 30, 2020 13:28    Post subject: Reply with quote
samba3 doesn't listen to SMB1 port 139.
it's useless to have an option NT1 for protocol version if no one listen on it.
Back to top View user's profile Send private message
jeeten
DD-WRT Novice


Joined: 16 Aug 2020
Posts: 12
PostPosted: Sat Sep 19, 2020 16:42    Post subject: Reply with quote
I am running this build on an ASRock G10 and I have noticed that when using iPhone WAN mode, it periodically changes which of the two USB ports is the one that the iPhone has to be connected to. I would estimate it happens roughly once a week.
Back to top View user's profile Send private message
Goto page Previous  1, 2 Display posts from previous:    Page 2 of 2
Post new topic   Reply to topic    DD-WRT 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