Notes: 1. SFE accelerated NAT is in 33006+ builds but only in kernel 3.10 and newer 2. 'KRACK' vulnerability fixes were completed in r33678 for Broadcom, 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.
5. Since 39469, udhcpd was removed and replaced with the already present dnsmasq, and PIE qdisc was added for some builds.
Issues, observations, and/or workarounds reported: 1. (egc) Policy-Based Routing broken if SFE enabled: 5900 quarkysg's PBR+SFE fix: 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:6246 4.WDS does not work on ARM devices (only MIPS<->MIPS) 5.K2.6 builds are broken since 38253(?); GUI issues:6538 6.VAPs not working at boot; workaround startup command:
sleep 10;stopservice nas;stopservice wlconf;startservice wlconf;startservice nas
This appears to be fixed for some routers (different kernels, modes, and radios) in build 39508.
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.):
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. _________________ #NAT/SFE/CTF: limited speed w/ DD#Repeater issues#DD-WRT info: FAQ, Builds, Types, Modes, Changes, Demo#
OPNsense x64 5050e ITX|DD: DIR-810L, 2*EA6900@1GHz, R6300v1, RT-N66U@663, WNDR4000@533, E1500@353,
WRT54G{Lv1.1,Sv6}@250|FreshTomato: F7D8302@532|OpenWRT: F9K1119v1, RT-ACRH13, R6220, WNDR3700v4
Last edited by jwh7 on Wed Apr 17, 2019 15:13; edited 3 times in total
Joined: 08 May 2018 Posts: 14126 Location: Texas, USA
Posted: Tue Apr 16, 2019 19:12 Post subject:
This build doesn't have the default dnsmasq cache size set in this commit. Not worth bothering with for me. If folks choose to flash this build, you will need the cache size set in the additional configs for dnsmasq.
This build doesn't have the default dnsmasq cache size set in this commit.
dnsmasq would just be using it's own default of 150 in this case, right? Otherwise a custom config can be used, or is that not working atm? _________________ #NAT/SFE/CTF: limited speed w/ DD#Repeater issues#DD-WRT info: FAQ, Builds, Types, Modes, Changes, Demo#
OPNsense x64 5050e ITX|DD: DIR-810L, 2*EA6900@1GHz, R6300v1, RT-N66U@663, WNDR4000@533, E1500@353,
WRT54G{Lv1.1,Sv6}@250|FreshTomato: F7D8302@532|OpenWRT: F9K1119v1, RT-ACRH13, R6220, WNDR3700v4
I would have to look at the source code for dnsmasq itself to see if there is a hard-coded default cache size, but I don't think there is. And this may cause issues like dnsmasq crashing or router locking up. BUT, to answer your question, additional / custom configs are working last I knew.
@kernel-panic69 i can confirm that dnsmasq is hard-coded to have 150 cache by default and in my opinion the less options implemented by the devs on dnsmasq the better.This way everyone has more choice/freedom to set it up the way they like. _________________ Router: ASUS AC1900(RT-AC68U)
Joined: 08 May 2018 Posts: 14126 Location: Texas, USA
Posted: Tue Apr 16, 2019 20:40 Post subject:
dTX wrote:
@kernel-panic69 i can confirm that dnsmasq is hard-coded to have 150 cache by default and in my opinion the less options implemented by the devs on dnsmasq the better.This way everyone has more choice/freedom to set it up the way they like.
@dTX - Thanks for that. I went ahead and added the cache-size additional config, saved, and flashed this build for giggles. Will report in separate post later after it's been up a while.
dnsmasq would just be using it's own default of 150 in this case, right? Otherwise a custom config can be used, or is that not working atm?
It's not 150, but 1500 in changeset 39539!
I meant dnsmasq's own default, not DD's dnsmasq default (as confirmed by dTX). Since we're discussing it, I also read that dnsmasq has a hard max cache size limit of 10000.
Router/Version: Netgear WNDR4500v2
File: .bin
Kernel: Linux WNDR4500v2 3.10.108-d8 #23894 Tue Apr 16 15:38:11 CEST 2019 mips DD-WRT
Mode: 2.4 GHz Client -> 5 GHz AP + VAP
Status: CLI update from r39486M test build. Wow, my VAP works again, without the workaround! I was hopeful after seeing BS messing w/ service inits, but not at all confident until jrscs's 39508 (though the before/after listed build was 39494) report. Anyone else test it? _________________ #NAT/SFE/CTF: limited speed w/ DD#Repeater issues#DD-WRT info: FAQ, Builds, Types, Modes, Changes, Demo#
OPNsense x64 5050e ITX|DD: DIR-810L, 2*EA6900@1GHz, R6300v1, RT-N66U@663, WNDR4000@533, E1500@353,
WRT54G{Lv1.1,Sv6}@250|FreshTomato: F7D8302@532|OpenWRT: F9K1119v1, RT-ACRH13, R6220, WNDR3700v4
Last edited by jwh7 on Tue Apr 16, 2019 22:03; edited 3 times in total
@jwh7 that is correct,but in case where the cache is not set by the devs(which is the DD's dnsmasq default) it will fall back to it's hard-coded default anyway.
About the max cache limit,on <Kong> builds last i checked that limit was removed,i even remember i set it once to 20000 just for the kicks and it gave me some warning but it worked so just FYI,in case you need to adjust it on your end. _________________ Router: ASUS AC1900(RT-AC68U)
Joined: 04 Jan 2007 Posts: 11563 Location: Wherever the wind blows- North America
Posted: Tue Apr 16, 2019 23:19 Post subject:
Router/Version: Netgear R6300v2
Firmware: DD-WRT v3.0-r39538 std (04/16/19)
Kernel: Linux 4.4.178 #85 SMP Tue Apr 16 08:51:46 CEST 2019 armv7l
Previous: r39508
Mode/Status: Repeater+VAP (2.4GHz) / AP (5GHz)
Reset: YES
Issues/Errors: VAP working with workaround. It still does NOT work without it.
Requires the workaround:
sleep 10
stopservice nas
wlconf eth1 down
wlconf eth2 down
wlconf eth1 up
wlconf eth2 up
startservice nas
redhawk _________________ The only stupid question....is the unasked one.
Last edited by redhawk0 on Wed Apr 17, 2019 13:57; edited 1 time in total
Router/Version: Cisco Linksys E4200 v1
File: dd-wrt.v24-39538_NEWD-2_K3.x_mega-e4200.bin
Firmware: DD-WRT v3.0-r39538 mega (04/16/19)
Kernel: Linux 3.10.108-d8 #23910 Tue Apr 16 15:55:14 CEST 2019 mips
Previous: DD-WRT v3.0-r39469M mega (04/10/19)
Reset: No
Mode: Gateway/AP (5GHz band only, 2.4 radio disabled)
Uptime: ~3 hrs
Status: OK
Issues/Errors:
1) Took a little bit for things to settle out and stabilize (nothing new), but so far, so good. No new crazy errors or issues. Will report back if anything comes up.
Summary of issues:
VAP not working without startup command.
5GHz radio VAPs aren't available as interfaces (cannot be bridged).
FYI: VAP is not working without the below startup script for virtual AP to work.
stopservice nas
wlconf eth1 down
wlconf eth2 down
wlconf eth1 up
wlconf eth2 up
startservice nas
Quote from BS: "The 'VAPs not working at boot' issue requiring a workaround startup command was fixed in build 39508." - Appears to still be an issue. At least for the Netgear R7000P.
Also, noticed VAP's on 5GHz band doesn't show as an interface, preventing them from being assigned to a bridge under the networking tab in setup. For example, you can see wl0.1 for 2.4GHz but wl1.1 doesn't exist for the 5GHz VAP.
Currently running VLAN trunk with 3 AP's on 2.4GHz that are bridged on their own individual VLANs.
Joined: 26 Mar 2013 Posts: 1855 Location: Hung Hom, Hong Kong
Posted: Wed Apr 17, 2019 14:51 Post subject: All variables MUST have default values!
kernel-panic69 wrote:
I would have to look at the source code for dnsmasq itself to see if there is a hard-coded default cache size, but I don't think there is. And this may cause issues like dnsmasq crashing or router locking up. BUT, to answer your question, additional / custom configs are working last I knew.
All variables MUST have default values! Otherwise, they will be undefined and ___ knows what would happen when the program is executed!!!!
You don't need to be a programmer to understand this.
_________________ Router: Asus RT-N18U (rev. A1)
Drink, Blink, Stretch! Live long and prosper! May the Force and farces be with you!