The "red" traffic will likely only pass bi-directionally if you'll implement hairpin NAT for that "public to public" NAT. Without it, webserver 2 will try to reply to client (accessing abcabc.com:9999) directly, but client will reject this as it will try to talk to your router's WAN IP address.
Hairpin NAT means, that server doesn't see the real client's IP address, it sees the NAT device's IP address. In certain cases this is a deal breaker, in some cases it's a nuisance (lack of observability on server) and in most cases it's not a problem at all.
Hairpin NAT means, that server doesn't see the real client's IP address, it sees the NAT device's IP address. In certain cases this is a deal breaker, in some cases it's a nuisance (lack of observability on server) and in most cases it's not a problem at all.
Statistics: Posted by mkx — Wed Mar 13, 2024 3:33 pm