On 2008-Dec-30 07:58:58 -0800, ibmed wrote:
>There's two FreeBSD boxes that do ipfw nat.
>Both worked with natd until some time ago, when it became clear that we need
>a better solution. So I upgraded sources and recompiled to kernel to include
>ipfw nat features. The boxes have onboard msk-net ca
1:1:01
inet 10.1.1.1 netmask 0xff00 broadcast 10.1.1.255
media: Ethernet autoselect (1000baseTX )
status: active
--
View this message in context:
http://www.nabble.com/em-driver-problems--taskq-em-goes-up-to-100--CPU-tp21218952p21218952.html
Sent from the freebsd-net mailing list a
On Mon, 20 Jun 2005, Patrick Domack wrote:
I have been using fxp network based cards, without issues. I have
recently changed over to em cards, and get kernel panics about once
every few days with them (mainly sbdrop panics). I already have
nsfclusters set to 32k, and freebsd vm memory set to
I have been using fxp network based cards, without issues. I have recently
changed over to em cards, and get kernel panics about once every few days
with them (mainly sbdrop panics). I already have nsfclusters set to 32k,
and freebsd vm memory
set to 850megs, with 4g memory installed.
After p
