Actions
Bug #327
closedIPv6 fast.log displays wrong protocol
Affected Versions:
Effort:
Difficulty:
Label:
Description
09/15/2011-07:30:51.902209 [**] [1:2013504:3] ET POLICY GNU/Linux APT User-Agent Outbound likely related to package management [**] [Classification: Potential Corporate Privacy Violation] [Priority: 1] {IP} 2001:0980:32b2:0002:0219:d2ff:fe97:1fd6:53085 -> 2001:07b8:0003:0037:0000:0000:0021:0002:80
the protocol field here list "{IP}", but this should have been "{TCP}".
Files
Updated by Victor Julien about 13 years ago
- Due date set to 10/31/2011
- Target version changed from 1.1beta3 to 1.1rc1
Updated by Victor Julien about 13 years ago
- Priority changed from Normal to High
Updated by Eileen Donlon about 13 years ago
- File 0001-set-layer4-protocol-when-no-ipv6-extension-headers.patch 0001-set-layer4-protocol-when-no-ipv6-extension-headers.patch added
- % Done changed from 0 to 100
Fixed bugs where layer 4 protocol was not set if there were no ipv6 extension headers. This resulted in fast.log showing the default protocol, which is ip.
Updated by Victor Julien about 13 years ago
Patch applied, thanks Eileen!
Keeping the ticket open pending investigations of related & similar issues.
Updated by Victor Julien about 13 years ago
- Status changed from Assigned to Closed
I see you opened a new ticket so closing this one. Thanks!
Actions