TCP Flags set bug?



  • I am about to set SYN packet high priority,detail is in TCP Flags, SYN set, ACK cleared, others don't care.
    After apply settings, I found the rules added by webui is,
    pass in on rl0 proto tcp all flags S/FSRPAU keep state tag qLANacks tagged unshaped
    pass out on vr0 proto tcp all flags S/FSRPAU keep state tag qWANacks tagged qLANacks

    S/FSRPAU, why not S/SA ? Is it a bug?



  • @hshh:

    I am about to set SYN packet high priority,detail is in TCP Flags, SYN set, ACK cleared, others don't care.
    After apply settings, I found the rules added by webui is,
    pass in on rl0 proto tcp all flags S/FSRPAU keep state tag qLANacks tagged unshaped
    pass out on vr0 proto tcp all flags S/FSRPAU keep state tag qWANacks tagged qLANacks

    S/FSRPAU, why not S/SA ? Is it a bug?

    flags <a>/ | / This rule only applies to TCP packets that have the flags</a> ****<a>set
              out of set **.  Flags not specified in **are ignored.  The flags
              are: (F)IN, (S)YN, (R)ST, (P)USH, (A)CK, (U)RG, (E)CE, and C(W)R.

    flags S/S  Flag SYN is set.  The other flags are ignored.

    flags S/SA  Out of SYN and ACK, exactly SYN may be set.  SYN,
                          SYN+PSH and SYN+RST match, but SYN+ACK, ACK and ACK+RST
                          do not.  This is more restrictive than the previous ex-
                          ample.

    flags /SFRA
                          If the first set is not specified, it defaults to none.
                          All of SYN, FIN, RST and ACK must be unset.</a>

    <a>–Bill**</a>**


Locked