[leaf-user] hardware requirements bering router 100 mbit+
hello I have been using bering for adsl /wireless routing a long time, and it's as stable as a rock. But i am now going to setup a DMZ for services. this will be on a 100 mbit switched network and it might become a 1000 mbit switched network in a year or so. what i am wondering is. what kind of hardware will i need to saturate a 100 mbit switched network. using bering, 2 nics and no vpn or masquerading this is pure routing. btw: can bering support ospf protocol ? mvh Ronny Aasen --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
Re: [leaf-user] hardware requirements bering router 100 mbit+
Ronny Aasen wrote: what kind of hardware will i need to saturate a 100 mbit switched network. using bering, 2 nics and no vpn or masquerading this is pure routing. A decent pentium class system should be capable of saturating a couple 100 MBit links. You will need to use server class PCI NIC's (like the DEC based cards using the tulip driver, or the 3COM 3C905...I've heard good things about the Intel based cards as well, but haven't tried them personally). You'll also want a good PCI chipset (hard to quantify without getting into lots of low-level hardware details). As a general rule of thumb, processing a packet takes a fairly fixed amount of CPU, so if your saturated 100 Mbits of traffic is lots of small packets, you'll need more CPU than if the traffic is mainly large packets for bulk transfers. I think anything over a P133/166 should work fine, and something like a P-2 or P-3 system with a BX chipset (or better...anything with a 100 MHz FSB) would give you quite a bit of headroom. -- Charles Steinkuehler [EMAIL PROTECTED] --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
Re: [leaf-user] hardware requirements bering router 100 mbit+
On Tue, 2003-02-18 at 15:07, Charles Steinkuehler wrote: Ronny Aasen wrote: what kind of hardware will i need to saturate a 100 mbit switched network. using bering, 2 nics and no vpn or masquerading this is pure routing. A decent pentium class system should be capable of saturating a couple 100 MBit links. You will need to use server class PCI NIC's (like the DEC based cards using the tulip driver, or the 3COM 3C905...I've heard good things about the Intel based cards as well, but haven't tried them personally). You'll also want a good PCI chipset (hard to quantify without getting into lots of low-level hardware details). As a general rule of thumb, processing a packet takes a fairly fixed amount of CPU, so if your saturated 100 Mbits of traffic is lots of small packets, you'll need more CPU than if the traffic is mainly large packets for bulk transfers. I think anything over a P133/166 should work fine, and something like a P-2 or P-3 system with a BX chipset (or better...anything with a 100 MHz FSB) would give you quite a bit of headroom. In other word i can't buy such prosessors anymore... I'v been using VIA's C3 a lot lately, since it don't need a cpu cooler, i guess i'll stick to that. and i have quite a lot of 3c905's around. Now i just need a fanless psu thx for the quick replies :) mvh Ronny Aasen Datapart AS --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
Re: [Leaf-user] Hardware requirements ;-)
Hey Guys: Connect Comp http://www.connectcomp.com is selling an ALR PII 266 with no hard drive, key board, mouse and cd. just a 3.5 disk drive. Specs are PII 266 with 512k cache, 32 megs of memory and a 3.5 disk drive for $80.00. Just add two nic's and instant LRP. Robert Chambers Kenneth Hadley wrote: My LEAF box is a AMD 586-133 (just a bit faster than a P-75) and its workinggreat for me.I will announce to both the dev and user Leaf email lists when Ive releaseda new image.-Kenneth Hadley- Original Message -From: "Robert Chambers" [EMAIL PROTECTED]To: "Kenneth Hadley" [EMAIL PROTECTED]Sent: Monday, October 15, 2001 12:28 AMSubject: Re: [Leaf-user] Hardware requirements ;-) Ken:Just to let you know, I am planning on upgrading my LRP to a Pentium orbetter. I have a 1.5meg/ 384k PPPoE DSL line from Covad and I only haveone computer behind the LRP in my house. I'll keep an eye on your webpage for any updates.Robert ChambersKenneth Hadley wrote: Unfourtunatly from my tests a 486DX4-100 is the minium speed CPU needed for PPPoE if your bandwidth is the standard 1.5mbit down/ 128kbit up and evenwith this CPU you will see your bandwidth go down the toilet with moreclients behind the LEAF box. Obviously if you have a slower line then youdont need that kind of power, say a 486sx25 if you have a 768k down/??k up. The newer Roaring Penguin PPPoE clients might be less CPU intensive butunfourtunatly you need Glibc 2.2 to compile it, and ive found no way around this (Hint: If someone can prove me wrong I would be most gratefull) which has kinda halted images from me till Dachstein is released.-Kenneth Hadley- Original Message -From: "Robert Chambers" [EMAIL PROTECTED]To: "leaf-user" [EMAIL PROTECTED]Sent: Sunday, October 14, 2001 12:42 AMSubject: Re: [Leaf-user] Hardware requirements ;-) Yes there is a limit on how slow of a processor one can use with an LRP.I am using Eigerstien2beta pppoe beta v.0.4 from Kenneth Hadley on a386 DX board running a Cyrix 486 DLC 40 mhz chip and the PPPoE islimited to about 500kbps down load. The speed limit has to do with theway pppoe sends the packets, the processor must recombine them. Alsoaccording to Ken Hadley on anything less than a 486 DX4 100mhz you willnotice a speed dive with PPPoE.Robert ChambersJeff Newmiller wrote: On Sat, 13 Oct 2001, Mark Plowman wrote: I have recently been encouraging my less Linux-centric colleagues touse LEAF as a fire-wall for their personal dial-up/cable/ADSL Internetconnections, having done the same with the company ISDN and ADSLconnections.Yesterday the trainee expressed interest, explained that he had cableaccess and asked about the hardware requirements. I explained thatalmost anything he could lay his hands on would be sufficient and hethen asked "but wouldn't that (a 386) perform *too* slowly?". Ireassured him that that would be OK and sent him off after anintroductory talk about LEAF with both an Eigerstien and a Dachsteinfloppy.Once at home I decided to put my "money where my mouth was" and*downgraded* my 486 DX2-80 with a 386 SX-33! I had to (of course)replace the kernel on my ISDN Eigerstien with a non-FPU example, butit all works a treat! What I do notice is that during start-up theunpacking of the Linux Kernel and initial ram disk images take an*age*! I found that there is a lower limit... the performance of a 386-33on a pppoe setup was significantly lower than no router. However, forstatic routing it should be okay, and almost any true 486 should keep up with pppoe. -- -
Re: [Leaf-user] Hardware requirements ;-)
Yes there is a limit on how slow of a processor one can use with an LRP. I am using Eigerstien2beta pppoe beta v.0.4 from Kenneth Hadley on a 386 DX board running a Cyrix 486 DLC 40 mhz chip and the PPPoE is limited to about 500kbps down load. The speed limit has to do with the way pppoe sends the packets, the processor must recombine them. Also according to Ken Hadley on anything less than a 486 DX4 100mhz you will notice a speed dive with PPPoE. Robert Chambers Jeff Newmiller wrote: [EMAIL PROTECTED]"> On Sat, 13 Oct 2001, Mark Plowman wrote: I have recently been encouraging my less Linux-centric colleagues touse LEAF as a fire-wall for their personal dial-up/cable/ADSL Internetconnections, having done the same with the company ISDN and ADSLconnections.Yesterday the trainee expressed interest, explained that he had cableaccess and asked about the hardware requirements. I explained thatalmost anything he could lay his hands on would be sufficient and hethen asked "but wouldn't that (a 386) perform *too* slowly?". Ireassured him that that would be OK and sent him off after anintroductory talk about LEAF with both an Eigerstien and a Dachsteinfloppy.Once at home I decided to put my "money where my mouth was" and*downgraded* my 486 DX2-80 with a 386 SX-33! I had to (of course)replace the kernel on my ISDN Eigerstien with a non-FPU example, butit all works a treat! What I do notice is that during start-up theunpacking of the Linux Kernel and initial ram disk images take an*age*! I found that there is a lower limit... the performance of a 386-33on a pppoe setup was significantly lower than no router. However, forstatic routing it should be okay, and almost any true 486 should keep upwith pppoe.---Jeff NewmillerThe . . Go Live...DCN:[EMAIL PROTECTED]Basics: ##.#. ##.#. Live Go... Live: OO#.. Dead: OO#.. PlayingResearch Engineer (Solar/BatteriesO.O#. #.O#. with/Software/Embedded Controllers) .OO#. .OO#. rocks...2k---___Leaf-user mailing list[EMAIL PROTECTED]https://lists.sourceforge.net/lists/listinfo/leaf-user
Re: [Leaf-user] Hardware requirements ;-)
Unfourtunatly from my tests a 486DX4-100 is the minium speed CPU needed for PPPoE if your bandwidth is the standard 1.5mbit down/ 128kbit up and even with this CPU you will see your bandwidth go down the toilet with more clients behind the LEAF box. Obviously if you have a slower line then you dont need that kind of power, say a 486sx25 if you have a 768k down/??k up. The newer Roaring Penguin PPPoE clients might be less CPU intensive but unfourtunatly you need Glibc 2.2 to compile it, and ive found no way around this (Hint: If someone can prove me wrong I would be most gratefull) which has kinda halted images from me till Dachstein is released. -Kenneth Hadley - Original Message - From: Robert Chambers [EMAIL PROTECTED] To: leaf-user [EMAIL PROTECTED] Sent: Sunday, October 14, 2001 12:42 AM Subject: Re: [Leaf-user] Hardware requirements ;-) Yes there is a limit on how slow of a processor one can use with an LRP. I am using Eigerstien2beta pppoe beta v.0.4 from Kenneth Hadley on a 386 DX board running a Cyrix 486 DLC 40 mhz chip and the PPPoE is limited to about 500kbps down load. The speed limit has to do with the way pppoe sends the packets, the processor must recombine them. Also according to Ken Hadley on anything less than a 486 DX4 100mhz you will notice a speed dive with PPPoE. Robert Chambers Jeff Newmiller wrote: On Sat, 13 Oct 2001, Mark Plowman wrote: I have recently been encouraging my less Linux-centric colleagues to use LEAF as a fire-wall for their personal dial-up/cable/ADSL Internet connections, having done the same with the company ISDN and ADSL connections. Yesterday the trainee expressed interest, explained that he had cable access and asked about the hardware requirements. I explained that almost anything he could lay his hands on would be sufficient and he then asked but wouldn't that (a 386) perform *too* slowly?. I reassured him that that would be OK and sent him off after an introductory talk about LEAF with both an Eigerstien and a Dachstein floppy. Once at home I decided to put my money where my mouth was and *downgraded* my 486 DX2-80 with a 386 SX-33! I had to (of course) replace the kernel on my ISDN Eigerstien with a non-FPU example, but it all works a treat! What I do notice is that during start-up the unpacking of the Linux Kernel and initial ram disk images take an *age*! I found that there is a lower limit... the performance of a 386-33 on a pppoe setup was significantly lower than no router. However, for static routing it should be okay, and almost any true 486 should keep up with pppoe. --- Jeff NewmillerThe . . Go Live... DCN:[EMAIL PROTECTED]Basics: ##.#. ##.#. Live Go... Live: OO#.. Dead: OO#.. Playing Research Engineer (Solar/BatteriesO.O#. #.O#. with /Software/Embedded Controllers) .OO#. .OO#. rocks...2k --- ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
[Leaf-user] Hardware requirements ;-)
I have recently been encouraging my less Linux-centric colleagues to use LEAF as a fire-wall for their personal dial-up/cable/ADSL Internet connections, having done the same with the company ISDN and ADSL connections. Yesterday the trainee expressed interest, explained that he had cable access and asked about the hardware requirements. I explained that almost anything he could lay his hands on would be sufficient and he then asked but wouldn't that (a 386) perform *too* slowly?. I reassured him that that would be OK and sent him off after an introductory talk about LEAF with both an Eigerstien and a Dachstein floppy. Once at home I decided to put my money where my mouth was and *downgraded* my 486 DX2-80 with a 386 SX-33! I had to (of course) replace the kernel on my ISDN Eigerstien with a non-FPU example, but it all works a treat! What I do notice is that during start-up the unpacking of the Linux Kernel and initial ram disk images take an *age*! I do love LEAF! Greetings Mark ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
Re: [Leaf-user] Hardware requirements ;-)
On Sat, 13 Oct 2001, Mark Plowman wrote: I have recently been encouraging my less Linux-centric colleagues to use LEAF as a fire-wall for their personal dial-up/cable/ADSL Internet connections, having done the same with the company ISDN and ADSL connections. Yesterday the trainee expressed interest, explained that he had cable access and asked about the hardware requirements. I explained that almost anything he could lay his hands on would be sufficient and he then asked but wouldn't that (a 386) perform *too* slowly?. I reassured him that that would be OK and sent him off after an introductory talk about LEAF with both an Eigerstien and a Dachstein floppy. Once at home I decided to put my money where my mouth was and *downgraded* my 486 DX2-80 with a 386 SX-33! I had to (of course) replace the kernel on my ISDN Eigerstien with a non-FPU example, but it all works a treat! What I do notice is that during start-up the unpacking of the Linux Kernel and initial ram disk images take an *age*! I found that there is a lower limit... the performance of a 386-33 on a pppoe setup was significantly lower than no router. However, for static routing it should be okay, and almost any true 486 should keep up with pppoe. --- Jeff NewmillerThe . . Go Live... DCN:[EMAIL PROTECTED]Basics: ##.#. ##.#. Live Go... Live: OO#.. Dead: OO#.. Playing Research Engineer (Solar/BatteriesO.O#. #.O#. with /Software/Embedded Controllers) .OO#. .OO#. rocks...2k --- ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
