> "Guy" == Guy Harris writes:
Guy> On Feb 23, 2012, at 7:58 PM, Paul Sheer wrote:
Paul> Would anyone consider adding this support to libpcap: i.e. a
Paul> new member within pcap_opt ?
I think that it should probably just be on. Principal of least
surpr
On Feb 23, 2012, at 7:58 PM, Paul Sheer wrote:
>>>
>>>Paul> Would anyone consider adding this support to libpcap: i.e. a
>>>Paul> new member within pcap_opt ?
>>>
>>> I think that it should probably just be on.
>>> Principal of least surprise.
>>
>> Here's why PACKET_MR_ALLMULTI is cur
>>
>> Paul> Would anyone consider adding this support to libpcap: i.e. a
>> Paul> new member within pcap_opt ?
>>
>> I think that it should probably just be on.
>> Principal of least surprise.
>
> Here's why PACKET_MR_ALLMULTI is currently *not* turned on:
>
>
> https://sourceforge.ne
On Feb 23, 2012, at 5:58 PM, Michael Richardson wrote:
>
>> "Paul" == Paul Sheer writes:
>Paul> Actually I found the answer to this, as below.
>
>Paul> Would anyone consider adding this support to libpcap: i.e. a
>Paul> new member within pcap_opt ?
>
> I think that it should p
> "Paul" == Paul Sheer writes:
Paul> Actually I found the answer to this, as below.
Paul> Would anyone consider adding this support to libpcap: i.e. a
Paul> new member within pcap_opt ?
I think that it should probably just be on.
Principal of least surprise.
--
] He who
There is a need.
Actually I found the answer to this, as below.
Would anyone consider adding this support to libpcap: i.e. a new
member within pcap_opt ?
Under Linux you have to explicitly enable support for "all multicast" packets.
libpcap does not have an option for this, but it can be done a
On Thu, Feb 23, 2012 at 10:20 AM, Paul Sheer wrote:
> Hi there,
>
> With promiscuous mode turned off, libpcap successfully captures
> ARP requests (since they are sent to hw address ff:ff:ff:ff:ff:ff).
>
> However I would expect the same behavior with IPv6 ICMPv6
> Neighbor Solicitation reques
Hi there,
With promiscuous mode turned off, libpcap successfully captures
ARP requests (since they are sent to hw address ff:ff:ff:ff:ff:ff).
However I would expect the same behavior with IPv6 ICMPv6
Neighbor Solicitation requests. These requests have the
destination HW address of 33:33:xx:xx
