knetworkmanager wireless

[v04OV8f8]

Wireless card: DLink G650

The network manager recognizes the device. The device is enabled and configured. The wireless network does not show up under Options > Show Network ... . When I use Wireless Assistant I can see the network, but the connection fails. I know it's not an issue with my wireless router/modem, because I can connect under XP.
I've someone could help me with this, I would really appreciate it. I've spent hours on this and I can't for the life of me figure it out!

Thanks!!!



Sys Log:

06/02/2007 03:12:06 PM d410 dhclient

06/02/2007 03:12:06 PM d410 dhclient All rights reserved.

06/02/2007 03:12:06 PM d410 dhclient Copyright 2004-2006 Internet Systems Consortium.

06/02/2007 03:12:06 PM d410 dhclient For info, please visit http://www.isc.org/sw/dhcp/

06/02/2007 03:12:06 PM d410 dhclient Internet Systems Consortium DHCP Client V3.0.4

06/02/2007 03:12:06 PM d410 dhclient Listening on LPF/ath0/00:13:46:13:72:c5

06/02/2007 03:12:06 PM d410 dhclient Sending on LPF/ath0/00:13:46:13:72:c5

06/02/2007 03:12:06 PM d410 dhclient Sending on Socket/fallback

06/02/2007 03:12:06 PM d410 dhclient There is already a pid file /var/run/dhclient.pid with pid 134993416

06/02/2007 03:12:06 PM d410 dhclient There is already a pid file /var/run/dhclient.pid with pid 134993416

06/02/2007 03:12:06 PM d410 dhclient wifi0: unknown hardware address type 801

06/02/2007 03:12:06 PM d410 dhclient wifi0: unknown hardware address type 801

06/02/2007 03:12:06 PM d410 dhclient wifi0: unknown hardware address type 801

06/02/2007 03:12:07 PM d410 dhclient wifi0: unknown hardware address type 801

06/02/2007 03:12:10 PM d410 dhclient DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 8

06/02/2007 03:12:18 PM d410 dhclient DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 19

06/02/2007 03:12:44 PM d410 dhclient DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 6

06/02/2007 03:12:50 PM d410 dhclient DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 16

06/02/2007 03:13:06 PM d410 dhclient DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 9

06/02/2007 03:13:15 PM d410 avahi-autoipd(ath0)[7325] fopen() failed: Permission denied

06/02/2007 03:13:15 PM d410 avahi-autoipd(ath0)[7325] Found user 'avahi-autoipd' (UID 103) and group 'avahi-autoipd' (GID 109).

06/02/2007 03:13:15 PM d410 avahi-autoipd(ath0)[7325] Starting with address 169.254.6.122

06/02/2007 03:13:15 PM d410 avahi-autoipd(ath0)[7325] Successfully called chroot().

06/02/2007 03:13:15 PM d410 avahi-autoipd(ath0)[7325] Successfully dropped root privileges.

06/02/2007 03:13:15 PM d410 dhclient No DHCPOFFERS received.

06/02/2007 03:13:15 PM d410 dhclient No working leases in persistent database - sleeping.

06/02/2007 03:13:21 PM d410 avahi-autoipd(ath0)[7325] Callout BIND, address 169.254.6.122 on interface ath0

06/02/2007 03:13:21 PM d410 avahi-daemon[4747] Joining mDNS multicast group on interface ath0.IPv4 with address 169.254.6.122.

06/02/2007 03:13:21 PM d410 avahi-daemon[4747] New relevant interface ath0.IPv4 for mDNS.

06/02/2007 03:13:21 PM d410 avahi-daemon[4747] Registering new address record for 169.254.6.122 on ath0.IPv4.

06/02/2007 03:13:25 PM d410 avahi-autoipd(ath0)[7325] fopen() failed: Permission denied

06/02/2007 03:13:25 PM d410 avahi-autoipd(ath0)[7325] Successfully claimed IP address 169.254.6.122

06/02/2007 03:17:01 PM d410 /USR/SBIN/CRON[7437] (root) CMD ( cd / && run-parts --report /etc/cron.hourly)

06/02/2007 03:17:34 PM d410 dhclient DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 5

06/02/2007 03:17:39 PM d410 dhclient DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 14

06/02/2007 03:17:53 PM d410 dhclient DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 12

06/02/2007 03:18:05 PM d410 dhclient No DHCPOFFERS received.

06/02/2007 03:18:05 PM d410 dhclient No working leases in persistent database - sleeping.

[The Liquidator]

Re: knetworkmanager wireless

What security protocol (WEP, WPA etc) are you using for your router?

[v04OV8f8]

Re: knetworkmanager wireless

My router only supports WEP (Westell Versalink 327W). I've tried various key settings (ascii/hex 64, 128, 256).

[kubrod]

Re: knetworkmanager wireless

My router only supports WEP (Westell Versalink 327W). I've tried various key settings (ascii/hex 64, 128, 256).

I am no expert but have just gone through the same with a Netgear WG311v3 and in the end it was just a matter of matching up the ascii key to the password in the Knetwork manager I also changed channel.

[The Liquidator]

Re: knetworkmanager wireless

Try this

If you have the package knetworkmanager installed, uninstall it.

Then run kwifmanager selecting settings/ show in system tray in close. That will give you a visible sign of connection in the taskbar.

Then go to kmenu/system settings/network settings. Go into administrator mode (type your password when asked). Select your wireless card and type in your settings. Also, if you wish select activate when system starts. Hit apply and you should then connect. You should see the kwifimanager icon go green as a sign you have connected.

Success?

Ian

[v04OV8f8]

Re: knetworkmanager wireless

No dice - I've un-installed Knetworkmanager. KWifiManager shows the connection speed and frequency and name, but no access point and local IP. Scan for Networks displays Network Name, etc. all correctly. I just can't connect to it. This has been extremely frustrating to me. I've used Ubuntu (Dapper) in the past with a different wireless card and it just worked. Now on this system I've a built in network card that I tried to get to work with ndiswrapper and I experienced exactly the same problem that I am experiencing now, so I decided to just get a new card that I know would work with Kubuntu Feisty out of the box and here I am having the same problems again. Sorry I needed to vent.
Any more ideas?! Anybody! .... argh!

Cheers

>

[mchuskie]

Re: knetworkmanager wireless

As a temporary measure, can you try turning off WEP and seeing if you can connect?

[v04OV8f8]

Re: knetworkmanager wireless

You know I did this before when I still had Knetworkmanager installed and it didn't work. Right now I only have Wireless Assistant installed and I was able to connect without WEP. Then I tried WEP again (I used a simple 64bit ascii key that I 1st typed in manually and the second time copy and pasted) - no luck. Well I feel like I am getting somewhere here. BTW my card also supports WPA. Is this currently supported? I don't see an option for it. Anyway if I could just get WEP working that would make me happy.

Cheers ... and thanks for all the feedback.

[lingenfr]

Re: knetworkmanager wireless

If you have not already done it, post the output of the following commands:

ifconfig
iwconfig

This should tell us what interfaces are recognized.

[v04OV8f8]

Re: knetworkmanager wireless

ifconfig
ath0 Link encap:Ethernet HWaddr 00:13:46:13:72:C5
inet6 addr: fe80::213:46ff:fe13:72c5/64 Scope:Link
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:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

eth0 Link encap:Ethernet HWaddr 00:13:72:6E:0D:69
inet addr:192.168.1.65 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::213:72ff:fe6e:d69/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:8410 errors:0 dropped:0 overruns:0 frame:0
TX packets:9571 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:6528225 (6.2 MiB) TX bytes:1110892 (1.0 MiB)
Interrupt:16

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:336 errors:0 dropped:0 overruns:0 frame:0
TX packets:336 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:30166 (29.4 KiB) TX bytes:30166 (29.4 KiB)

wifi0 Link encap:UNSPEC HWaddr 00-13-46-13-72-C5-00-00-00-00-00-00-00-00-00-00
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1915 errors:0 dropped:0 overruns:0 frame:490
TX packets:5689 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:199
RX bytes:123226 (120.3 KiB) TX bytes:266027 (259.7 KiB)
Interrupt:17


------------------------

iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

wifi0 no wireless extensions.

ath0 IEEE 802.11g ESSID:"" Nickname:""
Mode:Managed Frequency:2.417 GHz Access Point: Not-Associated
Bit Rate:1 Mb/s Tx-Power:18 dBm Sensitivity=0/3
Retryff RTS thrff Fragment thrff
Power Managementff
Link Quality=35/94 Signal level=-60 dBm Noise level=-95 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

[lingenfr]

Re: knetworkmanager wireless

OK, I assume that the ESSID of your network is not "Nickname". I would use iwconfig to input the information that you know. Normally for me that means that I can input at least the ESSID and the channel. After you make each change, I suggest you do an ifconfig to see if ath0 has an IP address. If you have used iwconfig to input all the information you have, do the following:

sudo ifdown ath0
sudo ifup ath0

If it doesn't come up, post any errors you get.

[v04OV8f8]

Re: knetworkmanager wireless

Here is what I did:
sudo iwconfig ath0 essid [myessid]
sudo iwconfig ath0 mode Managed
sudo iwconfig ath0 freq 2.422G
sudo iwconfig ath0 channel 3
sudo iwconfig ath0 ap any
sudo iwconfig ath0 rate auto
sudo iwconfig ath0 key [mykey]

No errors thus far, but ifconfig also did not show an IP

Then:
sudo ifdown ath0
RTNETLINK answers: No such process
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wifi0: unknown hardware address type 801
wifi0: unknown hardware address type 801
Listening on LPF/ath0/[myMAC]
Sending on LPF/ath0/[myMAC]
Sending on Socket/fallback
DHCPRELEASE on ath0 to 192.168.1.1 port 67

Then:
sudo ifup ath0
There is already a pid file /var/run/dhclient.ath0.pid with pid 134993416
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wifi0: unknown hardware address type 801
wifi0: unknown hardware address type 801
Listening on LPF/ath0/[myMAC]
Sending on LPF/ath0/[myMAC]
Sending on Socket/fallback
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 6
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 10
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 15
No DHCPOFFERS received.
No working leases in persistent database - sleeping.

[lingenfr]

Re: knetworkmanager wireless

OK. We may be getting there. There are a number of potential error messages there that I am not familiar with. Probably card/machine specific. Do the ifdown and then delte the pid file referenced in the message. Then do your ifup and see what you get. I think the pid file and the process message from your ifdown are related, but others certainly know more than I.

[v04OV8f8]

Re: knetworkmanager wireless

I've deleted dhclient.ath0.pid (although I did a cat and the pid # in it was different from 134993416), did a ifdown and ifup and still no dice.
I just don't get it. Obviously my card is recognized, but only connecting without WEP works. Are there any gurus out there who could shine some light on this?!

[v04OV8f8]

Re: knetworkmanager wireless

I've added the latest madwifi atheros driver and followed the instructions here:
http://madwifi.org/wiki/UserDocs/FirstTimeHowTo
It just won't grab an IP address, neither static or dhcp.