" Providing you have a single gateway on your network, and providing it is set up as the default gateway in dhcpd.conf, and providing that gateway has the hosts properly defined (or dns set up), then it should just work."
I totally understand, but this is an ideal situation. Maybe my experience has always been in less than ideal network setups. I have never had a network that was setup in this manner for the entire time I ran it. Legacy implementations die slowly, and often work-arounds upon work-arounds later are made that affect complex implementations like LTSP. My only point is that assumptions are made in the documentation (documentation is better now than when I installed the system last spring) which lead you in the wrong direction. Foundations must be laid correctly, and the network is the foundation for LTSP. If the network has any hiccups, or changes from the norm (Define: norm), LTSP will not work correctly (as advertised). This should be stated early on, so admins are looking in the right direction. If I had not been curious about the slowness of ssh logins and then arp requests on my Ubuntu+LTSP, I would not have asked the questions that lead me to the fact that even though static IP addresses are used, Host Files & DNS is still queried. Without these present you must wait for some timeout before the network app gets to using the static IP. A private IP host file fixed this problem. Many network apps utilize proxies, but not all. Those that can use a proxy did not have a problem on our network. Now we are looking at a single gateway that will solve our problems in the future. "I really do see this as a sticking plaster over serious issue." I agree, and I think you prove my point. Work-arounds are done to solve immediate problems, then we must discipline ourselves to ultimately fix the problems at hand. In the interim, complex software packages get a bad rap, because of the intricacies of individual networks and their legacy implementations. -- Thanks, Job Cacka -----Original Message----- From: Chris Roberts [mailto:c...@tridentgarages.co.uk] Sent: Thursday, April 30, 2009 2:25 AM To: ltsp-discuss@lists.sourceforge.net Subject: Re: [Ltsp-discuss] rdesktop lock ups On Wednesday 29 Apr 2009, Job Cacka wrote: > So after reading through your thread I would ask if you found any > documentation on how the routing should be setup. Specifically a best > practice for LTSP environments. I have seen other problems with LTSP > performance because we do not use an internal DNS, and ended up creating a > large host file that we propagate to the Thin Client with a script and run > on the server. However, in my four years experience of running thin clients > I have never seen a network admin's guide to providing the proper > foundation of services. I think there are unique situations with the > combination of services that LTSP requires for educating admins before they > get themselves into trouble. Providing you have a single gateway on your network, and providing it is set up as the default gateway in dhcpd.conf, and providing that gateway has the hosts properly defined (or dns set up), then it should just work. The issue for us, is that we have an additional gateway/router set-up inside our network, which needs to have the windows rdp traffic. The default gateway is set-up with a static route back to this gateway, so again it should just work. And it does for 15/20 minutes sometimes, and then it goes and drops a packet or two, just sufficient to break rdp. This just should not happen in a decent network, and I have got to get to the bottom of why this is happening. For the time being I have set up and RCFILE script to add the static route to the clients, and the problem has gone away. But I really do see this as a sticking plaster over serious issue. Ideally I would replace our ipcop firewall, with a multi-wan firewall, and move this router outside of our network. -- Chris Roberts +------------------+------------------+ | Distribution | Debian Etch | | LTSP Version | 5.1.10-1~40 | | Windows Manager | KDE 3.5.5 | | Kernel | 2.6.26-bpo.1-686 | +------------------+------------------+ | Distribution | Debian Lenny | | LTSP Version | 5.1.10-2 | | Windows Manager | KDE 3.5.10 | | Kernel | 2.6.26-2-686 | +------------------+------------------+ ---------------------------------------------------------------------------- -- Register Now & Save for Velocity, the Web Performance & Operations Conference from O'Reilly Media. Velocity features a full day of expert-led, hands-on workshops and two days of sessions from industry leaders in dedicated Performance & Operations tracks. Use code vel09scf and Save an extra 15% before 5/3. http://p.sf.net/sfu/velocityconf _____________________________________________________________________ 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 ------------------------------------------------------------------------------ Register Now & Save for Velocity, the Web Performance & Operations Conference from O'Reilly Media. Velocity features a full day of expert-led, hands-on workshops and two days of sessions from industry leaders in dedicated Performance & Operations tracks. Use code vel09scf and Save an extra 15% before 5/3. http://p.sf.net/sfu/velocityconf _____________________________________________________________________ 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
