Are the MAC addresses for custom apps on a bridge static

TrueNAS General
, , ,
1

I’m running some network services as custom apps on the bridge device so I have full control over port access etc especially for SSDP. At present they start up using DHCP, but I don’t know where I can check what MAC address is being provided or where it is even defined.

I currently manage all of my static IP address allocations from my home router based on MAC address.

I can’t see any network controllers running in kube-system, but I was surprised to see openebs running on 24.04

# k3s kubectl get all -n kube-system
NAME                                       READY   STATUS    RESTARTS   AGE
pod/csi-smb-node-fwd96                     3/3     Running   0          4d17h
pod/csi-nfs-node-mjbqv                     3/3     Running   0          4d17h
pod/snapshot-controller-546868dfb4-4j7sc   1/1     Running   0          4d17h
pod/csi-smb-controller-7fbbb8fb6f-lj6xt    3/3     Running   0          4d17h
pod/snapshot-controller-546868dfb4-vzlbh   1/1     Running   0          4d17h
pod/amdgpu-device-plugin-daemonset-ktpvl   1/1     Running   0          4d16h
pod/csi-nfs-controller-7b74694749-z4z9l    4/4     Running   0          4d17h
pod/openebs-zfs-node-6drm4                 2/2     Running   0          4d16h
pod/openebs-zfs-controller-0               5/5     Running   0          4d17h
pod/coredns-59b4f5bbd5-kxs8s               1/1     Running   0          4d17h

NAME               TYPE        CLUSTER-IP    EXTERNAL-IP   PORT(S)                  AGE
service/kube-dns   ClusterIP   172.17.0.10   <none>        53/UDP,53/TCP,9153/TCP   142d

NAME                                            DESIRED   CURRENT   READY   UP-TO-DATE   AVAILABLE   NODE SELECTOR            AGE
daemonset.apps/csi-smb-node                     1         1         1       1            1           kubernetes.io/os=linux   142d
daemonset.apps/csi-nfs-node                     1         1         1       1            1           kubernetes.io/os=linux   142d
daemonset.apps/amdgpu-device-plugin-daemonset   1         1         1       1            1           <none>                   142d
daemonset.apps/openebs-zfs-node                 1         1         1       1            1           <none>                   142d

NAME                                  READY   UP-TO-DATE   AVAILABLE   AGE
deployment.apps/csi-smb-controller    1/1     1            1           142d
deployment.apps/csi-nfs-controller    1/1     1            1           142d
deployment.apps/coredns               1/1     1            1           142d
deployment.apps/snapshot-controller   2/2     2            2           142d

NAME                                             DESIRED   CURRENT   READY   AGE
replicaset.apps/csi-smb-controller-7fbbb8fb6f    1         1         1       142d
replicaset.apps/csi-nfs-controller-7b74694749    1         1         1       142d
replicaset.apps/coredns-59b4f5bbd5               1         1         1       142d
replicaset.apps/snapshot-controller-546868dfb4   2         2         2       142d

NAME                                      READY   AGE
statefulset.apps/openebs-zfs-controller   1/1     142d

For example my minidlna pod has the following networking

/ # ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
3: eth0@if16: <BROADCAST,MULTICAST,UP,LOWER_UP,M-DOWN> mtu 1500 qdisc noqueue state UP 
    link/ether e2:c5:fa:fd:57:54 brd ff:ff:ff:ff:ff:ff
    inet 172.16.0.28/16 brd 172.16.255.255 scope global eth0
       valid_lft forever preferred_lft forever
    inet6 fe80::e0c5:faff:fefd:5754/64 scope link 
       valid_lft forever preferred_lft forever
5: net1@if17: <BROADCAST,MULTICAST,UP,LOWER_UP,M-DOWN> mtu 1500 qdisc noqueue state UP 
    link/ether ca:34:bc:1c:8c:39 brd ff:ff:ff:ff:ff:ff
    inet 192.168.0.115/24 brd 192.168.0.255 scope global net1
       valid_lft forever preferred_lft forever
    inet6 fe80::c834:bcff:fe1c:8c39/64 scope link 
       valid_lft forever preferred_lft forever

Is there anyway to take a deeper look into the network setup?

2

They are not static, but you can assign static on the custom app screen, not router.

Hopefully in the next version of Scale, and I’ll be testing specifically for it, they WILL be able to keep the same MAC address since IX is switch to docker compose, and that’s a feature.

So for now, I have them defined in the apps that need static ip, and will remove those and back to the router once Eel comes out.