bonienl
-
Posts
10233 -
Joined
-
Last visited
-
Days Won
65
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by bonienl
-
-
A fix will come in a future release.
It will allow users to specify additional interfaces or IP addresses to listen to, this may include any custom tunnels.
-
Use /mnt/user as path.
-
On 5/16/2023 at 8:11 PM, mrmint said:
Is there an easy way I can rename the folder?
DFM does not allow you to rename a share name.
Use the regular rename function under Shares to do this.
Renaming a share manually on a single disk will break that share if it exists on other disks as well!
-
No, in this case you use a custom bridge network which does network address translation.
The container uses an address in the 172.20.0.x network but communicates to the outside world using address 10.0.0.211 (this is expected)
-
Check your docker containers running on a custom network.
To avoid IP overlap, you need to set a DHCP range for the custom network which assigns addresses outside to what your router is assigning.
-
33 minutes ago, T0rqueWr3nch said:
Pull requests in:
Thanks, I will look into this when time permits.
Currently the focus is on Unraid 6.12, which should be released "soon"
-
Sorry, there is an error in the latest version which needs to be corrected, but I haven't had time yet to do so.
-
8 minutes ago, Nodiaque said:
Now the problem is how I make this permanent accross reboot
Normally I don't recommend this, because people tend to forget this in the future, but you can add the disable line in the 'go' file on your USB device.
Put the line before starting the GUI (emhttp).
5 minutes ago, Nodiaque said:Would be good when someone select ipv4 only to really disable it everywhere like in all.
The all setting is not used because you should enable or disable IPv6 per individual interface, it is allowed to mix between ipv4 and ipv6 depending on requirements
-
2 minutes ago, Nodiaque said:
Shim isn't there
When docker is stopped all the shim interfaces are removed, they only exist when docker is running
3 minutes ago, Nodiaque said:can I simply change this one to 1
You can, but look at my test with Unraid 6.12.0-rc5
-
1 minute ago, Nodiaque said:
Hmmm... do I need to put the command you gave me un a script for each reboot?
The command I gave is a temporary fixe and does not survive a reboot (you need to run it again)
1 minute ago, Nodiaque said:I also see ipv6 on loopback
That is correct, loopback interface is configured for both ipv4 and ipv6. It won't interfere with docker
-
I did a quick test,
docker network create my-bridge --subnet=192.168.255.0/24 --gateway=192.168.255.1# docker network inspect my-bridge [ { "Name": "my-bridge", "Id": "a92c67493cc6ae2dc42c23b538c6d2eae3faf0498b456a017edddad091a3d8ed", "Created": "2023-05-02T19:30:31.173992897+02:00", "Scope": "local", "Driver": "bridge", "EnableIPv6": false, "IPAM": { "Driver": "default", "Options": {}, "Config": [ { "Subnet": "192.168.255.0/24", "Gateway": "192.168.255.1" } ] }, "Internal": false, "Attachable": false, "Ingress": false, "ConfigFrom": { "Network": "" }, "ConfigOnly": false, "Containers": {}, "Options": {}, "Labels": {} } ]268: br-a92c67493cc6: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default link/ether 02:42:9a:6e:fa:95 brd ff:ff:ff:ff:ff:ff inet 192.168.255.1/24 brd 192.168.255.255 scope global br-a92c67493cc6 valid_lft forever preferred_lft forever
No IPv6 address.
I am using Unraid 6.12.0-rc5 with docker version 20.10.23
-
3 minutes ago, Nodiaque said:
but it already have enableipv6: false
Yes config looks alright, docker apparently doesn't fully disable ipv6 and always create the link-local address
-
2 minutes ago, Nodiaque said:
The 2nd docker is on my-bridge
You need to delete and recreate this network "'my-bridge" without ipv6 settings.
-
8 minutes ago, Nodiaque said:
the only one that have ipv6 right now is the shim-br0
The shim-br0 interface is created because host access to custom network is enabled.
If you don't need host access, you should disable it under Docker settings
I put on my todo list to include shim interfaces as well when not using ipv6. Merci
You can manually disable ipv6 for this interface by doing
echo 1 > /proc/sys/net/ipv6/conf/shim-br0/disable_ipv6 -
1 minute ago, Nodiaque said:
ok, if I restart unraid and prevent all container from starting up?
We were typing at the same time....
Yes you should do that.
-
A container created this interface, it won't go away when you stop docker.
If you can't find out, reboot your system but don't autostart docker containers, that should clear it.
-
br-22a634b77f67 is created by a docker container, you need to find out which container
-
Your "regular" interface is br0, which is ipv4 only
Try the following:
- Re-enable IPv6 for br0 (docker and vm services must be stopped to do this)
- Go to docker configuration and if any IPv6 assignment is checked, uncheck it
- Reconfigure br0 back to ipv4 only again
- Start docker and vm services
-
When IPv4 only is used all the "regular" interfaces have no IPv6 assignments at all
Example
217: br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether a0:36:9f:79:84:ac brd ff:ff:ff:ff:ff:ff inet 10.0.101.13/24 scope global br0 valid_lft forever preferred_lft forever 218: br0.2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether a0:36:9f:79:84:ac brd ff:ff:ff:ff:ff:ff 219: br0.3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether a0:36:9f:79:84:ac brd ff:ff:ff:ff:ff:ff 220: br0.4: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether a0:36:9f:79:84:ac brd ff:ff:ff:ff:ff:ff 221: br0.5: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether a0:36:9f:79:84:ac brd ff:ff:ff:ff:ff:ff 222: br0.6: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000 224: br1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether a0:36:9f:79:84:ad brd ff:ff:ff:ff:ff:ff inet 10.0.101.84/24 brd 10.0.101.255 scope global dynamic noprefixroute br1 valid_lft 85402sec preferred_lft 74602sec
In your picture the IPv6 assignments are to virtual interfaces (veth).
Make sure your docker configuration and docker containers are not configured for ipv6.
As a test disable the docker and vm services and check again.
-
21 hours ago, Squid said:
Should we mark the plugin as being only compatible with 6.12+
I need to test this on a system with older Unraid version to see what happens exactly.
The plugin is supposed to be compatible from 6.9 onwards.
-
Can you logout, then wait 1 minute and login again.
Another thing to try: switch to English GUI and see if it loads.
-
I updated the plugin "Dynamix Share Floor", which should fix the issue.
-
7 hours ago, Titan84 said:
Diags attached from yesterday when i had the plugin installed if it helps you 🙂
I need to look into this
Thanks
-
1
-
-
25 minutes ago, robti said:
System reset plug-in rebooted the server but sitting with no access to it for an hour now, is something wrong as I can’t find out how long it takes to finish?
Thanks
After reboot it comes back immediately, but the network settings and management settings are reset to default.
And you may need to re-open the page using the default access mode (if this was changed):
http://tower or http://ip-address
-
1
-
[Plugin] Tailscale
in Plugin Support
Posted
These changes are currently under test and likely too soon for 6.12.0 release.
I expect to include them in 6.12.1