Jung-uk Kim wrote:
On Tuesday 23 August 2005 04:15 pm, Pieter de Boer wrote:
Matthew Grooms wrote:
Is anyone else seeing this issue? I get useless output from
tcpdump ( no header or protocol decode ) but only when I
specify a filter on the command line.
listening on xl0, link-type EN10MB (Eth
On Tuesday 23 August 2005 04:15 pm, Pieter de Boer wrote:
> Matthew Grooms wrote:
> >>> Is anyone else seeing this issue? I get useless output from
> >>> tcpdump ( no header or protocol decode ) but only when I
> >>> specify a filter on the command line.
> >>> listening on xl0, link-type EN10MB (Et
Matthew Grooms wrote:
>>> Is anyone else seeing this issue? I get useless output from tcpdump ( no
>>> header or protocol decode ) but only when I specify a filter on the
>>> command line.
>>> listening on xl0, link-type EN10MB (Ethernet), capture size 96 bytes
>>> 11:33:32.920031 [|ether]
>>> 11:
Pieter de Boer wrote:
Matthew Grooms wrote:
Is anyone else seeing this issue? I get useless output from tcpdump ( no
header or protocol decode ) but only when I specify a filter on the
command line.
listening on xl0, link-type EN10MB (Ethernet), capture size 96 bytes
11:33:32.920031 [|ethe
On 8/23/05, Brooks Davis <[EMAIL PROTECTED]> wrote:
> On Tue, Aug 23, 2005 at 10:09:06AM -0700, Maksim Yevmenkin wrote:
> > Hello,
> >
> > please try the attached patch.
> >
> > > >Description:
> > > assigning an address to ng_fec(4) iface causes panic
> > > during dumping to dumpde
Matthew Grooms wrote:
> Is anyone else seeing this issue? I get useless output from tcpdump ( no
> header or protocol decode ) but only when I specify a filter on the
> command line.
> listening on xl0, link-type EN10MB (Ethernet), capture size 96 bytes
> 11:33:32.920031 [|ether]
> 11:33:35.20399
On Tue, Aug 23, 2005 at 10:09:06AM -0700, Maksim Yevmenkin wrote:
> Hello,
>
> please try the attached patch.
>
> > >Description:
> > assigning an address to ng_fec(4) iface causes panic
> > during dumping to dumpdev another panic occurs preventing to
> > identify the source of t
Hello,
please try the attached patch.
> >Description:
> assigning an address to ng_fec(4) iface causes panic
> during dumping to dumpdev another panic occurs preventing to identify
> the source of the first panic and having the crash dump
>
> ng_iface creation sequence:
Is anyone else seeing this issue? I get useless output from tcpdump ( no
header or protocol decode ) but only when I specify a filter on the
command line.
For example ...
[EMAIL PROTECTED] tcpdump -ne -i pflog0 src or dst www.21.com
tcpdump: WARNING: BIOCPROMISC: Network is down
tcpdump: WARNI
> I hope this is the right place that I post to!
>
>
>
> When I enabled polling in 5.4 and 4.11, I found that CPU load
> in 5.4 is much higher than 4.11. For example, suppose HZ is 5000, in 5.4
> the idle CPU is about 87%, but in 4.11, the idle CPU is about 99.9%. Is
> this ri
10 matches
Mail list logo
