[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Help Please: Network Down



hjvm@freenet.de wrote:
> On 24 Apr 2005 at 12:42, Marc Shapiro wrote:
> 
> > As of yesterday (April 24) my home network has stopped working.  It WAS working the day before.  I am running Sarge and I did do an upgrade.  I don't remember seeing anything that I would expect to affect the network, but I also don't remember just what it did say was being upgraded.
> > I am no longer able to ssh between my two boxes.
> > Although my gateway box will dial in to my ISP if I access it directly, it does not pass anything on to my desktop box.
> > The gateway box is running Woody and has not been upgraded within the timeframe of this problem.
> > Has anyone else had this problem?
> Yes. I installed Sarge on a Laptop and sometimes the network goes down randomly. At
> least, I can't figure out why.
> 
> > Any ideas on how to fix this will be appreciated.  I am sending this from a Windows laptop and would like to get back to my desktop machine.
> > The error that I receive from ssh, /etc/hosts, and output from dmesg from my desktop box follow:
> > mns@xander:~$ ssh mareschal
> > ssh: connect to host mareschal port 22: No route to host
> > mns@xander:~$
> This is exactly my error message. I think it can have several reasons. In my case it's the
> firewire card (eth1) that takes over the network card (eth0), I don't know how this
> happens. But in my case the fix is relatively easy. I do as root
> ifconfig
> 
> Something like eth0 or eth1 should show up. If you have a Protocol:UNSPEC
> something is wrong. You can try a combination of
> 
> ifconfig eth1 down (if this is the wrong card) and then
> ifconfig eth0 up (if this is the right card).

*** 
I appologize for the initial double post.  I'm not sure how that happened.  I blame either Windows, or the lousy webmail interface that I am forced to use until I get this problem fixed. 
***

According to ifconfig eth0 and lo are up on both the gateway and the desktop machines.  The outputs of ifconfig follow:

Desktop:

eth0      Link encap:Ethernet  HWaddr 00:11:5B:1B:8F:1F  
          inet addr:192.168.0.3  Bcast:192.168.0.255  Mask:255.255.255.0
          inet6 addr: fe80::211:5bff:fe1b:8f1f/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:534 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 b)  TX bytes:22764 (22.2 KiB)
          Interrupt:19 Base address:0xe400 

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:230 errors:0 dropped:0 overruns:0 frame:0
          TX packets:230 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:19436 (18.9 KiB)  TX bytes:19436 (18.9 KiB)



Gateway:

eth0      Link encap:Ethernet  HWaddr 00:40:05:73:C8:11  
          inet addr:192.168.0.1  Bcast:192.168.0.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:3 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100 
          RX bytes:0 (0.0 b)  TX bytes:180 (180.0 b)
          Interrupt:10 Base address:0x300 

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:3924  Metric:1
          RX packets:18 errors:0 dropped:0 overruns:0 frame:0
          TX packets:18 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:1784 (1.7 KiB)  TX bytes:1784 (1.7 KiB)


-- 
Marc Shapiro



Reply to: