GeoSnipes

Found a discussion that answer my questions: [6.9.0-BETA25] HOST ACCESS TO CUSTOM NETWORKS" OPTION IN DOCKER CHANGES MAC ADDRESS OF UNRAID SERVER

When looking in Settings > Network, Interface eth0 reports a mac of 70:58:00:00:00:01 HOWEVER, when looking in my unifi clients I see this unknown mac address of b2:24:00:00:00:5c that has the ip and switch port mapping as my Unraid server. If I block mac 70:58:00:00:00:01 I can still access the gui but if I block b2:24:00:00:00:5c, I immediately cannot access the Unraid Gui. Any thoughts? Update Did some digging and found the following when ran ifconfig (ive modified the MAC addresses for public posting) eth0: flags=6211<UP,BROADCAST,RUNNING,SLAVE,MULTICAST> mtu 1500 ether 70:58:00:00:00:01 txqueuelen 1000 (Ethernet) RX packets 237192771 bytes 210661360859 (196.1 GiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 189551710 bytes 82347919550 (76.6 GiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 bond0: flags=5443<UP,BROADCAST,RUNNING,PROMISC,MASTER,MULTICAST> mtu 1500 ether 70:58:00:00:00:01 txqueuelen 1000 (Ethernet) RX packets 237192771 bytes 210661360859 (196.1 GiB) RX errors 0 dropped 4916 overruns 0 frame 0 TX packets 189551710 bytes 82347919550 (76.6 GiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 br0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.57.175 netmask 255.255.255.0 broadcast 0.0.0.0 ether 70:58:00:00:00:01 txqueuelen 1000 (Ethernet) RX packets 234627773 bytes 207436546508 (193.1 GiB) RX errors 0 dropped 1172 overruns 0 frame 0 TX packets 184221561 bytes 81852227063 (76.2 GiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 shim-br0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.57.175 netmask 255.255.255.255 broadcast 0.0.0.0 inet6 fe80::b03c:abff:1111:5c5c prefixlen 64 scopeid 0x20<link> ether b2:24:00:00:00:5c txqueuelen 1000 (Ethernet) RX packets 1888063 bytes 1182435586 (1.1 GiB) RX errors 0 dropped 408 overruns 0 frame 0 TX packets 566203 bytes 689037239 (657.1 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 Anybody able to give a rundown of why networking is done like this in Unraid?

Did anyone ever figure this out?

Do we uninstall the cli tools first then uninstall the old plugin, or just uninstalling the plug is enough?

Not to worry. Found it, just add ":rw,slave" to the end. Eg: /usr/share/elasticsearch/data:/mnt/disks/ZR12EKK3/appdata/elasticsearch/data:rw,slave

How would you go about setting the slave option if you are using docker-compose through portainer?