cloudstack-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From GitBox <...@apache.org>
Subject [GitHub] rafaelweingartner commented on issue #2514: [CLOUDSTACK-10346] Problem with NAT configuration and VMs not accessing each other via public IPs
Date Wed, 18 Apr 2018 19:18:43 GMT
rafaelweingartner 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-382498868
 
 
   The first time when I saw this `throw` clause in the @ustcweizhou comments, I googled and
I found this:
   > throw - a special control route used together with policy rules. If such a route is
selected, lookup in this table is terminated pretending that no route was found. Without policy
routing it is equivalent to the absence of the route in the routing table. The packets are
dropped and the ICMP message net unreachable is generated. The local senders get an ENETUNREACH
error. 
   
   That is why I said I do not understand how that `throw` option can solve the NAT translation
that we are having

----------------------------------------------------------------
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

Mime
View raw message