Changing destination pool TCP port via iRules

Of course it works in CLIENT_ACCEPTED but that doesn't particularly matter if you want to make load balancing decisions in CLIENT_DATA. We are looking for the ability to read the first message from the socket and then to change the destination port while still letting the F5 select which node to load balance to.

 

 

If the client connects on the virtual server at port 2010...

 

 

In CLIENT_DATA you can do this:

 

 

pool mypool member 192.168.1.50:2001

 

 

The problem is that there is no way to change the destination port without selecting the pool member as well which means if .50 is down then the user is unable to connect even if there is another node available in the pool.

 

 

What would work perfectly is a semantic like:

 

 

pool mypool port 2001

 

-or-

 

pool mypool member :2001

 

 

Unfortunately that is not supported.