Thanks Charles.
Some more questions.
I don't want anyone accessing my servers without an encrypted connection.
So as you said I will need IPSec or other VPN solution on my office LRP.
1) What components do I need? I undertand freeswan is an IPSec "daemon", is this
true? So, will I need client software? Can I use plain W98 to access through an
IPSec LRP?
2) What protocol does M$ VPN use? I would like my remote users to access my
Terminal Server using just the Terminal Server software and out of the box M$
software. Is this possible?
3) In order to have an "static or permanent encrypted" (sorry about the terms)
connection between two LRPs, I would need IPSec on both od them. Is this
practical, doable?? Hints please.
4) Is there some easier wy to do this??? Am I on track??
Thanks
Sergio Morilla
> -----Mensaje original-----
> De: [EMAIL PROTECTED]
> Enviado el: Tuesday, July 03, 2001 11:27
> Para: [EMAIL PROTECTED]
> Asunto: Re: [Leaf-user] IPSEC, VPN et al
>
> > I have two LRP (Eigerstein), one at work, one at the office.
> > I would like to be able to connect my home W98 to my office network.
> > So far I'm using ssh at both LRP so I can admin them remotely. So far so
> good!!
> >
> > Home ------------ ------------
> > ----------- Office
> > -----------------| LRP 2 |-------( internet )----------|
> LRP
> > 1|--------------
> > Network ----------- ------------
> > ---------- Network
> > |
> > |
> > ---------------
> > | Remote |
> > | Users |
> > ---------------
> >
> > LRP 1 is an Eigerstein 2.2.16
> > LRP 2 is an Eigerstein 2.2.16
> > Remote users using any imaginable version os M$ OS
> > Computers on Office Network are a mix of Netware and NT
> >
> > Now, there are some tasks I need to do at my office servers, so here are
> the
> > questions.
> > 1) Do I need to set up IPSEC on both machines in order to log in at my
> office NT
> > Terminal Server? This is a computer
> > behind LRP2 talking to a computer behind LRP1
>
> You don't need IPSec at all to log into terminal server. If you want the
> terminal server data encrypted as it passes through the internet, you will
> need IPSec (or some other VPN solution) on both ends. You can run IPSec on
> the LRP boxes, windows boxes, or wherever you want, as long as you're using
> IPSec implementations that interoperate, and you've got one on each end.
>
> > 2) If a remote user (connected to internet somewhere on the world) needs
> to
> > access this Terminal Server, what software does he need? This is through
> LRP1
>
> Obviously the Terminal Server client, and whatever VPN software you decide
> you need, if any. If you use IPSec, there are many clients available for
> windows, but most cost money.
>
> > 3) What will be the easiest way to accomplish this? My objective is to
> access
> > the computers behind LRP1 with the minimal installation/configuration on
> > travelling computers. So there is a lot few thing an user can break.
>
> Can't help you here...there are MANY different ways to set this up,
> requiring different knowledge and expertise, different amounts of money
> spent to purchase software, and many other factors. You'll have to read up
> on possible solutions and decide what makes sense for your particular
> situation.
>
> > 4) Some good reference on IPSEC, and other software needed will ve VERY
> > appreciates!!! How-TOs??
>
> For linux IPSec, see the FreeS/WAN site www.freeswan.org There are many
> example configurations and explinations.
>
> Charles Steinkuehler
> http://lrp.steinkuehler.net
> http://c0wz.steinkuehler.net (lrp.c0wz.com mirror)
>
>
> _______________________________________________
> Leaf-user mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/leaf-user
>
>
_______________________________________________
Leaf-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/leaf-user
