Project

General

Profile

Actions
Copy link

Bug #7477

closed

Log data does not match documented schema

Added by Ted Lum over 7 years ago. Updated over 7 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
Logging
Target version:
-
Start date:
04/17/2017
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.2.x
Affected Architecture:

Description

RE: https://doc.pfsense.org/index.php/Filter_Log_Format_for_pfSense_2.2

For example:

sequence-number="2855194778:2855195413"

2017-03-19T09:00:15-04:00 fw1srvp01 filterlog: 9,16777216,,1000000103,lagg0_vlan5,match,block,in,4,0x0,,64,37427,0,DF,6,tcp,687,192.168.2.16,172.217.11.40,54791,443,635,PA,2855194778:2855195413,1862930181,291,,nop;nop;TS

does not validate against:

<sequence-number> ::= <integer> -- TCP Sequence ID

which I have defined as:

<xs:simpleType name="tcp-sequence-number">
<xs:annotation>
<xs:documentation>TCP Sequence ID</xs:documentation>
</xs:annotation>
<xs:restriction base="xs:unsignedInt">
<xs:minInclusive value="0"/>
<xs:maxInclusive value="4294967295"/>
</xs:restriction>
</xs:simpleType>

I'm guessing that complex type was intentional, but the documented schema does not reflect what's being generated.

Actions
Copy link
 #1

Updated by Jim Pingle over 7 years ago

  • Status changed from New to Rejected

As stated on that page, the BNF is not complete. It isn't a specification, it is a rough guide.

Actions
Copy link

Also available in: Atom PDF