From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1GcQXC-0008Tc-Ib for garchives@archives.gentoo.org; Tue, 24 Oct 2006 17:57:55 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.8/8.13.6) with SMTP id k9OHsOke017805; Tue, 24 Oct 2006 17:54:24 GMT Received: from wr-out-0506.google.com (wr-out-0506.google.com [64.233.184.236]) by robin.gentoo.org (8.13.8/8.13.6) with ESMTP id k9OHpo3l001332 for ; Tue, 24 Oct 2006 17:51:50 GMT Received: by wr-out-0506.google.com with SMTP id 67so586813wri for ; Tue, 24 Oct 2006 10:51:50 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=e6mmYqzXIF5w9+9ncTOlrUfn7rddtMec3cOoLLolXU131LWCMSP3skkpsu6gClDQ36tKHB0EteOwKDgtC2U4nl1MbTH5MVr9tpYp6sRWQLhp9uuqc61YsLveQUaOPDItJ5DCRvC4XgwNL7yHMXwS2S8i/GyfcziY7jBYLsbKRiM= Received: by 10.78.170.17 with SMTP id s17mr9669188hue; Tue, 24 Oct 2006 10:51:48 -0700 (PDT) Received: by 10.78.128.3 with HTTP; Tue, 24 Oct 2006 10:51:48 -0700 (PDT) Message-ID: <49bf44f10610241051k23576055t35703bff160ee790@mail.gmail.com> Date: Tue, 24 Oct 2006 10:51:48 -0700 From: Grant To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Re: Wireless trouble, bad hardware? In-Reply-To: <49bf44f10610232026n33dde26ax19a47e3cd3086145@mail.gmail.com> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <49bf44f10610231804s1c558ea3h8f2dcd8dce0d30e7@mail.gmail.com> <49bf44f10610231813n7d612f49sa34fae0c2e6a76b9@mail.gmail.com> <2354.210.55.22.193.1161654011.squirrel@drgnfire.is-a-geek.com> <49bf44f10610231900r6052fb8fr97cd1110095e6d88@mail.gmail.com> <3090.210.55.22.193.1161656613.squirrel@drgnfire.is-a-geek.com> <49bf44f10610232026n33dde26ax19a47e3cd3086145@mail.gmail.com> X-Archives-Salt: 153bd0db-3cf6-4edb-a349-6d5bfd63080a X-Archives-Hash: 5bc7195307a063f557c338c4ad2a706f > > >> What WAN Address? I cannot see any address other than one of the > > >> reserved > > >> class C's. I would suggest that either the PC you are pinging from > > >> ("desktop") does not have an address in the same range as the router, or > > >> the default gateway is incorrect on the "desktop". Another possibility > > >> is > > >> a an IP conflict but this is less likely. > > >> Can you possibly post the IP configuration (ifconfig) from the "desktop" > > >> machine so that we can see how the interface is set up. > > > > > > After rebooting the desktop, all I get from ping attempts is: > > > > > > connect: Network is unreachable > > > > > > so I guess it won't connect at all now. I don't think ifconfig would > > > be useful now, but let me know if I'm wrong or if you have any other > > > ideas. > > > > The output of ifconfig would certainly be useful but it sounds to me like > > the configuration of eth0 has been changed somehow. > > Perhaps you could post the output of ifconfig, and the contents of > > /etc/conf.d/net as this should list the configuration of all of the > > network adapters (just in case eth0 is not the interface that you are > > using). > > > > Hopefully this information will allow someone on the list to help you > > diagnose your problem. > > I'm connected directly to the DSL modem/router via eth0 right now. > This is not normal and I'm only connected like this so I can get > online to write this message. I'm usually trying to connect via ath0 > to the Gentoo router which is then connected to the modem/router. > Here is my current ifconfig: > > ath0 Link encap:Ethernet HWaddr 00:0F:B5:86:C0:E1 > inet6 addr: fe80::20f:b5ff:fe86:c0e1/64 Scope:Link > UP 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:0 > RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) > > eth0 Link encap:Ethernet HWaddr 00:16:17:76:37:82 > inet addr:192.168.1.2 Bcast:192.168.1.255 Mask:255.255.255.0 > inet6 addr: fe80::216:17ff:fe76:3782/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:967 errors:0 dropped:0 overruns:0 frame:0 > TX packets:868 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:743136 (725.7 Kb) TX bytes:243477 (237.7 Kb) > Interrupt:169 Base address:0xd800 > > 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:0 errors:0 dropped:0 overruns:0 frame:0 > TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) > > wifi0 Link encap:UNSPEC HWaddr > 00-0F-B5-86-C0-E1-80-79-00-00-00-00-00-00-00 -00 > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:7782 errors:0 dropped:0 overruns:0 frame:3492 > TX packets:1561 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:199 > RX bytes:742503 (725.1 Kb) TX bytes:71806 (70.1 Kb) > Interrupt:161 Memory:ffffc20000100000-ffffc20000110000 > > and /etc/conf.d./net : > > modules_ath0=( "wpa_supplicant" ) > wpa_supplicant_ath0=( "-Dmadwifi" ) > config_ath0=( "192.168.0.3 netmask 255.255.255.0 broadcast 192.168.0.255" ) > routes_ath0=( "default via 192.168.0.1" ) > essid_ath0=( "network2" ) > > although I currently have a couple eth0 lines so I can connect to the > modem/router. They aren't usually there. > > I must admit I don't know what the broadcast and netmask are and they > are set the same for the Gentoo router and the laptop that connects to > it. > > Please let me know if you have any idea what the problem might be, or > where I should look for the problem. > > - Grant I switched the identical wireless cards between the router and the non-connecting desktop and the functionality is the same so it must not be a hardware problem. - Grant -- gentoo-user@gentoo.org mailing list