New BS Build: 01-18-2019-r38326

Post new topic   Reply to topic    DD-WRT Forum Index -> Broadcom SoC based Hardware
Author Message
flyzipper
DD-WRT Guru


Joined: 21 Feb 2016
Posts: 504

PostPosted: Fri Jan 18, 2019 23:14    Post subject: New BS Build: 01-18-2019-r38326 Reply with quote
Downloads at:
https://download1.dd-wrt.com/dd-wrtv2/downloads/betas/2019/01-18-2019-r38326/
ftp://ftp.dd-wrt.com/betas/2019/01-18-2019-r38326/
Also: possible alternate on DD-WRT website.

Changelogs:
SVN Changelog: Since last build: 38253
Summary: (deprecated after 29739)

Notes:
1. SFE accelerated NAT is in 33006+ builds but only in kernel 3.10 and newer
2. krack fixes for Broadcom were completed in r33678, including k26 (33655) & k24 (33656); use build 33772 or later.
3. Bridge modes on k4.4 devices may sometimes work in some configurations in certain builds but are not supported by the bcmdhd driver. Use client or repeater instead as WDS doesn't work with Broadcom ARM either (see Issue #4 below).
4. R6400v2 support added in r36811-36818, 36825, and 36826. R6700v3 support added in r36828-36840.

Tickets closed as 'fixed' (Broadcom-related and general): -

Issues, observations, and/or workarounds reported:
1. (egc) Policy-Based Routing broken if SFE enabled: http://svn.dd-wrt.com/ticket/5900
quarkysg's PBR+SFE fix: http://svn.dd-wrt.com/ticket/5986
2. Trendnet 81*DRU models are missing factory-to-flash
3. DNScrypt is mostly only using v2 protocols now, but requires Golang that DD can't use:
http://svn.dd-wrt.com/ticket/6246
4. WDS does not work on ARM devices (only MIPS<->MIPS)
5. VAPs not working at boot (k3.10?); workaround startup command:
sleep 10;stopservice nas;stopservice wlconf;startservice wlconf;startservice nas

Important: if any issues are found, please provide log info (GUI syslog, `dmesg`, `cat /var/log/messages`).
Or put into SVN ticket. For firewall issues, also provide "iptables" info (`iptables -L`, `iptables -t nat -L`, & the /tmp/.ipt file).

Template to copy (after "Code:") for posting issues, be sure to include the mode in use (gateway, AP, CB, etc.):
Code:
[b]Router/Version: [/b]
[b]File: [/b]
[b]Kernel: [/b]
[b]Mode: [/b]
[b]Status: [/b]

WARNING: This thread is to report on flashing this experimental test build, providing important info for both developers and users. Always state your hardware model, version, mode (e.g. Repeater) and SPECIFIC build (e.g. 33555_NEWD-2_K3.x_mega-nv64k.bin). Please avoid discussions and create a new thread to discuss specific problems or questions, as this thread is for reporting, not support. Posts may be deleted or moved to keep this thread manageable and useful. If you don't understand the risks or what to flash and how, with a means of recovery if it bricks, do NOT flash this experimental test build.


Last edited by flyzipper on Sat Jan 19, 2019 8:28; edited 1 time in total
Sponsor
flyzipper
DD-WRT Guru


Joined: 21 Feb 2016
Posts: 504

PostPosted: Fri Jan 18, 2019 23:20    Post subject: Reply with quote
Router/Version: Netgear R7000
Firmware: DD-WRT v3.0-r38326 std (01/18/19)
Kernel: Linux 4.4.171 #4479 SMP Fri Jan 18 08:23:20 CET 2019 armv7l
Previous: r38302
Mode/Status: Gateway / working
Reset: no
Issues/Errors: No issues so far.

Uptime: 17m
Temperatures: CPU 61.9 °C / WL0 47.5 °C / WL1 51.5 °C
Spc.
DD-WRT User


Joined: 29 Mar 2007
Posts: 74

PostPosted: Sat Jan 19, 2019 2:30    Post subject: Reply with quote
Router/Version: Asus RT-AC68U HW Rev: E1
Firmware Version: DD-WRT v3.0-r38326 (01/18/19)
Kernel Version: Linux 4.4.171 #4479 SMP Fri Jan 18 18:23:20 CET 2019 armv7l

Previous: Asus original Firmware Version 3.0.0.4.384.45149

Mode/Status: Access Point
Reset: yes
Issues/Errors: No issues / Cosmetic Issue 5GHz LED Diod not working.

Uptime: 25m
Temperatures: CPU 72.5 °C / WL0 46.8 °C / WL1 48.9 °C


Last edited by Spc. on Sun Jan 20, 2019 3:50; edited 1 time in total
SinCalChewy
DD-WRT User


Joined: 09 Nov 2014
Posts: 314
Location: Bakersfield, CA

PostPosted: Sat Jan 19, 2019 6:27    Post subject: Reply with quote
Router/Version: 2x Linksys E3000
Firmware: dd-wrt.v24-38326_NEWD-2_K3.x_mega-e3000.bin
Previous: dd-wrt.v24-38253_NEWD-2_K3.x_mega-e3000.bin
Kernel: Linux 3.10.108-d8 #22645 Fri Jan 18 15:50:42 CET 2019 mips
Mode: Both are client bridges to my gateway R7000, with all settings NOT needed for a bridge turned off.
Status: So far so good. Gonna run a few speedtests to make sure. Smile

Note: It seems faster at loading pages and speedtests compared to the last build. Speedtest is quite a bit faster. Smile

Router/Version: Trendnet TEW811DRU
Firmware: DD-WRT v3.0-r38326 mini (01/18/19)
Kernel: Linux 4.4.171 #4482 Fri Jan 18 08:52:26 CET 2019 armv7l
Mode: AC only client bridge, with all settings not required for a bridge disabled.
Status: Once again, working okay so far. If problems arise, I'll report back.

Router/Version: Linksys E1200v2
Firmware: dd-wrt.v24-38326_NEWD-2_K3.x_mega-e1200v2.bin
Previous: dd-wrt.v24-38155_NEWD-2_K3.x_mega-e1200v2.bin
Kernel: Linux 3.10.108-d8 #22645 Fri Jan 18 15:50:42 CET 2019 mips
Mode: Repeater that we use for our guests
Status: So far so good! Lol

_________________

Deployed Routers:
Netgear R7800 - 1x build 46979
- Gateway (USB /w Entware, CAKE QoS)
Netgear R7000 - 3x build 46979
Mile-Lile
DD-WRT Guru


Joined: 24 Feb 2013
Posts: 1634
Location: Belgrade

PostPosted: Sat Jan 19, 2019 11:20    Post subject: Reply with quote
Router Model Netgear R6250
Firmware Version DD-WRT v3.0-r38326 std (01/18/19)
Kernel Version Linux 4.4.171 #4479 SMP Fri Jan 18 08:23:20 CET 2019 armv7l


Status: Working great!
Reset: No
Errors: None

Thx BS for great work!
I tested your last feature added - Tor on unbridged VAP. Works. I wish it could be different. Tor is working for whole network but it would be more better if it could be running only on unbridged VAP. We could have separate, unbridged VAP with Tor on it, so when you want to have different IP or be anonimized when surfing just connect to that VAP... but assume lots of work is needed...
kernel-panic69
DD-WRT Guru


Joined: 08 May 2018
Posts: 14221
Location: Texas, USA

PostPosted: Sat Jan 19, 2019 16:07    Post subject: Cisco Linksys E4200 v1 Reply with quote
Router/Version: Cisco Linksys E4200 v1
File: dd-wrt.v24-38326_NEWD-2_K3.x_mega-e4200.bin
Firmware: DD-WRT v3.0-r38326M mega (01/18/19)
Kernel: Linux 3.10.108-d8 #22645 Fri Jan 18 15:50:42 CET 2019 mips
Previous: DD-WRT v3.0-r38302M mega (01/15/19)
Reset: No
Mode: Gateway/AP
Uptime: ~45 min
Status: OK
Issues/Errors:

No new errors. Same things are still broken in public builds.


Last edited by kernel-panic69 on Fri Jan 25, 2019 17:50; edited 1 time in total
Brimmy
DD-WRT User


Joined: 29 Mar 2015
Posts: 398

PostPosted: Sat Jan 19, 2019 19:39    Post subject: Reply with quote
Router/Version: Buffalo WZR-1750DHP/DHPD
Firmware: DD-WRT v3.0-r38326 std (01/18/19
Kernel: Linux 4.4.171 #4479 SMP Fri Jan 18 08:23:20 CET 2019 armv7l
Previous: BSr38253
Mode/Status: Gateway / WIFI = AP / Seems ok
CPU overclocked to 1400mhz from default 800mhz via r33006
Reset: No but i did power cycle after flashing
Issues/Errors: None
UpTime: 10m

This build flashed with no problems. Thanks for fixing whatever it was.
marklg
DD-WRT Novice


Joined: 19 Oct 2017
Posts: 29

PostPosted: Sun Jan 20, 2019 14:49    Post subject: Reply with quote
Router/Version: E3000
File: dd-wrt.v24-38326_NEWD-2_K3.x_mega-e3000.bin
Kernel: Linux 3.10.108-d8 #22645 Fri Jan 18 15:50:42 CET 2019 mips
Mode: AP
Reset: No
Status: With workaround, VAPs work. Must use Auto channels. AP Isolation still seems to be enabled even though set to disabled. Used as one of three APs. Auto channels seems to be working.
ellul
DD-WRT Novice


Joined: 28 Dec 2018
Posts: 3

PostPosted: Sun Jan 20, 2019 15:33    Post subject: Reply with quote
Router/Version: Asus RT-AC56U
File: New BS Build: 01-18-2019-r38326
Kernel: Linux 4.4.171 #4479 SMP Fri Jan 18 08:23:CET armv7l
Mode: Gateway/AP
Uptime: 1hr
Status: OK
Issues/Errors: None
denislen
DD-WRT User


Joined: 16 Sep 2015
Posts: 50

PostPosted: Sun Jan 20, 2019 19:36    Post subject: Reply with quote
asus rtn10u (black)

no start with usb flash inserted

no usb support: no ext3 and others
lsmod
Module Size Used by
nf_nat_pptp 1440 0
nf_conntrack_pptp 3456 1 nf_nat_pptp
nf_nat_proto_gre 816 1 nf_nat_pptp
nf_conntrack_proto_gre 2704 1 nf_conntrack_pptp
shortcut_fe 132960 0
tun 16192 2
usb_storage 38176 0
sr_mod 11680 0
cdrom 31280 1 sr_mod
sd_mod 26960 0
scsi_mod 75648 3 usb_storage,sr_mod,sd_mod
ohci_hcd 15520 0
ehci_pci 2496 0
ehci_hcd 32016 1 ehci_pci
usbcore 118960 5 usb_storage,ohci_hcd,ehci_pci,ehci_hcd
usb_common 1040 1 usbcore
watchsat
DD-WRT User


Joined: 31 Oct 2017
Posts: 55

PostPosted: Mon Jan 21, 2019 14:49    Post subject: Reply with quote
Router Model: Linksys EA6700
Firmware Version: DD-WRT v3.0-r38326 std (01/18/19)
Kernel Version: Linux 4.4.171 #4479 SMP Fri Jan 18 08:23:20 CET 2019 armv7l
Uptime: 1 day, 23:35
Mode: AP
Reset: No
Status: Okay, but wireless devices easily lost connections and took long time to get re-connrect


Router Model: Linksys EA6400
Firmware Version: DD-WRT v3.0-r38326 std (01/18/19)
Kernel Version: Linux 4.4.171 #4479 SMP Fri Jan 18 08:23:20 CET 2019 armv7l
Uptime: 1 day, 23:25
Mode: AP
Reset: No
Status: Okay, but wireless devices easily lost connections and took long time to get re-connrect
Wildlion
DD-WRT Guru


Joined: 24 May 2016
Posts: 1415

PostPosted: Mon Jan 21, 2019 16:05    Post subject: Reply with quote
Router: Buffalo WZR-1750DHP
Firmware: buffalo-wzr-1750dhp-webflash.bin (v3.0-r38326 std)
Kernel: Linux 4.4.171 #4479 SMP Fri Jan 18 08:23:20 CET 2019 armv7l
Status: Working
Reset: No
Notes on configuration:

    FTP server
    DNSMasq
    USB v3.0
    DHCP reservation

Errors:

    1. No overclocking

itsnewtoyou
DD-WRT Novice


Joined: 21 Dec 2011
Posts: 3

PostPosted: Mon Jan 21, 2019 18:44    Post subject: New BS Build: 01-18-2019-r38326 Reply with quote
To get things working again I had to revert all the way back to DD-WRT v3.0-r37305 std (10/10/1Cool. Which was the last running version I was able to not have any issues with.

Router/Version: Netgear R8000
File: DD-WRT v3.0-r38326 std (01/18/19) ftp://ftp.dd-wrt.com/betas/2019/01-18-2019-r38326/netgear-r8000/netgear-r8000-webflash.bin
Kernel: Linux 4.4.171 #4484 SMP Fri Jan 18 09:05:08 CET 2019 armv7l
Previous: 12-12-2018-r37961
Mode: Gateway
Uptime: 19:16
Status: The previous version had one iPhone X connection would drop and come back over and over. New version fixed that so far but now there are two Amazon devices not connecting. One is a Fire8 tablet and the other is Alexa Echo. There is another Alexa Dot that connects fine and another Fire8 tablet that connects with no issue. Both devices are saying authentication failed. I did not do a 30/30/30 yet but will try later today.


DD-WRT v3.0-r38326 std (c) 2019 NewMedia-NET GmbH
Release: 01/18/19


NightHawk login: root
Password:
==========================================================

___ ___ _ _____ ______ ____ ___
/ _ \/ _ \___| | /| / / _ \/_ __/ _ __|_ / / _ \
/ // / // /___/ |/ |/ / , _/ / / | |/ //_ <_/ // /
/____/____/ |__/|__/_/|_| /_/ |___/____(_)___/

DD-WRT v3.0
http://www.dd-wrt.com

==========================================================


BusyBox v1.30.0 (2019-01-18 09:06:12 CET) built-in shell (ash)

root@NightHawk:~# dmesg
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
br0: received packet on eth3 with own address as source address
br0: received packet on eth3 with own address as source address
br0: received packet on eth3 with own address as source address
br0: received packet on eth3 with own address as source address
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
br0: received packet on eth3 with own address as source address
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
net_ratelimit: 6 callbacks suppressed
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
net_ratelimit: 14 callbacks suppressed
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
br0: received packet on eth3 with own address as source address
br0: received packet on eth3 with own address as source address
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
br0: received packet on eth3 with own address as source address
br0: received packet on eth3 with own address as source address
net_ratelimit: 5 callbacks suppressed
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
net_ratelimit: 11 callbacks suppressed
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
br0: received packet on eth3 with own address as source address
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
net_ratelimit: 12 callbacks suppressed
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
net_ratelimit: 7 callbacks suppressed
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
br0: received packet on eth3 with own address as source address
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
net_ratelimit: 5 callbacks suppressed
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
net_ratelimit: 6 callbacks suppressed
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
br0: received packet on eth3 with own address as source address
br0: received packet on eth3 with own address as source address
net_ratelimit: 6 callbacks suppressed
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
br0: received packet on eth3 with own address as source address
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
br0: received packet on eth3 with own address as source address
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
br0: received packet on eth3 with own address as source address
br0: received packet on eth3 with own address as source address
br0: received packet on eth3 with own address as source address
br0: received packet on eth3 with own address as source address
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
net_ratelimit: 17 callbacks suppressed
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
net_ratelimit: 8 callbacks suppressed
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
br0: received packet on eth3 with own address as source address
br0: received packet on eth3 with own address as source address
br0: received packet on eth3 with own address as source address
br0: received packet on eth3 with own address as source address
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
net_ratelimit: 3 callbacks suppressed
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
br0: received packet on eth3 with own address as source address
net_ratelimit: 17 callbacks suppressed
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
br0: received packet on eth3 with own address as source address
br0: received packet on eth3 with own address as source address
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
net_ratelimit: 3 callbacks suppressed
br0: received packet on eth3 with own address as source address
br0: received packet on eth3 with own address as source address
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
br0: received packet on eth2 with own address as source address
root@NightHawk:~# cat /var/log/messages
Dec 31 17:00:26 NightHawk syslog.info syslogd started: BusyBox v1.30.0
Dec 31 17:00:26 NightHawk syslog.info syslogd started: BusyBox v1.30.0
Jan 1 00:00:26 NightHawk user.info : syslogd : daemon successfully started
Jan 1 00:00:26 NightHawk user.info : wland : daemon successfully started
Jan 1 00:00:26 NightHawk user.info : telnetd : daemon successfully started
Jan 1 00:00:26 NightHawk user.info : upnp : daemon successfully started
Jan 1 00:00:26 NightHawk user.info : cron : daemon successfully started
Jan 1 00:00:26 NightHawk cron.info cron[962]: (CRON) STARTUP (fork ok)
Jan 1 00:00:26 NightHawk daemon.info radvd[951]: version 2.17 started
Jan 1 00:00:26 NightHawk user.info : radvd : RADVD daemon successfully started
Jan 1 00:00:27 NightHawk user.info : dnsmasq : daemon successfully started
Jan 1 00:00:27 NightHawk user.info : vpn modules : vpn modules successfully unloaded
Jan 1 00:00:27 NightHawk user.info : vpn modules : nf_conntrack_proto_gre successfully loaded
Jan 1 00:00:27 NightHawk user.info : vpn modules : nf_nat_proto_gre successfully loaded
Jan 1 00:00:27 NightHawk user.info : vpn modules : nf_conntrack_pptp successfully loaded
Jan 1 00:00:27 NightHawk user.info : vpn modules : nf_nat_pptp successfully loaded
Jan 1 00:00:27 NightHawk user.info : ttraff : traffic counter daemon successfully started
Jan 1 00:00:28 NightHawk user.info : dnsmasq : daemon successfully stopped
Jan 1 00:00:28 NightHawk user.info : dnsmasq : daemon successfully started
Jan 1 00:00:28 NightHawk user.info : upnp : daemon successfully stopped
Jan 1 00:00:28 NightHawk user.info : upnp : daemon successfully started
Jan 1 00:00:28 NightHawk user.info : wland : daemon successfully stopped
Jan 1 00:00:28 NightHawk user.info : wland : daemon successfully started
Jan 1 00:00:28 NightHawk user.info : wan : WAN is up. IP: 71.205.194.69
Jan 1 00:00:28 NightHawk user.info : speedchecker : client started
Jan 1 00:00:28 NightHawk user.info : radvd : daemon successfully stopped
Jan 1 00:00:28 NightHawk daemon.warn radvd[963]: exiting, 1 sigterm(s) received
Jan 1 00:00:28 NightHawk daemon.info radvd[963]: sending stop adverts
Jan 1 00:00:28 NightHawk daemon.info radvd[963]: removing /var/run/radvd.pid
Jan 1 00:00:28 NightHawk daemon.info radvd[963]: returning from radvd main
Jan 1 00:00:28 NightHawk daemon.info radvd[1102]: version 2.17 started
Jan 1 00:00:28 NightHawk daemon.warn radvd[1102]: invalid all-zeros prefix in /tmp/radvd.conf, line 11
Jan 1 00:00:28 NightHawk user.info : radvd : RADVD daemon successfully started
Jan 1 00:00:28 NightHawk user.info : process_monitor : successfully started
Jan 1 00:00:28 NightHawk user.info : scc : speedchecker successfully stopped
Jan 1 00:00:28 NightHawk daemon.debug ntpclient[1106]: Connecting to 2.pool.ntp.org [73.113.173.127] ...
Jan 1 00:00:28 NightHawk user.info : speedchecker : client started
Jan 20 23:21:24 NightHawk daemon.info ntpclient[1106]: Time set from 2.pool.ntp.org [73.113.173.127].
Jan 20 23:21:24 NightHawk daemon.info process_monitor[1105]: cyclic NTP Update success (servers 2.pool.ntp.org 212.18.3.19 88.99.174.22)
Jan 20 23:21:24 NightHawk daemon.debug process_monitor[1105]: Restarting cron (time sync change)
Jan 20 23:21:24 NightHawk user.info : cron : daemon successfully stopped
Jan 20 23:21:24 NightHawk user.info : process_monitor : daemon successfully stopped
Jan 20 23:21:24 NightHawk user.info : cron : daemon successfully started
Jan 20 23:21:24 NightHawk cron.info cron[1192]: (CRON) STARTUP (fork ok)
Jan 20 23:21:24 NightHawk daemon.info httpd[1143]: httpd : httpd server started at port 80
Jan 20 23:21:25 NightHawk user.info : vpn modules : vpn modules successfully unloaded
Jan 20 23:21:25 NightHawk user.info : vpn modules : nf_conntrack_proto_gre successfully loaded
Jan 20 23:21:25 NightHawk user.info : vpn modules : nf_nat_proto_gre successfully loaded
Jan 20 23:21:25 NightHawk user.info : vpn modules : nf_conntrack_pptp successfully loaded
Jan 20 23:21:25 NightHawk user.info : vpn modules : nf_nat_pptp successfully loaded
Jan 20 23:21:25 NightHawk user.info : process_monitor : successfully started
Jan 20 23:21:25 NightHawk daemon.debug process_monitor[1256]: We need to re-update after 3600 seconds
Jan 20 23:21:25 NightHawk daemon.info process_monitor[1256]: process_monitor : set timer: 3600 seconds, callback: ntp_main()
Jan 20 23:21:28 NightHawk user.info : dhcp6c : daemon successfully stopped
Jan 20 23:21:28 NightHawk user.info : dnsmasq : daemon successfully stopped
Jan 20 23:21:28 NightHawk user.info : dnsmasq : daemon successfully started
Jan 20 23:21:28 NightHawk user.info : upnp : daemon successfully stopped
Jan 20 23:21:28 NightHawk user.info : upnp : daemon successfully started
Jan 20 23:21:28 NightHawk user.info : wland : daemon successfully stopped
Jan 20 23:21:28 NightHawk user.info : wland : daemon successfully started
Jan 20 23:21:28 NightHawk user.info : wan : WAN is up. IP: 71.205.194.69
Jan 20 23:21:28 NightHawk user.info : scc : speedchecker successfully stopped
Jan 20 23:21:28 NightHawk user.info : speedchecker : client started
Jan 20 23:21:28 NightHawk user.info : radvd : daemon successfully stopped
Jan 20 23:21:28 NightHawk daemon.warn radvd[1103]: exiting, 1 sigterm(s) received
Jan 20 23:21:28 NightHawk daemon.info radvd[1103]: sending stop adverts
Jan 20 23:21:28 NightHawk daemon.info radvd[1103]: removing /var/run/radvd.pid
Jan 20 23:21:28 NightHawk daemon.info radvd[1103]: returning from radvd main
Jan 20 23:21:28 NightHawk daemon.info radvd[1295]: version 2.17 started
Jan 20 23:21:28 NightHawk daemon.warn radvd[1295]: invalid all-zeros prefix in /tmp/radvd.conf, line 11
Jan 20 23:21:28 NightHawk user.info : radvd : RADVD daemon successfully started
Jan 20 23:21:28 NightHawk user.info : process_monitor : daemon successfully stopped
Jan 20 23:21:28 NightHawk user.info : process_monitor : successfully started
Jan 20 23:21:28 NightHawk user.info : scc : speedchecker successfully stopped
Jan 20 23:21:28 NightHawk user.info : speedchecker : client started
Jan 20 23:21:28 NightHawk daemon.debug ntpclient[1299]: Connecting to 2.pool.ntp.org [73.113.173.127] ...
Jan 20 23:21:28 NightHawk daemon.info ntpclient[1299]: Time set from 2.pool.ntp.org [73.113.173.127].
Jan 20 23:21:28 NightHawk daemon.info process_monitor[1298]: cyclic NTP Update success (servers 2.pool.ntp.org 212.18.3.19 88.99.174.22)
Jan 20 23:21:28 NightHawk daemon.debug process_monitor[1298]: We need to re-update after 3600 seconds
Jan 20 23:21:28 NightHawk daemon.info process_monitor[1298]: process_monitor : set timer: 3600 seconds, callback: ntp_main()
Jan 20 23:21:29 NightHawk user.info : vpn modules : vpn modules successfully unloaded
Jan 20 23:21:29 NightHawk user.info : vpn modules : nf_conntrack_proto_gre successfully loaded
Jan 20 23:21:29 NightHawk user.info : vpn modules : nf_nat_proto_gre successfully loaded
Jan 20 23:21:29 NightHawk user.info : vpn modules : nf_conntrack_pptp successfully loaded
Jan 20 23:21:29 NightHawk user.info : vpn modules : nf_nat_pptp successfully loaded
Jan 20 23:21:36 NightHawk user.info : nas : start nas lan
Jan 20 23:21:36 NightHawk user.info : nas : start nas for wl0
Jan 20 23:21:36 NightHawk user.info : nas : NAS lan (wl0 interface) successfully started
Jan 20 23:21:36 NightHawk user.info : nas : start nas lan
Jan 20 23:21:36 NightHawk user.info : nas : start nas for wl1
Jan 20 23:21:36 NightHawk user.info : nas : NAS lan (wl1 interface) successfully started
Jan 20 23:21:36 NightHawk user.info : nas : start nas lan
Jan 20 23:21:36 NightHawk user.info : nas : start nas for wl2
Jan 20 23:21:36 NightHawk user.info : nas : NAS lan (wl2 interface) successfully started
Jan 20 23:21:36 NightHawk user.info : httpd : daemon successfully stopped
Jan 20 23:21:36 NightHawk daemon.info httpd[1195]: httpd : httpd server shutdown
Jan 20 23:21:36 NightHawk daemon.info httpd[1443]: httpd : httpd server started at port 80
Jan 20 23:21:36 NightHawk user.info : resetbutton : daemon successfully stopped
Jan 20 23:21:36 NightHawk user.info : resetbutton : resetbutton daemon successfully started
Jan 20 23:21:36 NightHawk user.info : Reinitialize Wifi0
Jan 20 23:21:38 NightHawk user.info : radvd : daemon successfully stopped
Jan 20 23:21:38 NightHawk daemon.warn radvd[1296]: exiting, 1 sigterm(s) received
Jan 20 23:21:38 NightHawk daemon.info radvd[1296]: sending stop adverts
Jan 20 23:21:38 NightHawk daemon.info radvd[1296]: removing /var/run/radvd.pid
Jan 20 23:21:38 NightHawk daemon.info radvd[1296]: returning from radvd main
Jan 20 23:21:38 NightHawk user.debug : ttraff: data collection started
Jan 20 23:21:38 NightHawk daemon.info radvd[1458]: version 2.17 started
Jan 20 23:21:38 NightHawk user.info : radvd : RADVD daemon successfully started
Jan 20 23:21:42 NightHawk user.info : Reinitialize Wifi1
Jan 20 23:21:44 NightHawk user.info : Reinitialize Wifi2
Jan 20 23:23:58 NightHawk user.info : nas : daemon successfully stopped
Jan 20 23:23:58 NightHawk user.info : ttraff : traffic counter daemon successfully stopped
Jan 20 23:23:58 NightHawk user.info : bridge : interface vlan1 successfully deleted from bridge br0
Jan 20 23:23:58 NightHawk user.info : bridge : interface eth1 successfully deleted from bridge br0
Jan 20 23:23:58 NightHawk user.info : bridge : interface eth2 successfully deleted from bridge br0
Jan 20 23:23:58 NightHawk user.info : udhcpc : udhcp client process successfully stopped
Jan 20 23:23:58 NightHawk user.info : bridge : interface eth3 successfully deleted from bridge br0
Jan 20 23:23:58 NightHawk user.info : bridge : bridge br0 successfully deleted
Jan 20 23:24:00 NightHawk user.info : nas : daemon hanging, send SIGKILL
Jan 20 23:24:00 NightHawk user.info : bridge : bridge br0 successfully added
Jan 20 23:24:00 NightHawk user.info : bridge : interface vlan1 successfully added to bridge br0
Jan 20 23:24:06 NightHawk user.info : bridge : interface eth1 successfully added to bridge br0
Jan 20 23:24:08 NightHawk user.info : bridge : interface eth2 successfully added to bridge br0
Jan 20 23:24:14 NightHawk user.info : bridge : interface eth3 successfully added to bridge br0
Jan 20 23:24:14 NightHawk user.info : vpn modules : vpn modules successfully unloaded
Jan 20 23:24:14 NightHawk user.info : vpn modules : nf_conntrack_proto_gre successfully loaded
Jan 20 23:24:14 NightHawk user.info : vpn modules : nf_nat_proto_gre successfully loaded
Jan 20 23:24:15 NightHawk user.info : vpn modules : nf_conntrack_pptp successfully loaded
Jan 20 23:24:15 NightHawk user.info : vpn modules : nf_nat_pptp successfully loaded
Jan 20 23:24:15 NightHawk user.info : ttraff : traffic counter daemon successfully started
Jan 20 23:24:15 NightHawk user.debug : ttraff: data collection started
Jan 20 23:24:15 NightHawk user.info : dnsmasq : daemon successfully stopped
Jan 20 23:24:15 NightHawk user.info : dnsmasq : daemon successfully started
Jan 20 23:24:15 NightHawk user.info : nas : start nas lan
Jan 20 23:24:15 NightHawk user.info : nas : start nas for wl0
Jan 20 23:24:15 NightHawk user.info : nas : NAS lan (wl0 interface) successfully started
Jan 20 23:24:15 NightHawk user.info : nas : start nas lan
Jan 20 23:24:15 NightHawk user.info : nas : start nas for wl1
Jan 20 23:24:15 NightHawk user.info : nas : NAS lan (wl1 interface) successfully started
Jan 20 23:24:15 NightHawk user.info : nas : start nas lan
Jan 20 23:24:15 NightHawk user.info : nas : start nas for wl2
Jan 20 23:24:15 NightHawk user.info : nas : NAS lan (wl2 interface) successfully started
Jan 20 23:24:15 NightHawk user.info : dhcp6c : daemon successfully stopped
Jan 20 23:24:16 NightHawk user.info : vpn modules : vpn modules successfully unloaded
Jan 20 23:24:16 NightHawk user.info : vpn modules : nf_conntrack_proto_gre successfully loaded
Jan 20 23:24:16 NightHawk user.info : vpn modules : nf_nat_proto_gre successfully loaded
Jan 20 23:24:16 NightHawk user.info : vpn modules : nf_conntrack_pptp successfully loaded
Jan 20 23:24:16 NightHawk user.info : vpn modules : nf_nat_pptp successfully loaded
Jan 20 23:24:16 NightHawk user.info : cron : daemon successfully stopped
Jan 20 23:24:16 NightHawk user.info : cron : daemon successfully started
Jan 20 23:24:16 NightHawk cron.info cron[2188]: (CRON) STARTUP (fork ok)
Jan 20 23:24:17 NightHawk user.info : dhcp6c : daemon hanging, send SIGKILL
Jan 20 23:24:17 NightHawk user.info : dnsmasq : daemon successfully stopped
Jan 20 23:24:17 NightHawk user.info : dnsmasq : daemon successfully started
Jan 20 23:24:17 NightHawk user.info : upnp : daemon successfully stopped
Jan 20 23:24:17 NightHawk user.info : upnp : daemon successfully started
Jan 20 23:24:17 NightHawk user.info : wland : daemon successfully stopped
Jan 20 23:24:18 NightHawk user.info : wland : daemon successfully started
Jan 20 23:24:18 NightHawk user.info : wan : WAN is up. IP: 71.205.194.69
Jan 20 23:24:18 NightHawk user.info : scc : speedchecker successfully stopped
Jan 20 23:24:18 NightHawk user.info : speedchecker : client started
Jan 20 23:24:18 NightHawk user.info : radvd : daemon successfully stopped
Jan 20 23:24:18 NightHawk daemon.warn radvd[1459]: exiting, 1 sigterm(s) received
Jan 20 23:24:18 NightHawk daemon.info radvd[1459]: sending stop adverts
Jan 20 23:24:18 NightHawk daemon.info radvd[1459]: removing /var/run/radvd.pid
Jan 20 23:24:18 NightHawk daemon.info radvd[1459]: returning from radvd main
Jan 20 23:24:18 NightHawk daemon.info radvd[2209]: version 2.17 started
Jan 20 23:24:18 NightHawk daemon.warn radvd[2209]: invalid all-zeros prefix in /tmp/radvd.conf, line 11
Jan 20 23:24:18 NightHawk user.info : radvd : RADVD daemon successfully started
Jan 20 23:24:18 NightHawk user.info : process_monitor : daemon successfully stopped
Jan 20 23:24:18 NightHawk user.info : process_monitor : successfully started
Jan 20 23:24:18 NightHawk user.info : scc : speedchecker successfully stopped
Jan 20 23:24:18 NightHawk user.info : speedchecker : client started
Jan 20 23:24:18 NightHawk daemon.debug ntpclient[2213]: Connecting to time.nist.gov [132.163.97.1] ...
Jan 20 23:24:18 NightHawk daemon.info ntpclient[2213]: Time set from time.nist.gov [132.163.97.1].
Jan 20 23:24:18 NightHawk daemon.info process_monitor[2212]: cyclic NTP Update success (servers time.nist.gov)
Jan 20 23:24:18 NightHawk daemon.debug process_monitor[2212]: We need to re-update after 3600 seconds
Jan 20 23:24:18 NightHawk daemon.info process_monitor[2212]: process_monitor : set timer: 3600 seconds, callback: ntp_main()
Jan 20 23:24:18 NightHawk user.info : httpd : daemon successfully stopped
Jan 20 23:24:18 NightHawk daemon.info httpd[1447]: httpd : httpd server shutdown
Jan 20 23:24:18 NightHawk daemon.info httpd[2243]: httpd : httpd server started at port 80
Jan 20 23:24:20 NightHawk user.info : vpn modules : vpn modules successfully unloaded
Jan 20 23:24:20 NightHawk user.info : vpn modules : nf_conntrack_proto_gre successfully loaded
Jan 20 23:24:20 NightHawk user.info : vpn modules : nf_nat_proto_gre successfully loaded
Jan 20 23:24:20 NightHawk user.info : vpn modules : nf_conntrack_pptp successfully loaded
Jan 20 23:24:20 NightHawk user.info : vpn modules : nf_nat_pptp successfully loaded
Jan 20 23:24:22 NightHawk user.info : radvd : daemon successfully stopped
Jan 20 23:24:22 NightHawk daemon.warn radvd[2210]: exiting, 1 sigterm(s) received
Jan 20 23:24:22 NightHawk daemon.info radvd[2210]: sending stop adverts
Jan 20 23:24:22 NightHawk daemon.info radvd[2210]: removing /var/run/radvd.pid
Jan 20 23:24:22 NightHawk daemon.info radvd[2210]: returning from radvd main
Jan 20 23:24:22 NightHawk daemon.info radvd[2295]: version 2.17 started
Jan 20 23:24:22 NightHawk user.info : radvd : RADVD daemon successfully started
Jan 21 00:24:18 NightHawk daemon.debug ntpclient[2798]: Connecting to time.nist.gov [2610:20:6f96:96::4] ...
Jan 21 00:24:18 NightHawk daemon.info ntpclient[2798]: Time set from time.nist.gov [2610:20:6f96:96::4].
Jan 21 00:24:18 NightHawk daemon.info process_monitor[2212]: cyclic NTP Update success (servers time.nist.gov)
Jan 21 01:24:18 NightHawk daemon.debug ntpclient[3096]: Connecting to time.nist.gov [2610:20:6f97:97::4] ...
Jan 21 01:24:18 NightHawk daemon.info ntpclient[3096]: Time set from time.nist.gov [2610:20:6f97:97::4].
Jan 21 01:24:18 NightHawk daemon.info process_monitor[2212]: cyclic NTP Update success (servers time.nist.gov)
Jan 21 02:24:18 NightHawk daemon.debug ntpclient[3406]: Connecting to time.nist.gov [2610:20:6f96:96::4] ...
Jan 21 02:24:18 NightHawk daemon.info ntpclient[3406]: Time set from time.nist.gov [2610:20:6f96:96::4].
Jan 21 02:24:18 NightHawk daemon.info process_monitor[2212]: cyclic NTP Update success (servers time.nist.gov)
Jan 21 03:24:18 NightHawk daemon.debug ntpclient[3716]: Connecting to time.nist.gov [2610:20:6f97:97::4] ...
Jan 21 03:24:18 NightHawk daemon.info ntpclient[3716]: Time set from time.nist.gov [2610:20:6f97:97::4].
Jan 21 03:24:18 NightHawk daemon.info process_monitor[2212]: cyclic NTP Update success (servers time.nist.gov)
Jan 21 04:24:18 NightHawk daemon.debug ntpclient[4011]: Connecting to time.nist.gov [2610:20:6f97:97::4] ...
Jan 21 04:24:19 NightHawk daemon.info ntpclient[4011]: Time set from time.nist.gov [2610:20:6f97:97::4].
Jan 21 04:24:19 NightHawk daemon.info process_monitor[2212]: cyclic NTP Update success (servers time.nist.gov)
Jan 21 05:24:19 NightHawk daemon.debug ntpclient[4340]: Connecting to time.nist.gov [2610:20:6f97:97::4] ...
Jan 21 05:24:19 NightHawk daemon.info ntpclient[4340]: Time set from time.nist.gov [2610:20:6f97:97::4].
Jan 21 05:24:19 NightHawk daemon.info process_monitor[2212]: cyclic NTP Update success (servers time.nist.gov)
Jan 21 06:24:19 NightHawk daemon.debug ntpclient[4635]: Connecting to time.nist.gov [2610:20:6f97:97::4] ...
Jan 21 06:24:19 NightHawk daemon.info ntpclient[4635]: Time set from time.nist.gov [2610:20:6f97:97::4].
Jan 21 06:24:19 NightHawk daemon.info process_monitor[2212]: cyclic NTP Update success (servers time.nist.gov)
Jan 21 06:59:38 NightHawk user.debug : ttraff: data for 20-1-2019 commited to nvram
Jan 21 07:24:19 NightHawk daemon.debug ntpclient[4932]: Connecting to time.nist.gov [2610:20:6f96:96::4] ...
Jan 21 07:24:19 NightHawk daemon.info ntpclient[4932]: Time set from time.nist.gov [2610:20:6f96:96::4].
Jan 21 07:24:19 NightHawk daemon.info process_monitor[2212]: cyclic NTP Update success (servers time.nist.gov)
Jan 21 08:24:19 NightHawk daemon.debug ntpclient[5228]: Connecting to time.nist.gov [2610:20:6f97:97::4] ...
Jan 21 08:24:19 NightHawk daemon.info ntpclient[5228]: Time set from time.nist.gov [2610:20:6f97:97::4].
Jan 21 08:24:19 NightHawk daemon.info process_monitor[2212]: cyclic NTP Update success (servers time.nist.gov)
Jan 21 09:24:19 NightHawk daemon.debug ntpclient[5525]: Connecting to time.nist.gov [2610:20:6f97:97::4] ...
Jan 21 09:24:19 NightHawk daemon.info ntpclient[5525]: Time set from time.nist.gov [2610:20:6f97:97::4].
Jan 21 09:24:19 NightHawk daemon.info process_monitor[2212]: cyclic NTP Update success (servers time.nist.gov)
Jan 21 10:24:20 NightHawk daemon.debug ntpclient[5821]: Connecting to time.nist.gov [2610:20:6f97:97::4] ...
Jan 21 10:24:20 NightHawk daemon.info ntpclient[5821]: Time set from time.nist.gov [2610:20:6f97:97::4].
Jan 21 10:24:20 NightHawk daemon.info process_monitor[2212]: cyclic NTP Update success (servers time.nist.gov)
Jan 21 11:24:20 NightHawk daemon.debug ntpclient[6117]: Connecting to time.nist.gov [2610:20:6f96:96::4] ...
Jan 21 11:24:20 NightHawk daemon.info ntpclient[6117]: Time set from time.nist.gov [2610:20:6f96:96::4].
Jan 21 11:24:20 NightHawk daemon.info process_monitor[2212]: cyclic NTP Update success (servers time.nist.gov)
Jan 21 12:24:20 NightHawk daemon.debug ntpclient[6413]: Connecting to time.nist.gov [2610:20:6f97:97::4] ...
Jan 21 12:24:20 NightHawk daemon.info ntpclient[6413]: Time set from time.nist.gov [2610:20:6f97:97::4].
Jan 21 12:24:20 NightHawk daemon.info process_monitor[2212]: cyclic NTP Update success (servers time.nist.gov)
Jan 21 13:24:20 NightHawk daemon.debug ntpclient[6709]: Connecting to time.nist.gov [2610:20:6f96:96::4] ...
Jan 21 13:24:20 NightHawk daemon.info ntpclient[6709]: Time set from time.nist.gov [2610:20:6f96:96::4].
Jan 21 13:24:20 NightHawk daemon.info process_monitor[2212]: cyclic NTP Update success (servers time.nist.gov)
Jan 21 14:24:20 NightHawk daemon.debug ntpclient[7005]: Connecting to time.nist.gov [2610:20:6f96:96::4] ...
Jan 21 14:24:20 NightHawk daemon.info ntpclient[7005]: Time set from time.nist.gov [2610:20:6f96:96::4].
Jan 21 14:24:20 NightHawk daemon.info process_monitor[2212]: cyclic NTP Update success (servers time.nist.gov)
Jan 21 15:24:20 NightHawk daemon.debug ntpclient[7338]: Connecting to time.nist.gov [2610:20:6f97:97::4] ...
Jan 21 15:24:21 NightHawk daemon.info ntpclient[7338]: Time set from time.nist.gov [2610:20:6f97:97::4].
Jan 21 15:24:21 NightHawk daemon.info process_monitor[2212]: cyclic NTP Update success (servers time.nist.gov)
Jan 21 16:24:21 NightHawk daemon.debug ntpclient[7653]: Connecting to time.nist.gov [2610:20:6f96:96::4] ...
Jan 21 16:24:21 NightHawk daemon.info ntpclient[7653]: Time set from time.nist.gov [2610:20:6f96:96::4].
Jan 21 16:24:21 NightHawk daemon.info process_monitor[2212]: cyclic NTP Update success (servers time.nist.gov)
Jan 21 17:24:21 NightHawk daemon.debug ntpclient[7948]: Connecting to time.nist.gov [2610:20:6f96:96::4] ...
Jan 21 17:24:21 NightHawk daemon.info ntpclient[7948]: Time set from time.nist.gov [2610:20:6f96:96::4].
Jan 21 17:24:21 NightHawk daemon.info process_monitor[2212]: cyclic NTP Update success (servers time.nist.gov)
Jan 21 18:04:37 NightHawk daemon.info httpd[2247]: httpd : Authentication fail
Jan 21 18:04:37 NightHawk daemon.err httpd[2247]: Request Error Code 401: Authorization required. please note that the default username is "root" in all newer releases
Jan 21 18:08:14 NightHawk user.info : nas : daemon successfully stopped
Jan 21 18:08:14 NightHawk user.info : bridge : interface vlan1 successfully deleted from bridge br0
Jan 21 18:08:14 NightHawk user.info : bridge : interface eth1 successfully deleted from bridge br0
Jan 21 18:08:14 NightHawk user.info : bridge : interface eth2 successfully deleted from bridge br0
Jan 21 18:08:14 NightHawk user.info : bridge : interface eth3 successfully deleted from bridge br0
Jan 21 18:08:14 NightHawk user.info : bridge : bridge br0 successfully deleted
Jan 21 18:08:16 NightHawk user.info : nas : daemon hanging, send SIGKILL
Jan 21 18:08:16 NightHawk user.info : bridge : bridge br0 successfully added
Jan 21 18:08:16 NightHawk user.info : bridge : interface vlan1 successfully added to bridge br0
Jan 21 18:08:22 NightHawk user.info : bridge : interface eth1 successfully added to bridge br0
Jan 21 18:08:24 NightHawk user.info : bridge : interface eth2 successfully added to bridge br0
Jan 21 18:08:30 NightHawk user.info : bridge : interface eth3 successfully added to bridge br0
Jan 21 18:08:30 NightHawk user.info : nas : start nas lan
Jan 21 18:08:30 NightHawk user.info : nas : start nas for wl0
Jan 21 18:08:30 NightHawk user.info : nas : NAS lan (wl0 interface) successfully started
Jan 21 18:08:30 NightHawk user.info : nas : start nas lan
Jan 21 18:08:30 NightHawk user.info : nas : start nas for wl1
Jan 21 18:08:30 NightHawk user.info : nas : NAS lan (wl1 interface) successfully started
Jan 21 18:08:30 NightHawk user.info : nas : start nas lan
Jan 21 18:08:30 NightHawk user.info : nas : start nas for wl2
Jan 21 18:08:30 NightHawk user.info : nas : NAS lan (wl2 interface) successfully started
Jan 21 18:08:30 NightHawk user.info : dhcp6c : daemon successfully stopped
Jan 21 18:08:32 NightHawk user.info : dhcp6c : daemon hanging, send SIGKILL
Jan 21 18:24:21 NightHawk daemon.debug ntpclient[10844]: Connecting to time.nist.gov [128.138.141.172] ...
Jan 21 18:24:21 NightHawk daemon.info ntpclient[10844]: Time set from time.nist.gov [128.138.141.172].
Jan 21 18:24:21 NightHawk daemon.info process_monitor[2212]: cyclic NTP Update success (servers time.nist.gov)
Jan 21 18:33:24 NightHawk auth.info login[11044]: root login on 'pts/0'
root@NightHawk:~#
John-Galt
DD-WRT Novice


Joined: 13 Sep 2015
Posts: 45

PostPosted: Fri Jan 25, 2019 17:31    Post subject: Reply with quote
Router/Version: EA6500v2
File: DD-WRT v3.0-r38326 std (01/18/19)
Kernel: Linux 4.4.171 #4479 SMP Fri Jan 18 08:23:20 CET 2019 armv7l
Mode: Gateway
Status: Working w/issue: box kern.warn kernel: br0: received packet on vlan1 with own address as source address
Reset: Yes, restored factory defaults and manually setup via GUI
Uptime: 20 hours, no reboots or failures
Temperatures: CPU 42.5 °C / Not available

Modifications: Large heatsinks installed on main chips in the router, and an 80mm cooling fan attached to the top - keeps temperatures down and increases stability

Configuration:
Wifi Radios Disabled - I use a Ruckus 7962 for WiFi
QOS: WAN, HTB, FQ_CODEL, Upload 11,500, Download 105,000 | no other QOS settings
DNSMasq: no dnssec or dns encryption

Notes:
This build seems to be running well. Speed and bufferbloat tests are good and in line with previous builds.

The br0: received packet on vlan1 with own address as source address issue seems to be new. And I've confirmed that br0 and vlan1 have different mac addresses? Is this an issue to be concerned about?

Notable issues in log:
Code:

Jan 1 00:00:11 box kern.warn kernel: PCI: Fixing up bus 0 domain 0
Jan 1 00:00:11 box kern.warn kernel: PCI: Fixing up bus 0 domain 1
Jan 1 00:00:11 box kern.warn kernel: pci 0001:01:00.0: can't set Max Payload Size to 512; if necessary, use "pci=pcie_bus_safe" and report a bug
Jan 1 00:00:11 box kern.warn kernel: PCI: Fixing up bus 1 domain 1
Jan 1 00:00:11 box kern.warn kernel: PCI: Fixing up bus 0 domain 2
Jan 1 00:00:11 box kern.warn kernel: PCI: Fixing up bus 1 domain 2
Jan 1 00:00:11 box kern.err kernel: bcmsflash: found no supported devices
Jan 1 00:00:11 box kern.warn kernel: The first offset=200000, 2nd offset=1f00000
Jan 1 00:00:11 box kern.warn kernel: Boot partition size = 524288(0x80000)
Jan 1 00:00:11 box kern.warn kernel: lookup_nflash_rootfs_offset: offset = 0x200000 size = 0x1d00000, 0x20000
Jan 1 00:00:11 box kern.warn kernel: lookup_nflash_rootfs_offset: offset = 0x1f00000 size = 0x2100000, 0x20000
Jan 1 00:00:11 box kern.warn kernel: nf_nat_rtsp v0.7 loading
Jan 1 00:00:11 box kern.warn kernel: Spare area=64 eccbytes 56, ecc bytes located at:
Jan 1 00:00:11 box kern.warn kernel: 2 3 4 5 6 7 8 9 10 11 12 13 14 15 18 19 20 21 22 23 24 25 26 27 28 29 30 31 34 35 36 37 38 39 40 41 42 43 44 45 46 47 50 51 52 53 54 55 56 57 58 59 60 61 62 63
Jan 1 00:00:11 box kern.warn kernel: Available 7 bytes at (off,len):
Jan 1 00:00:11 box kern.warn kernel: (1,1) (16,2) (32,2) (48,2) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0) (0,0)
Jan 1 00:00:11 box kern.warn kernel: Options: NO_SUBPAGE_WRITE,
Jan 1 00:00:11 box kern.warn kernel: et: module license 'Proprietary' taints kernel.
Jan 1 00:00:11 box kern.warn kernel: Disabling lock debugging due to kernel taint
Jan 1 00:00:11 box kern.warn kernel: et_module_init: passivemode set to 0x0
Jan 1 00:00:11 box kern.warn kernel: et_module_init: txworkq set to 0x0
Jan 1 00:00:11 box kern.warn kernel: et_module_init: et_txq_thresh set to 0x400
Jan 1 00:00:11 box kern.warn kernel: et_module_init: et_rxlazy_timeout set to 0x3e8
Jan 1 00:00:11 box kern.warn kernel: et_module_init: et_rxlazy_framecnt set to 0x20
Jan 1 00:00:11 box kern.warn kernel: et_module_init: et_rxlazy_dyn_thresh set to 0
Jan 1 00:00:11 box kern.warn kernel: eth0: Broadcom BCM47XX 10/100/1000 Mbps Ethernet Controller 7.14.89.21 (r524987)
Jan 1 00:00:11 box kern.warn kernel: wl_module_init: passivemode set to 0x0
Jan 1 00:00:11 box kern.warn kernel: wl_module_init: txworkq set to 0x0
Jan 1 00:00:11 box kern.warn kernel: PCI: Enabling device 0001:01:00.0 (0140 -> 0142)
Jan 1 00:00:11 box kern.warn kernel: eth1: Broadcom BCM4331 802.11 Wireless Controller 7.14.89.21 (r524987)
Jan 1 00:00:11 box kern.warn kernel: eth2: Broadcom BCM4360 802.11 Wireless Controller 7.14.89.21 (r524987)
Jan 1 00:00:11 box kern.warn kernel: eth0: mixed HW and IP checksum settings.
Jan 25 00:04:09 box kern.warn kernel: br0: received packet on vlan1 with own address as source address
Jan 25 00:47:43 box kern.warn kernel: br0: received packet on vlan1 with own address as source address
Jan 25 00:49:53 box kern.warn kernel: br0: received packet on vlan1 with own address as source address
Jan 25 01:37:32 box kern.warn kernel: br0: received packet on vlan1 with own address as source address
Jan 25 01:56:03 box kern.warn kernel: br0: received packet on vlan1 with own address as source address
Jan 25 02:28:01 box kern.warn kernel: br0: received packet on vlan1 with own address as source address
Jan 25 02:30:47 box kern.warn kernel: br0: received packet on vlan1 with own address as source address
Jan 25 03:05:39 box kern.warn kernel: br0: received packet on vlan1 with own address as source address
Jan 25 04:04:32 box kern.warn kernel: br0: received packet on vlan1 with own address as source address
Jan 25 04:04:35 box kern.warn kernel: br0: received packet on vlan1 with own address as source address
Jan 25 04:04:42 box kern.warn kernel: br0: received packet on vlan1 with own address as source address
Jan 25 04:04:47 box kern.warn kernel: br0: received packet on vlan1 with own address as source address
Jan 25 04:06:52 box kern.warn kernel: br0: received packet on vlan1 with own address as source address
Jan 25 04:07:33 box kern.warn kernel: br0: received packet on vlan1 with own address as source address
Jan 25 05:14:42 box kern.warn kernel: br0: received packet on vlan1 with own address as source address
Jan 25 05:15:13 box kern.warn kernel: br0: received packet on vlan1 with own address as source address
Jan 25 05:16:58 box kern.warn kernel: br0: received packet on vlan1 with own address as source address
Jan 25 05:20:26 box kern.warn kernel: br0: received packet on vlan1 with own address as source address
Jan 25 05:56:52 box kern.warn kernel: br0: received packet on vlan1 with own address as source address
Jan 25 06:05:20 box kern.warn kernel: br0: received packet on vlan1 with own address as source address
Jan 25 06:05:30 box kern.warn kernel: br0: received packet on vlan1 with own address as source address
Jan 25 06:12:20 box kern.warn kernel: br0: received packet on vlan1 with own address as source address
Jan 25 06:12:23 box kern.warn kernel: br0: received packet on vlan1 with own address as source address
Jan 25 15:27:41 box kern.warn kernel: br0: received packet on vlan1 with own address as source address


Regarding the "br0: received packet on vlan1 with own address as source address" error, I ran 'ifconfig | grep HWaddr' and got the following. vlan1 and br0 have different addresses:

br0 Link encap:Ethernet HWaddr 48:F8:B3:85:3B:78
eth0 Link encap:Ethernet HWaddr 48:F8:B3:85:3B:76
eth1 Link encap:Ethernet HWaddr 48:F8:B3:85:3B:78
eth2 Link encap:Ethernet HWaddr 48:F8:B3:85:3B:7A
imq0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
imq1 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
vlan1 Link encap:Ethernet HWaddr 48:F8:B3:85:3B:79
vlan2 Link encap:Ethernet HWaddr 48:F8:B3:85:3B:77
Display posts from previous:    Page 1 of 1
Post new topic   Reply to topic    DD-WRT Forum Index -> Broadcom SoC 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 can attach files in this forum
You can download files in this forum