Re: [tcpdump-workers] Disable address/name resolution in libpcap

[...] > Presumably, if pcap_compile_ex() or pcap_compile_nonameres() or whatever > were to disable name resolution, it would treat *all* host names as failing > to resolve, so > > host www.example.com > > would fail to compile. This means, of course, that the pre-test would >

Re: [tcpdump-workers] Disable address/name resolution in libpcap

On Apr 14, 2016, at 12:05 AM, Denis Ovsienko wrote: > On Wed, 13 Apr 2016 16:44:24 +0100 Ed Sealing wrote >> We're writing an application around libpcap. The app may or may not have >> DNS resolution available. We've noticed that when DNS resolution is not >>

Re: [tcpdump-workers] Disable address/name resolution in libpcap

On Apr 13, 2016, at 8:44 AM, Ed Sealing wrote: > Is there a way to programatically disable name resolution in libpcap No. > (similar to tcpdump "-n" argument)? I haven't been able to find a variable > to pass in that would accomplish this directly in the library.

Re: [tcpdump-workers] Disable address/name resolution in libpcap

On Wed, 13 Apr 2016 16:44:24 +0100 Ed Sealing wrote >We're writing an application around libpcap. The app may or may not have >DNS resolution available. We've noticed that when DNS resolution is not >available, we experience long delays when pre-testing the filters (prior to

[tcpdump-workers] Disable address/name resolution in libpcap

We're writing an application around libpcap. The app may or may not have DNS resolution available. We've noticed that when DNS resolution is not available, we experience long delays when pre-testing the filters (prior to applying them). Is there a way to programatically disable name resolution in