Re: VPN server -- MIDRANGE-L

I think your key phrase is "But they all work most of the time."
I don't want a "most of the time" solution.
Obviously our net tech failed to verify all parts of the connection.
Yes- we do require the Cisco proprietary tunnel.
He just "assumed" his Cisco router could be substituted for
the Bellsouth Cayman router. In this particular site he was told
his Cisco router would not work (with tunnel & vpn).
My only point was "assume nothing, verify everything".
jim

----- Original Message -----
From: "Jeff Silberberg" <jsilberberg@mindspring.com>
To: <midrange-l@midrange.com>
Sent: Tuesday, February 26, 2002 8:35 PM
Subject: Re: VPN server


> Jim,
>         Does not make a lot of sense.  The nature of VPN over DSL is just
> not router dependant, although many vendors have "proprietary"
> implementations of the standards when you use a tunnel between their
> products. Also, while many vendors do not "support" the circuit with out
> there hardware, that have no objection to your using your own gear, just
be
> prepared to do detail trouble shooting. BellSouth is a great example of
this
> I know of ADSL's with Cayman, Cisco, and Speedstream routers in the end
and
> none of them are quote supported. But they all work most of the time.  By
> the way I am partial to the Speedstream 5861 currently because it has the
> ability to do a PPP when the ADSL is down.
>
>         JMS...
>
> ----- Original Message -----
> From: "Jim Franz" <franz400@triad.rr.com>
> To: <midrange-l@midrange.com>
> Sent: Tuesday, February 26, 2002 8:10 PM
> Subject: Re: VPN server
>
>
> > I would verify with the dsl provider that they "fully support" what you
> are
> > doing with the
> > equipment you are doing it with.
> > Our network guy asked BellSouth if we could install the cheaper dsl
> > connection at a remote site in Miami, FL.
> > They said yes.
> > He asked - can we run VPN
> > They said yes.
> > He flew to Miami to install - didn't work!
> > Asked BellSouth why.
> > Answer - we support vpn on "our supplied routers", not your Cisco
> > routers-you didn't ask us that!
> > (and our routers don't support your Cisco vpn!)
> > Morale of this story - Verify the entire setup - routers, firewall,
ports
> > for traffic, etc.
> > jim
> >
> > ----- Original Message -----
> > From: "Chris Bipes" <chris.bipes@cross-check.com>
> > To: <midrange-l@midrange.com>
> > Sent: Tuesday, February 26, 2002 6:50 PM
> > Subject: RE: VPN server
> >
> >
> > > Well DSL is FAST in ONE direction.  Though the upload speed is 128K or
> > that
> > > of the ISDN line.  VPN does add lots of overhead to your network
> traffic.
> > I
> > > find DSL to be very reliable.  Brand new installation was only down
> twice
> > in
> > > the first year and has been rock solid for the last 6 months.  I would
> say
> > > our T1 dies about once a year, well we just changed ISPs so we will
see.
> > If
> > > the branch offices currently have internet access or need access, VPN
> > would
> > > be the way to go.  Private FR is more secure with PtoP leased lines
the
> > most
> > > secure you can get and be connected 24x7.  I would put DSL at one
> location
> > > and see how it works with VPN and add locations one at a time.
> > >
> > >
> > > Good Luck
> > >
> > > -----Original Message-----
> > > From: Steve Richter [mailto:srichter@autocoder.com]
> > > Sent: Tuesday, February 26, 2002 1:19 PM
> > > To: midrange-l@midrange.com
> > > Subject: RE: VPN server
> > >
> > >
> > > Our current topology is frame relay, cisco routers, T1 from central
> office
> > > to the frame cloud, branch offices use expensive and slow 64kb/128kb
> > > connections to the cloud.
> > >
> > > Any thoughts on replacing the cloud with router to router vpn over the
> > > internet ?
> > >
> > > Esp where less expensive, higher speed DSL is used to connect the
remote
> > > branches to the internet.
> > >
> > > Is DSL too unreliable for business use ?
> > >
> > > Thanks,
> > >
> > > Steve Richter
> > > _______________________________________________
> > > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
> > list
> > > To post a message email: MIDRANGE-L@midrange.com
> > > To subscribe, unsubscribe, or change list options,
> > > visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
> > > or email: MIDRANGE-L-request@midrange.com
> > > Before posting, please take a moment to review the archives
> > > at http://archive.midrange.com/midrange-l.
> > >
> > >
> >
> >
> > _______________________________________________
> > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
> list
> > To post a message email: MIDRANGE-L@midrange.com
> > To subscribe, unsubscribe, or change list options,
> > visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
> > or email: MIDRANGE-L-request@midrange.com
> > Before posting, please take a moment to review the archives
> > at http://archive.midrange.com/midrange-l.
> >
>
> _______________________________________________
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
> To post a message email: MIDRANGE-L@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
> or email: MIDRANGE-L-request@midrange.com
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>
>