bonienl
-
Posts
10,233 -
Joined
-
Last visited
-
Days Won
65
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Report Comments posted by bonienl
-
-
No more DHCPv6 errors and interface gets IPv6 address using SLAAC.
There is a call trace when your custom bridge (vpn) network is created, but afterwards it looks all containers started successfully and can use this bridge network.
Do you have any problems?
-
2 hours ago, RiDDiX said:
My Log is full with these entrys since rc5.
Start your server in safe mode
-
4 minutes ago, sonic6 said:
Looks like it should:
Genau
-
2
-
-
4 minutes ago, sonic6 said:
But if i'm right, it should be enough deactivating the DHCPv6 function in my router
The manual isn't very clear when disabling the DHCPv6 function, it will use only SLAAC.
You can try, and it might be necessary to set a fixed DNSv6 server in your Unraid system. You can use the Google servers:
2001:4860:4860::8888 and/or 2001:4860:4860::8844
-
2 minutes ago, sonic6 said:
In this Case i used the "IPv4 only" mode, like you suggested. But my LXC Container was pingable over IPv6... i was just wondering.
Sorry, I misunderstood. In IPv4 only mode it is normal that IPv6 does not work.
Apparently the LXC container does its own thing independently of the Unraid settings, I guess it is created with both ipv4 and ipv6 enabled.
The DHCP error related to IPv6 and network call trace, I saw last time are not there anymore.
Your router is set up using DHCP for IPv6, can it be changed to use SLAAC instead?
7 minutes ago, sonic6 said:I am using both in my setup, br0 and host access.
Why do you need host access?
-
1 hour ago, sonic6 said:
so, after enabling "host access"
In your latest diagnostics there is indeed a macvlan call trace.
Since you don't need host access, better switch it off.
-
1 hour ago, sonic6 said:
Unraid itself and Dockers aren't pingable with ipv6
To me that looks like a configuration or network setup error. The PC, when it has both IPv4 and IPv6 addresses should be able to reach the server.
I am running pi-hole as a docker container on my server, pinging it from my pc just works fine
C:\>ping -4 10.0.101.100 Pinging 10.0.101.100 with 32 bytes of data: Reply from 10.0.101.100: bytes=32 time<1ms TTL=64 Reply from 10.0.101.100: bytes=32 time<1ms TTL=64 Reply from 10.0.101.100: bytes=32 time<1ms TTL=64 Reply from 10.0.101.100: bytes=32 time<1ms TTL=64 Ping statistics for 10.0.101.100: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms C:\>ping -6 2a02:a448:32d5:101::100 Pinging 2a02:a448:32d5:101::100 with 32 bytes of data: Reply from 2a02:a448:32d5:101::100: time<1ms Reply from 2a02:a448:32d5:101::100: time<1ms Reply from 2a02:a448:32d5:101::100: time<1ms Reply from 2a02:a448:32d5:101::100: time<1ms Ping statistics for 2a02:a448:32d5:101::100: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms C:\>Note: for this there is no need to enable host access (Unraid itself is not involved in this communication)
-
I am not sure what is happening here, but it is not macvlan related.
The call trace is network related and in the dhcp log there is this message
May 02 06:56:09 [1130]: route socket overflowed (rcvbuflen 106496) - learning interface state
May 02 06:56:09 [1130]: drained 123 messagesCan you try in IPv4 only mode?
-
2
-
-
This is expected behavior.
When you rename a pool, you need to adjust manually the affected share(s) settings.
-
Changed Status to Closed
Changed Priority to Other
-
Only when there are unacknowledged messages, the corresponding section(s) are enabled.
When all is disabled, you can view the messages under Tools -> Archived Notifications
-
When a share exists on both the array and pool, it won't have exclusive access and works as before. Meaning all your data is still visible/accessible regardless of location.
-
The WRITE operation does not change the primary location, it only changes the settings related to the share allocation.
-
1
-
-
7 minutes ago, Zonediver said:
Have you seen this "RED MARKED" Text on the right side?
The biggest confusion for many (new) users is the use of the name "cache", mainly because not all users are familiar with the specific implementation of Unraid and how "cache" is used.
The new approach in Unraid 6.12 takes that confusion away and shows primary and secondary storage instead.
This storage can be the array or any of the existing pools, including a pool called "cache".
-
1
-
-
4 minutes ago, Titan84 said:
Does 6.12 do something similar?
The automatic size calculation of Unraid 6.12 takes 10% of the reported disk size as reported by the file system, which is static. There is no need to schedule rechecks.
The plugin determines the minimum size based on content and make changes depending on the size of the biggest file, which is dynamic. Here a scheduled recheck is needed as content can change.
-
1
-
-
27 minutes ago, itimpi said:
Guess I could try that out and see
For a share which resides on a pool only, it will take the size of the pool as reported by the file system.
For a share which resides on the array, it will take the size of the smallest disk in the array, again as reported by the file system.
-
The plugin is still useful for shares which have not set a minimum free space value. AKA the user has never set anything explicitely for the current shares.
New shares which get an automatic value assigned in 6.12 are not touched by the plugin.
-
This version also does automatic calculation of the minimum free space setting for any new share.
Existing shares can be easily updated by forcing a change in the settings (e.g. enter a space in the min. free space field) and apply.
The user can still set a designated value and overruling the automatic calculation.
Values can be entered as absolute numbers with an optional suffix or as a percentage value.
-
Thanks for reporting, fixed.
-
Please add more information, like screenshots of what you are trying to do.
What are the source settings? What are the destinations? What are the results?
Using the "Write" function to copy settings from source to destination(s) works as expected for me.
-
By default all folders are part of the caching system, it is however recommended to do caching for specific folders which need it. This is done by either defining an explicit "include" list, or alternatively create an "exclude" list, which ever suits best. It is not necessary to set both include and exclude lists.
-
Restarting the docker service does nothing with the plugin. Try a reboot.
If that doesn't work, start your system in safe mode and retest.
-
Can you try without the "docker folder" plugin installed.
-
I have mitigations=OFF too and see a slight improvement when using v6.12.0-rc
6.12.0-rc4 "macvlan call traces found", but not on <=6.11.x
-
-
-
-
-
in Prereleases
Posted
@alturismo can you do the following?
Reason for this test
There is a suspicion that there occurs a conflict situation between bridge function and macvlan function.
Letting macvlan operate directly on the interface should take away this conflict.
Thanks for all your help