Hi, everybody,
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
Paul Khavkine wrote:
On Mon, 22 Aug 2005, Julian Elischer wrote:
Paul Khavkine wrote:
Julian.
You should probably look at the ng_etf node too BTW.
How does ng_etf deal with that ?
no, but as an example of something that is designed to be attached directly
to the ng_ether nodes.
i
On Mon, 22 Aug 2005, Julian Elischer wrote:
>Paul Khavkine wrote:
>> Julian.
>>
>>
>You should probably look at the ng_etf node too BTW.
How does ng_etf deal with that ?
>>>
>>>no, but as an example of something that is designed to be attached directly
>>>to the ng_ether nodes.
>
Paul Khavkine wrote:
Julian.
You should probably look at the ng_etf node too BTW.
How does ng_etf deal with that ?
no, but as an example of something that is designed to be attached directly
to the ng_ether nodes.
in ng_etf, do you check ethertype for only Ethernet II frames ? or also
>Submitter-Id: current-users
>Originator:Evgueni V. Gavrilov
>Organization: rusunix.org
>Confidential: no
>Synopsis: assigning an address to ng_fec(4) iface causes panic
>Severity: serious
>Priority: medium
>Category: kern
>Class: sw-bug
>Release: FreeBSD 6
Hi,
I recently upgraded my FreeBSD/sparc64 5.4 router at home to 6-BETA2,
without changing pf.conf. Since this upgrade, UDP packets redirected
with pf's route-to feature get the wrong checksum.
My complete ruleset:
[EMAIL PROTECTED] grep -v ^# /etc/pf.conf
ext_if="hme0" # replace with actual
Julian.
>>>You should probably look at the ng_etf node too BTW.
>>
>>
>> How does ng_etf deal with that ?
>
>no, but as an example of something that is designed to be attached directly
>to the ng_ether nodes.
in ng_etf, do you check ethertype for only Ethernet II frames ? or also
802.3 frames ?
Current FreeBSD problem reports
Critical problems
Serious problems
Non-critical problems
S Submitted Tracker Resp. Description
---
o [2003/07/11] kern/54383 net [nfs] [patch] NFS root configurations w
