Package: waproamd
Severity: important

This software doesn't properly detect my network essid, with a
Lynksys AP and an Asus Ralink 2400 PCMCIA card with ndiswrapper
modules, but iwlist does it fine:

tulio:~# iwlist wlan0 scan
wlan0     Scan completed :
          Cell 01 - Address: 00:14:BF:B6:EF:A1
          ESSID:"casa"
          Protocol:IEEE 802.11b
          Mode:Managed
          Frequency:2.437 GHz (Channel 6)
          Quality:0/100
          Signal level:-57 dBm
          Noise level:-256 dBm
          Encryption key:off
          Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s;11 Mb/s
          Extra:bcn_int=100
          Extra:atim=0

tulio:~# waproamd -n -i wlan0
waproamd 0.6 initializing, using wireless event notifications.
Enabling user space roaming failed, doing without.
Currently not associated, interface enabled.
Initialization complete.
Scanning...
Scan results:
1. Found AP 00:14:bf:b6:ef:a1, ESSID '', script: no
2. Found AP 00:a0:c5:f9:d7:c6, ESSID 'R', script: no
Scan completed with 2 suitable networks. (total: 2)
Selected new AP 00:14:bf:b6:ef:a1 with ESSID ''
Running script '/etc/waproamd/scripts/default start'
client: Setting policy 'open'
client: Internet Software Consortium DHCP Client 2.0pl5
client: Copyright 1995, 1996, 1997, 1998, 1999 The Internet Software
Consortium.
client: All rights reserved.
client: Please contribute if you find this software useful.
client: For info, please visit http://www.isc.org/dhcp-contrib.html
client: sit0: unknown hardware address type 776
client: sit0: unknown hardware address type 776
client: Listening on LPF/wlan0/00:11:2f:d3:b7:c3
client: Sending on   LPF/wlan0/00:11:2f:d3:b7:c3
client: Sending on   Socket/fallback/fallback-net
client: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
client: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 10
client: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
client: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
client: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 10
client: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 15
client: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 2
client: No DHCPOFFERS received.
client: No working leases in persistent database.
client: Exiting.
client: Failed to bring up wlan0.
Script successfully executed.


To solve this problem i have to manually set my AP essid and bring
the interface up:

tulio:~# iwconfig wlan0 essid casa
tulio:~# ifup wlan0
Internet Software Consortium DHCP Client 2.0pl5
Copyright 1995, 1996, 1997, 1998, 1999 The Internet Software Consortium.
All rights reserved.

Please contribute if you find this software useful.
For info, please visit http://www.isc.org/dhcp-contrib.html

sit0: unknown hardware address type 776
sit0: unknown hardware address type 776
Listening on LPF/wlan0/00:11:2f:d3:b7:c3
Sending on   LPF/wlan0/00:11:2f:d3:b7:c3
Sending on   Socket/fallback/fallback-net
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
DHCPOFFER from 192.168.1.1
DHCPREQUEST on wlan0 to 255.255.255.255 port 67
DHCPACK from 192.168.1.1
bound to 192.168.1.102 -- renewal in 43200 seconds.


If i can help in any way, just let me know.
This is my first bug report, so if i'm doing it wrong please excuse me.

-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.16-1-k7
Locale: LANG=es_CL.UTF-8, LC_CTYPE=es_CL.UTF-8 (charmap=UTF-8)

Versions of packages waproamd depends on:
ii  debconf                       1.4.72     Debian configuration management sy
ii  libc6                         2.3.6-3    GNU C Library: Shared libraries an
ii  libdaemon0                    0.10-1     lightweight C library for daemons

waproamd recommends no packages.

-- debconf information:
* waproamd/hotplug_interfaces: wlan0
* waproamd/args:
* waproamd/interfaces:
       


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to