On Oct 29, 2007, at 7:30 PM, Mel Wade wrote: > <clip> > No, it's not possible, as all the traffic is, indeed, coming from > one box: > the ltsp server itself. > </clip> > > Well, It's obviously possible because Citrix found a way to do it. > How > difficult it may be would be another question. They obviously > found a way > to associate each session with an IP address from a pool. Here's a > troubleshooting doc that may give some insight into the process: > http://support.citrix.com/article/CTX111898&searchID=-1 > > Mel
2 things come immediately to mind... Local app IP tunneling Local app is obvious (my entire ENV is local app)(just because I can). It gives me the best of both worlds and meets my needs. YMMV in making this a viable solution for other sites. IP tunneling would be a bit more unique... I would think some type of socket connection is assigned that would go back to the diskless. A quick way might be setting http_proxy_server in the user env to be the actual diskless client running a simple tcp redirection back to the real proxy. A combination of bash and perl should get the job done, but IP tables on the diskless might be lighter weight for those of you who are cpu constrained. You would need to set the IP address of the diskless in the xserver (can LDM set env variables for the user to inherit like KDM?). A third, heavy, and very bad alternative in my opinion, would be to utilize some manner of virt interface that is auto-configed on user login. then bind all outgoing requests to that IP. Much more difficult and best implemented in kernel space. AKA beyond my ability. FWIW I have been lurking here for about a year now. I have seen requests like this worked out and included in the actual LTSP. If I remember correctly LDM in C is just one example. If we make it work we ALL win. Climbing off the soap box... I have finally managed to roll out my first "commercial" LTSP ENV. I have migrated 15 full systems running M$ to 4 heavy LTSP running local apps. Estimated $ savings in software (lic and support) is estimated at $15K/y. Labor costs > $45k/y (avoided hiring full time support). Everyone wins except M$ (i was the $45K and just kept my current position ;-) All that to say "thank you for LTSP 5." Jaysen O'Dell. ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _____________________________________________________________________ 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
