Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!simtel!chi-news.cic.net!newsxfer.itd.umich.edu!gumby!andrews-cc!gillham From: gillham@andrews.edu (Andrew Gillham) Newsgroups: comp.unix.bsd.netbsd.misc Subject: Re: ISDN for NetBSD Date: 5 Nov 1995 21:47:38 GMT Organization: Andrews University Lines: 26 Message-ID: <47jbdq$3k0@orion.cc.andrews.edu> References: <46gifk$d2n@cousteau.norcen.com> <DH2tFH.GJx@GTS.NET> <47egb7$1bh@cynic.portal.ca> <87lopv86ir.fsf@hrothgar.mindspring.com> NNTP-Posting-Host: edmund.cs.andrews.edu In article <87lopv86ir.fsf@hrothgar.mindspring.com> Robert Sanders <rsanders@mindspring.com> writes: > >Although we use them in great abundance here, I'd never to so far as >to call the Ascend Pipelines *good* routers. Their sole routing >protocol is RIPv1 and their routing table doesn't fully support >classless addressing yet. Uhmm, why would you use RIP at all? A static route entry for the ethernet, and a default route out the ISDN port, should suffice. Then all routing decisions are made by the intelligent ISDN router the Ascend is talking to. Even using multiple ip addresses for the ethernet would not require RIP, just more static entries. >For home and small offices they're tolerable, but for anything more >serious I'd prefer a solid ISDN card or TA on a sync serial port under >one of the source-available *BSDs. I'd go one step further and say that for anything serious I would use a cisco 25xx or better.. :) -Andrew -- ============================ Real 32bit multi-tasking UN*X System Andrew Gillham | TCP/IP,NFS,PPP,4.4BSD-lite,multi-user gillham@andrews.edu | i386,sparc,alpha,mac68k,amiga,others LAN/WAN/NW/UN*X specialist | ---> http://www.NetBSD.org <---