I'm using a trial version of F-Secure SSH. I've tried connecting to my linode using both of the eth0 IP's and using the default SSH /port 22. Each time it tells me the host is unreachable. Obviously it isn't connecting in order to attempt authentication, but I tried my main linode un/pass as well as my root/pass.

I know you mentioned that SSH should start automatically on the big distros, but perhaps it isn't.

Ok, after digging around a little - I realized the (host) kernel needs to be updated - its compiling now, should be installed in a few minutes (after a reboot).

The problem with the old kernel is that it didn't allow DHCP traffic over the ethernet bridge. The newer bridge code allows this.

So, networking wasn't getting configured, BUT you should have still be able to SSH into the host (host2.linode.com in your case), log into the host with your Linode Members username/pass, and then you should have seen your Linode's console login prompt, where you'd use your root/pass.

Ok, I was able to login using the dns. It would probably be best to use the dns anyhow, in case the IP changes.

Ok, rebooted - something is still screwed up.

You might have been able to get in via Lish, but DHCP and my iptable rules don't seem to be working on the Linode 128/host2 server.

Still digging into this. This problem doesn't exist on host1 (Linode 64).

Glad that I signed up for the big boy then.. I tried to sign up for the highest linode, but was unable to do so.. At least you're getting to put host1 and host2 through their paces. =)

Ok, I didn't have tun/tap utilities installed, so it wasn't creating the network device before launching your Linode.

Networking and DHCP should be working fine on host2 now.

Hmm. For some reason, I cannot log in using either the DNS or the IP address of my linode.

It was working earlier this morning with the DNS host2.linode.com.

Here is the screen cap of what I saw when attempting to log in.

[awest@host2] Wed Jun 4 13:53:13 EDT 2003
[awest@host2] Linode.com Console Access starting...
[awest@host2] There is no screen to be resumed matching awest.
[awest@host2] Closing Connection

Ahh crap. Scrap the previous post...

My linode is powered off. I'm guessing you reboot host2 and thus all linodes on host2 need to be cycled. =)

Actually, I have a shutdown/startup script which remembers which Linodes were running when the cluster software was shutdown.

It then adds a job with a date of 1974-01-01 (so it's definately NEXT) in the job queue to reboot the last profile.

But, I've been screwing around with that machine. I'm sorry about the cycles! I did figure out a few things, though.

It's interesting how many different scenarios you guys have uncovered already!

The reboots should stop, for now at least ... BTW, you should be able to SSH directly into your IP address, by-passing my little console tunnel.

You know, I now remember reading about you creating that "smart" script. Guess it didn't catch mine and reboot it though.

>>It's interesting how many different scenarios you guys have uncovered already!

Good!

And yes, once I rebooted my linode I was able to SSH directly albeit I am using the DNS and not the IP.

I had to kill the processes because it needed to start anew with some changes I made.



What domain-name/address are you SSHing into?

host2.linode.com

BTW, you can get my AIM and MSN IM handles out of my profile. =)