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

Icon for Admin rank

Admin

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.

Icon for Admin rank

Admin

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.

Icon for SIRT rank

SIRT

Jun 25, 2020

Yes, you're correct:

---

} else {

set optaddr [IP::addr parse -ipv4 $opt28 1]

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

log local0. "$optaddr is not a valid address"

snat automap

---

That $x should be $optaddr in this example.

It isn't clear from https://clouddocs.f5.com/api/irules/IP__addr.html if it throws an exception, and I'm not sure offhand - probably something to check.