[CONTROLLER-807] Payload in non-first fragment of IPv4 packet should not be deserialized. Created: 11/Sep/14 Updated: 19/Oct/17 Resolved: 05/May/15 |
|
| Status: | Resolved |
| Project: | controller |
| Component/s: | adsal |
| Affects Version/s: | Helium |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Shigeru Yasuda | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: Linux |
||
| External issue ID: | 1808 |
| Description |
|
When AD-SAL IPv4 class deserializes a raw packet, it deserializes the payload If a non-first fragment of an ICMP packet is deserialized as ICMP header, 1. ICMP header is not present in non-first fragments of an ICMP packet. 2. If a deserialized ICMP instance is serialized again, ICMP class always That is why IPv4 class should not set a protocol class to "payloadClass" field |
| Comments |
| Comment by Shigeru Yasuda [ 11/Sep/14 ] |
|
I verified that the following patch fixed this issue. |
| Comment by Carol Sanders [ 05/May/15 ] |
|
This bug is part of the project to Move all ADSAL associated component bugs to ADSAL. |