I was hoping someone could help me implement a current netplan yaml that I have working on a number of Ubuntu installations into working routes on my TrueNAS scale installation.
This is my current working netplan yaml in Ubuntu 22.04 LTS:
As you can see I have one interface that gets routed to various other subnets.
Many of the use the "to: IP, scope: link, metric: 100" format.
Is there any way to accomplish this in TrueNAS Scale?
Any help would be appreciated.
This is my current working netplan yaml in Ubuntu 22.04 LTS:
Code:
network: renderer: NetworkManager version: 2 ethernets: eth0: match: macaddress: 00:xx:xx:xx:xx:xx mtu: 1500 set-name: eth0 dhcp4: false accept-ra: false addresses: - 172.17.255.30/24 nameservers: search: [xxx.net,ssn.xxx.net] addresses: [172.17.255.10,172.17.255.169] routes: - to: default via: 172.17.255.254 - to: 172.18.99.0/24 scope: link metric: 100 - to: 172.27.0.0/24 scope: link metric: 100 - to: 172.20.187.0/24 scope: link metric: 100 - to: 172.17.46.0/24 via: 172.17.255.138 - to: 172.17.48.0/24 via: 172.17.255.138 - to: 172.20.188.0/24 via: 172.17.255.138
As you can see I have one interface that gets routed to various other subnets.
Many of the use the "to: IP, scope: link, metric: 100" format.
Is there any way to accomplish this in TrueNAS Scale?
Any help would be appreciated.