2021-03-03 20:51:34 +0000 | commented question | WS is non-responsive when capturing many packets @grahamb. its 1Gb/s tcp. Trying to figure out what causes: [Reassembly error, protocol TCP: New fragment overlaps old da |
2021-03-03 20:51:16 +0000 | commented question | WS is non-responsive when capturing many packets @grahamb. its 1GB/s tcp. Trying to figure out what causes: [Reassembly error, protocol TCP: New fragment overlaps old da |
2021-03-03 20:48:27 +0000 | commented answer | WS is non-responsive when capturing many packets Sorry I can only mark one as answer. so had to pick one. |
2021-03-03 20:47:05 +0000 | marked best answer | WS is non-responsive when capturing many packets When starting a capture (no filter) with a lot of traffic - after few tens of seconds WS becomes non-responsive - even stopping the capture takes long time. Is this normal and to expect? I assume it is due to the large volume of data and fair enough. But never the less it is a bit annoying. Are there tricks to tame it before it grinds to a halt except stopping manually after few 10 seconds? Thanks for hints. Version inf: |
2021-03-03 20:47:05 +0000 | received badge | ● Scholar (source) |
2021-03-03 20:46:50 +0000 | received badge | ● Rapid Responder |
2021-03-03 20:46:50 +0000 | answered a question | WS is non-responsive when capturing many packets Thank you for your hints. I am very new to this so if nothing else but for myself I added screen dumps of the relevant s |
2021-03-03 09:00:05 +0000 | received badge | ● Editor (source) |
2021-03-03 09:00:05 +0000 | edited question | WS is non-responsive when capturing many packets WS is non-responsive when capturing many packets When starting a capture (no filter) with a lot of traffic - after few t |
2021-03-02 23:18:54 +0000 | asked a question | WS is non-responsive when capturing many packets WS is non-responsive when capturing many packets When stating a capture (no filter) with a lot of traffic - after few te |