RE: VPN

["Mark Knecht" <mknecht controlnet com>]

> >    Help!!! ;-)
>
> Ahhhhh!  First off, it rather depends on which M$ OS you're running.
> The VPN clients for 98 and ME don't support encryption.  The ones for
> W2K-based stuff (XP/2K/2003) use L2TP and IPSEC encryption mechanisms,
> so make sure your Linux VPN uses the same stuff.  If you can tell us
> which Linux VPN stuff you're using, perhaps I can help more.
>
> For some interesting stuff, see:
>
> 	http://www.trellisnet.com/Security/Microsoft/vpn.asp
> 	http://rucs.rutgers.edu/vpn/vpn_files/os_clients.php3
>

Rick,
Win XP.

I'm not using ANY Linux VPN stuff as none of it seems to address this issue
for me. I really only converted to 90% Linux in my home recording studio 6
months ago, and since I still need Windows XP to run Pro Tools (audio
recording software) I just use that box to do my VPN connection back to the
office. However, I'd like to move that function completely away from the XP
box since my understanding is that not only am *I* connected to my worksys,
but every hacker attached to the worksys network is now connected to my XP
machine! I don't want an hacker that gets access to my work network to see
my XP box in any way shape or form!

So, how can I duplicate, under Linux, the basic operation I showed in my
version of your diagram? If I have a VNC server on worksys, how can I tell
homesys1 to attach itself to the worksys network so I can run a VNC viewer
on my home network and see it? How can I run a local copy of Mozilla, but it
sees a private web server running inside of worksys3? Both of these are
trivial with M$'s VPN client, but doing the same thing eludes me under
Linux.

It is perfectly OK for my homesys machine to not have access to local
resources when I do this. That's all M$ gives me when I use their client.
(as far as I know...) However, I would have thought some Linux guru would
have written something that only made processes started in a specific xterm
be connected, so that I could run this client in a specific xterm, and then
Mozilla started in that specific xterm would be connected to worksys, while
apps running outside of that xterm on homesys1 would still have access to
local resources.

Cheers,
Mark