Hi... . Do yourself a big faviour... Get a Portmaster or a similar external modem rack. It's going to save you ALLOT of troubles... Authentication wise, yes, it will more than likely be best suited with a Radius configuration. The other services you require (DNS / Proxy), shouldn't be any real problem for the amount of users you are talking about. A standardish linux box will be able to do the authentication (Radius), aswell as other related services as you require. As to your question about the system specs... Have a look at the Squid web site (I believe it is at http://squid.nlanr.net).. They have quite a few detailed reports about system performance and recommended hardware and usage and so forth. It will be well forth the visit for you. While I'm on this subject... Does anyone here have a GOOD solution towards getting Unix based machines to SHARE account / login data with Windows NT? >From what I heard, the NT port of kerberos isn't compatible, so I can't really use it. I can't use a database, because NT doesn't support authentication from Databases, and I can't use Radius either, because Radius will only be able to handle dial-up authentication... A simple scenario would be to have all the account names on say a Linux Machine, then have NT Authenticate the user over a web interface, from the passwd db on the Linux Machine. FTP and Dialup authentication must also work in a similar fashion. I've been looking and thinking for a solution for this now for about the last year - year and a half, and it's REALLY starting to give me a headache now... Any help will be appreciated. Regards Chris Knipe Cell: (083) 430-8151 Natural ability without education has more often attained to glory and virtue, than education without natural ability at all. ----- Original Message ----- From: Ahsan Ali <ahsan.ali@mail.com> To: <linux-admin@vger.rutgers.edu>; <linux-net@vger.rutgers.edu> Sent: 05 July 2000 05:06 Subject: Hardware selection for a Linux based ISP > We need to provide dial-in access to 120 clients simultaneously though > we expect a total number of clients much greater than that and we expect > major growth. We will also be providing them email and proxied web > access although the real reason these clients will be dialing in is to > access services and application servers on our network. > > We are thinking of going with Linux as the OS for this ISPish setup. > > The Linux servers will need to do authentication (RADIUS?), DNS (BIND), > mail relaying (SendMail), web hosting (Apache), ftp hosting > (WuFTPd/NCFTPd/etc), proxying (SQUID) and other miscellaneous services > like irc, news etc. > > What I need to know now is that are there any recommended dial-in > solutions for Linux? We have yet to decide on what Remote Access > Servers/Concentrators to go for and I would love to hear of any > experiences or words of advice you guys might have for me. One other > thing worth mentioning is that latency is more important to us than raw > throughput for the clients who have dialed in... > > Our incoming lines are all E1s (30 data channels/analog lines > equivalent) for a total of 4 E1s though we will expand later. They don't > all need to be homed on the same box though. > > Also, would a dual P3-550, 256s megs ram and RAID 0 SCSI / IDE be good > enough as a proxy for the above using SQUID/Linux ? > > Thank you! > > -Ahsan > > > > - > : send the line "unsubscribe linux-net" in > the body of a message to majordomo@vger.rutgers.edu - : send the line "unsubscribe linux-net" in the body of a message to majordomo@vger.rutgers.edu
