Mutator LINK::qos and IP::tos syntax

You should simply need to add the value. eg:

LINK::qos 3

You still have CLIENT_ACCEPTED, LB_SELECTED, SERVER_CONNECTED, etc.

I'll give try in the morning, didn't see that take. Also, I need it applied in the return path to the client, not on the server side.

Setting the link qos or IP tos on the clientside will only set it for egress on that side. You can alternatively specify "clientside" or "serverside" on the command to further indicate the side it should effect. eg:

LINK::qos 3 serverside

will set it for the serverside egress traffic regardless of the event it is done in. In your example, to set the clientside egress qos, you can either set it in CLIENT_ACCEPTED or another clientside event or use "LINK::qos 3 clientside" in a serverside event.

HTH!

I am getting the following error:

01070151:3: Rule [Firewall_Select-rule] error:

line 5: [wrong args] [LINK::qos 3 clientside]

On this rule (logging lines removed):

when CLIENT_ACCEPTED {
   if { [IP::addr [IP::remote_addr] equals "10.10.1.0/24"] } {
      LINK::qos 3 clientside
      use pool Firewall_Select-pool member 10.29.10.5
   } elseif { [IP::addr [IP::remote_addr] equals "10.10.2.0/24"] } {
      use pool Firewall_Select-pool member 10.29.20.5
   } elseif { [IP::addr [IP::remote_addr] equals "10.10.3.0/24"] } {
      use pool Firewall_Select-pool member 10.29.30.5
   } else { 
      discard
      log "Discarding packets from [IP::remote_addr]"
   }
}

Thanks!

Jason

I think the clientside specifier goes before the value. For example, LINK::qos clientside 3.

Uh, I don't think so:

 

 

Oct 4 13:54:50 tmm tmm[29897]: 01220001:3: TCL error: Rule Firewall_Select-rule - expected integer but got "clientside" while executing "LINK::qos clientside 3"

 

 

I don't get any errors when syntax is (adding serverside/clientside doesn't seem to change anything)

 

 

IP::tos 16

 

or

 

LINK::qos 3

 

 

But it is never anything but zero:

 

 

setting IP::tos to 16

 

Oct 4 13:59:24 tmm tmm[29897]: 01220002:6: Rule Firewall_Select-rule : Client 10.10.1.1 using eBiz-Firewall, DSCP is 0

 

 

setting LINK::qos to 3

 

Oct 4 13:58:05 tmm tmm[29897]: 01220002:6: Rule Firewall_Select-rule : Client 10.10.1.1 using eBiz-Firewall, COS is 0

 

What are you using to print the DSCP and COS above?

 

 

When you use IP::tos or LINK::qos without a value they return what the ingress TOS or QOS was. When you specify the value, they set the egress TOS or QOS - so the only way to verify it is actually getting set correctly would be to use tcpdump (well for the TOS anyway, as I'm not sure tcpdump will show the QOS even with the -e flag, maybe ethereal will).

 

 

BTW, the clientside/serverside options were added in either 9.0.4 or 9.0.5 (can't remember for sure).

 

 

Do you know of any working examples of setting this? Nothing I've tried makes a difference. tcpdump shows 0 in the dscp offset (viewed in ethereal) no matter what I try. Thanks.

 

 

Jason

Case C229092 created this morning. Thanks.

I have a very large project whose main requirement is having the ability to direct traffic based on the entire DSCP value. I just want to confirmation this functionality exists in BIGIP and there will not be any issues with directing traffic based on the DSCP value. Based on this post it appears this is supported but I'd just like confirmation.

 

 

I did see the post about LINK::qos being broken so I will address that via a hotfix or the general release when it's ready.