Pawel Pokrywka wrote:
Back to pcap_direction() function. I think I better like idea, that
pcap_direction() should return error when given direction is not
supported on users platform.
If there are no better ways, enclosing pcap_direction() body and
direction checks in pcap_read_packet() with #ifdef
Greetings,
I have attached two patches to the current tcpdump and
libpcap source. It is a patch to add a fourth dflag (-). When
this option is enabled it will print out all packets with
the packet matching code that would be executed for that packet
if - was not supplied. Typing tc
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Guy Harris wrote:
> Pawel Pokrywka wrote:
>
>> For me, only D_IN is required, so I would be happy with this direction
>> only :)
>> I don't know other platforms, but are you sure that there is no way to
>> implement for example D_IN, when there is D_O
Pawel Pokrywka wrote:
For me, only D_IN is required, so I would be happy with this direction
only :)
I don't know other platforms, but are you sure that there is no way to
implement for example D_IN, when there is D_OUT and D_INOUT? Maybe there
are other problems, but substracting D_OUT from D_INO
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
>> To specify direction pcap_direction() have to be called after
>> pcap_open_live() with desired direction (D_IN, D_OUT, D_INOUT). Default
>> direction, in case pcap_direction() was not called is D_INOUT.
>
>Are all three of those needed?
>
>On some p
CVS log entries from 01.05.2005 (Sun) 09:07:33 - 02.05.2005 (Mon) 09:06:47 GMT
=
Summary by authors
=
Author: guy
File: libpcap/rawss7.h; Revisions: 1.2, 1.1.4.1
File: libpcap/gen
Alexander Dupuy wrote:
If that's unavoidable (i.e., if some system header file we're including
drags in pmap_prot.h), perhaps we should modify our pmap_prot.h so
that it
uses different names for what it defines, so we don't get the name
collisions that I'm assuming are causing the compile problems
