Thanks Jeff - I will look into this.
Fred
> -----Original Message-----
> From: wireshark-users-bounces@xxxxxxxxxxxxx [mailto:wireshark-users-bounces@xxxxxxxxxxxxx] On Behalf
> Of Jeff Morriss
> Sent: Thursday, June 12, 2014 5:57 PM
> To: Community support list for Wireshark
> Subject: Re: [Wireshark-users] aero
>
> On 06/12/2014 06:45 PM, Templin, Fred L wrote:
> > Hi,
> >
> > Wireshark currently correctly recognizes UDP port 8060 as "aero" but
> > it does not interpret the data immediately following the UDP header.
> > The data following the UDP header is simply an IPv6 packet (beginning
> > with the IPv6 header), which should be very easy to interpret using
> > existing wireshark protocol dissectors.
> >
> > Can wireshark be updated to interpret and print the IPv6 packet that
> > immediately follows the aero UDP header?
> >
> > Note that the correct reference for this is 'draft-templin-aerolink',
> > which obsoletes RFC6706:
> >
> > https://datatracker.ietf.org/doc/draft-templin-aerolink/
>
> Probably. What would help would be:
>
> 1) An enhancement request filed on https://bugs.wireshark.org
> 2) ... with an attached sample capture for testing.
>
> Of course a patch (submitted to Gerrit) would make it even more likely. :-)
>
> ___________________________________________________________________________
> Sent via: Wireshark-users mailing list <wireshark-users@xxxxxxxxxxxxx>
> Archives: http://www.wireshark.org/lists/wireshark-users
> Unsubscribe: https://wireshark.org/mailman/options/wireshark-users
> mailto:wireshark-users-request@xxxxxxxxxxxxx?subject=unsubscribe