Wireshark-bugs: [Wireshark-bugs] [Bug 9996] IPv6 Next Header is Unknown yet Wireshark tries pars
Comment # 12
on bug 9996
from boaz.brickner@gmail.com
(In reply to comment #11)
> (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.
ok.
I think Wireshark should assume an unknown protocol should be the payload of
the IPv6 layer.
It is much more likely that an unknown protocol would be a layer over IPv6 than
an extension header, since there are far fewer extension headers than payloads.
Makes sense?
You are receiving this mail because:
- You are watching all bug changes.
