Article View: comp.os.linux.networking
Article #29Re: Help: ISDN and firewall
From: Allen Todd
Date: Sat, 27 Jan 1996 02:51
Date: Sat, 27 Jan 1996 02:51
56 lines
3026 bytes
3026 bytes
In article <4e866r$riv@superb.csc.ti.com>, Bob Peterson <peterson@csc.ti.com> wrote: >In article <31052904.225B@boeing.hq.nasa.gov>, Chris Kleiman <ckleiman@boeing.hq.nasa.gov> writes: >|> H J Lu wrote: >|> ><snip> >|> > 4. To access our Class C network from the outside, we should be able to >|> > login on the firewall machine and go from there. >|> > >|> > H.J. >|> >|> quite frankly, I'd be reluctant to let any access through the firewall. > > Agreed. The only way I would allow outside access though our firewall would be using one-time passwds -- we use SecurID, but there are several other solutions including the freely available S-Key. allen@botcc.com > >|> the last place I worked at went with a separate dial-in connection >|> instead; nothing was allowed through the firewall, and that was exactly >|> the way I liked it. You can set up a decent ISDN dial-in solution w/out >|> exposing your firewall; unless your doing a lot of long distance calls, >|> that's what I would recommend, for what it's worth.;-) > > Except that the ISDN solution won't work when traveling. Most of my >dial in happens from out of town. Another option might be to contract >with a private network, e.g., Compuserve, and establish a connection >from their net to the company LAN. This addresses the out of town >situation, but (usually) without the bandwidth provided by ISDN. > > On a few occasions we've actually intalled an ISDN line for a one day >demo. It actually worked! (I was afraid the telco wouldn't get the >switch configuration right.) > > Another option, appropriate in some situations, is to establish a >server connected to the Internet completely separate from the company's >internal LAN. This can support some needs, such as demonstrations, but >probably won't suffice for checking email. An "outdial" capability on >such a system, configured to use a hard wired connection, could enable >terminal sessions. > >|> Fefe Kleiman > > Bob >-- >Bob Peterson Work: peterson@csc.ti.com Expressway Site >Texas Instruments Home: peterson@mail.zgnews.com North Building >P.O. Box 655474, MS238 TIMSG: RWP Voice: +1 214 995 6080 Aisle A4 >Dallas, Tx USA 75265 Fido:1:124/5148 FAX: +1 214 995 0304 2-88V97
Technical Details
Message-ID:
<DLtJxq.J1r@midway.uchicago.edu>Path:
arc1-ca.pugleaf.net!vixen.cso.uiuc.edu!uchinews!cicero!psyche!spcapt1References:
<4deaub$nll@aurora.romoidoy.com> <4dgk7n$qj6@aurora.romoidoy.com> <31052904.225B@boeing.hq.nasa.gov> <4e866r$riv@superb.csc.ti.com>Show Full Headers
Complete Article Headers
Newsgroups: comp.os.linux.networking,comp.security.firewalls,comp.dcom.isdn,comp.os.linux.hardware Path: arc1-ca.pugleaf.net!vixen.cso.uiuc.edu!uchinews!cicero!psyche!spcapt1 From: spcapt1@psyche.spc.uchicago.edu (Allen Todd) Subject: Re: Help: ISDN and firewall X-Nntp-Posting-Host: cicero.spc.uchicago.edu Message-ID: <DLtJxq.J1r@midway.uchicago.edu> Originator: daemon@cicero.spc.uchicago.edu Sender: news@midway.uchicago.edu (News Administrator) Organization: Social Sciences and Public Policy Computing References: <4deaub$nll@aurora.romoidoy.com> <4dgk7n$qj6@aurora.romoidoy.com> <31052904.225B@boeing.hq.nasa.gov> <4e866r$riv@superb.csc.ti.com> Date: Sat, 27 Jan 1996 02:51:25 GMT