Hi, Guy,
First of all, thanks so much for your help and detailed explanation! --
I really appreciate it...
On 06/15/2014 08:07 PM, Guy Harris wrote:
>
>> which would seem to indicate that pcap_inject() is overwriting the
>> value I set with something else (pseudo_AF_HDRCMPLT?).
>
> It indicates
Hello list,
Just a simple question: I have eth1 with some VLAN's. When tcpdumping
with:
# tcpdump -h
tcpdump version 3.9.8
libpcap version 0.9.8
the vlan tags are printed using "tcpdump -ni eth1":
10:16:12.068967 vlan 65, p 0, IP 10.65.0.196.49189 > 10.2.131.14.2598
But using a newer version,
On Jun 15, 2014, at 1:56 PM, Fernando Gont wrote:
> I will certainly file a bug report, and CC you. My understanding is that
> this should be filled in most (if not all) of the BSD variants? (because
> besides the error message one obtains, it seems that in several flavors
> of them, pcap_inject
Michael Richardson writes:
> Yeah, my bad; was sick that weekend, and stuff... happened.
No problem.
> How about July 1?
So -rc1 on July 1, then release a week later? Or -rc1 in the meantime,
and release on July 1? (Works for me either way.)
___
tcpd
On Jun 16, 2014, at 1:53 AM, richard lucassen wrote:
> Just a simple question: I have eth1 with some VLAN's. When tcpdumping
> with:
>
> # tcpdump -h
> tcpdump version 3.9.8
> libpcap version 0.9.8
>
> the vlan tags are printed using "tcpdump -ni eth1":
>
> 10:16:12.068967 vlan 65, p 0, IP 10
On Jun 16, 2014, at 2:50 AM, Guy Harris wrote:
> On Jun 15, 2014, at 1:56 PM, Fernando Gont wrote:
>
>> I will certainly file a bug report, and CC you. My understanding is that
>> this should be filled in most (if not all) of the BSD variants? (because
>> besides the error message one obtains,
On Mon, 16 Jun 2014 13:11:22 +0200
Romain Francoise wrote:
> richard lucassen writes:
>
> > Is this a bug or has this been changed?
>
> Are you using Debian or a derivative like Ubuntu? The tcpdump package
> used to have a patch to reverse the meaning of the -e flag, but it was
> dropped a few
Romain Francoise wrote:
>> Yeah, my bad; was sick that weekend, and stuff... happened.
> No problem.
>> How about July 1?
> So -rc1 on July 1, then release a week later? Or -rc1 in the meantime,
> and release on July 1? (Works for me either way.)
-rc1 on July 1.
Release a
