From: Kevin Day [mailto:toasty@;dragondata.com]
> When we're pushing 250-300mbits through, we're using about 15% of its
> 2.4Ghz P4 Xeon CPU. All of it is in "interrupt" time... that
> seems a bit
> high, but that'll still let us max things out at 1gbit so we're ok.
Try applying these diff to y
another way to do the count efficiently is to use dummynet dynamic pipes:
ipfw add 100 pipe 1 ip from 10.0.0.0/24 to any
ipfw add 100 pipe 2 ip from any to 10.0.0.0/24
ipfw pipe 1 config mask src-ip 0x
ipfw pipe 2 config mask dst-ip 0x
sysctl
oops, duh, Take the 'count' keyword out.. they count anyhow..
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-net" in the body of the message
> I have a server acting as a router. Dual bge gigabit network interfaces
> (PCI-X), one is the WAN side the other is the LAN side.
> When we're pushing 250-300mbits through, we're using about 15% of its
> 2.4Ghz P4 Xeon CPU. All of it is in "interrupt" time... that seems a bit
> high, but tha
I have a server acting as a router. Dual bge gigabit network interfaces
(PCI-X), one is the WAN side the other is the LAN side.
When we're pushing 250-300mbits through, we're using about 15% of its
2.4Ghz P4 Xeon CPU. All of it is in "interrupt" time... that seems a bit
high, but that'll still
