Multi-Homed Server?

I'm in the process of segmenting my home network, primarily for moving Wifi and IOT stuff off to its own segment.  I'm using physical segments vs VLANS because my Firewalla Router has the extra ports.  I would like to take the Home Theater and make it a separate segment.  Wifi/IOT/Guest one segment, Home Theater one segment, Servers one segment.  The issue is with Discovery only working on the Server subnet.  Does myServer support multi-homing (meaning, if I hit discovery it will hit all configured networks)?   

We will need specifics. All devices need to be on the same subnet as myServer. No exceptions. There are many reasons for this.

Allonis uses VLans:
Our specifics:
VLAN 5 = AES67 digital audio network
VLAN 10 = "Control" devices that require Internet
VLAN 20= Video over IP network
VLAN 40= TVs that do not require Internet

You will see these VLANs identified in many of the drivers as vlans to discover devices on. You will also see commands for "SetMulticastDevice" that may be needed if not Eth0 connected. You will see most Master Images preset and assign the Pi to these Vlans. With our most current software, this will be removed and optionally preset.

You are venturing into a very complicated discussion. Keep it simple. Put everything on one subnet.  If you have digital audio and video distribution, follow Allonis's VLAN examples.

You can set your scope to be 255.255.0.0 (/16)  And then put "network stuff" on 192.168.3.X  and automation / control stuff on 192.168.2.X and general household computers on 192.168.1.x  as example.  That tidys things up and it's all on one wide subnet.

If you network requires VLANs, strongly consider purchasing our Allonis L3 managed switches that are the best deal in the industry for more sophisticated networking.  This is what we use on all of our digital media systems (the great majority of Allonis's business now).  You can spend MANY months figuring this stuff out.  We have done all of that hard work and it's encapsulated in these L3 switches.

Thanks David. My network is similiar to your suggestion...

192.168.1.x = Wireless Devices
192.168.2.x = Servers
192.168.3.x = Wired Devices
192.168.6.x = Home Theater Control Devices

The 192.168.6.x was needed because the Global Cache Devices and the HDfury Vrroom would drop off the network after their network interface was overloaded with too many management packets. There is a router between the 2.x and 6.x network with a static route defined.

Everything is working properly now... If I need to discover a device, I just plug it into the "Server" network, discover it and move it to the proper network...and update the IP address in Myserver.

My home network is now super quiet and fast I had to do a couple of tweaks.. for example, I needed to enable Wifi on my Anthem AVM-70 because the mobile app wouldn't find it across networks. Most of the other mobile apps allow you to manually enter the IP address of the device and they work fine.

Thanks again for the detailed reply!

My concern is if Discovery isn't working, then your network is not setup correctly to allow all packet types to go to myServer. For example, UDP does not go across subnets. Sometimes that is only used for Discovery. But other devices need UDP for daily function. So, you might be lucky that your devices don't use UDP. But it's just a matter of time before you get stung and THEN have to completely redo your network. Better to get it setup correctly day one and then expand it. Put your subnet on 255.255.0.0 and NOT 255.255.255.0

Firewalla doesn't allow for 255.255.0.0 for each network. It does have mDNS and SSDP relays turned on.

I can dig a bit more on the Firewalla config.

Thanks!

that is a pretty basic setting....If "Firewalla" doesn't support that then change to OpnSense of PFSense or Ubiquiti or any other firewall application.