Maybe that's much more traffic than you expect. There are a few packets per second, and bursts of maybe 20 packets per second when we collect data every 5 - 10 minutes.ĭid you check the RDP feedback problem I mentioned above. I'm not logging tremendous amount of traffic. General soultion: Use dumpcap instead of Wireshark to capture traffic (see the links above). See the many other questions about RAM problems and the solutions. Same, if you use any other remote Desktop solution. The RDP screen updates will create a feed-back loop like this: Wireshark screen gets updated due to new packets, this creates RDP traffic (screen update), which creates new packets, which creates Wireshark screen updates, and so on. 2 GByte is not much, especially if you connect via RDP (through the VPN tunnel) and don't add a capture filter to ignore the RDP traffic (Capture filter: not port 3389). generally wireshark runs for about 15 - 45 minutes before crashing. It is at a remote location, I VPN into it.
0 Comments
Leave a Reply. |