slangasek

If it's about getting machines connected to eth0 to route out to the Internet, yes that's a NAT question which is separate from netplan

@ylluminate gist.github.com/ylluminate/1a3c21f127bfe3d4c93fa79effc097c6 looks solid to me as far as routing now based on what I understand you're expecting. Traffic for the local 192.168.10.0/24 network will be on eth0, all Internet traffic will route via eth1, unless eth1 is down and then it will fall back to eth2. What else are you expecting regarding routing?

but the dhcp server on that interface is handing out a default route with 192.168.0.1 as the gateway, which is wrong if your server is supposed to be 192.168.0.1. So you probably should have this interface configured with a static address only and disable dhcp

ok, whereas you do have 192.168.0.0 routes being provided on eth0. I think you should drop the 0.0.0.0 route from eth1 (which I guess is not actually in use anyway - the default route you currently have via 192.168.0.1 comes via dhcp). also you currently have two ips assigned to eth0 in the 192.168.0.0 subnet - you have 192.168.0.137 which is assigned by the dhcp server, and 192.168.0.1 which is statically assigned in the netplan config...

also the ip route definitely shows that the default route via 192.168.0.1 is being added to your eth0, which is marked as being your LAN (implies, has no Internet) - so that's consistent with your netplan yaml, and I think this yaml is wrong for the config you're trying to achieve. But to know what additional config (if any) you need on eth1, would need to see what the DHCP server there provides when it's working

@ylluminate hi, so in your `ip output gist.github.com/ylluminate/6435840c37edc01e82c047c61f4c071b I see that eth1, which I understood to be your primary ISP, is "up" but has only a local ipv6 address. Is that correct? Is your DSL router currently not functional?

Your screenshot shows that the bridge is using a different mac address than its physical interface (ens18). Is your upstream router rejecting the traffic because it comes from the wrong mac address? Try setting the macaddress for br0 to match the one for ens18.