weird iRule behaviour UDP/TCP profiles data leak?

Hi nitass,

 

 

The idea was to create an iRule which you can hand to a customer to obtain some visibility about his virtual server and its connections, regardless of its configuration.

 

I'm looking for an explanation why something in the UDP:: struct would be filled out when there is no udp profile attached to the virtual server.

 

Code-wise I can imagine it is just a reference to an address in memory containing the ports and that this address is the same for the UDP and TCP structs. What I don't get is why the UDP struct is initialized even though there is no UDP profile attached to the virtual server. This would lead me to conclude that unneccesary amounts (however small) of memory are being used for never-used variables. So I was wondering if I could get a confirmation on this, or even better, an explanation of why I'm wrong if I'm wrong. :)

 

 

I think that it is the goal of the iRule editor (on F5 or the standalone program) to not let you enter iRules that are invalid. So when I manage to enter something invalid anyways (like referencing UDP:: when there is no UDP profile - something the iRule editor aptly says I cannot do), the last thing I expect to see is that it is actually working, even though it is not a valid statement.

 

 

 

Kind regards,

 

 

Thomas