For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Accessing TCP Options from iRules

I’ve written several articles on the TCP profile and enjoy digging into TCP.  It’s a beast, and I am constantly re-learning the inner workings.  Still etched in my visual memory map, however, is the ...
Published Mar 25, 2011
Version 1.0
application delivery
BIG-IP
dev
devops
iRules
news
tech tip
JRahm's avatar
Icon for Admin rankAdmin
Christ Follower, Husband, Father, Technologist. I love community and I especially love THIS community. My background is networking, but I've dabbled in all the F5 iStuff, I'm a recovering Perl guy, and am very much a python enthusiast. Learning alongside all of you in this accelerating industry toward modern apps and architectures.
View Profile
JRahm's avatar
Icon for Admin rankAdmin
Christ Follower, Husband, Father, Technologist. I love community and I especially love THIS community. My background is networking, but I've dabbled in all the F5 iStuff, I'm a recovering Perl guy, and am very much a python enthusiast. Learning alongside all of you in this accelerating industry toward modern apps and architectures.
View Profile
Joel_Smith's avatar
Joel_Smith
Icon for Altostratus rankAltostratus
Jun 25, 2020

Jason,

 

Shouldn't the line:

 

if { [catch {IP::addr $x mask 255.255.255.255}] } {

 

Be:

 

if { [catch {IP::addr $optaddr mask 255.255.255.255}] } {

 

Also, does [IP::addr parse] throw an exception if the bytearray doesn't contain a valid IP address?

 

If so, then the catch block around the [IP:addr] on the next line should be moved up a line.

 

Joel