Hi,
If NCP fragmentation works similar to ipv4 fragmentation then it should be
quite easy
for someone knowing how NCP fragmentation works to add the appropriate calls
to reassemble.c .
See the diff's for packet-ip.c or packet-ipv6.c when reassembly was added
for examples.
I dont know how NCP fragmentation works and I dont have a protocol spec for
NCP so I cant
do that work. Someone else on the list might do it though.
----- Original Message -----
From: Pete
To: Gilbert Ramirez
Cc: Guy Harris ; ethereal-dev@xxxxxxxxxxxx
Sent: Friday, June 29, 2001 1:45 PM
Subject: Re: [Ethereal-dev] NCP Packets
Thanks for the help on this. I compiled the latest cvs code this afternoon
and was able to load the captures and immediately noticed a large
improvement. Unfortunately, I think the information I really need is in the
fragmented requests and I hope the infrastructure will be able to handle the
fragments in the future. They are IPX/SPX packets and I am not sure they use
the same start, offset, end sequence that IP does.
We are still having the login problems and I will be getting more traces
tomorrow. If you want them I will send them to the list.
Thanks again,
Pete
Your trace has fragmented NDS requests in it (NCP code 0x6802).It will be
interesting to see what Ethereal can do withthese fragments in the future,
i.e., will the infrastructurewe put in place be able to unfragment the NDS
requests????
The current fragment reassembly code in "reassemble.c" should be able
tohandle any form of fragment reassembly that's similar to IPv4's; bothIPv6
and CLNP fragmentation are similar, so it currently handles IPv4,IPv6, and
CLNP.If NDS's fragmentation is similar (meaning each fragment has: a
starting offset within the fragmented packet; a length; a "this is the last
fragment" Boolean)it should be abel to use it.