- Annoyance
Unraid’s ifconfig reports 0.0.0.0 when the bridge’s member interfaces or the underlying configuration (via ip addr or brctl) doesn’t explicitly define a broadcast value. Most modern Linux networking tools (like iproute2) don’t require or even use the broadcast field for L2-bridged interfaces anymore, because the bridge itself operates at Layer 2 and passes broadcast frames transparently...
However, Docker configures its bridge with ip commands when it creates docker0, explicitly including the broadcast:
example: ip addr add 172.17.0.1/16 brd 172.17.255.255 dev docker0
to get the actual get my broadcast ip from the system I need to know the broadcast ip... When the command should be able to tell and give that to me...
to get the actual broadcast its using: exampleip route get 192.168.1.255
Example as i'm using 192.168.201.x/24
root@The-Borg:~# ip route get 192.168.201.255
broadcast 192.168.201.255 dev br0 table local src 192.168.201.100 uid 0
cache <local,brd>
root@The-Borg:~#
root@The-Borg:~# ip addr show dev br0
4: br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether 10:70:fd:cd:08:6e brd ff:ff:ff:ff:ff:ff
inet 192.168.201.100/24 metric 1 scope global br0
valid_lft forever preferred_lft forever
inet6 fe80::1270:fdff:fecd:86e/64 scope link proto kernel_ll
valid_lft forever preferred_lft forever
So we have a display bug. I don't know when it stopped working, and thanks To Mame59 to bring it to my attention and having found a workaround...
this doesn't prevent unriad network nor broadcast from working as it should due to the iptroue2 authorize networking system setup. This is only to fix the display output of running the recommend ifconfig to see and get the actual data that is displayed incorrectly.