On Sat, 19 Apr 2008 07:37:48 +0100 Bob Cox <[EMAIL PROTECTED]> wrote:
> > I'm sure that re-installing from scratch is unnecessary, but a re-flash > may be required I suppose (in "upgrade-mode" as you mentioned above). > > Good luck anyway. > > > > HAM Callsign G8JVM : Locator IO82SP > > 73 de G4AEL ;-) > N Thanks Bob The network scripts have the ip address as 192.168.1.77, in upgrade mode its responding to 192.168.0.1. I can ping that address, and I can telnet to port 9000, upslug2 cant find a slug in upgrade mode, but its sitting there with the top led flashing red. [EMAIL PROTECTED] debian-slug]# upslug2 -i di-nslu2.bin [no NSLU2 machines found in upgrade mode] [EMAIL PROTECTED] debian-slug]# ping 192.168.0.1 PING 192.168.0.1 (192.168.0.1) 56(84) bytes of data. 64 bytes from 192.168.0.1: icmp_seq=1 ttl=64 time=2.40 ms 64 bytes from 192.168.0.1: icmp_seq=2 ttl=64 time=0.992 ms 64 bytes from 192.168.0.1: icmp_seq=3 ttl=64 time=0.466 ms --- 192.168.0.1 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 1999ms rtt min/avg/max/mdev = 0.466/1.289/2.409/0.820 ms [EMAIL PROTECTED] debian-slug]# telnet 192.168.0.1 [EMAIL PROTECTED] debian-slug]# upslug2 -i di-nslu2.bin [no NSLU2 machines found in upgrade mode] [EMAIL PROTECTED] debian-slug]# ping 192.168.0.1 PING 192.168.0.1 (192.168.0.1) 56(84) bytes of data. 64 bytes from 192.168.0.1: icmp_seq=1 ttl=64 time=2.40 ms 64 bytes from 192.168.0.1: icmp_seq=2 ttl=64 time=0.992 ms 64 bytes from 192.168.0.1: icmp_seq=3 ttl=64 time=0.466 ms --- 192.168.0.1 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 1999ms rtt min/avg/max/mdev = 0.466/1.289/2.409/0.820 ms [EMAIL PROTECTED] debian-slug]# telnet 192.168.0.1 9000 Trying 192.168.0.1... Connected to 192.168.0.1 (192.168.0.1). Escape character is '^]'. Trying 192.168.0.1... Connected to 192.168.0.1 (192.168.0.1). Escape character is '^]'. At This point you can type anything but no response. I did find that the network scripts were not being invoked on start up so I've put the symlink back S40networking pointing to /etc/init.d/networking in RC3, RC4 and RC5. Dropping the telnet session ,stops any further attempt to telnet to it, but it can still be pinged. In normal mode it looks as if its booting, but it can't be pinged. I'll try adding a script in /etc/init.d to ping the host machine and watch the port with tcpdump. Any suggestions welcome -- Best Wishes Richard Bown ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Registered Linux User 365161 OS Mandriva x86_64 2008.0 Kernel 2.6.22.9-1mdv HAM Callsign G8JVM : Locator IO82SP QRV all bands 80mtrs to 3 cms ,( non WARC ) http://www.software-radio.org.uk ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ A computer is like a Native American Indian teepee, it has no gates, no windows and has an apache inside. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
