sjaak

well, my network skills are from duckduckgo/Google IPv6 is still new to me too.. if it wasn't that annoying Geolocation(and block), i would still using ipv6, but later this you i'm switching to an another isp with ipv6 support...

what are those backnet and backnetipv6 networks? settings > network settings settings > docker (Advanced View enabled) note; i dont have IPv6 anymore, maybe it better to continue in you own topic '

no, you have to enable 'network bridging' in the network setting of unraid itself. then after doing that, under the dockercontainer setting 'network type' Custom : br0 i didn't got Letsencrypt fully working with ipv6...

Br0 is a 'custom' network. (br0 is in the same network as unraid) it will be there is you enable 'network bridging' in the network settings. but, currently i have disabled IPv6 on the network, i had to much trouble with Geo location..

i have the exact same setting and its working fine, think its better to follow johhnie.black answer...

your screenshot says: http://localhost:8086 this need to be: http://YOURSERVERIPADDRESS:8086

its downloaded to the download folder, its not 'imported' to the right folder, Sonarr will import it, or it will hang on downloaded, especially with those <weird names>.avi you can check this inside Sonarr under 'activity' > 'queue', i think it is still here, if so, Plex cant find it because its still in the download folder, here you can do a manual import.

thats setup as it should be, for what i know is that Sonarr cant find the folder TV Shows because there is no. create a folder 'TV Shows inside /media. (/mnt/user/TV Shows/TV shows) i don't use Krusader so can't help with that..

it should be... what is the "command code" when you click apply? just see the edit: Sonarr cant find the folder /media/TV Shows because there is no 'TV Shows' folder inside /media (/mnt/user/tv shows)

inside sonarr you need to go to /media, not /mnt. /mnt/user/downloads is inside the container: /data /mnt/user/TV Shows is inside the container: /media /mnt inside the container is just a folder inside the container, no need to go there.

will do soon, if i got some free time

i cant found them complete (coffee isn't kicked in yet...) but levelonetech is my information source: https://forum.level1techs.com/t/vega-10-and-12-reset-application/145666 https://forum.level1techs.com/t/navi-reset-kernel-patch/147547 maybe you can ask @Leoyzen for the patches? he is also creating a custom kernel and include those patches. i prefer to chose to install one or bold...

Nice to see this! it would also be awesome if it got a option to include the Vega Reset Bug Patch (and/or Navi Reset Bug Patch)...

i switched the RA setting back to assistant, now unraid got a /128 address but at least it can be set static. i found out that now i do see the ipv6 subnet in the docker container setup on br0, so the extra parameters are not needed anymore. i still think i am gonna wait for the next unraid version (as bonienl already mentioned, he found a way to keep docker happy with a /128 address) and for now a just change the containers, what need ipv6 connection to br0. (i hope that letsencrypt, nextcloud, ombi and plex will accept this, especially the connection wit LE...) interesting, keep this in my mind.

well in that cage, i have to wait for the new unraid version so i can switch back to dhcpv6 and use static ip settings and let unraid handle it /128 address (or i find the right config on the router 😅 ) my other vlan is using dhcpv6+slaac and every device has there ip static, even with a reboot. unraid isn on that vlan and with every reboot it got an other ip

small update, Docker containers with the network set on "bridge" and "Host" doesn't work with ipv6, only set on br0. works with ipv6. i am not sure if docker accepts SLAAC... unraid itself is still using an /64 address and it's holding it, where my vm change daily from ip address...

after reading the tutorial from PFsense (and i use OPNsense) i though: lets change the Router Advertisements from 'Assisted' to 'unmanaged', after reboot i got an /64 address! # ip -6 a 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 state UNKNOWN qlen 1000 inet6 ::1/128 scope host valid_lft forever preferred_lft forever 8: eth0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 state UP qlen 1000 inet6 fe80::XXXX:XXXX:XXXX:7fb3/64 scope link valid_lft forever preferred_lft forever 11: br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 state UP qlen 1000 inet6 2001:XXX:XXXX:XXX:XXXX:XXXX:XXXX:9065/64 scope global dynamic mngtmpaddr noprefixroute valid_lft 86020sec preferred_lft 14020sec inet6 fe80::XXXX:XXXX:XXXX:7fb3/64 scope link valid_lft forever preferred_lft forever i guess that the Router Advertisements wasn't setup correctly. (or at least, i or the Manuel tell something wrong) now i cant see the leases in the dhcpv6 anymore, after some reading i find out that RA unmanaged means only SLAAC. the only thing what is not working is IPv6 in the management GUI boot, no IPv6 at ipv6-test.com (i know, it isn't mean to browser the www) i tried to do some port scans, the ports what are configured in the firewall are working correctly. Nice!

did removed and changed the lines; after reboot i lost all network activities, changed ip to ipv4 only, reboot, back in business! ipv6 enabled. still no proper ipv6... (set dns static) i have no idea why the /128 is here. i just followed the instructions: https://docs.opnsense.org/manual/how-tos/ipv6_tunnelbroker.html al my devices have a /128 address (those are visible in the dhcpv6 leases). but all my other devices are working fully on ipv6, tested it by disable ipv4 on it.. "ip -6 a" shows me this (this is on the VM): 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 state UNKNOWN qlen 1000 inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: enp1s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 state UP qlen 1000 inet6 2001:XXX:XXXX:XXX:XXXX:77d2:2124:62e7/128 scope global dynamic noprefixroute valid_lft 7196sec preferred_lft 4496sec inet6 2001:XXX:XXXX:XXX:XXXX:5886:cc08:3b44/64 scope global temporary dynamic valid_lft 86396sec preferred_lft 14396sec inet6 2001:XXX:XXXX:XXX:XXXX:fee8:3879:4ebf/64 scope global dynamic mngtmpaddr noprefixroute valid_lft 86396sec preferred_lft 14396sec inet6 fe80::XXXX:XXXX:b550:ed55/64 scope link noprefixroute valid_lft forever preferred_lft forever "noprefixroute"...

sure, ignore those notifications from upsd[7111], a network switch is on it last miles... ps. i still don't understand why unraid is the only one why its not getting the ipv6 dns on it own, every device here got it automatic, its set in the dhcp6 server.

sure:

after reading this topic: https://forums.unraid.net/topic/78382-docker-ipv6-fixed-ip-address/ i don't have any ipv6 subnet visible, only the ipv4 subnet is showed... firefox container is not listening on ipv6? 04/05/2020 19:08:08 listen6: bind: Address in use 04/05/2020 19:08:08 Not listening on IPv6 interface. (i can browser the WWW thought ipv6...)

thanks, currently i'm still on 6.8.2, but will upgrade its available. and the "net.ipv6.conf.all.disable_ipv6=0", i need this one, is this a bug too? or did i something wrong?

tried to enable ipv6 privacy extensions, every time i click apply, it resets to disabled. tried this with automatic setting and static. on auto the ipv6 dns server fails, its set in the DHCP6 server, only unraid is not getting the ipv6 dns server, so its now set to static. i have no idea why the privacy extensions cant be enabled... (noting about is mentioned in the logbook.) also, i removed the parameter: "--sysctl net.ipv6.conf.all.disable_ipv6=0" from the firefox container, it lose the ipv6 connection, putting it back, ipv6 is back... i have no idea what going on here 🙄

tested the "Proxynet" (make this one with the video from spaceinvaderone), not working. using the default "bridge", not working setting the docker container to "host", works! i'm going to enable the privacy extension and remove those extra parameters and test if it works.

the problem is not the letsencrypt container. i changed the network from "proxynet" to br0, at first i didn't get a ipv6 address, after putting the extra parameters "--sysctl net.ipv6.conf.all.disable_ipv6=0 --sysctl net.ipv6.conf.eth0.use_tempaddr=2" letsencrypt got a ipv6 address (but its is not visible in the DHCP6 server leases. tested inside the console of the container: ping6 google.com works, i can use its ipv6 address to gain access to its interface. so, br0 works fine, but every 'custom network' inside docker isn't working with ipv6...