Project

General

Profile

Actions

Bug #771

closed

curious ip proto break fast.log

Added by rmkml rmkml almost 11 years ago. Updated almost 11 years ago.

Status:
Closed
Priority:
Normal
Target version:
Affected Versions:
Effort:
Difficulty:
Label:

Description

Hi,

I have a curious "break" on fast.log with theses lines on /etc/protocols :
sscopmce 128 SSCOPMCE
iplt 129 IPLT
udplite 136 UDPLite
mpls-in-ip 137 MPLS-in-IP
(no comment on theses lines)

because cause this fast.log:
03/02/2009-10:23:58.161246 [**] [1:1627:3] BAD-TRAFFIC Unassigned/Reserved IP protocol [**] [Classification: Detection of a non-standard protocol or event] [Priority: 2] {MPLS-in-IP
} 172.20.2.51:0 -> 172.20.0.90:0

03/02/2009-10:23:58.239356 [**] [1:92583:5] BAD TRAFFIC Non-Standard IP protocol Crusoe [**] [Classification: Detection of a non-standard protocol or event] [Priority: 2] {IPLT
} 172.20.2.51:0 -> 172.20.0.101:0

03/02/2009-10:23:58.239063 [**] [1:1627:3] BAD-TRAFFIC Unassigned/Reserved IP protocol [**] [Classification: Detection of a non-standard protocol or event] [Priority: 2] {UDPLite
} 172.20.2.51:0 -> 172.20.0.101:0

03/02/2009-10:23:58.239464 [**] [1:92583:5] BAD TRAFFIC Non-Standard IP protocol Crusoe [**] [Classification: Detection of a non-standard protocol or event] [Priority: 2] {SSCOPMCE
} 172.20.2.51:0 -> 172.20.0.101:0

Yes, "...{UDPLite" are not on same line than "} 172...".

Do you known this pb please?
Regards
Rmkml


Subtasks 1 (0 open1 closed)

Bug #773: curious ip proto break fast.log (1.4.x)ClosedAnoop Saldanha03/12/2013Actions
Actions #1

Updated by Anoop Saldanha almost 11 years ago

  • Assignee set to Anoop Saldanha
Actions #2

Updated by Anoop Saldanha almost 11 years ago

  • Target version set to 1.4.2
Actions #4

Updated by Victor Julien almost 11 years ago

  • Status changed from New to Closed
  • Target version changed from 1.4.2 to 2.0beta1

Merged pr/315, thanks.

Actions

Also available in: Atom PDF