Hi Anselm
> Good point! For X, any secure link should be OK.
> I'd not recommend dhcp over such setup, if you can get it another way.
> In most cases, a small (386) box for tftp serving and dhcp should be
> enough in the "branch office", while the X programs (LTSP server) can
> be linked via internet, T1 or whatever.
So, if i put dhcp and tftp on the client network, he will have access to
ltsp server without modification on routers (passing broadcasts).
All action going on inside intranet
|--router|--dhcp--|
| |-ltsp.client
| ....
ltsp.server-|
|--router|
|----dhcp--|---ltsp.client
|---ltsp.client
.....
-------------------------------------------------------
This SF.Net email sponsored by: Parasoft
Error proof Web apps, automate testing & more.
Download & eval WebKing and get a free book.
www.parasoft.com/bulletproofapps
_____________________________________________________________________
Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto:
https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help, try #ltsp channel on irc.freenode.net
