Date: Tue, 19 Nov 1996 15:53:02 -0600 From: "Randy DuCharme" <randyd@nconnect.net> To: <questions@freebsd.org> Subject: FreeBSD as dedicated router Message-ID: <199611192201.QAA06012@atlantis.nconnect.net>
next in thread | raw e-mail | index | archive | help
Greetings, I have to provide a low-cost, high-performance routing solution. I'm wondering how FBSD would work in this scenario. I've never tried to do this with FBSD and don't have too much time for experimentation in this case. Has anyone done this??? Here's the scenario..... 2 Sister companies formerly connected via frame relay, now sharing adjacent office space. Company A has 1 NT server, and one SCO (yecch!!) box. Company B has 1 NT server. Both companies access the SCO host. Company A has 2 class B addresses -> 132.140.x.x and 132.148.x.x and company B has addresses ->132.141.x.x and will have 132.147.x.x. after the move is complete. (this is a totally closed network) Routing used to be handled with the WAN hardware (Motorola Vanguard 300 etc) but I'm wondering if a FBSD box would be up to the job in this case. I need to route 132.140... to 132.141..., 132.141...to 132.140... 132.147... to 132.148... and 132.148... to 132.147... The network backbones are 10B2 coax with hubs on the ends (nothing fancy). Is FreeBSD up to the task? Can one machine handle it ( 4 interfaces ) or would 2 be necessary? How much horsepower would it take ( 386, 486, P-x ) or would one be better of with specialized switching hardware? Opinions?? Thanks --- Randall D. DuCharme Systems Engineer Computer Specialists
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199611192201.QAA06012>