Wireshark mailing list archives
Re: Memory consumption in tshark
From: Anders Broman <a.broman () bredband net>
Date: Thu, 29 Aug 2013 21:02:34 +0200
Anders Broman skrev 2013-08-29 17:20:
I have checked in a change to not store addresses in the hash table when name resolution is off. It remains to do changes to not store unresolved addresses when address resolution is used.*From:*wireshark-dev-bounces () wireshark org [mailto:wireshark-dev-bounces () wireshark org] *On Behalf Of *Dario Lombardo*Sent:* den 29 augusti 2013 17:07 *To:* Developer support list for Wireshark *Subject:* Re: [Wireshark-dev] Memory consumption in tsharkOn Thu, Aug 29, 2013 at 4:35 PM, Evan Huus <eapache () gmail com <mailto:eapache () gmail com>> wrote:Basically, but it's also more. If your capture contains a DNS packet resolving a name in a certain way, and the system name resolver gives a different answer, we prefer the DNS packet in the capture (since presumably the capture was on some local network where that name resolves differently). For this reason we can't just drop old cache entries unless name resolution is disabled completely.That's really interesting. This means that if a DNS packet with a fake resolution is got, it can pollute the "cache".I've triggered this behaviour in the attached pcap file. It appears that I'm pinging google (in my svn wireshark), while actually I'm pinging a private addres :).We should probably have a ****load of parameter to tune the behavior of address resolution JAs there seems to be many opinions on the subject.
___________________________________________________________________________ Sent via: Wireshark-dev mailing list <wireshark-dev () wireshark org> Archives: http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-request () wireshark org?subject=unsubscribe
___________________________________________________________________________ Sent via: Wireshark-dev mailing list <wireshark-dev () wireshark org> Archives: http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-request () wireshark org?subject=unsubscribe
Current thread:
- Re: Memory consumption in tshark, (continued)
- Re: Memory consumption in tshark Dario Lombardo (Aug 28)
- Re: Memory consumption in tshark Evan Huus (Aug 28)
- Re: Memory consumption in tshark Evan Huus (Aug 28)
- Re: Memory consumption in tshark Dario Lombardo (Aug 29)
- Re: Memory consumption in tshark Evan Huus (Aug 29)
- Re: Memory consumption in tshark Dario Lombardo (Aug 29)
- Re: Memory consumption in tshark Evan Huus (Aug 29)
- Re: Memory consumption in tshark Dario Lombardo (Aug 29)
- Re: Memory consumption in tshark Evan Huus (Aug 29)
- Re: Memory consumption in tshark Anders Broman (Aug 29)
- Re: Memory consumption in tshark Anders Broman (Aug 29)
- Re: Memory consumption in tshark Evan Huus (Aug 29)
- Re: Memory consumption in tshark Dario Lombardo (Aug 30)
- Re: Memory consumption in tshark Anders Broman (Aug 29)