Omri
-
Posts
96 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Report Comments posted by Omri
-
-
I followed the recommendation in first post
But unfortunately, this configuration is preventing clean shutdown because some of the snapshots prevent unmount of /cache/docker and therefore unmounting of /mnt/user
-
Hi
My cache is zfs in raid 1 mode
When using dedicated share for docker (in folder mode) it create many (many) snapshots and some of them blocking unmounting /mnt/user when stopping array (until I force it by umount -l /cache/docker).
What is the best practice for this or how do I stop this share from creating snapshots? (Don't need them in docker folder)
Thanks
-
Unraid 6.11.2 fixed the issue and IPV6 allocation is now EUI-64 as it should be.
-
In the past I definitely deleted it and it restored default settings. Now it's not creating a file and it's not setting default settings. (I had to use console because DHCP wasn't working)
-
Well, your right of course
but I already up and running after creating the file manually
but it's easy to reproduce
Just thought I share this uncomfortable situation
-
Hi
can you guide me to documantation regrading the change
and/or show me how to roll back to previous behaviour?
Thanks
-
Thanks
I still don't understand how to make it use the mac address as suffix like before
Because my prefix isn't fixed and changes upon renew, I can't use it in docker template
-
Any chance that thunderbolt networking would be supported in future versions?
It's working ootb in other Linux distros (and of course in Mac and windows).
As of now, even after setting up in ifconfig it's not visible in network settings and IP link showing its always down.
Thanks
-
RC4 fixed the problem with the certificate provision
Thanks
- 1
- 1
-
6 hours ago, MammothJerk said:
looks right to me.
DNS rebind protection is set to "No" in my router.
Linux 5.15.27-Unraid. root@Snorlax:~# nslookup rebindtest.unraid.net Server: 8.8.8.8 Address: 8.8.8.8#53 Non-authoritative answer: Name: rebindtest.unraid.net Address: 192.168.42.42 root@Snorlax:~# nslookup rebindtest.myunraid.net Server: 8.8.8.8 Address: 8.8.8.8#53 Non-authoritative answer: Name: rebindtest.myunraid.net Address: 192.168.42.42 Name: rebindtest.myunraid.net Address: fd42::
i also have the same error in my syslog like @kaiguy
Mar 18 06:55:42 Snorlax root: Error: Cannot renew cert until within 30 days of expiry
It's supposedly related to IPV6 configuration.
Let's hope it will be fixed in rc4
-
1 hour ago, ljm42 said:
Sorry for the delay, we now have a way to test for DNS Rebinding protection specifically for the myunraid.net domain. This will be included in rc4 so we can provide better messaging.
To confirm your issue is DNS Rebinding protection, please open a web terminal and run these two commands:
nslookup rebindtest.unraid.net nslookup rebindtest.myunraid.net
If DNS Rebinding protection is NOT an issue you should see something like this, where both addresses resolve to 192.168.42.42
root@Tower:~# nslookup rebindtest.unraid.net Server: 8.8.8.8 Address: 8.8.8.8#53 Non-authoritative answer: Name: rebindtest.unraid.net Address: 192.168.42.42 root@Tower:~# nslookup rebindtest.myunraid.net Server: 8.8.8.8 Address: 8.8.8.8#53 Non-authoritative answer: Name: rebindtest.myunraid.net Address: 192.168.42.42 Name: rebindtest.myunraid.net Address: fd42::
Please post your results.
Here are my results
really appreciate your help
-
Hi
Any clue what causing the "DNS Propagation is PENDING" problem?
-
Any updates on the "DNS Propagation is PENDING" problem?
-
6 hours ago, ljm42 said:
Here it is
Thanks
-
9 hours ago, ljm42 said:
Unraid 6.10 will only respond via https to urls that are specified in the cert, so it is intentional that https://ip does not work.
Anticipating your next question... if you can't access the server while DNS is down see:
https://wiki.unraid.net/My_Servers#How_to_access_your_server_when_DNS_is_down
Unfortunately my router (nest wifi) doesn't have this option.
The way to disable DNS rebinding is mentioned here:
https://support.google.com/googlenest/answer/9144137?hl=en
And it used to work until rc3
-
Any solution to get out of "DNS Propagation is PENDING"?
my system has IPV6+IPV4
at first, GUI address was ip6.hash
after deleting the certificate and provisioning it's stuck at the above.
can't use ssl for GUI now
-
50 minutes ago, Omri said:
After upgrading the certificate, the status is "DNS Propagation is PENDING"
can no longer access https://[lan-ip].[hash].myunraid.net (with my real IP and hash obvoiusly)
can sign in with tower.local (not https)
in diagnostics i see this
DNS Rebinding Protection is disabled, myunraid.net urls will work on this network
also, can't select Auto under use SSL/TLS
-
After upgrading the certificate, the status is "DNS Propagation is PENDING"
can no longer access https://[lan-ip].[hash].myunraid.net (with my real IP and hash obvoiusly)
can sign in with tower.local (not https)
-
Another update
when using Windows 10 - it doesn't matter if the device is eth* or thunderbolt*
I can establish connection (shows as 20gb/s) but it's not reliable
from pc to tower link is very slow, few mb/s
from tower to pc it's not as fast as it should be but it's better +/- 4gb/s
not matter if coping file or using iperf3 (one time as client and other as server)
maybe it's a driver issue...
when switching to mac os - still can't establish connection (although my mac is recognized in tower)
tower booted with ubuntu instead of unraid:
with windows same behaviour
with mac os - full speed both ways
out of ideas
-
Just a little update
on windows it's ( kind of) work
I can establish 20gb/s link but the real transfer speed is ridiculous (less than 10mb/s)
will continue testing
Thanks
-
Yes, I did
-
Here is my output after setting everything
it's showing ATTR{operstate}=="down"
although it's recognizing my computer (ASUS is my server and Macmini8,1 my PC)
-
Hi @SimonF
I had it wrong before, didn't replace KERNEL=="eth* with KERNEL=="thunderbolt*
now I get eth10/3 (doesn't seem to matter) in ifconfig and Unraid network settings
I still can't get the connection to work though.
with Ubuntu for example, I set static IP (different from my DHCP range)
for example - server 192.168.1.2 an PC 192.168.1.3 and that's it
now after setting it, no connection (can't ping either)
I'm on mac (as you can see from the output before which is strange cause it's detecting my mac with 20GB/s link)
-
Hi
I followed your post
but can't seem to make it work
here is my output for udevadm info -a -p /sys/class/net/thunderbolt0
Udevadm info starts with the device specified by the devpath and then walks up the chain of parent devices. It prints for every device found, all possible attributes in the udev rules key format. A rule to match, can be composed by the attributes of the device and the attributes from one single parent device. looking at device '/devices/pci0000:00/0000:00:1b.4/0000:03:00.0/0000:04:00.0/0000:05:00.0/domain0/0-0/0-1/0-1.0/net/thunderbolt0': KERNEL=="thunderbolt0" SUBSYSTEM=="net" DRIVER=="" ATTR{carrier_changes}=="0" ATTR{dev_id}=="0x0" ATTR{carrier_down_count}=="0" ATTR{proto_down}=="0" ATTR{address}=="02:1f:1e:cf:86:86" ATTR{operstate}=="down" ATTR{link_mode}=="0" ATTR{mtu}=="1500" ATTR{gro_flush_timeout}=="0" ATTR{carrier_up_count}=="0" ATTR{ifalias}=="" ATTR{netdev_group}=="0" ATTR{napi_defer_hard_irqs}=="0" ATTR{ifindex}=="10" ATTR{broadcast}=="ff:ff:ff:ff:ff:ff" ATTR{type}=="1" ATTR{dev_port}=="0" ATTR{addr_assign_type}=="0" ATTR{addr_len}=="6" ATTR{threaded}=="0" ATTR{tx_queue_len}=="1000" ATTR{iflink}=="10" ATTR{flags}=="0x1002" looking at parent device '/devices/pci0000:00/0000:00:1b.4/0000:03:00.0/0000:04:00.0/0000:05:00.0/domain0/0-0/0-1/0-1.0': KERNELS=="0-1.0" SUBSYSTEMS=="thunderbolt" DRIVERS=="thunderbolt-net" ATTRS{prtcstns}=="0x00000003" ATTRS{prtcvers}=="1" ATTRS{prtcrevs}=="1" ATTRS{key}=="network" ATTRS{prtcid}=="1" looking at parent device '/devices/pci0000:00/0000:00:1b.4/0000:03:00.0/0000:04:00.0/0000:05:00.0/domain0/0-0/0-1': KERNELS=="0-1" SUBSYSTEMS=="thunderbolt" DRIVERS=="" ATTRS{vendor_name}=="Apple Inc." ATTRS{maxhopid}=="15" ATTRS{vendor}=="0xa27" ATTRS{device}=="0xa" ATTRS{rx_lanes}=="1" ATTRS{rx_speed}=="20.0 Gb/s" ATTRS{unique_id}=="6f46b3a2-b973-4458-a3ff-b8193a7114b5" ATTRS{tx_lanes}=="1" ATTRS{tx_speed}=="20.0 Gb/s" ATTRS{device_name}=="Macmini8,1" looking at parent device '/devices/pci0000:00/0000:00:1b.4/0000:03:00.0/0000:04:00.0/0000:05:00.0/domain0/0-0': KERNELS=="0-0" SUBSYSTEMS=="thunderbolt" DRIVERS=="" ATTRS{nvm_authenticate}=="0x0" ATTRS{vendor_name}=="ASUS" ATTRS{vendor}=="0x31" ATTRS{generation}=="3" ATTRS{device}=="0x5007" ATTRS{nvm_version}=="56.0" ATTRS{unique_id}=="cf030000-0070-740e-033a-832f2c337126" ATTRS{device_name}=="PROART Z490-CREATOR 10G" looking at parent device '/devices/pci0000:00/0000:00:1b.4/0000:03:00.0/0000:04:00.0/0000:05:00.0/domain0': KERNELS=="domain0" SUBSYSTEMS=="thunderbolt" DRIVERS=="" ATTRS{boot_acl}==",,,,,,,,,,,,,,," ATTRS{security}=="none" ATTRS{deauthorization}=="0" ATTRS{iommu_dma_protection}=="1" looking at parent device '/devices/pci0000:00/0000:00:1b.4/0000:03:00.0/0000:04:00.0/0000:05:00.0': KERNELS=="0000:05:00.0" SUBSYSTEMS=="pci" DRIVERS=="thunderbolt" ATTRS{power_state}=="D0" ATTRS{broken_parity_status}=="0" ATTRS{subsystem_device}=="0x8794" ATTRS{dma_mask_bits}=="64" ATTRS{vendor}=="0x8086" ATTRS{local_cpus}=="fff" ATTRS{class}=="0x088000" ATTRS{numa_node}=="-1" ATTRS{max_link_width}=="4" ATTRS{msi_bus}=="1" ATTRS{device}=="0x15eb" ATTRS{current_link_width}=="4" ATTRS{max_link_speed}=="2.5 GT/s PCIe" ATTRS{local_cpulist}=="0-11" ATTRS{driver_override}=="(null)" ATTRS{d3cold_allowed}=="1" ATTRS{irq}=="16" ATTRS{revision}=="0x06" ATTRS{current_link_speed}=="2.5 GT/s PCIe" ATTRS{consistent_dma_mask_bits}=="64" ATTRS{ari_enabled}=="0" ATTRS{enable}=="1" ATTRS{subsystem_vendor}=="0x1043" looking at parent device '/devices/pci0000:00/0000:00:1b.4/0000:03:00.0/0000:04:00.0': KERNELS=="0000:04:00.0" SUBSYSTEMS=="pci" DRIVERS=="pcieport" ATTRS{secondary_bus_number}=="5" ATTRS{power_state}=="D0" ATTRS{subordinate_bus_number}=="5" ATTRS{broken_parity_status}=="0" ATTRS{subsystem_device}=="0x8794" ATTRS{dma_mask_bits}=="32" ATTRS{vendor}=="0x8086" ATTRS{local_cpus}=="fff" ATTRS{class}=="0x060400" ATTRS{numa_node}=="-1" ATTRS{max_link_width}=="4" ATTRS{msi_bus}=="1" ATTRS{device}=="0x15ea" ATTRS{current_link_width}=="4" ATTRS{max_link_speed}=="8.0 GT/s PCIe" ATTRS{local_cpulist}=="0-11" ATTRS{driver_override}=="(null)" ATTRS{d3cold_allowed}=="1" ATTRS{irq}=="128" ATTRS{revision}=="0x06" ATTRS{current_link_speed}=="2.5 GT/s PCIe" ATTRS{consistent_dma_mask_bits}=="32" ATTRS{ari_enabled}=="0" ATTRS{enable}=="1" ATTRS{subsystem_vendor}=="0x1043" looking at parent device '/devices/pci0000:00/0000:00:1b.4/0000:03:00.0': KERNELS=="0000:03:00.0" SUBSYSTEMS=="pci" DRIVERS=="pcieport" ATTRS{secondary_bus_number}=="4" ATTRS{power_state}=="D0" ATTRS{subordinate_bus_number}=="109" ATTRS{broken_parity_status}=="0" ATTRS{subsystem_device}=="0x8794" ATTRS{dma_mask_bits}=="32" ATTRS{vendor}=="0x8086" ATTRS{local_cpus}=="fff" ATTRS{class}=="0x060400" ATTRS{numa_node}=="-1" ATTRS{max_link_width}=="4" ATTRS{msi_bus}=="1" ATTRS{device}=="0x15ea" ATTRS{current_link_width}=="4" ATTRS{max_link_speed}=="8.0 GT/s PCIe" ATTRS{local_cpulist}=="0-11" ATTRS{driver_override}=="(null)" ATTRS{d3cold_allowed}=="1" ATTRS{irq}=="16" ATTRS{revision}=="0x06" ATTRS{current_link_speed}=="8.0 GT/s PCIe" ATTRS{consistent_dma_mask_bits}=="32" ATTRS{ari_enabled}=="0" ATTRS{enable}=="2" ATTRS{subsystem_vendor}=="0x1043" looking at parent device '/devices/pci0000:00/0000:00:1b.4': KERNELS=="0000:00:1b.4" SUBSYSTEMS=="pci" DRIVERS=="pcieport" ATTRS{secondary_bus_number}=="3" ATTRS{power_state}=="D0" ATTRS{subordinate_bus_number}=="109" ATTRS{aer_rootport_total_err_cor}=="0" ATTRS{broken_parity_status}=="0" ATTRS{subsystem_device}=="0x8694" ATTRS{dma_mask_bits}=="32" ATTRS{vendor}=="0x8086" ATTRS{local_cpus}=="fff" ATTRS{class}=="0x060400" ATTRS{numa_node}=="-1" ATTRS{max_link_width}=="4" ATTRS{aer_rootport_total_err_fatal}=="0" ATTRS{msi_bus}=="1" ATTRS{device}=="0x06ac" ATTRS{current_link_width}=="4" ATTRS{max_link_speed}=="8.0 GT/s PCIe" ATTRS{local_cpulist}=="0-11" ATTRS{driver_override}=="(null)" ATTRS{d3cold_allowed}=="1" ATTRS{irq}=="124" ATTRS{revision}=="0xf0" ATTRS{current_link_speed}=="8.0 GT/s PCIe" ATTRS{consistent_dma_mask_bits}=="32" ATTRS{ari_enabled}=="0" ATTRS{enable}=="2" ATTRS{aer_rootport_total_err_nonfatal}=="0" ATTRS{subsystem_vendor}=="0x1043" looking at parent device '/devices/pci0000:00': KERNELS=="pci0000:00" SUBSYSTEMS=="" DRIVERS=="" ATTRS{waiting_for_supplier}=="0"
I created /etc/udev/rules.d/71-persistent-net.rules
Quoteroot@Tower:~# cat /etc/udev/rules.d/71-persistent-net.rules
# Thunderbolt
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="02:1f:1e:cf:86:86", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth10"
and still network doesn't work after these:
udevadm control --reload
udevadm trigger --action=add --attr-match=address="02:1f:1e:cf:86:86"
any help will be appriciated
Unraid OS version 6.12.0-rc5 available
-
-
-
-
-
in Prereleases
Posted
It's because of docker snapshots
But the result is the same
How to handle this problem? Only move to img?