I have just checked in a change that will again dissect CLDAP RPC responses.
Please test with latest SVN.
Also, please comment on how to prettify the dissection and presentation of LDAP.
The change from an incomplete subset handwritten dissector to a
complete autogenerated full dissector is very intrusive and changes a
lot. But this is the best opportunity to do this change since there
are several months (post 1.0 at the earliest) before the new ldap
dissector will hit normal not-compiling-svn-yourself users and buying
us lots of time to refine it.
LDAP had to be redone since it was the last big dissector left using
the old depreciated asn1 api.
sorry for the regression.
On 5/3/06, ronnie sahlberg <ronniesahlberg@xxxxxxxxx> wrote:
Hi,
The LDAP dissector was recently replaced by a new one generated by by the
ASN1 compiler ASN2ETH.
As a result some parts of LDAP (including CLDAP) will have temporary
regression in the SVN branch.
The CLDAP breakage will be addressed shortly.
On 5/3/06, Xiaoguang Liu <syslxg@xxxxxxxxx> wrote:
>
> hi,
>
> I just download 1.1-svn 18079 for fc4 and windows. I found one of my
color
> filter is no longer valid. it is "mscldap.netlogon.type".
> And I also found the CLDAP packets between windows client and DC are not
> pasered as before. Here I attacded a sample trace the display result.
>
>
> No. Time Source Destination
> Protocol Info
> 2 15:27:00.527361 157.60.73.105 157.60.72.125
> CLDAP searchResEntry(1) searchResDone(1) [1 result]
>
> Frame 2 (218 bytes on wire, 218 bytes captured)
> Ethernet II, Src: Microsof_e0:af:8c (00:03:ff:e0:af:8c), Dst:
> Microsof_d9:af:8c (00:03:ff:d9:af:8c)
> Internet Protocol, Src: 157.60.73.105 (157.60.73.105), Dst:
157.60.72.125(
> 157.60.72.125)
> User Datagram Protocol, Src Port: 389 (389), Dst Port: 1029 (1029)
> Lightweight-Directory-Access-Protocol
> LDAPMessage searchResEntry(1) [1 result]
> messageID: 1
> protocolOp: searchResEntry (4)
> searchResEntry
> attributes: 1 item
> Item
> type: netlogon
> vals: 1 item
> Item:
> 18000000FC01000002A0BED71554BC4487E47F1B9E6E17DC...
> Response To: 1
> Time: 0.005610000 seconds
> LDAPMessage searchResDone(1) [1 result]
> messageID: 1
> protocolOp: searchResDone (5)
> searchResDone
> Response To: 1 Time: 0.005610000 seconds
>
> ---
>
> the netlogon atribute is parsered very well before. now ethereal only
> display a long binary string. is it a design change or a bug? If it is
> intended to be so, can I know why? I really need this work to help my
> trouble shoot dc locating issue in windows domain.
>
> _______________________________________________
> Ethereal-users mailing list
> Ethereal-users@xxxxxxxxxxxx
> http://www.ethereal.com/mailman/listinfo/ethereal-users
>
>
>
>