ATT wireless a no-go

[Stuart Biggerstaff]

Actually, with AT&T it CAN be both.  If you do DSL with them you have
the choice of buying a "modem" or a "router"--actually both similar
routers with the DSL modem built in.  The one has a single LAN port, the
other one has four plus wireless.

Though apparently that's not the case here, and even so, if the one
system was connecting okay with wired ethernet to the same device it
pretty much makes wireless the problem.


Stuart Biggerstaff
Systems Technician
Linda Hall Library of Science Engineering & Technology
5109 Cherry St.
Kansas City, Missouri 64110-2498

Phone:	(816) 926-8748
	(800) 662-1545 x748
FAX:	(816) 926-8790
URL:	www.lindahall.org 
-----Original Message-----
From: linux-users-bounces at linux-sxs.org
[mailto:linux-users-bounces at linux-sxs.org] On Behalf Of Lonni J Friedman
Sent: Sunday, October 21, 2007 1:51 PM
To: Linux tips and tricks
Subject: Re: ATT wireless a no-go

I must be missing something.  Is this DSL or wifi?  It can't be both.

On 10/21/07, Ed Jabbour <ejbr at att.net> wrote:
> I just had AT&T Uverse service installed, replacing Comcast cable.  
> The desktop, running Debian etch, performs with an ethernet 
> connection, but I can't get wireless going on a  laptop, IBM T30, also
etch.
>
> The card is recognized:
>         dmesg|grep wlan0:
>         wlan0: vendor: 'NETGEAR WG511 54 Mbps Wireless PC Card'
>         wlan0: ethernet device [MAC addreess] using NDIS driver
>          netwg511 . . .
>
> /etc/network/interfaces:
>         iface wlan0 inet dhcp
>                 wireless-essid 2wire341
>                 wireless-mode managed
>                 wireless key ******
>
> iwlist s finds 3 ssid, including mine.  (How does iwlist find anything

> with no connection?)
>
> Running /etc/init.d/networking restart, I see:
>         DHCPRELEASE on wlan0 to 192.168.1.1 port 67
>         send_packet: Network is unreachable
>
> 192.168.1.1 was the IP of the old router I had, now disconnected.  The

> ATT "RG" - the router -  is 192.168.1.254.  I haven't a clue where 
> that wrong IP is coming from:
>         grep -r 192.168.1.1 /etc
>         /etc/ppp/options:# ms-dns 192.168.1.1
>
> route -n comes up blank, of course.  route -n on the desktop gives 
> 192.168.15.0 as the Destination.  I think the ATT system is DSL.  
> Win2k connects with no problems, as does the lap when connected with
cat5.
>
> Any hints, answers, pointers, etc. greatly appreciated.  Thanks.

--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
L. Friedman                                    netllama at gmail.com
LlamaLand                       https://netllama.linux-sxs.org
_______________________________________________
Linux-users mailing list ( Linux-users at linux-sxs.org )
Unsub/Password/Etc: 
http://mail.linux-sxs.org/mailman/listinfo/linux-users

Need to chat further on this subject? Check out #linux-users on
irc.linux-sxs.org !