ARGH.

So I was working on a backup script on a remote debian backup server via console SSH.

I couldn't travel the private network of 10.0.0.x to a different campus on 10.0.x.x Ahhh.. I set netmask wrong. Oops silly me. It was 255.255.255.0 D'oh No problem.

I mosey over to /etc/network/interfaces and change it to 255.255.0.0 Aha! Should work fine, no problem to get to 10.0.x.x


Just need to flush eth0... so like a genius I issue the command:

ifdown eth0

(ssh console freezes)

Uhhh.... *smack head with a hammer I had laying next to me*


Don't do that. If nothing else, just REBOOT the dang server instead of "ifdown eth0" when you're far far away from the serve, and eth0 is the only way you can talk to it.

*sigh*

Use a nondescriptive title in ur post so people have no idea what ur issues are. Using descriptive titles will help you solve ur probs quicker. Read the forum rules

Err, maybe i didn't understand ur post

Still, I'm not sure this really belongs in here

No, I'm not asking for help...

I'm saying what NOT TO DO....

I'm just ranting. And passing on Lesson Learned:


E.g. if you're a long drive to the server and the only connection you have to it is via the server's "eth0" don't do an "ifdown eth0" when you just want to refresh your new netmask settings.



I know the solution.. and there really is only one: Drive for a hour to the server. Walk up to it, login into the console. become root.

"ifup eth0"

log out... walk out, drive a hour back home.

I don't have access to anyone locally there that can do it for me. Oh wellllllll..

But still, maybe it belongs in general

/etc/init.d/networking restart was the proper command instead of you using the ifdown.

I'll remember that next time Thank you!