Great performance, OK for FTP type access, lousy for shell

There's likely a lot of Internet between you and Fremont. No one else has reported issues, so the problem is probably somewhere closer to you than it is Fremont.

Also, the private network is a secured LAN. A Linode can NOT sniff another Linode's traffic or spoof other Linode IP addresses. You don't need to encrypt traffic.

I suggest you give a different facility a shot - you may have better routes from your area to it. You can do this by adding another Linode, or we can move one if you shoot us a support ticket.

Thanks for your comments,

-Chris

You might want to consider something like screen to keep sessions persistent – this will prevent lost work when network outages happen.

Do you have any data on the network outages (e.g. from mtr or traceroute)? I'm not a Fremont apologist by any stretch, but that sounds very unusual. My ssh sessions (to Newark) typically last for days, if not weeks.

I'm in Freemont and other than that outage, I've not had any issues. I can and do have SSH sessions open for days without issue.

@waldo:

I'm in Freemont and other than that outage, I've not had any issues. I can and do have SSH sessions open for days without issue.
+1

I've had a 'node at Fremont since 2003 and regularly keeps SSH sessions open from the Netherlands without difficulties. That said, I use screen for things like system updates, just to be on the safe side.

Funkily, I do see network issues to Fremont… but only from certain places. It never drops out, but it has high latency. And it's intermittent. But if I use my HE IPv6 tunnels then it works just fine. traceroute and ping show no issues, so I'm sure why I sometimes see this latency. Very odd…

@sweh:

so I'm sure why I sometimes see this latency.
Well the Feds can only sniff traffic so fast…

Periods of high latency occur when your traffic is being routed via China for analysis.

@pclissold:

Periods of high latency occur when your traffic is being routed via China for analysis.
Haha, that actually happened a couple of times lately. They might even drop your connection if you transmit some random bits that happen to spell "The Dalai Lama".

@pclissold:

That said, I use screen for things like system updates, just to be on the safe side.

Is it dangerous to run system updates without something like screen?

@jzimmerlin:

@pclissold:

That said, I use screen for things like system updates, just to be on the safe side.

Is it dangerous to run system updates without something like screen? No.. it should complete on it's own.. what would be dangerous.. is to pull the plug on a server while it's running a update..

Also I'm on fremont, and never had a problem with client disconnecting, always been on my end. I sometimes keep my session open for days.. probably not the smartest thing to do though.. !

Hi their.

During my experinece (though I've only deploid in the Dalass datacenter and am in Arizona at present, I have never had an issue. But still.

I wouldn't pull a plug on a running server when an update or updates are in progres, because in general that will cause FileSystem issues.

But if you do have a lot of Internet between you and Fremont, that might cause some interesting issues.

Mrt like Caker pointed out combines ping and other stuff I think.

I believe the Linode library, has a colection of documents, one on network troubleshooting that might help.

Hope you find Linode still useable, I find the network that linode has period to be wonderful.

I think that they are quite good at communicating with datacenters when problems do occur.

Also, who ever heard of a provider that credits you for downtime that you don't cause yourself? I have not heard of one that does that other than Linode.

Although as far as the crediting for downtime I wonder if all NOdes would need to be down for twenty four hours or longer?

BTW, to get back on topic, about the screen program, that program can be handy. I've used it, myself as a blind fello Linode customer in the passed to maintain sessions. I just log out via ssh after detatching (control-a followed by D usually does that for you.

Then I get out, and I could come back days on end later, and still find screen running without an issue.

I like that program for many things.

Take care, and enjoy your Linode!