Malformed IP packet used in code example
Bug #1178441 reported by
Didier Barvaux
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | ||
|---|---|---|---|---|---|---|
| rohc | Status tracked in Rohc-main | |||||
| 1.3.x |
Invalid
|
Undecided
|
Didier Barvaux | |||
| 1.4.x |
Invalid
|
Undecided
|
Didier Barvaux | |||
| Rohc-1.5.x |
Fix Released
|
Low
|
Didier Barvaux | |||
| Rohc-main |
Fix Released
|
Low
|
Didier Barvaux | |||
Bug Description
There is something wrong with the example application. It should compress the IP packet with the best profile that was enabled, ie. the IP-only profile.
That's not the case because a mistake was done when building the fake IP packet. The Total Length field is in Host Byte Order instead of Network Byte Order. The ROHC library therefore detects that the packet is not a valid IP packet. In consequence it chooses the Uncompressed profile instead of the IP-only profile.
Problem reported by Wei Wang. Thank to him.
Revision history for this message
| Didier Barvaux (didier-barvaux) wrote | #1 |
| tags: | added: example |
| description: | updated |
Revision history for this message
| Didier Barvaux (didier-barvaux) wrote | #2 |
To post a comment you must log in.
Fixed in branch 1.5.x.
See http://