Can't get IP addresses assigned properly

I followed your instructions and configured my 3 Minisforum MS-01 the same way. However I can't assign the IP addresses properly to EN05 and EN06. This is my configuration:

**Cluster Management Network:** `192.168.3.0/24` (vmbr0)
- n1: 192.168.3.11
- n2: 192.168.3.12
- n3: 192.168.3.13

**VM Network and Backup Cluster Network:** `192.168.6.0/24` (vmbr1)
- n1: 192.168.6.11
- n2: 192.168.6.12
- n3: 192.168.6.13

**TB4 Mesh Network:** `10.100.0.0/24` (en05/en06)
- **OpenFabric Router IDs:**
  - 10.100.0.101 (n1)
  - 10.100.0.102 (n2)
  - 10.100.0.103 (n3)

**TB4 controllers and interfaces:**
```bash
martin@Lenovo-Laptop:~$ for node in 192.168.3.11 192.168.3.12 192.168.3.13; do
  echo "=== TB4 hardware on $node ==="
  ssh root@$node "lspci | grep -i thunderbolt"
  ssh root@$node "ip link show | grep -E '(en0[5-9]|thunderbolt)'"
done
=== TB4 hardware on 192.168.3.11 ===
00:07.0 PCI bridge: Intel Corporation Raptor Lake-P Thunderbolt 4 PCI Express Root Port #0
00:07.2 PCI bridge: Intel Corporation Raptor Lake-P Thunderbolt 4 PCI Express Root Port #2
00:0d.0 USB controller: Intel Corporation Raptor Lake-P Thunderbolt 4 USB Controller
00:0d.2 USB controller: Intel Corporation Raptor Lake-P Thunderbolt 4 NHI #0      
00:0d.3 USB controller: Intel Corporation Raptor Lake-P Thunderbolt 4 NHI #1      
9: en05: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 65520 qdisc fq_codel state UP mode DEFAULT group default qlen 1000
10: en06: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 65520 qdisc fq_codel state UP mode DEFAULT group default qlen 1000
=== TB4 hardware on 192.168.3.12 ===
00:07.0 PCI bridge: Intel Corporation Raptor Lake-P Thunderbolt 4 PCI Express Root Port #0
00:07.2 PCI bridge: Intel Corporation Raptor Lake-P Thunderbolt 4 PCI Express Root Port #2
00:0d.0 USB controller: Intel Corporation Raptor Lake-P Thunderbolt 4 USB Controller
00:0d.2 USB controller: Intel Corporation Raptor Lake-P Thunderbolt 4 NHI #0      
00:0d.3 USB controller: Intel Corporation Raptor Lake-P Thunderbolt 4 NHI #1      
9: en06: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 65520 qdisc fq_codel state UP mode DEFAULT group default qlen 1000
11: en05: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 65520 qdisc fq_codel state UP mode DEFAULT group default qlen 1000
=== TB4 hardware on 192.168.3.13 ===
00:07.0 PCI bridge: Intel Corporation Raptor Lake-P Thunderbolt 4 PCI Express Root Port #0
00:07.2 PCI bridge: Intel Corporation Raptor Lake-P Thunderbolt 4 PCI Express Root Port #2
00:0d.0 USB controller: Intel Corporation Raptor Lake-P Thunderbolt 4 USB Controller
00:0d.2 USB controller: Intel Corporation Raptor Lake-P Thunderbolt 4 NHI #0      
00:0d.3 USB controller: Intel Corporation Raptor Lake-P Thunderbolt 4 NHI #1      
9: en05: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 65520 qdisc fq_codel state UP mode DEFAULT group default qlen 1000
11: en06: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 65520 qdisc fq_codel state UP mode DEFAULT group default qlen 1000
```

Renaming to en05 and en06 seems to work properly, even after restart.

I created `/etc/systemd/network/00-thunderbolt0.link` and `/etc/systemd/network/00-thunderbolt1.link` with exactly the same content as you did.

**Network Interface configuration:**

This is the part where I'm unsure. `/etc/network/interfaces` looks like this:
```bash
root@ms01:~# cat /etc/network/interfaces
# network interface settings; autogenerated
# Please do NOT modify this file directly, unless you know what
# you're doing.
#
# If you want to manage parts of the network configuration manually,
# please utilize the 'source' or 'source-directory' directives to do
# so.
# PVE will preserve these directives, but will NOT read its network
# configuration from sourced files, so do not attempt to move any of
# the PVE managed interfaces into external files!

auto lo

iface en05 inet manual
#do not edit in GUI

iface en06 inet manual
#do not edit in GUI

iface lo inet loopback

iface enp90s0 inet manual

iface enp87s0 inet manual

iface enp2s0f0np0 inet manual

iface enp2s0f1np1 inet manual

iface wlp91s0 inet manual

auto vmbr0
iface vmbr0 inet static
        address 192.168.3.11/24
        bridge-ports enp90s0
        bridge-stp off
        bridge-fd 0
#Primary cluster communication and ssh access

auto vmbr1
iface vmbr1 inet static
        address 192.168.6.11/24
        gateway 192.168.6.1
        bridge-ports enp2s0f1np1
        bridge-stp off
        bridge-fd 0
#VM traffic and backup cluster communication

auto en05
iface en05 inet static
    address 10.100.0.5/30
    mtu 65520

auto en06
iface en06 inet static
    address 10.100.0.2/30
    mtu 65520

source /etc/network/interfaces.d/*
```

`en05` and `en06` show up in the proxmox gui with their respective ip address:

<img width="1216" height="101" alt="Image" src="https://github.com/user-attachments/assets/7508c96f-fb84-4b74-8633-7a7a6b8b5e0c" />

However `ip addr show` does not report the IPv4 address:

```bash
martin@Lenovo-Laptop:~$ for node in 192.168.3.11 192.168.3.12 192.168.3.13; do
  echo "=== TB4 interface status on $node ==="
  ssh root@$node 'for i in en05 en06; do ip addr show "$i"; done'
done
=== TB4 interface status on 192.168.3.11 ===
9: en05: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 65520 qdisc fq_codel state UP group default qlen 1000
    link/ether 02:c6:24:16:26:d6 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::c6:24ff:fe16:26d6/64 scope link proto kernel_ll
       valid_lft forever preferred_lft forever
10: en06: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 65520 qdisc fq_codel state UP group default qlen 1000
    link/ether 02:db:3c:ac:63:b5 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::db:3cff:feac:63b5/64 scope link proto kernel_ll
       valid_lft forever preferred_lft forever
=== TB4 interface status on 192.168.3.12 ===
11: en05: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 65520 qdisc fq_codel state UP group default qlen 1000
    link/ether 02:19:3c:93:00:b7 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::19:3cff:fe93:b7/64 scope link proto kernel_ll
       valid_lft forever preferred_lft forever
9: en06: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 65520 qdisc fq_codel state UP group default qlen 1000
    link/ether 02:19:d3:60:d8:45 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::19:d3ff:fe60:d845/64 scope link proto kernel_ll
       valid_lft forever preferred_lft forever
=== TB4 interface status on 192.168.3.13 ===
9: en05: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 65520 qdisc fq_codel state UP group default qlen 1000
    link/ether 02:3a:88:fd:13:de brd ff:ff:ff:ff:ff:ff
    inet6 fe80::3a:88ff:fefd:13de/64 scope link proto kernel_ll
       valid_lft forever preferred_lft forever
11: en06: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 65520 qdisc fq_codel state UP group default qlen 1000
    link/ether 02:71:b7:e0:c3:c6 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::71:b7ff:fee0:c3c6/64 scope link proto kernel_ll
       valid_lft forever preferred_lft forever
```

Do you have any idea what I'm missing? Is it really correct to put the `iface en0x inet manual` statement as well as the `iface en0x inet static` configuration in the same file?

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Can't get IP addresses assigned properly #4

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Can't get IP addresses assigned properly #4

Description

Metadata

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Issue actions