Wireshark · Wireshark-bugs: [Wireshark-bugs] [Bug 9252] WCCP fix hash buckets assignment info decoding

[bugzilla-daemon@xxxxxxxxxxxxx]

Comment # 3 on bug 9252 from Peter Van Eynde

(In reply to comment #2)
> http://tools.ietf.org/id/draft-wilson-wrec-wccp-v2-01.txt, the Bucket
> encoding is:
> ...
>        0 1 2 3 4 5 6 7
>       +-+-+-+-+-+-+-+-+
>       | Index       |A|
>       +-+-+-+-+-+-+-+-+

This is using the confusing 'MSB at the right' notation. As does the rest of
the file :(. Even the new standard at
http://tools.ietf.org/id/draft-mclaggan-wccp-v2rev1-00.txt is using that
notation.

I keep running into this, but take for example:

3.12.1
...
   The Redirect Header is defined as follows:

    0                   1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |T|A|U|Reserved |  Service ID   |  Alt Bucket   |Primary Bucket |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+


The T bit is 0x01 decoded using:

       { &hf_gre_wccp_dynamic_service,
          { "Dynamic Service", "gre.wccp.dynamic_service",
           FT_BOOLEAN, 8, TFS(&gre_wccp_dynamic_service_val), 0x01,
          NULL, HFILL }

Not using 0x8000 0000...

I also checked the current IOS code just to be certain ;)

Peter

---

      You are receiving this mail because:

• You are watching all bug changes.