What filter rules can be used for custom Packet Sniffing or xFlow (NetFlow/sFlow/jFlow) sensors?

Votes:

0

Your Vote:

Up

Down

What is the filter rule syntax? What xFlow (NetFlow/sFlow) filter parameters are supported by PRTG?

cisco custom-sensor filter include jflow netflow packet-sniffing sensor sflow xflow

Created on Feb 3, 2010 2:34:58 PM by  Jens Rupp [Paessler Support] (609) 3 1

Last change on Mar 31, 2011 9:36:25 AM by  Daniel Zobel [Paessler Support] (19,813) 3 3



1 Reply

Accepted Answer

Votes:

0

Your Vote:

Up

Down

This article applies to PRTG Network Monitor 7 or 8

Filter Rules for Custom Packet Sniffing or Netflow Sensors Under PRTG Network Monitor 7 or 8

Note: To view this information for PRTG Network Monitor 9, please see PRTG 9 Manual: Filter Rules for xFlow and Packet Sniffer Sensors.


Filter rules are used for the include, exclude and channel definition fields of custom packet sniffer and netflow sensors.

Filter rules are based on the following format:

field[filter]

Valid fields are:

  • IP
  • Port
  • SourceIP
  • SourcePort
  • DestinationIP
  • DestinationPort
  • Protocol (values: TCP, UDP, ICMP, OSPFIGP or any number)
  • ToS

Additional Sniffer Fields:

  • MAC
  • SourceMAC
  • DestinationMAC
  • EtherType (values IPV4, ARP,RARP,APPLE, AARP,IPV6 ,IPXold, IPX or any number)

Additional NetFlow v5 / jFlow fields:

  • Interface
  • ASI
  • InboundInterface
  • OutboundInterface
  • SourceASI
  • DestinationASI

Additional NetFlow v9 fields:

  • Interface
  • ASI
  • InboundInterface
  • OutboundInterface
  • SourceASI
  • DestinationASI
  • MAC
  • SourceMAC
  • DestinationMAC
  • Mask
  • SourceMask
  • DestinationMask
    • Note: 'Masks' represent subnet masks in the form of a single number ('number of contiguous bits')
  • NextHop (IP address)
  • VLAN
  • SourceVLAN
  • DestinationVLAN
    • Note: 'VLANs' represent a VLAN identifier

Additional sFlow fields:

  • Interface
  • InboundInterface
  • OutboundInterface
  • MAC
  • SourceMAC
  • DestinationMAC

Data Formats:

  • IP fields support wildcards (*), range (10-20) and hostmask ( /10, /255.255.0.0) syntax.
  • Number fields support range (80-88) syntax.
  • Protocol and EtherType fields support numbers and a list of predefined constants.

Samples:

SourceIP[10.0.0.1]
SourceIP[10.*.*.*]
SourceIP[10.0.0.0/10]
DestinationIP[10.0.0.120-130]
DestinationPort[80-88]
Protocol[UDP]

Complex expressions can be created using parentheses and and/or/not:

Protocol[TCP] and not (DestinationIP[10.0.0.1] or SourceIP[10.0.0.120-130])

See also

Created on Feb 3, 2010 2:35:17 PM by  Jens Rupp [Paessler Support] (609) 3 1

Last change on Sep 15, 2011 9:58:52 AM by  Daniel Zobel [Paessler Support] (19,813) 3 3



Please log in or register to enter your reply.


Disclaimer: The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.

PRTG
Network Monitor
Intuitive to Use.
Easy to manage.

150.000 administrators have chosen PRTG to monitor their network. Find out how you can reduce cost, increase QoS and ease planning, as well.

Visit
www.paessler.com

What is this?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general. You are invited to get involved by asking and answering questions!

Learn more

Top Tags


View all Tags