Forum Discussion
ClientSSL_clientCert variables not avail in HTTP_Request
Setting certData as a global variable does work. It is my understanding that local variables are shared between the different events for a given virtual. Is this not the case?
Is the CLIENTSSL_CLIENTCERT event in a different namespace?
If I use global variables are they only available with-in the given virtual or "globally" across the device?
Thanks.
Anthony
If SNAT is not involved, filtering the packet capture as below will give you the picture of communication either side.
ip.src == SRC IP and ip.dst == VS_IP
ip.src == SRC IP and ip.dst == POOL_Member_IP
Look for communication for the destination port you are interested in.
Since it is STD VS, 3 way handshake will first happen between client and F5 and then F5 will initiate a 3 way handshake with server
you could try source port, it isn't 100% but it might work. also if there is not SNAT the source IP is the same from the client to the F5 and from the F5 to the pool member. so why not test from a client that you further don't use here?
depending on the VIP and traffic type you could also just send specific data. of course TCP 3way handshake has to happen first for that.
and you have to consider it just doesn't work. if you don't see it, perhaps the F5 isn't configured correctly. you have check the config on it or can't you see that either?
Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com