New Build 40065: BS 06-20-2019-r40065

Post new topic   Reply to topic    DD-WRT Forum Forum Index -> Broadcom SoC based Hardware
Goto page Previous  1, 2
Author Message
mwchang
DD-WRT Guru


Joined: 26 Mar 2013
Posts: 573
Location: Hung Hom, Hong Kong

PostPosted: Tue Jun 25, 2019 13:38    Post subject: DD-WRT BS build 40065 and Asus RT-N18U Reply with quote
Router/Version: Asus RT-N18U(rev. A1)
Firmware: DD-WRT v3.0-r40065 std (06/20/19)
Kernel: Linux 4.4.182 #288 PREEMPT Thu Jun 20 11:56:05 CEST 2019 armv7l
Previous: DD-WRT v3.0-r39944 std (06/04/19)
Mode: WAN @ DHCP, Wireless @ AP
Status: Working (not 24/7 & not using IPv6, VAP, VPN, NAS nor USB)
Reset: NO reset during firmware upgrade but cold boot

Firmware Size

From 30515200 (b.31277) to 24711168 (b.33555) = -5804032 bytes
From 24711168 (b.33555) to 27054080 (b.34929) = 2342912 bytes
From 27054080 (b.34929) to 26640384 (b.35531) = -413696 bytes
From 26640384 (b.35531) to 25022464 (b.36995) = -1617920 bytes
From 25022464 (b.36995) to 25427968 (b.37961) = 405504 bytes
From 25427968 (b.37961) to 25804800 (b.38570) = 376832 bytes
From 25804800 (b.38570) to 27574272 (b.38840) = 1769472 bytes
From 27574272 (b.38840) to 27774976 (b.39031) = 200704 bytes
From 27774976 (b.39031) to 27779072 (b.39137) = 4096 bytes
From 27779072 (b.39137) to 27779072 (b.39144) = 0 byte
From 27779072 (b.39144) to 28672000 (b.39267) = 892928 bytes
From 28672000 (b.39267) to 27926528 (b.39296) = -745472 bytes
From 27926528 (b.39296) to 27918336 (b.39494) = -8192 bytes
From 27918336 (b.39494) to 27918336 (b.39508) = 0 byte
From 27918336 (b.39508) to 28147712 (b.39572) = 229376 bytes
From 28147712 (b.39572) to 28151808 (b.39654) = 4096 bytes
From 28151808 (b.39654) to 28151808 (b.39715) = 0 byte
From 28151808 (b.39715) to 27938816 (b.39800) = -212992 bytes
From 27938816 (b.39800) to 27938816 (b.39884) = 0 byte
From 27938816 (b.39884) to 27942912 (b.39944) = 4096 bytes
From 27942912 (b.39944) to 28024832 (b.40065) = 81920 bytes

_________________
Router: Asus RT-N18U (rev. A1)

May the Force and farces be with you! Live long and proper!

Facebook: https://www.facebook.com/changmanwai
Website: https://sites.google.com/site/changmw
SETI@Home profile: http://setiathome.berkeley.edu/view_profile.php?userid=211832
Sponsor
ninjadawg
DD-WRT Novice


Joined: 18 Feb 2019
Posts: 21

PostPosted: Tue Jun 25, 2019 23:22    Post subject: Reply with quote
ninjadawg wrote:
If modem is rebooted (or occasionally loses connection?), no clients can access internet. Pressing apply settings in router lets all devices access internet again.


I think I've figured this out. The modem (4g) gets a new IP address on reboot. I guess I just need to test ping every so often and release/renew WAN DHCP.
kernel-panic69
DD-WRT Guru


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

PostPosted: Wed Jun 26, 2019 4:25    Post subject: Reply with quote
Looking at commits since this build, I noticed in revision 40130 that all traces to udhcpd haven't been removed. I didn't go back to look at makefiles and .configs, but why the hell is it even being referenced in any code anymore if it's no longer included? I guess I have no GLUE. Rolling Eyes
kernel-panic69
DD-WRT Guru


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

PostPosted: Mon Jul 01, 2019 9:51    Post subject: Reply with quote
Having had to recover from a brick after attempting to flash 40167, coming back to this build and leaving the GTK renewal at the default interval (3600) and only changing a couple of wireless advanced settings (beacon interval) to something other that default and other than my previous settings, but OTHERWISE using my previous settings seems to have resulted in no issues with GTK renewal or wireless stability. Not sure what commits may have affected this, but this is making me wonder how far to backtrack to see when it was exactly fixed.

EDIT: GTK renewal / radio timer syslog messages still an issue, but it doesn't cripple wireless connectivity like it used to.
lazardo
DD-WRT User


Joined: 17 Apr 2014
Posts: 91
Location: SF Bay Area

PostPosted: Sun Jul 14, 2019 23:30    Post subject: Reply with quote
Router/Version: n66u/b1
File: dd-wrt.v24-40065_NEWD-2_K3.x_mega_RT-N66U.trx
Kernel: 3.10.108-d8 #24993
Mode: AP, 2.4+5+GbE clients
Status: Up for several days.

experimental:
* SFE off (stability over performance)
* wireless->security->rekey values offset by 10
* wireless->advanced 101/103 beacon intervals, DTIM 2
* changed DROP to REJECT which seems to reduce hostile firewall hits by 66%
Code:
cat /tmp/.ipt |
sed 's/"DROP/"REJECT/; s/j DROP/j REJECT --reject-with icmp-port-unreachable/' > IPT &&
iptables-restore IPT || startservice firewall
kernel-panic69
DD-WRT Guru


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

PostPosted: Mon Jul 15, 2019 0:31    Post subject: Reply with quote
lazardo wrote:
Router/Version: n66u/b1
File: dd-wrt.v24-40065_NEWD-2_K3.x_mega_RT-N66U.trx
Kernel: 3.10.108-d8 #24993
Mode: AP, 2.4+5+GbE clients
Status: Up for several days.

experimental:
* SFE off (stability over performance)
* wireless->security->rekey values offset by 10
* wireless->advanced 101/103 beacon intervals, DTIM 2
* changed DROP to REJECT which seems to reduce hostile firewall hits by 66%
Code:
cat /tmp/.ipt |
sed 's/"DROP/"REJECT/; s/j DROP/j REJECT --reject-with icmp-port-unreachable/' > IPT &&
iptables-restore IPT || startservice firewall


I am curious to see how the GTK re-key offset works out. I presume you are running in ROUTER mode, not GATEWAY...?
lazardo
DD-WRT User


Joined: 17 Apr 2014
Posts: 91
Location: SF Bay Area

PostPosted: Mon Jul 15, 2019 17:35    Post subject: Reply with quote
Router mode, 2.4 at 3610 w 101 beacon, 5 at 3620 w 103 beacon, no keep alive reboot, no SFE.

Down to less than 1 nas/timer event per 24 hours.
kernel-panic69
DD-WRT Guru


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

PostPosted: Mon Jul 15, 2019 22:35    Post subject: Reply with quote
lazardo wrote:
Router mode, 2.4 at 3610 w 101 beacon, 5 at 3620 w 103 beacon, no keep alive reboot, no SFE.

Down to less than 1 nas/timer event per 24 hours.


Thanks for the update. I'm at 59 and 79 on beacon intervals, but I can test the GTK intervals just the same.
Goto page Previous  1, 2 Display posts from previous:    Page 2 of 2
Post new topic   Reply to topic    DD-WRT Forum 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