FreeNX Terminal Server Setup on SUSE 10 22
TRussell writes to tell us that Mad Penguin recently had the opportunity to review SUSE 10 and found that they had included the latest version of FreeNX on their installation media. FreeNX is a relatively new technology for remote display providing "near local speed application responsiveness over high latency, low bandwidth links." The article provides a nice guide on how to get it set up for several different operating systems.
Re:Application? (Score:2, Informative)
Re:Application? (Score:1)
HTH, HAND
Re:Application? (Score:2)
Re:Application? (Score:2, Interesting)
Re:Application? (Score:5, Informative)
Dialup is high latency, low bandwidth.
Dialup? Slow latency.
I think your confused here. Latency is the time it takes for a packet to reach its destination. (And get back if talking round trip time) Bandwidth is how much data can be transmitted per second. See here [wikipedia.org]
Re:Application? (Score:2, Funny)
Speed (Score:2, Interesting)
Is it just me or are the speed claims overblown by NX? I have run it between work and home and I really dont see any diff between VNC and NX. NX seems to need to totally refresh the screen like VNC does and what ever compresssion it uses seems to not give it any advantage. What are your thoughts?
Seraphim
Re:Speed (Score:5, Informative)
Basically, there's a server on my local network that's routed via two different machines and going over a VPN (our WAN has about 2500 customers on it..). With VNC, it's not too bad. If I grab a window and yank it around the screen, there are some redraw issues and it basically looks like a slideshow.
So, I decided to give FreeNX a try.
I'm using FC4 on both client and server. I simply grabbed some RPMS (easy to follow instructions) here [madpenguin.org], loaded them up and I was off and running.
First impressions: wow! holy crap! I can now grab a window and yank it around the desktop with near fluid speed. Everything is highly responsive. I'm a big fan of VNC and have used it for many years now, but I think it's time to switch.
Keep in mind that this test was made over a low latent connection and with decent throughput.
Re:Speed (Score:3, Informative)
Here are the Fedora instructions [fedoranews.org]
Re:Speed (Score:2)
Re:Speed (Score:1)
It goes through port 22, which is the proven SSH method and connects to user NX on the server, then redirect itself to it's X and pass it back, so no fancy new firewall hole or no need to put in your ssh forward or don't need to risk goin
Re:Speed (Score:1)
Setup? (Score:1, Informative)
Re:Setup? (Score:2)
Connection from the server to the client. (Score:2)