Search results

I am also running "ANRPL357.0027.2023.0607.1754 ", I updated all firmware before I began with the rest. What type of issues did you notice with the ethernet board?

Good it works fine for you, so I have most likely a small typo somewhere and good you spotted the naming of the file. My original files were named 00-thunderboltX.link, but when I copied it ... I change it to 10/11, do not know why :) More testing is required on my side.

@scyto - question: how do you get around the en05/en06 naming, depending on who connects first? So if I have connected: nuc1 thunderbolt0 -> nuc2 thunderbolt1 Then on both I see them getting en05. Where I expect nuc1 get en05 and nuc2 get en06. The dmesg output shows it sees thunderbolt0 on...

Good to hear you got a step further/fixing it! Also, in your list IP addresses you used for node 2 and 3 the same "lo:0 = 10.0.0.82/32".

I believe you need to configure them as: Node1 en05: 10.0.0.5 Node1 en06: 10.0.0.9 Node2 en05: 10.0.0.10 Node2 en06: 10.0.0.13 Node3 en05: 10.0.0.14 Node3 en05: 10.0.0.6 All /30 of course … 3 subnets, instead of 6 you have now.

@scyto are you sure you configure an unique /30 for each en05/en06 interface? Should it not be 3 subnets only (each host in 2 subnets)?

@scyto I do not use a cluster YET, I am still in the process of getting the network stable. I also tested with a vanilla Debian 12, and it shows the same problem as you had before in Proxmox 8. IPv4 works perfectly, IPv6 does not work (only ping works). Seems IPv6 in the thunderbolt-net is just...

@scyto at this moment, most useful information I am getting from l-koeln and you ... Also, trying to google for thunderbolt-net, is also mission impossible - I could not find anything useful.

Your ip tables should allow anything for IPv6, it could be a bug in the thunderbolt driver.

Yes the Intel add-on is a nice card, i have it too in my NUC13 :-) I would guess an underlying issue, Proxmox just use Debian iptables and their kernel (based on Ubuntu). If you got time, you could try with a vanilla Debian on both nodes and see if it works or does not work. If it works, you...

The firewall/iptables of Proxmox is a bit strange, so best to add an explicit rule to allow anything on thunderbolt0/1/en05/en06. Please note port 8006 is implicit enabled, so that always work (ssh should only work in the same OAM subnet, of your first NIC. So thunderbolt will not work by...

Fresh install. I directly installed Proxmox 8 on my NUC13i3.

1. Strange, on my Proxmox 8 it works fine, when I have the following rule in "/etc/firewall/cluster.fw": IN ACCEPT -i thunderbolt0 -p tcp -log nolog Other ones I cannot comment on, I only have IPv4 an no ring cluster (just 2 nodes).

@scyto thanks! for the write-up. I got it your message partially in the email notification, but the link is handier :)

@scyto I need to check where I seen it. I got a PiKVM connected to all my NUCs, so it could be the console too. I also need to note I only seen it on my NUC8i5, not on the NUC13i3. The behavior when I see it, the thunderbolt0 device does *not* show up ever, a reboot is required. Thus if you...

You must use thunderbolt0/thunderbolt1 in the udev rule, but use en05/en06 in the script. That is making it a bit confusing.

Issue 1 I resolved using udev. I created "/etc/udev/rules.d/10-thunderbolt0.rules" with content: ACTION=="add", SUBSYSTEM=="net", KERNEL=="thunderbolt0", RUN+="/usr/local/bin/pve-thunderbolt0.sh" The script I created contains the following: #!/bin/bash /usr/sbin/ip link set thunderbolt0 up...

@Docop2 i am not what you mean with your reply? Can you also assign an IP via USB4? I got a few issues: 1) assign an IP address when plugging in the thunderbolt cable (using thunderbolt-net) 2) flaky behavior, with the "cannot obtain PCI resources, aborting" error message

Other annoying behavior that sometimes the Thunderbolt link does not come up on my NUC8, and I only see in dmesg: [ 2.420057] ACPI: bus type thunderbolt registered [ 2.420293] thunderbolt 0000:04:00.0: error -EINVAL: cannot obtain PCI resources, aborting [ 2.420301] thunderbolt: probe...

I tried it, but the thunderbolt0 link does. not come "UP" and no IP address automatically assigned.