Re: absurdly simple LAN problem

From: Alvin Oga (aoga_at_mail.Linux-Consulting.com)
Date: 09/15/05

  • Next message: mess-mate: "Re: bootsplash"
    Date: Thu, 15 Sep 2005 08:54:51 -0700 (PDT)
    To: Anthony Campbell <ac@acampbell.org.uk>
    
    

    On Thu, 15 Sep 2005, Anthony Campbell wrote:

    > On 15 Sep 2005, Thomas Adam wrote:
    > >
    > > --- Anthony Campbell <ac@acampbell.org.uk> wrote:
    > >
    > > > I've struggled with this one for months! Much perusing of HOWTOs and
    > > > googling hasn't helped.

    tooo much effort :-) ... but good .. thanx for trying so hard

    > > > I have two computers, desktop and laptop, and a wireless router and
    > > > ADSL
    > > > modem. Both machines reach the internet without problems, one via a
    > > > cable link to the modem, the other via a wireless link to the
    > > > router.

    did you configure the router ??

    > > > to the other though I can ping localhost on each. Turning off the
    > > > firewall (shorewall) does not help.

    ping localhost is 100% guaranteed to work ... as long as 127.0.0.1 is in
    /etc/hosts and you do use /etc/hosts in your /etc/resolv.conf

            - ping of it's own ip# will always work evenwith the ethernet
            cable disconnected

    what is your contents of /etc/hosts and /etc/resolv.conf

     
    > ac:~:$ route -n
    > Kernel IP routing table
    > Destination Gateway Genmask Flags Metric Ref Use Iface
    > 192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
    > 0.0.0.0 192.168.0.1 0.0.0.0 UG 0 0 0 eth0

    192.168.0.1 is presumably your router thru which you expect to get out
     
    > ifconfig -a:
    >
    > eth0 Link encap:Ethernet HWaddr 00:0B:2B:02:32:FB
    > inet addr:192.168.0.20 Bcast:192.168.0.255 Mask:255.255.255.0

    good ... your ip# is *.20

    > For laptop:
    >
    > Destination Gateway Genmask Flags Metric Ref Use Iface
    > 192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1
    > 0.0.0.0 192.168.0.1 0.0.0.0 UG 0 0 0 eth1

    good ... your gateway is the same *.1
     
    > ac:/usr/share/doc/shorewall:$ ifconfig -a
    > eth0 Link encap:Ethernet HWaddr 00:06:1B:DE:4B:CF

    bad .. this does NOT have an ip# assigned to it ...
    ===================================================

    > eth1 Link encap:Ethernet HWaddr 00:40:96:44:B5:A6
    > inet addr:192.168.0.22 Bcast:192.168.0.255 Mask:255.255.255.0

    good ... this is *.22

    > wifi0 Link encap:UNSPEC HWaddr 00-40-96-44-B5-A6-00-00-00-00-00-00-00-00-00-00
    > BROADCAST MULTICAST MTU:2312 Metric:1

    bad ... this does NOT have an ip# assigned to it
    /////////////////////////////////////////////////

    c ya
    alvin

    -- 
    To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org 
    with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
    

  • Next message: mess-mate: "Re: bootsplash"

    Relevant Pages

    • Re: Routing problem
      ... > this is the perliminary routing table I had: ... > Kernel IP routing table ... The default router for B is A. ... gateway fails. ...
      (comp.os.linux.networking)
    • Routing problem
      ... Kernel IP routing table ... B --> D: Fail ... The default router for B is A. ...
      (comp.os.linux.networking)
    • Routing problem
      ... Kernel IP routing table ... B --> D: Fail ... The default router for B is A. ...
      (comp.os.linux.setup)
    • Re: 3com ethernet card failure
      ... > Kernel IP routing table ... You have no route to your ISP. ... Or are you using a router? ...
      (comp.os.linux.networking)
    • Problem with route
      ... Pings to Internet from router are fine, ... Kernel IP routing table ... route on PC: ...
      (comp.os.linux.networking)