Let me start with praising you for supplying such a nice stream of ready-to-use builds for the venerable wndr3[7|8]000v[1|2] that makes keeping up to date with lede development a breeze that requires no actual firmware building from my side
I have a question regarding the IPv6/WAN6 default configuration in your builts (as I have been plagued by erratic IPv6 and DNS issues since winter); at least on my wndr3700v2 the interface name for the WAN6 interface defaults to eth1 (after a "sysupgrade -n", so I believe this to show the defaults of your builts/lede):
"config interface 'wan6'
option ifname 'eth1'
This seems to be sensible in that eth1 really is the ethernet interface that directs towards the internet.
But it does not work for setting up IPv6 on my "deutsche telekom vdsl50 link", resulting in a weird router state over-all where DNS (IPv6 and IPv4) is severely wonky (e.g. "nslookup www.heise.de" on the router will not work like 19 out of 20 attempts).
According to a Hans Dedecker (https://bugs.lede-project.org/index.php?do=details&task_id=668) the issue is that for links where IPv6 is negotiated over an IPv4 PPPoE link (like mine) the wan6 ifname should be "@wan" (or alternatively the wan6 interface should be nuked completely). And lo and behold with:
config interface 'wan6'
option proto 'dhcpv6'
option _orig_ifname 'eth1'
option _orig_bridge 'false'
option ifname '@wan'
option reqaddress 'try'
option reqprefix 'auto'
I get both working IPv6 and IPv4 DNS working again. So I wonder does @wan also work for users that do get IPv6 directly via DHCP, and if yes, would you consider switching the default? I have not looked into the defaults lede's stable version or snapshots, so for all I know this might be an issue with "upstream lede" as well.