[Oisf-devel] curious ip proto break fast.log
Anoop Saldanha
anoopsaldanha at gmail.com
Sun Mar 10 06:46:04 UTC 2013
On Sun, Mar 10, 2013 at 2:42 AM, rmkml <rmkml at yahoo.fr> wrote:
> 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?
>
Can you open a ticket on this?
--
Anoop Saldanha
More information about the Oisf-devel
mailing list