|
Bugzilla – Full Text Bug Listing |
| Summary: | m_type not set for Ipv6OptionRouterAlertHeader in file 'ipv6-option-header.cc' | ||
|---|---|---|---|
| Product: | ns-3 | Reporter: | francisco javier sanchez-roselly <franciscojavier.sanchezroselly> |
| Component: | ipv6 | Assignee: | Tommaso Pecorella <tommaso.pecorella> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | ns-bugs |
| Priority: | P5 | ||
| Version: | ns-3-dev | ||
| Hardware: | All | ||
| OS: | All | ||
| Attachments: | packed diff file solving the bug | ||
Fixed in changeset 9761 - 32e15e895529 |
Created attachment 1581 [details] packed diff file solving the bug In file 'ipv6-option-header.cc', for Ipv6OptionRouterAlertHeader constructor, m_type is not set, i.e. there is no call to SetType() method. This implies that the mentioned option has the same m_type as Pad1. A sample application will be provided to reproduce this bug. An IPv6 packet containing a Router Alert Option Header is not properly parsed in Wireshark. Router Alert Option is decoded as Pad1 Option; Headers and/or Payload following get misaligned. Router Alert Option must have its type set as 5 in Ipv6OptionRouterAlertHeader::Ipv6OptionRouterAlertHeader() included in ipv6-option-header.cc Changeset 9715:90e0789f7951 Build 2013-04-25 on Linux 3.7.9-gentoo