Hi,

I am in the process of trying to create a remote probe on one of the remote sites and then run a bandwith monitor on a second nic card to find top talkers over an mpls link (switch has been configured correctly)

The remote probe seems to be working, and is displayed in the main Admin console, since then i have created a packet sniffer sensor (header and content) but the data being displayed seems to only be relevant to a 192 and 169 networks - not the core ip addressing. I have checked that the network card has port mirroring configured correctly using wireshark and this displays the expected traffic - any ideas?

Tim

Article Comments

Dear Tim,

which exact version of PRTG are you running?

best regards


Nov, 2011 - Permalink

Hi Torsten,

The version is •PRTG Network Monitor 8.4.2.2357

Thanks

Tim


Nov, 2011 - Permalink

Are there any filters set on the Packet Sniffer Sensors?


Nov, 2011 - Permalink

Hi Torsten,

No there has not been any configured, on the setting tab - include and exclude has been left blank and the interface that we are expecting to monitor is ticked.


Nov, 2011 - Permalink

One thing I have noticed which I hope is not an issue - I have not assigned the interface an IP address as it is purely for monitoring. I have tried with the TCP/IP stack installed and without but each time the same issue is apparent


Nov, 2011 - Permalink

We can't say for sure if not having an IP is an issue. Could you try verifying this by applying an IP? Furthermore, would an upgrade to PRTG 9 be an option (as PRTG 9 uses Wiresharks Winpcap-engine)? You can also enable the Stream-Logging and check the log then for the traffic but this might only show the same as in the sensor results.


Nov, 2011 - Permalink