Hello! I described my experience and posted some samples here - http://cf-dev.70369.x6.nabble.com/cf-dev-Recipe-to-install-Diego-tp40.html wrote:

He also probably listens for udp4 connections. Have you tried to allow udp4 traffic to ports 3456-3457 and check if loggregator collects the logs after it?

Sorry, I've missed your notes about the firewalls you configure for each CF machine - this firewalls is what needs to be configured to accept UDP traffic to ports 3456 and 3457 from any host. vSphere

I have never worked with vSphere, unfortunately. I've googled a bit and found this table which shows which TCP and UDP ports are open by default on vSphere VMs - https://pubs.vmware.com/vsphere-55/ind

You have posted your Application Security Groups - http://docs.pivotal.io/pivotalcf/adminguide/app-sec-groups.html. This groups are created and managed by Cloud Foundry. But the issue here is with sec

Hi, At least for loggregator to successflly talk to metron agents, you need to add a rule to a security group for your private subnet allowing the ingress UDP traffic through ports 3456 and 3457 from

As far as I know, it is so by design - in order to setup a connection to the same host you need to explicitly tell Warden to allow external traffic - https://github.com/cloudfoundry/warden/blob/master

Hello, everyone! I have a Diego application. From the app's Garden container I can access the Internet and establish connections with tcp services running on other VMs but I can't connect to a tcp ser

Hi, I can share my experience on installing Diego on AWS. I followed the instructions for BOSH Lite deployment <https://github.com/cloudfoundry-incubator/diego-release#deploying-diego-to-a-local-bosh-