Can't Navigate My LAN Or Ping

[Leonard Chatagnier]

--- On Sun, 12/7/08, Nils Kassube <kassube at gmx.net> wrote:

> From: Nils Kassube <kassube at gmx.net>
> Subject: Re: Can't Navigate My LAN Or Ping
> To: ubuntu-users at lists.ubuntu.com
> Date: Sunday, December 7, 2008, 1:50 AM
> Leonard Chatagnier wrote:

> Well, I don't know if you are still waiting for my
> reply before you change 
> anything (from another of your mails I think you do). The
> problem of a 
> conversation over different continents is a possibly long
> delay between 
> replies. However I don't really know what the current
> state of your 
> problem is. I'm a bit confused from the many mails in 2
> threads.
> 
Yep, me too.  And, of course, I was waiting for NoOP and your reply. Did't want to jump the gun on something I perhaps couldn't undo. Besides, I thought you list gurus stayed awake, 24-7, answering list mail-:)) My list mail indicates that anyway.

> Anyway, here is my comment on your setup:
> 
> I'm not sure if there are any other wireless networks
> in your 
> neighbourhood but the networkmanager wouldn't connect
> to an open network 
> unless you tell it to do so at least once. Therefore it is
> unlikely that 
> you get your internet access from another router like I
> supposed 
> yesterday.
Don't know.  Neibors are spread apart and don't communicat/visit in the country where I live. I think someone else said I wasn't using another service based on data he asked for. In any case, I've never seen any other service available and certainly didn't ask to connect to one. Unless, it connects automatically without my knowledge, it's safe to say I've always been on the ATTYahoo DSL service.

However, Karl mentioned it already, your router
> probably will 
> not let you get to the setup page via WLAN but only via the
> wired 
> interface. Probably that is the reason why you couldn't
> see your router.
> 
It appears he was right; already told him so. I could not connect with the wired connection though until I disabled the wifi setup.  That fixed it.  Not knowing much about routers, modems and such, I find it strange that a wireless capable router/modem will only connect to 2wire.net with a wired connnectiom.  Need to download the manual again and read-:))

> And like Luke Militello said, you seem to have duplicate
> routes via eth0 
> and wlan0. As long as both interfaces point to your router,
> you will have 
> problems if only one is connected. It may work sometimes
> but it isn't 
> reliable. 
Yes, as indicated above.  However, both cards have been set that way for many moons and worked before.  I even have bookmarks to several 2wire setup pages that worked in the past.  Why it suddenly quit working I'll never know. I had two machines in the wired position and am sure that with the older machine I could access 192.168.1.254.

Did you at least use different IP addresses for
> eth0 and wlan0? 
No, never.  And I think the NIC card was automatically configured initially. I don't recall doing it.

> Sorry if you sent it already and I overlooked it, but maybe
> you could 
> post the output of the command "ifconfig -a".
> 
It'll be different now that I've disabled wlan0.  Well, no it isn't even though I unticked the nm wlan0 profile and erased the IPS etc.  Strange, so here it is:
lchata at ubuntu:/var/log$ ifconfig -a
eth0      Link encap:Ethernet  HWaddr 00:50:04:99:48:F4
          inet addr:192.168.1.2  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::250:4ff:fe99:48f4/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:5923 errors:0 dropped:0 overruns:0 frame:0
          TX packets:14747 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:626359 (611.6 KB)  TX bytes:3012098 (2.8 MB)
          Interrupt:11 Base address:0xc000

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:101 errors:0 dropped:0 overruns:0 frame:0
          TX packets:101 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:7596 (7.4 KB)  TX bytes:7596 (7.4 KB)

wlan0     Link encap:Ethernet  HWaddr 00:12:17:92:33:D8
          inet addr:192.168.1.2  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::212:17ff:fe92:33d8/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:28105 errors:0 dropped:0 overruns:0 frame:0
          TX packets:8020 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:14657069 (13.9 MB)  TX bytes:1352077 (1.2 MB)

wmaster0  Link encap:UNSPEC  HWaddr 00-12-17-92-33-D8-00-00-00-00-00-00-00-00-00-00
          UP BROADCAST RUNNING 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:1000
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

lchata at ubuntu:/var/log$
Aparently nm automatically reconfigured wifi again-:))  Thanks for your help, Nils.
> 
> Nils
> 

Leonard Chatagnier
lenc5570 at sbcglobal.net