Jump to content

Dataone

Members
  • Content Count

    62
  • Joined

  • Last visited

Community Reputation

1 Neutral

About Dataone

  • Rank
    Advanced Member

Recent Profile Visitors

186 profile views
  1. At least by default I assume so, yes. My containers using bridged all go through the vpn and all containers using br0 use my home network. I'm sure you can set some iptable/routing rules to modify this if you liked though
  2. WireGuard support hasn't been merged into the 5.x kernel yet anyway, so that means limetech would be building it into the kernel themselves. So I assume they will keep doing the same with the latest 4.x kernels. If you check the release notes for rc8 you'll see it does mention a wireguard update too, so I assume it's still there and will be in the upcoming stable version
  3. I know that this is the trick for Plex, but you may be able to do the same with the jellyfin ports. PostUp = iptables -t nat -I PREROUTING -p tcp --dport *external port* -j REDIRECT --to-ports 32400 (internal plex port) PreDown = iptables -t nat -D PREROUTING -p tcp --dport *external port* -j REDIRECT --to-ports 32400 (internal plex port)
  4. Bug report submitted here: https://forums.unraid.net/bug-reports/stable-releases/672-ipv6-internet-access-despite-ipv4-only-r754/
  5. This bug report is based on the following thread: While the version of Unraid I am using there is 6.8.0-rc7, I have also tested with 6.7.2 as well as both in safe mode, the results always being the same. My Unraid server appears to have IPv6 internet access despite it being disabled from within the settings. Summary: When choosing "IPv4 only" in "Network Settings", IPv6 network addresses are assigned to network interfaces Those network interfaces can access the local network via IPv6 They can be pinged via IPv6 Those interfaces can access the internet via IPv6 I believe the intended behaviour when choosing "IPv4 only" in Network Settings is that IPv6 is disabled IPv6 network functionality is only disabled after the follwing commands: sysctl net.ipv6.conf.all.disable_ipv6=1 sysctl net.ipv6.conf.default.disable_ipv6=1 sysctl -p Fresh diagnostics attached, Thanks. tower-diagnostics-20191202-0736.zip
  6. Thanks for the info, do you know if the routes showing with "IPv4 only" is a bug/unintended behaviour? It still doesn't seem like IPv6 should be doing anything with that network setting presumably disabled. Cheers
  7. Assuming Firefox, does it look like this? If so, you need to disable "privacy.resistFingerprinting" in your about:config, or just use ssh or something similar instead
  8. Hi, My modem does support IPv6, and Unraid appears to be using it to access certain domains. (Notably google) I suppose my issue here is that I believe Unraid should not be assigning IPv6 adresses to interfaces nor even have the routes available when set to "IPv4 only". However, ideally yes, I should be setting up my network to be compatible with IPv6 but for the moment I'd prefer if everything was disabled rather than left in a default state until I decide to manually configure it. (I believe it's using DHCPv6?) Cheers
  9. As long as your docker containers are using the bridged network option, they will be routed through the vpn. You can verify this by going into a docker container's shell and typing the below text. (Assuming that the docker has curl) curl https://ipinfo.io/ip
  10. "IPv4 + IPv6": root@tower:~# ip route show table all default dev wg0 table 51820 scope link default via 192.168.1.1 dev br0 192.168.1.0/24 dev br0 proto kernel scope link src 192.168.1.101 local 10.64.16.210 dev wg0 table local proto kernel scope host src 10.64.16.210 broadcast 127.0.0.0 dev lo table local proto kernel scope link src 127.0.0.1 local 127.0.0.0/8 dev lo table local proto kernel scope host src 127.0.0.1 local 127.0.0.1 dev lo table local proto kernel scope host src 127.0.0.1 broadcast 127.255.255.255 dev lo table local proto kernel scope link src 127.0.0.1 broadcast 192.168.1.0 dev br0 table local proto kernel scope link src 192.168.1.101 local 192.168.1.101 dev br0 table local proto kernel scope host src 192.168.1.101 broadcast 192.168.1.255 dev br0 table local proto kernel scope link src 192.168.1.101 local ::1 dev lo proto kernel metric 0 pref medium ::1 dev lo proto kernel metric 256 pref medium local 2404:4408:2375:d500:bdb9:e06b:cd34:24bd dev br0 proto kernel metric 0 pref medium 2404:4408:2375:d500::/64 dev br0 proto ra metric 225 pref medium local fe80::4216:7eff:fe63:b6ba dev eth0 proto kernel metric 0 pref medium local fe80::f083:abff:fe7d:721a dev br0 proto kernel metric 0 pref medium fe80::/64 dev br0 proto kernel metric 256 pref medium fe80::/64 dev eth0 proto kernel metric 256 pref medium ff00::/8 dev wg0 metric 256 pref medium ff00::/8 dev br0 metric 256 pref medium ff00::/8 dev eth0 metric 256 pref medium default via fe80::1af1:45ff:fea4:9ff0 dev br0 proto ra metric 225 pref medium "IPv4 only": root@tower:~# ip route show table all default dev wg0 table 51820 scope link default via 192.168.1.1 dev br0 192.168.1.0/24 dev br0 proto kernel scope link src 192.168.1.101 local 10.64.16.210 dev wg0 table local proto kernel scope host src 10.64.16.210 broadcast 127.0.0.0 dev lo table local proto kernel scope link src 127.0.0.1 local 127.0.0.0/8 dev lo table local proto kernel scope host src 127.0.0.1 local 127.0.0.1 dev lo table local proto kernel scope host src 127.0.0.1 broadcast 127.255.255.255 dev lo table local proto kernel scope link src 127.0.0.1 broadcast 192.168.1.0 dev br0 table local proto kernel scope link src 192.168.1.101 local 192.168.1.101 dev br0 table local proto kernel scope host src 192.168.1.101 broadcast 192.168.1.255 dev br0 table local proto kernel scope link src 192.168.1.101 local ::1 dev lo proto kernel metric 0 pref medium ::1 dev lo proto kernel metric 256 pref medium local 2404:4408:2375:d500:4216:7eff:fe63:b6ba dev br0 proto kernel metric 0 pref medium 2404:4408:2375:d500::/64 dev br0 proto kernel metric 256 expires 691200sec pref medium local fe80::1c3a:dcff:fede:bb53 dev br0 proto kernel metric 0 pref medium local fe80::4216:7eff:fe63:b6ba dev eth0 proto kernel metric 0 pref medium fe80::/64 dev br0 proto kernel metric 256 pref medium fe80::/64 dev eth0 proto kernel metric 256 pref medium ff00::/8 dev wg0 metric 256 pref medium ff00::/8 dev br0 metric 256 pref medium ff00::/8 dev eth0 metric 256 pref medium default via fe80::1af1:45ff:fea4:9ff0 dev br0 proto ra metric 1024 expires 298sec hoplimit 64 pref medium The only difference I see between the two is a different IPv6 IP for the br0 interface.
  11. Bump. Would someone with 6.8.0-rc7 be able to verify that with "IPv4 only" all IPv6 access is disabled?
  12. btrfs-scrub(8) recommends around once a month, but less is fine. https://github.com/kdave/btrfsmaintenance is a really nice set of scripts for other distros, but you can look at the timers and etc to figure out what a good frequency is. Follwing this, btrfs-scrub & btrfs-balance are run monthly.
  13. If this is the SQLite DB corruption issue, wasn't there a fix for this in 6.8.0-rc5? You should try upgrading to the latest rc, but make a flash backup first.