On Tue, 4 Jul 2006 22:40:17 +0200, Gert Stappers wrote > On Tue, Jul 04, 2006 at 09:20:38AM +0200, Svante Signell wrote: >> Hi, >> [ strange network problem on hardware that worked before ] >> >> The only command connecting to the network I found is wget. No ping, ssh >> etc. How to debug using wget only?
>Only limitted. >If wget works, you have a working network. It did not work! >If not, see I you can see a log entry on the server. >An entry means that that the cable is connected for the transmit part >and that you have trace why the recieve fails. I do not know where to find the log entry. Nevertheless, something like ifup/ifdown would be nice to have access to in the shell available with the installer. I did not know by heart the commands to use with ifconfig and route to take down the network interface and getting it up again. However, after finishing the crippled install without the network, the reboot made eth0 to work again. After the reboot the ifup/ifdown commands were available! Was the ifupdown package installed from the netinst CD in the first place? How come I did not get access to these commands in the installer shell? Later on when installing and upgrading packages the network stopped working showing problems with an interrupt for the ethernet card. Maybe this was the cause of malfunctioning during the install. After power down he network card works properly again :) Some conclusions and wishes: 1) Access to ifup and ifdown commands in the installer shell (ifupdown) 2) Ping would be nice to have (netkit-ping) 3) Reduce timeouts for trying to access the network. 4) Alternately, and better, implement a method to break the network attempts when failing. 5) The installer use two accesses to the network: Getting the Release file and setting up apt mirrors. If the network fails one should still be able to continue the install without the network. One should not have to wait for the two timeouts before entering to the install menu!! 6) Is it possible to have manpages available for the most important commands, or at least a file describing the commands (including vim-minimal and wget) and the most common switches? In practise doing anything requires another computer running with manpages available. >> (Maybe I should get the netinst iso file from the daily builds to get >> access to sid/unstable, but this is unimportant wrt the network.) > >Doing nothing, will change nothing. > >You reported that the hardware did work, >so give changing the software a chanche. See above, no need to burn a new netinst CD. > >> >> Thanks, > >Geert Stappers Please Cc: me, since I'm not subscribed! Thanks, Svante Signell -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
