I am a little out of my depth here with what to do.

I have my unraid server and other servers on my main LAN - 192.168.1.0/24.

I dont have bridging set.

I have three VLANS also : 10.10.10.0/24 (IOT), 10.10.20.0/24 (Home deices, iphones etc), 10.10.30.0/24 (XBoxes with open networking) and 10.10.40.0/24 (Cams).

I use unify equipment and have firewall rules from the vlans to allowed servers/ports on the main lan.

The issue :

I would like to use a container - WatchYourLan.

These apps can ONLY find devices on my main network where unraid is - i.e 192.168.1.0/24. I believe it uses an arp ping, which cannot traverse the network, even though unraid and the container can ping these devices on the vlans.

I have done some googling and it suggests I need to enable bridging on the nic, and maybe add vlans on unraid network config br0.10, br0.20, br0.30 and br0.40.

And I suppose change the unify port for the unraid server to allow all (rather than block all).

I do not want to give these VLAN's IP addresses as the unraid server should not be contactable from the VLANs.

Any idea what of the above is needed - or if there is another way I should do it ?

If I cant get an answer to this query, maybe cant I ask - Is bridging now fully supported for the macvlan option ? I need macvlan as I use unifi networking stuff.

Edited June 20, 20251 yr by vw-kombi

Never mind, through trial and error using my backup unraid server I got this working.

In case it helps anyone else :

1 - No need to enable bridging

2 - turned on vlans in network settings, and added 4 (vlan10, 10, vlan20, 20, vlan30, 30, vlan40, 40, all these I left NONE for the IP4 address assignment (as I did not want the vlans to talk back to unraid host).

3 - enabled the vlans on the port used by the unraid server (in unify terms, changed to allow all instead of block all).

4 - in netstat -i, this shows then as etho0.10, eth0.20, eth0.30 and eth0.40.

5 - I added these interfaces to the watchyourlan container and this can now see the vlans.

Throw back - I have had to turn on bridging in the network settings for a different issue with my VM's, as I had to edit one to add insert an OS DVD ISO, and after saving and restarting, then IP address was in the 192.168.1.122 range. Some googling said I have to change the interface to br0 for the VM's, so I activated bridging again in the network settings.

Now I have lost viability to the vhost0 interface where all the docker containers were showing in watchyourlan.

Still not managed to find them. I am monitoring br0 but they dont show there.

16 hours ago, vw-kombi said:

Now I have lost viability to the vhost0 interface where all the docker containers were showing in watchyourlan.

Depends on the docker and setting in what network mode , for example, I assign Wireshark in host mode and it can access all interface., you can open different Windows to monitor different interface.

In previous, I use Fing Box to do same work as "container - WatchYourLan", but to be honest , not much meaning of that. But Fing develop a hardware and Apps for this solutions.

Edited July 29, 2025Jul 29 by Vr2Io

17 hours ago, vw-kombi said:

Still not managed to find them. I am monitoring br0 but they dont show there.

If VM and docker set in same br0, then no reason both wouldn't see each other. Does your VM ( Windows ? ) allow response PING ?

To clarify.

The docker container is called WatchYourLan.

My unraid server is configured with vlans - and this container can see all the vlans and the devices (br0.10, br0.20, br0.30 etc).

This container can also see all other devices on br0 (unraid server, and the devices on 192.168.1.10/24)

But - This container cannot see the other docker containers that are using br0 and have IP addresses set in the 192.168.1.0/24 range.

The container config states it must be run as Host networking. If I set it to Bridge or br0-LAN (with an IP), then it does not start.

I also have host access to container allowed.To clarify.

Strange haven't detect docker on br0, but expected won't detect device / docker on br0.xx.

3 hours ago, Vr2Io said:

Strange haven't detect docker on br0, but expected won't detect device / docker on br0.xx.

You misunderstood - It IS reading all the VLANs on BR10,20,30,40 etc.

And all devices on br0

It just cant read any other containers.

The arp strings for the vlans are :

arp-scan -gNx 10.10.10.0/24 -Q 10 -I br0.10

arp-scan -gNx 10.10.20.0/24 -Q 20 -I br0.20

arp-scan -gNx 10.10.30.0/24 -Q 30 -I br0.30

arp-scan -gNx 10.10.40.0/24 -Q 40 -I br0.40

And the interfaces it is setup to look for are br0.

It finds everything except the other containers.

I can pass in extra arguments for arp-scan, but I dont know what exactly may help there.

By default, it does this - arp-scan -glNx -I br0

and if I run that in the container console, it indeed only finds the other stuff - just not containers.

Edited July 30, 2025Jul 30 by vw-kombi

Further to this, netalertX container has the same issue - no containers can be found but all else is.

Basically, a container setup with host networking CANNOT see other containers on br0.

Success........

I did an ifconfig -a and there is an interface called shim-br0.

For fun and giggles, I added this interface to the containers.

And there you go - they all come up. also netAlertX works too.....