Didn't reply to your original email because we aren't an ISP and therefore don't see the number of connections you mention ; Hennings advice is much more relevant. However we are at late stages of testing FreeBSD 5.3 based pf setup which we have benchmarked with 1 Gb in and out concurrently with 2 x 100Mb in and out. We are interested in the ability to back some of our servers up across the firewall.

2 points.
We are running on dual 3.2Ghz Xeons on an Intel JR2 motherboard. Cpu consumption by interface processes was high however system was still responsive at console due to second cpu and FreeBSD removal (reduction) of Giant lock. We are running 3 dual Intel Gb cards in the server but you are likely to hit a PCI bios limitation re the number of network cards that you can have active concurrently. To get 3 active we had to disable the motherboard networking.

We plan to use VLAN and Gb switch to reduce the need for network adapters in the firewall server.

Kirill Ponazdyr wrote:

On 10 Jul 2005 15:44:53 -0700, [EMAIL PROTECTED] (Gustavo A.
Baratto) wrote:

What is "Very Fast" memory? ;)
for example, between DDR533 and DDR800 RAM modules, get a DDR800 (or faster, if they are out there)

AFAIK no serious server board/chipset supports anything better then
PC2100 DDR or 400Mhz DDR2 memory.

Would not one 66MHz/64-bit bus which is not used by anything in
system, but ethernet cards be sufficient? In theory 66MHz/64-bit PCI
bus should be well enough even for wirespeed GigE
it really depends on the amount of rules and amount of packets per second, but having one dedicated PCI controller per NIC is gonna be better than sharing one controller between 2 NICs.

What about Intel Pro/100 S Server Dual Port 64bit/66Mhz adapters
(fxp)?
Like Henning said earlier in this thread: "there is really no reason to buy 100MBit/s cards at all any more". Go for gigabit. Definetely.

We will probably go for single xeon 2.8Ghz Dell 2850 with dual 4-port
Intel pro 1000/MT PCI-X cards.
-------------------------------------------------
When replying via E-Mail, please remove duplicate
"@" from the address.
-------------------------------------------------

Reply via email to