Hello Michel, Monday, February 03, 2003, 10:13:31 AM, you wrote:
MvH> [...Introduction...] MvH> [...Present Situation...] MvH> The future situation: MvH> The way we think it should work is that the remote sites have a xDSL MvH> connection to the internet and thru VPN tunneling connect to our LTSP MvH> server(s) with dumb clients. We have a 2Mbit SDSL line at our site. The question is what the VPN tunneling device on the client side should look like. MvH> I know it works for W2K terminal services (no citrix) because I control a MvH> few machines from home that way, and the speed is workable considering the MvH> overhead of W2K. MvH> The question is, did we propose something that can't be realised? Should we MvH> tell the client it's a "no go"? Of course it can do. Let's assume one customer site looks like this ClientPC1 --\ ClientPC2 --+--- LAN 10.0.a.x --- LocalServer --- xDSL line ClientPC3 --/ (a: 1-255, for each site) Where LocalServer takes the task of tunneling packets via VPN and is necessary anyway. I cannot report what CPU you need to tunnel an average 512k SymDSL e.g., but just guess any P2 machine could handle the load (comments, anybody?). You would have to setup a small linux there (my favorite would be Debian, but that's up to you), and in addition, for LTSP to work, there must be the files the client-PCs boot from and a dhcp server (that cannot be relayed over internet, no) - perhaps you want an ssh access to the LocalServer's and sync the /tftpboot directory. Probably it would be reasonable as well to have the /opt/ltsp/i386 hierarchy on the LocalServers as it speeds up the boot process. You could sync them as well, but in most cases the only changes you will do inside that directory would be to adapt lts.conf for additional terminals. Then, do NOT run an xdm on the LocalServer. Let's assume your Server Network looks like xDSL 2MBit --- VPNGateway/Firewall... --- Servers (10.0.0.1-199) Then make your clients use the 10.0.0.1 server (or whichever you like). In your case, I would make a testrun for performance, as too slow packet transmission could disnerve your customer... Mouse moves ok, but reaction for a mouseclick takes 12 seconds... ummph... (But that highly depends on your internet connection) MvH> If this is zillioned time it is asked just point my nose in the right MvH> direction and I will read on and don't bother you with this question MvH> anymore. :-) There were questions like this before, but I cannot remember them being answered fully. You have the mission to write a howto when finished!? Let us know anyhow. Best regards, Anselm mailto:[EMAIL PROTECTED]
smime.p7s
Description: S/MIME Cryptographic Signature
