Re: can't SSH, can't telnet, can't do nothing to Z

On Wednesday 12 November 2003 02:20 pm, you wrote:
> On Wednesday 12 November 2003 06:49 am, Reuben D. Budiardja wrote:
<snip>
> > I can't figure out where is the log message for all this activity.
> > So I plugged the Z's craddle back to Win2000 and was planning to
> > SSH to it for easier debugging. Now, I cannot even SSH, Sync, or do
> > anything with the Z from Win2000, which used to work before. What
> > in the world has gone wrong ??
> >
> > Someone please help. Thanks a lot in advance. Included below are
> > the kernel message from my Linux desktop (Redhat 7.3) when I plug
> > in Z into the USB.
>
> Reuben,

Hello,
Let us forget about my problem with the Win2000 desktop. I figure that out, 
somehow the IP address listed in Network & Sync got changed, and change it 
back to default fixed the problem. 
So for now on, Desktop = Redhat linux 7.3


> Can we start with finding out what you know?  What ROM are you running
> on your Z?  Is this an SL-5500 or SL-5600?

SL-5500, the ROM is the original that shipped with it. 

> What is the complete output of ifconfig on your Z and desktop?

Two things that I tried. First, using the CDCether module, the one that's 
automatically loaded by Linux, Second, using usbdnet module. 

Using CDCEther:
Nothing really happened, here is the desktop ifconfig:

eth0    [ Just my regular NIC card output ]

eth1      Link encap:Ethernet  HWaddr 40:00:02:00:00:01  
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100 
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:11341979 errors:0 dropped:0 overruns:0 frame:0
          TX packets:11341979 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:2311152634 (2204.0 Mb)  TX bytes:2311152634 (2204.0 Mb)

This way I cannot even ping 192.168.129.201. 

Then, I did
$> cat CDCEther >> /etc/hotplug/blacklist
$> rmmod CDCEther
$> insmod usbdnet

and have the following script in /etc/sysconfig/network-scripts/ifcfg-usb0:

BOOTPROTO=static
BROADCAST=192.168.129.255
IPADDR=192.168.129.201
NETMASK=255.255.255.0
NETWORK=192.168.129.0
DEVICE=usb0
NOZEROCONF=yes

I got there somewhere off  the net. Plugging the zaurus back in, I got this 
from ifconfig:
eth0     <snip>

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:11342627 errors:0 dropped:0 overruns:0 frame:0
          TX packets:11342627 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:2312497210 (2205.3 Mb)  TX bytes:2312497210 (2205.3 Mb)

usb0      Link encap:Ethernet  HWaddr 40:00:00:00:FF:16  
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100 
          RX bytes:0 (0.0 b)  TX bytes:130 (130.0 b)

Now, I can ping 192.168.129.201. When I try 
$> ssh 192.168.129.201 -l root

I got prompted password but then entering the root password for my desktop, 
which is the same for the Z, I see my desktop back, all my files in my 
desktop and everything. So it is as if usb0 is a loopback interface, which I 
thought is very very weird.

Both cases, the outpuf for ifconfig in Z is:

lo        Link encap:Local Loopback   
          inet addr:127.0.0.1  Mask:255.0.0.0 
          UP LOOPBACK RUNNING  MTU:16436  Metric:1 
          RX packets:10 errors:0 dropped:0 overruns:0 frame:0 
          TX packets:10 errors:0 dropped:0 overruns:0 carrier:0 
          collisions:0 txqueuelen:0  
          RX bytes:752 (752.0 b)  TX bytes:752 (752.0 b) 
 
usbd0     Link encap:Ethernet  HWaddr 40:00:01:00:00:01   
          inet addr:192.168.129.201  Bcast:192.168.129.255  Mask:255.255.255.0 
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1 
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0 
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 
          collisions:0 txqueuelen:100  
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b) 
 
> Especially what does your Z show?  Use the Terminal or Konsole app.
> Is sshd running on the Z (use 'ps aux'). 

Yes, sshd is always running on Z. I just plug it back in to win2000 desktop 
and I can ssh 192.168.129.201 right away.

>  Have you rebooted the Z?
Yes

Thanks for the help.
-- 
Reuben D. Budiardja
Department of Physics and Astronomy
The University of Tennessee, Knoxville, TN
---------------------------------------------------------
"To be a nemesis, you have to actively try to destroy 
something, don't you? Really, I'm not out to destroy 
Microsoft. That will just be a completely unintentional 
side effect."
                 - Linus Torvalds -