Linux tip.

[n0cmonkey]

Never remotely reboot a Linux machine to test something if you have grub setup to boot into Windows...

 

[Noema]

 

[KIRBYEE]

Or try to configure your firewall over a SSH-connection when the computers are miles away.

 

[n0cmonkey]

Originally posted by: KIRBYEE
Or try to configure your firewall over a SSH-connection when the computers are miles away.

I've done that.

Successfully too.

/etc/init.d/iptables start && sleep 10 && nohup /etc/init.d/iptables stop

 

[Goosemaster]

Originally posted by: n0cmonkey

Originally posted by: KIRBYEE
Or try to configure your firewall over a SSH-connection when the computers are miles away.

I've done that.

Successfully too.

/etc/init.d/iptables start && sleep 10 && nohup /etc/init.d/iptables stop

I too have locked myself out

That's why it's good to have a good host that can TTY into the badboy for ya.

 

[Zolty]

I actually did the opposite, rebooted windows remotely and the system booted into ubuntu w/o vnc set up.

 

[n0cmonkey]

Originally posted by: Zolty
I actually did the opposite, rebooted windows remotely and the system booted into ubuntu w/o vnc set up.

That's why god invented OpenSSH.

OpenSSH > *.

 

[drag]

haha.

Screen + OpenSSH.

That way you can reconfigure network interfaces remotely without the phear. At least as long as you know your doing it right.

 

[drag]

You know what is scary?

Installing a entire operating system over ssh.

Here is what you do:
Boot up a knoppix cdrom.
Make sure ssh server is running.
Now go to work.

At work when it's slow, ssh into knoppix.
Install the latest version of debootstrap.
follow the directions:
http://d-i.alioth.debian.org/manual/en.i386/apds03.html#id325096
Make sure that the network is going to be configured correctly, make sure that openssh is installed and ready to go.

Reboot.

Wait 5 minutes.
delete the entry in ~/.ssh/known_hosts for the knoppix install.

ssh into your new install.

I have had that work maybe 1 out of 3 times. It's always stupid little things. But it's great when it does work.

 

[nweaver]

Originally posted by: Goosemaster

Originally posted by: n0cmonkey

Originally posted by: KIRBYEE
Or try to configure your firewall over a SSH-connection when the computers are miles away.

I've done that.

Successfully too.

/etc/init.d/iptables start && sleep 10 && nohup /etc/init.d/iptables stop

I too have locked myself out

That's why it's good to have a good host that can TTY into the badboy for ya.

Had a remote host having MAJOR issues...finally sent one of our techs out to check it (I felt like it WAS NOT my firewall script). Turns out the darn techs in the data center didn't PUSH THE CABLE IN UNTIL IT CLICKED!!!

that's ok though, we didn't pay for those 3 weeks.

 

[Goosemaster]

Originally posted by: nweaver

Originally posted by: Goosemaster

Originally posted by: n0cmonkey

Originally posted by: KIRBYEE
Or try to configure your firewall over a SSH-connection when the computers are miles away.

I've done that.

Successfully too.

/etc/init.d/iptables start && sleep 10 && nohup /etc/init.d/iptables stop

I too have locked myself out

That's why it's good to have a good host that can TTY into the badboy for ya.

Had a remote host having MAJOR issues...finally sent one of our techs out to check it (I felt like it WAS NOT my firewall script). Turns out the darn techs in the data center didn't PUSH THE CABLE IN UNTIL IT CLICKED!!!

that's ok though, we didn't pay for those 3 weeks.

:beer:

 

[xSauronx]

Originally posted by: nweaver

Originally posted by: Goosemaster

Originally posted by: n0cmonkey

Originally posted by: KIRBYEE
Or try to configure your firewall over a SSH-connection when the computers are miles away.

I've done that.

Successfully too.

/etc/init.d/iptables start && sleep 10 && nohup /etc/init.d/iptables stop

I too have locked myself out

That's why it's good to have a good host that can TTY into the badboy for ya.

Had a remote host having MAJOR issues...finally sent one of our techs out to check it (I felt like it WAS NOT my firewall script). Turns out the darn techs in the data center didn't PUSH THE CABLE IN UNTIL IT CLICKED!!!

that's ok though, we didn't pay for those 3 weeks.

the company I work for bought a smaller wisp down near wichita at the beginning of the year. part of the buyout agreement required the previous owners to a little infrastructure work to keep the current customers with service.

they were to move up a radio acting as a backhaul, because the signal was bad, and run a new cat5 line for it. i was sent .....well, im not sure why, as it turns out. they didnt listen to me, and i didnt do anything since they spent the day on a tower.

instead of running a line....they coupled it, 80' up, with a dinky cat5 coupler and a makeshift weatherbox. i told them it was a bad idea, and since they were having to go up, it wouldnt take any effort to just tie the cat5 line to their belt.

noooo...they coupled it.

it didnt work, it was almost 6 when they got down...they went home. customers were displeased, which is typical. they were losing customers left and right because of their lousy service.