[wellylug] Help with wireless & WRT54G

[David Harrison]

What happens when you statically assign an IP address to the client?
Does the wireless connection work or are the packets dropped?

If the packets are dropped if possible you should turn WEP and Mac  
address locking off to test whether you can get a vanilla wireless  
connection.
If that succeeds enabled MAC locking and try again. If things are  
still looking good turn and WEP and cross your fingers.
If you can figure out which aspect of the wireless connection is  
giving you grief its a lot easier and less frustrating.


D.


On 3/01/2006, at 11:58 AM, Bret Comstock Waldow wrote:

> Hi
>
> I'm trying to get my T42 (Intel Pro Wireless 2200BG) to connect  
> with my
> Linksys WRT54G using Kubuntu Breezy 5.10.
>
> The connection works fine via cat5 cable from the onboard ethernet  
> adapter.
>
>
> I am using WEP (I'll get to WPA once I've figured this out).  I  
> copy my key
> from the Linksys administrative page, and the link appears to  
> happen, but I
> can't get DHCP to assign an IP.
>
> Here is the report:
> root at ganesha:/etc/network# dhclient eth1
> Internet Systems Consortium DHCP Client V3.0.2
> Copyright 2004 Internet Systems Consortium.
> All rights reserved.
> For info, please visit http://www.isc.org/products/DHCP
>
> sit0: unknown hardware address type 776
> irda0: unknown hardware address type 783
> sit0: unknown hardware address type 776
> irda0: unknown hardware address type 783
> Listening on LPF/eth1/00:0e:35:95:06:70
> Sending on   LPF/eth1/00:0e:35:95:06:70
> Sending on   Socket/fallback
> DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 6
> DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 14
> DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 12
> DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 19
> DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 9
> DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 1
> No DHCPOFFERS received.
> No working leases in persistent database - sleeping.
>
>
> root at ganesha:/etc/network# iwconfig
> lo        no wireless extensions.
>
> eth0      no wireless extensions.
>
> eth1      IEEE 802.11g  ESSID:"ssss"
>           Mode:Managed  Frequency:2.462 GHz  Access Point:  
> 00:12:17:B9:F1:5B
>           Bit Rate=54 Mb/s   Tx-Power=20 dBm
>           Retry limit:7   RTS thr:off   Fragment thr:off
>           Encryption key:xxxx-xxxx-xxxx-xxxx-xxxx-xxxx-xx    
> Security mode:open
>           Power Management:off
>           Link Quality=92/100  Signal level=-35 dBm  Noise  
> level=-85 dBm
>           Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
>           Tx excessive retries:0  Invalid misc:0   Missed beacon:1
>
> eth2      no wireless extensions.
>
> irda0     no wireless extensions.
>
> sit0      no wireless extensions.
>
>
> This is /etc/network/interfaces:
> root at ganesha:/etc/network# cat interfaces
> # This file describes the network interfaces available on your system
> # and how to activate them. For more information, see interfaces(5).
>
> # The loopback network interface
> auto lo
> iface lo inet loopback
> address 127.0.0.1
> netmask 255.0.0.0
>
> # This is a list of hotpluggable network interfaces.
> # They will be activated automatically by the hotplug subsystem.
> mapping hotplug
>         script grep
>         map eth0
>
> # The primary network interface
> iface eth0 inet dhcp
> auto eth0
>
> iface eth1 inet dhcp
> wireless-essid ssss
> wireless-key xxxxxxxxxxxxxxxxxxxxxxxxxx
> auto eth1
>
>
> Was it something I said?
>
> Thanks in advance,
> Bret
>
> -- 
> Wellington Linux Users Group Mailing List:  
> wellylug at lists.wellylug.org.nz
> To Leave:  http://lists.wellylug.org.nz/mailman/listinfo/wellylug