alexandru-bagu edited a comment on issue #4454: URL: https://github.com/apache/cloudstack/issues/4454#issuecomment-724777595
> @alexandru-bagu I could only imagine that unpredictable conflicts may arise from binds on forwarded ports choosing ports in use by an outgoing connection, or so. I think you are right and it could work in principle. cc @andrijapanicsb @PaulAngus ? Any service that relies on the source nat ip would create a conflict like the VPN that can be setup with one click. However that should not restrict it's usage. Unless the system is intended to be idiot-proof the possible conflicts should not prevent other proper uses. At the moment the public ip used for source-nat is somewhat wasted because it can be used for only vpn (or other pre-defined services). Edit 1: I suppose outgoing port binds might also create some conflicts but again that should not prevent all port forwards. Outgoing ports are generally above 50k and most services use ports below 10k. Edit 2: I imagine the source-nat for a vpc network works the same as a wan connection on a normal house-hold router. Am I wrong? ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
