lets have it BOY
1 Like
Ah, that means that the NAT of the vnet only created a NAT between the vnet interface and your default LAN interface, but not between the vnet and the newly created link.
Yes, mulling it over with all I’ve learned today, that sounds plausible. Seeing as though this works, I’ve no inclination to adjust things further haha
I cannot thank you enough for the help!
1 Like
I’m not a jails man, but I know docker for example uses 172 cidr for internal container ips and namespaces. If you happen to use the same subnet externally (which sounds like you do), you can no longer route to it from within a network namespace that has that setup to be routed as a cross container network.
I know this from experience as one of the companies I worked for ended up using all of the possible internal subnets, causing issues with containerised environments as the network namespaces used for containers would clash with genuine external services running in that subnet.
1 Like
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.