APM :: VMware View :: PCoIP & UDP/0

Still trying to figure this out...

An inside source says:

“Yes, this is expected behavior. From what I was told by a developer who is no longer with F5 the PCoIP server (virtual desktop) will send these initial UDP packets to the bigip during initial PCoIP connections and there is no way to stop the PCoIP server from doing this. We found that the port(s) used by the PCoIP server in these initial requests led to an intermittent problem described in bug ID457865-1. The fix for this bug included the behavior of what you/the customer is reporting now where bigip tells the PCoIP server to make these initial UDP to port 0 and so you will see the PCoIP server sending bigip initial UDP packets (src port 4172, dst port 0) and bigip responding with ICMP unreachable. The bigip has no problems with port 0. This behavior cannot be changed.”

The ENE on the case states:

"The overall issue stems from PCoIP client/server behavior, they simultaneously start sending each other UDP packets when switching from TCP to UDP (likely for overcoming NATs) and once one of them reaches out to another, they agree on ports to use."

But in my case, I'm not using NAT... and the latter is not happening regardless... and therefore a port is not agreed upon and the PCoIP connection times out.

More to come...