Hi,
We have been running our sFlow capture a few days now and it does not seem to be analyzing protocols. "Top Protocols" all return as "Other"
Article Comments
Attention: This article is a record of a conversation with the Paessler support team. The information in this conversation is not updated to preserve the historical record. As a result, some of the information or recommendations in this conversation might be out of date.
Hi,
The "Other" channel sums up the traffic of network packets that can not be allocated to one of the existing filter channel settings for the flow Sensors. You can get more detailed information by creating new channels for the flow and Packet Sniffer sensors: https://helpdesk.paessler.com/en/support/solutions/articles/76000063052
Have a look here for the correct syntax and here for a list of the predefined filter rules.
Please consider that if you follow the knowledge base article 60203, all flow and Packet Sniffer sensors will be affected by the adjustments of the flowrules.osr file. If you want to avoid this, use the flow custom sensors to create your own definitions.
Best regards
Mar, 2015 - Permalink
Hi,
The "Other" channel sums up the traffic of network packets that can not be allocated to one of the existing filter channel settings for the flow Sensors. You can get more detailed information by creating new channels for the flow and Packet Sniffer sensors: https://helpdesk.paessler.com/en/support/solutions/articles/76000063052
Have a look here for the correct syntax and here for a list of the predefined filter rules.
Please consider that if you follow the knowledge base article 60203, all flow and Packet Sniffer sensors will be affected by the adjustments of the flowrules.osr file. If you want to avoid this, use the flow custom sensors to create your own definitions.
Best regards
Mar, 2015 - Permalink