Loading...
Loading...
The result returned from the "IP::tos" iRule in the FLOW_INIT event is always zero (Normal-Service), even when the actual packet from the client has TOS set to a different value.
Cannot make the correct service or routing decision at FLOW_INIT, based on the TOS provided in the initial packet in the flow.
Calling the IP::tos iRule from within a FLOW_INIT event handler for a virtual server always returns zero. The following iRule demonstrates the issue: when FLOW_INIT { log local0. "TOS from [IP::client_addr] is [IP::tos]" } when CLIENT_ACCEPTED { log local0. "TOS from [IP::client_addr] is [IP::tos]" } The logs will show that the IP::tos value is always 0 at FLOW_INIT, and always correct at CLIENT_ACCEPTED.
None.
The IP::tos iRule now correctly returns the TOS value from the initial client packet initiating a flow in the FLOW_INIT event handler.
Click on a version to see all relevant bugs
F5 Integration
Learn more about where this data comes from
BugZero Plan
Streamline upgrades with automated vendor bug scrubs
BugZero Prevent
Wish you caught this bug sooner? Get proactive today.