[cid:image001.png(a)01D13347.127C0FB0]
Hi,


・ Inbound: From the load balancer through the router to the DEA, then from the DEA to the App Container.

・ Outbound: From the App Container to the DEA, then to the gateway on the DEA virtual network interface.

・ This gateway might be a NAT to external networks depending on your IaaS.

・ -------- this is come from CloudFoundry official docs.





Do Load Balancer and NAT have the same ip? In other words, do the two appliance locate on one host( or VM)?



If not, client send a request , destination ip is LoadBalancer’s address, then client receive a response, source ip is NAT address.

I think, in this situation, client can not communicate with cloudfoundry.





Regards,

jiangenlong



来自华信咨询设计研究院有限公司友情提醒：
为确保邮件沟通畅通，如你不能投递到jiangenlong(a)hxdi.com，
请临时将邮件地址中com变更为cn尝试投递，谢谢！

According to your graph, outbound traffic is not the response, it refers to how your app connect to the outside world.




--
Lei Zhang (Harry Zhang)

TEL: (+86) 15157180183
Cloud Team
VLIS Lab
Zhejiang University



在 2015-12-10 12:35:55，"姜恩龙jiangenlong" <jiangenlong(a)hxdi.com> 写道：


Hi,



· Inbound: From the load balancer through the router to the DEA, then from the DEA to the App Container.

· Outbound: From the App Container to the DEA, then to the gateway on the DEA virtual network interface.

· This gateway might be a NAT to external networks depending on your IaaS.

· -------- this is come from CloudFoundry official docs.





Do Load Balancer and NAT have the same ip? In other words, do the two appliance locate on one host( or VM)?



If not, client send a request , destination ip is LoadBalancer’s address, then client receive a response, source ip is NAT address.

I think, in this situation, client can not communicate with cloudfoundry.





Regards,

jiangenlong





来自华信咨询设计研究院有限公司友情提醒：
为确保邮件沟通畅通，如你不能投递到jiangenlong(a)hxdi.com，
请临时将邮件地址中com变更为cn尝试投递，谢谢！

Inbound is connexion initiate from external, in this case dialog between
app and client is throught the LB / Gorouter

Outbound is connexion initiate from Internal that's mean your app want to
connect to something ....

Not sure I am clear ...

On Thu, Dec 10, 2015 at 1:35 PM, 姜恩龙jiangenlong <jiangenlong(a)hxdi.com>
wrote:

Hi,



· Inbound: From the load balancer through the router to the DEA,
then from the DEA to the App Container.

· Outbound: From the App Container to the DEA, then to the
gateway on the DEA virtual network interface.

· This gateway might be a NAT to external networks depending on
your IaaS.

· -------- this is come
from CloudFoundry official docs.





Do Load Balancer and NAT have the same ip? In other words, do the two
appliance locate on one host( or VM)?



If not, client send a request , destination ip is LoadBalancer’s address,
then client receive a response, source ip is NAT address.

I think, in this situation, client can not communicate with cloudfoundry.





Regards,

jiangenlong






*来自华信咨询设计研究院有限公司友情提醒：为确保邮件沟通畅通，如你不能投递到jiangenlong(a)hxdi.com
<jiangenlong(a)hxdi.com>，请临时将邮件地址中com变更为cn尝试投递，谢谢！*

Outbound traffic is not the response, it refers to how your app connect to the outside world.