Wireshark-bugs: [Wireshark-bugs] [Bug 9996] IPv6 Next Header is Unknown yet Wireshark tries pars
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Thu, 31 Jul 2014 05:28:35 +0000

changed bug 9996

What Removed Added
CC   anish@chelsio.com

Comment # 11 on bug 9996 from 
(In reply to comment #10)
> (In reply to comment #9)
> > From code (packet-ipv6.c)
> > 
> >         switch (nxt) {
> > [...]
> >         default:
> >             /* Since we did not recognize this IPv6 option, check
> >              * whether it is a known protocol. If not, then it
> >              * is an unknown IPv6 option
> >              */
> 
> Assuming this talks about IPv6 extension headers and not about IPv6 options,
> why would we assume an unknown next protocol is an unknown IPv6 extension
> header?

Boaz, this is just a feature of code right now, where an unknown next is
assumed to be an unknown header. I don't know the initial reasoning for this,
but if you can explain a more correct approach to this, I could fix this for
you.

You are receiving this mail because:
  • You are watching all bug changes.