wlassistant gives wrong status messages

Bug #67020 reported by lucia
12
Affects Status Importance Assigned to Milestone
wlassistant (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: wlassistant

If I connect to a hidden accesspoint, wlassistant says the connection fails. But if I try the connection with ping, firefox etc. I can use the internet with this connection.

Here is my output, if I run wlassistant from the konsole:

$ sudo wlassistant
ScimInputContextPlugin()
Loaded application options.
DHCP Client: dhclient
All executables found.
iwconfig_status: /sbin/iwconfig
==>stderr: lo no wireless extensions.

eth0 no wireless extensions.

sit0 no wireless extensions.

Wireless interface(s): wlan0
Permissions checked.
ifconfig_status: /sbin/ifconfig wlan0
scan: /sbin/iwlist wlan0 scan
Networks found: 2
Checking for active connection.
Trying to get gateway address...
...from /var/lib/dhcp3/dhclient.leases
Gateway address: 192.168.178.1
kill_dhcp: /sbin/dhclient -r wlan0
==>stderr: Internet Systems Consortium DHCP Client V3.0.3
Copyright 2004-2005 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/products/DHCP

Listening on LPF/wlan0/00:11:d8:22:a2:d5
Sending on LPF/wlan0/00:11:d8:22:a2:d5
Sending on Socket/fallback
DHCPRELEASE on wlan0 to 192.168.178.1 port 67
send_packet: Network is unreachable
send_packet: please consult README file regarding broadcast address.
ifup: /sbin/ifconfig wlan0 up
iwconfig_set: /sbin/iwconfig wlan0 mode managed channel 10 key open XXXXXXXXXXXXXXXXXXXXXXXXXXXX essid XXXXX
iwconfig_ap: /sbin/iwconfig wlan0 ap 00:04:0E:97:10:83
ifconfig_dhcp: /sbin/dhclient -q wlan0
Application options saved.
Kernel socket closed.
~ScimInputContextPlugin()
$ ping heise.de
PING heise.de (193.99.144.80) 56(84) bytes of data.
64 bytes from redirector.heise.de (193.99.144.80): icmp_seq=223 ttl=244 time=71.2 ms
64 bytes from redirector.heise.de (193.99.144.80): icmp_seq=224 ttl=244 time=71.3 ms

Revision history for this message
Andrew Ash (ash211) wrote :

Thank you for the bug report. There has been an update to wlassistant since Edgy was first released. Could you please update and try to replicate the bug?

If you can replicate it, please provide the output of `apt-cache policy wlassistant` so we know what version of wlassistant you have installed.

Changed in wlassistant:
assignee: nobody → ash211
status: Unconfirmed → Needs Info
Revision history for this message
Andrew Ash (ash211) wrote :

I'm closing this bug. If it's still a problem for you, lucia, please let us know and we'll continue discussion.

Changed in wlassistant:
assignee: ash211 → nobody
status: Needs Info → Rejected
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.