Re: 5.1 Restore - can't telnet?

[Andy Ruhl <acruhl%gmail.com@localhost>]

On Sat, Nov 12, 2011 at 12:46 PM, Mark Benson <markbenson%mac.com@localhost> 
wrote:
> Hi. I just did a NetBSD 5.1 Restore on my Qube2 (which I just built a new 
> power supply and power plug for).
>
> Restore went great - VERY smooth operation - really nice to be able to just 
> 'do' it with no serial terminal etc.
>
> I changed the IP, netmask, default route to match my LAN once I had it hooked 
> up using the panel (I prefer a fixed IP).
>
> That went fine, I can now ping the Qube2 from another box.
>
> $ ping 192.168.1.103
> PING 192.168.1.103 (192.168.1.103): 56 data bytes
> 64 bytes from 192.168.1.103: icmp_seq=0 ttl=255 time=0.704 ms
> 64 bytes from 192.168.1.103: icmp_seq=1 ttl=255 time=0.472 ms
> 64 bytes from 192.168.1.103: icmp_seq=2 ttl=255 time=0.568 ms
> ^C
> --- 192.168.1.103 ping statistics ---
> 3 packets transmitted, 3 packets received, 0.0% packet loss
> round-trip min/avg/max/stddev = 0.472/0.581/0.704/0.095 ms
>
> All good.
>
> I can't telnet to the box to continue my setup/secure the box though?
>
> $ telnet -l root 192.168.1.103
> Trying 192.168.1.103...
> Connected to 192.168.1.103.
> Escape character is '^]'.
> telnetd: Authorization failed.
> Connection closed by foreign host.

For the heck of it, did you just try:

telnet 192.168.1.103

I'm not sure why this would work though. I think I used rlogin on mine
when I used the restore CD. That might work.

>
> That's what I get back. I'm guessing I need to telnet as root? I can't 
> remember how to do it. I thought -l root would map 'root' as the user but I 
> might be wrong?
>
> This isn't documented anywhere I can find it. The RestoreCD HowTo gives the 
> impression it should 'just work' which it does... but...
>
> Oh also, when I serial console the box I get a db> (debugger?) prompt not a 
> login? What gives? That used to work :\

Yeah, this is because your serial terminal program might be sending
"break" to the console, which tells NetBSD to go into the debugger.

You might be able to type "continue" at the db prompt and get back to
a login prompt.

Put this in the /etc/sysctl.conf file to prevent the serial terminal
from doing this:

ddb.fromconsole=0

Andy