This is our old Q&A Site. Please post any new questions and answers at ask.wireshark.org.

Yes, this is another WireShark Crash Question....

So, I've used Wireshark in the following OS's:

  • Win7 x64
  • Server 2008r2 (x64)
  • Server 2012r2 (x64)

I'm testing software in an environment consisting of multiple instances of the aforementioned OS's.

My filter is ip.addr == 192.168.1.1.

(I can't give the actual IP for security purposes).

I have an SNMP Trap set up on 192.168.1.1 and am using wireshark to make sure errors are sent to the Trap.

When I have WireShark running, it records the SNMP's just fine. For no reason, it randomly crashes. It doesn't matter which machine I'm using it on.

I'm using WireShark 1.10.3 (64-bit).

Any thoughts on this?

asked 20 Nov '13, 09:43

xenoranger's gravatar image

xenoranger
11112
accept rate: 0%


That's a display filter so Wireshark will be capturing and recording all the other traffic received by the NIC (presumably you're running the capture in promiscuous mode) and is likely to be running out of memory. See the OutOfMemory page on the wiki for more info.

Try setting a capture filter (in the Capture Options dialog) of host 192.168.1.1 to restrict the raffic that Wireshark actually receives.

permanent link

answered 20 Nov '13, 10:10

grahamb's gravatar image

grahamb ♦
19.8k330206
accept rate: 22%

Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

By RSS:

Answers

Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text](http://url.com/ "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Question tags:

×84
×12
×7
×5

question asked: 20 Nov '13, 09:43

question was seen: 3,866 times

last updated: 20 Nov '13, 11:47

p​o​w​e​r​e​d by O​S​Q​A