@tyler_rm your links vs just posting the image here is a bit off putting for someone wanting to help. Here is a post I did year a go or so on how to validate if avahi is working. https://forum.netgate.com/post/1003226 I personally am not a fan of breaking the L2 barrier like this - but in the link I go over how to actually validate if its working or not, etc. Hope that helps.

@JeGr said in Multiple Gateways on same subnet: Why not simply reconfigure those routers Because some devices (not mine) directly connected to router 1 have in their routing table certain rules to redirect traffic through 10.1.0.4. Hence those routers need to be on the same subnet. These routers are shared by around 20 people, in 4 rooms on single floor. Hence I cannot change settings on those routers.

@Derelict Okie, i'll give it a try!

Diese Option ist gesetzt? System > Routing > Gateways > Edit Gateway > Display Advanced > Use non-local gateway -Rico

So a smart/managed layer 2 then ;) BTW, if your going to route and your wanting to access something on your downstream from a IP that is on your transit network you are always going to run into asymmetrical problems.. [image: 1568768481992-asymmetrical.png] If you want to route to other networks on your downstream, then that needs to be connected to your upstream router via a transit network.. If you going to want to get to it from devices on your transit network.. Then you need to host route on them, or you run into the above asymmetrical problem. Connect your upstream to your downstream via transit network (no hosts on it) and your asymmetrical issues are gone [image: 1568768794638-17216.png] Also if you created your SVI on the L2 that your 10 network is on, then its IP would be in the 10 nework.. If you created put the svi on a different L2, then you need to route it via a transit or host routes or your going to have the asymmetrical problems.

@johnpoz I use IPSec to create a site-to-site tunnel should the wireless bridge go down. (Hilariously, this is no longer working, but that is a different problem for a different day). I wanted to use the pfSense for the VPN clients but had too much problems setting it up with the win 10 clients. I only have two VPN clients so it is not really a problem at the moment. But I will probably sit and redesign the whole network. Or I should just get some hardware routers. The win 10 hosts are giving me hell as well.

How are the two networks connected now? You can't send traffic through a gateway in another subnet like that. You need some kind of transit network. For example, if it's a dedicated circuit, you'd have that plugged into an additional NIC (or VLAN) on both pfSense firewalls, and then you'd have some other unrelated subnet to talk between them there. Then you use the address in that subnet as a gateway to reach the other. If you have your LANs plugged together so they're all in the same Layer 2/flat network that is going to be a huge mess.

@leonardo-fernandes You are my hero. Thank you very much. My OpenVPN with AWS works perfectly now

You will neef IGMP proxy for 'discovery' to work. Unless you can use mDNS instead in which case try Avahi. Of coarse if you can enter the IP address of the NAS directly in the devices then you don't need either. But alas that's too easy for most manufacturers it seems. Steve