V2 will continue to be optional. I have not looked but surely someone is already working to push version 2 to trunk?
I suspect this hasn't been done yet because of the implications of causing issues across all the different platforms. Heck I wouldn't want to stick my head into that oven either 
I still hope that there will be a lucy-app for v2 and it will be integrated in your future builds...
Btw, i saw that there is a new driver available: 10.3.8.0-20180906
Thanks for the heads up...
hi,
Anyone else having problems with DDNS in the last build? (no-ip.com)
it worked fine at the first config and then the installation is not updating ip anymore, next to no-ip.
@Kherby @davidc502 I've been running 10.3.8.0-20180906 for nearly 24hrs now. No issues to report.
I also swapped out dnscrypt proxy v2 for https_dns_proxy to see what it's like. Seems much simpler to use and is much smaller. Not sure if it's more/less secure.
See above in this thread. You need to change which network interface the daemon is checking for the wan ip.
I am spammed with these kernel messages
[ 3882.262720] IPv6: ADDRCONF(NETDEV_UP): tmp.radio0: link is not ready
[ 3882.633185] IPv6: ADDRCONF(NETDEV_UP): tmp.radio0: link is not ready
[ 3882.779780] IPv6: ADDRCONF(NETDEV_UP): tmp.radio0: link is not ready
[ 3882.893576] IPv6: ADDRCONF(NETDEV_UP): tmp.radio1: link is not ready
[ 3883.235789] IPv6: ADDRCONF(NETDEV_UP): tmp.radio1: link is not ready
[ 3883.380959] IPv6: ADDRCONF(NETDEV_UP): tmp.radio1: link is not ready
[ 3883.388822] IPv6: ADDRCONF(NETDEV_UP): tmp.radio0: link is not ready
[ 3883.708592] IPv6: ADDRCONF(NETDEV_UP): tmp.radio1: link is not ready
I have both wlan deactivated but also ipv6. Whats causing it, how do I get rid of the spam? Why is this happening with
net.ipv6.conf.all.disable_ipv6=1 ?
On latest Davidc502 build R7938 I get the following new errors in the System log:
Model: WRT3200ACM
Lede SNAPSHOT r7938-5dd745588e / LuCI Master (git-18.232.74480-b93d3f3)
Sat Sep 8 10:02:22 2018 user.info wsdd2[10308]: starting.
Sat Sep 8 10:02:22 2018 user.err wsdd2[10308]: Can't open '/etc/machine-id', trying '/proc/sys/kernel/random/boot_id'
Sat Sep 8 10:02:22 2018 user.err wsdd2[10308]: cannot read workgroup from testparm
Sat Sep 8 10:02:22 2018 user.err wsdd2[10308]: cannot read netbios name from testparm
Is this a problem or can I just ignore it?
@FCS001FCS I assume you have samba4 disabled or not installed?
If you don't have a samba4 share just disable wsdd2 via startup, its only purpose is to announce samba shares to windows clients.
Samba 4 dependency issues?
Collected errors:
* satisfy_dependencies_for: Cannot satisfy the following dependencies for luci-app-samba4:
* libcap * jansson * libnettle * libarchive * libgcrypt * libpam * dbus * libavahi-client *
* opkg_install_cmd: Cannot install package luci-app-samba4.
package/Makefile:65: recipe for target 'package/install' failed
make[2]: *** [package/install] Error 255EDIT
I'm thinking these are required to be a part of the build, so I'm trying to take these packages out of module and include them as part of the build to see if that fixes the issue.
Correct, Samba 4 is not installed.
Thanks for the fix.
I am trying out your build, but cannot find Transmission Daemon, am I missing something or isn't it available? This is on a WRT1200AC V1
There is no Transmission in the build. As soon as the next build comes out, upgrade, and then grab transmission off of the daily builds.
Adding the dependencies into the build fixed the problem. We will have Samba4 included in the build this time.
Thanks, do you have a link to the daily builds? Is that the default Lede stuff or do you have those on your server?
The packages are here -> https://downloads.openwrt.org/snapshots/packages/arm_cortex-a9_vfpv3/
If you are on build r7938 this method will not work because the daily snapshot already changed to a different kernel. Just wait until the next release which should be today or tomorrow, and then you can grab transmission from the daily builds.
If you want to try a daily build they are found here > https://downloads.openwrt.org/snapshots/targets/mvebu/cortexa9/
Warning: People using DNSCrypt-proxy Version 2
Samba4 creates a conflict with dnscrypt-proxy version 2. Samba4 requires avahi-deamon which uses port 5353 which conflicts with dnscrypt-proxy version 2 as it is using the same port.
The work around is to configure dnscrypt-proxy version 2 to use a different port. I will be changing the dncrypt-proxy2 script to configure another port so not to interfere with avahi-deamon.
I guess the same goes for v1?
If v1 is using port 5353, then yes.
root@lede:/etc/avahi# netstat -tulpn |grep :5353
Yes, standard port is 5353. I'm using 5353 and 5454 for the second instance.