[07:31] <slyon> genkgo: is the ens18 interface (or rather your default GW 172.16.20.254) connected to that other networks? Could you use some kind of traceroute to check at which hop it fails? mtr -I ens18 -c 5 --tcp -P 80 -r -n 46.0.0.2
[07:39] <genkgo> slyon: I fixed it already by disabling the prefix routes
[07:39] <genkgo> although that only works by disabling the prefix routes manually (bash script), not via a .network file which I understand is the preferred option
[07:39] <genkgo> why that is not working, I don't know
[07:39] <slyon> OK, good to know that you found a solution!
[07:44] <genkgo> slyon: are you also aware of FAN overlay networks?
[07:45] <genkgo> because containers on this machine using the overlay network are still not able to connect to resources on the subnets of those external ips
[08:04] <slyon> not really... no