On 8/18/05, Ian Dowse <[EMAIL PROTECTED]> wrote:
>
> There appear to be some braces missed in that revision of bpf.c. Does
> the following patch help?
>
> Ian
>
Thank you very much, your patch works fine for me...
___
freebsd-stable@freebsd.org mailing
Or if you want, I will commit it.
On Thu, Aug 18, 2005 at 09:59:50AM +0100, Ian Dowse wrote:
> In message <[EMAIL PROTECTED]>, Iva Hesy writes:
> >OK, now, I get the result:
> >"tag=RELENG_6 date=2005.07.30.22.00.00" works fine, "tag=RELENG_6
> >date=2005.07.31.03.00.00" makes noise, many many eth
Yes,
This appears to be a mistake on my part, please commit this patch.
Thanks for catching this!
On Thu, Aug 18, 2005 at 09:59:50AM +0100, Ian Dowse wrote:
> In message <[EMAIL PROTECTED]>, Iva Hesy writes:
> >OK, now, I get the result:
> >"tag=RELENG_6 date=2005.07.30.22.00.00" works fine, "ta
In message <[EMAIL PROTECTED]>, Iva Hesy writes:
>OK, now, I get the result:
>"tag=RELENG_6 date=2005.07.30.22.00.00" works fine, "tag=RELENG_6
>date=2005.07.31.03.00.00" makes noise, many many ethernet frames can
>be sniffered.
>the cvsup log:
>Updating collection src-all/cvs
> Edit src/sys/dev/ml
On 8/16/05, Brooks Davis <[EMAIL PROTECTED]> wrote:
>
> Sounds like someone introduced a bug in the nic driver or the ethernet
> code, but I'm not seeing anything obvious between those dates. If you
> could narrow the date range further that would help.
>
> -- Brooks
OK, now, I get the result:
"
On Sat, Aug 13, 2005 at 02:01:26AM -0700, Iva Hesy wrote:
> Just now, I add "date=2005.07.31.03.00.00" to my src cvsup sup-file
> and make kernel, too short ethernet frames are still sniffered. But
> when I add "date=2005.07.22.03.00.00" to sup-file and cvsup and make
> kernel, the damn datagrams g
Just now, I add "date=2005.07.31.03.00.00" to my src cvsup sup-file
and make kernel, too short ethernet frames are still sniffered. But
when I add "date=2005.07.22.03.00.00" to sup-file and cvsup and make
kernel, the damn datagrams gone!!!
___
freebsd-sta
On 8/12/05, Brooks Davis <[EMAIL PROTECTED]> wrote:
>
> Most likely, your cabling, duplex configuraion, nic, switch are
> misconfigured and a high traffic ap like rdesktop is pushing them over
> the edge. I'd check the duplex settings on each end and try another
> cable first. Then try a differe
On Fri, Aug 12, 2005 at 02:37:04AM -0700, Iva Hesy wrote:
> OS: RELENG_6 (Beta2)
> NIC: vr0:
> # tcpdump -penv -i vr0 less 32
> 16:15:42.512701 [|ether]
> 16:15:44.523102 [|ether]
> 16:15:46.522495 [|ether]
> 16:16:00.540387 [|ether]
> 16:16:02.541834 [|ether]
> 16:16:08.550068 [|ether]
> 16:16:10
OS: RELENG_6 (Beta2)
NIC: vr0:
# tcpdump -penv -i vr0 less 32
16:15:42.512701 [|ether]
16:15:44.523102 [|ether]
16:15:46.522495 [|ether]
16:16:00.540387 [|ether]
16:16:02.541834 [|ether]
16:16:08.550068 [|ether]
16:16:10.570483 [|ether]
# snort -pev -i vr0 less 32
Captured data length < Ethernet h
10 matches
Mail list logo
