[07:24] <slyon> JornS: Yeah, you cannot have two default gateways "gateway4" fields.. those will be in conflict with each other, but need to configure your routes manually: https://netplan.io/reference/#default-routes
[09:13] <JornS> tried setting up routing tables and via per the documentation, but still no replies on ping for the 10/16 interface :/ https://pastebin.com/nPZCQGx2
[09:14] <JornS> anyone able of seeing what i'm doing wrong here?
[09:25] <schopin> JornS: on-link: true + gateway feels weird to me? Are you sure about that part?
[09:31] <schopin> JornS: more generally, do you know if the pings actually get to your interface? Are they registering if you use `tcpdump -i enp1s0 icmp` ?
[09:39] <JornS> tried adding the on-link-parameter per netplan docs, but I've tried quite a few variations to this without success so far :/
[09:41] <JornS> pings are getting through to the interface: 09:40:15.441275 IP 10.249.137.8 > 10.249.32.104: ICMP echo request, id 8, seq 2695, length 64
[11:11] <schopin> JornS: on-link means machines on the subnetwork are reachable directly, e.g. are on the same switch as your interface. That's usually incompatible with having a gateway specified.
[11:11] <schopin> At least that's my understanding of it.
[11:15] <schopin> JornS: My understanding of routing tables is somewhat fuzzy, but shouldn't your routing-policy also specify that all traffic *to* 10.0.0.16 should use the table 101?
[11:15] <schopin> Hem, to 10.0.0.0/16
[12:37] <JornS> idk, I'm out of ideas - imho this should work, but I'm too dumb to figure it out :/ https://pastebin.com/4UtkzuDZ
[12:38] <JornS> like, the setup is far form complex - it's just a host with two nics, where one would be used for internal traffic, and another one for internet
[12:38] <JornS> shouldn't be _that_ much of an issue to figure out :'(