You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cloudstack.apache.org by GitBox <gi...@apache.org> on 2018/10/03 08:25:44 UTC

[GitHub] izenk commented on issue #2514: [CLOUDSTACK-10346] Problem with NAT configuration and VMs not accessing each other via public IPs

izenk commented on issue #2514: [CLOUDSTACK-10346] Problem with NAT configuration and VMs not accessing each other via public IPs
URL: https://github.com/apache/cloudstack/pull/2514#issuecomment-426552700
 
 
   @rhtyd may be this helps..
   Looks like routing goes in such way, that packets do not go through SNAT rule
   if two vms are in on TIER and vm1 wants to connect to vm2 through PUBLIC IP, it should look like:
   vm1 internal ip -> VR SNAT -> VR DNAT -> vm2 internal ip
   **now on vm2 I can see packets from vm1, but** source ip is set to vm1 internal ip (not VR SNAT)
   
   So if I try telnet from vm1 to VR publicIP:80 (which is forwarded to vm2:80), on vm2 I can see packets on port 80, but these packets are from vm1 internal ip. Next, **I even can see replies from vm2 on vm1**, but because this replies are coming from vm2 directly to vm1:internal ip and not from VR (how it should be), in fact connection is not established
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services