Gustin Johnson schrieb: > Try running: > ip link set wlan0 up > before you connect.
Unfortunately this doesn't help. This what I get in syslog: > Jan 29 10:35:56 voyage vmunix: ADDRCONF(NETDEV_UP): wlan0: link is not ready > Jan 29 10:35:56 voyage pumpd[2701]: PUMP: sending discover > Jan 29 10:35:56 voyage vmunix: wlan0: Initial auth_alg=0 > Jan 29 10:35:56 voyage vmunix: wlan0: authenticate with AP 00:15:c7:29:82:f0 > Jan 29 10:35:56 voyage vmunix: wlan0: RX authentication from > 00:15:c7:29:82:f0 (alg=0 transaction=2 status=0) > Jan 29 10:35:56 voyage vmunix: wlan0: authenticated > Jan 29 10:35:56 voyage vmunix: wlan0: associate with AP 00:15:c7:29:82:f0 > Jan 29 10:35:56 voyage vmunix: wlan0: RX AssocResp from 00:15:c7:29:82:f0 > (capab=0x421 status=0 aid=86) > Jan 29 10:35:56 voyage vmunix: wlan0: associated > Jan 29 10:35:56 voyage vmunix: wlan0: CTS protection enabled > (BSSID=00:15:c7:29:82:f0) > Jan 29 10:35:56 voyage vmunix: wlan0: switched to short barker preamble > (BSSID=00:15:c7:29:82:f0) > Jan 29 10:35:56 voyage vmunix: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes > ready > Jan 29 10:35:56 voyage vmunix: wlan0: association frame received from > 00:15:c7:29:82:f0, but not in associate state - ignored > Jan 29 10:35:56 voyage vmunix: wlan0: CTS protection disabled > (BSSID=00:15:c7:29:82:f0) > Jan 29 10:36:00 voyage pumpd[2701]: got dhcp offer > Jan 29 10:36:00 voyage pumpd[2701]: PUMP: sending second discover > Jan 29 10:36:00 voyage pumpd[2701]: PUMP: got an offer > Jan 29 10:36:00 voyage pumpd[2701]: PUMP: got lease > Jan 29 10:36:00 voyage pumpd[2701]: intf: device: wlan0 > Jan 29 10:36:00 voyage pumpd[2701]: intf: set: 416 > Jan 29 10:36:00 voyage pumpd[2701]: intf: bootServer: 160.45.0.250 > Jan 29 10:36:00 voyage pumpd[2701]: intf: reqLease: 43200 > Jan 29 10:36:00 voyage pumpd[2701]: intf: ip: 172.25.61.23 > Jan 29 10:36:00 voyage pumpd[2701]: intf: next server: 0.0.0.0 > Jan 29 10:36:00 voyage pumpd[2701]: intf: netmask: 255.255.192.0 > Jan 29 10:36:00 voyage pumpd[2701]: intf: gateways[0]: 172.25.0.1 > Jan 29 10:36:00 voyage pumpd[2701]: intf: numGateways: 1 > Jan 29 10:36:00 voyage pumpd[2701]: intf: dnsServers[0]: 160.45.8.8 > Jan 29 10:36:00 voyage pumpd[2701]: intf: dnsServers[1]: 160.45.10.12 > Jan 29 10:36:00 voyage pumpd[2701]: intf: dnsServers[2]: 130.133.1.57 > Jan 29 10:36:00 voyage pumpd[2701]: intf: numDns: 3 > Jan 29 10:36:00 voyage pumpd[2701]: intf: domain: zedat.fu-berlin.de > Jan 29 10:36:00 voyage pumpd[2701]: intf: broadcast: 172.25.63.255 > Jan 29 10:36:00 voyage pumpd[2701]: intf: network: 172.25.0.0 > Jan 29 10:36:00 voyage vmunix: ADDRCONF(NETDEV_UP): wlan0: link is not ready > Jan 29 10:36:00 voyage pumpd[2701]: configured interface wlan0 The problem seems to be that second "ADDRCONF(NETDEV_UP): wlan0: link is not ready" after that iwconfig shows me: > voyage:~# iwconfig wlan0 > wlan0 IEEE 802.11 ESSID:"FUnkLAN" > Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated > Tx-Power=16 dBm > Retry min limit:7 RTS thr:off Fragment thr=2352 B > Encryption key:off > Link Quality:0 Signal level:0 Noise level:0 > Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 > Tx excessive retries:0 Invalid misc:0 Missed beacon:0 And this leaves me with a configured interface with a dhcp assigned ip address but no communication possible: As I mentioned earlier the only difference to a voyage linux 0.6pre installation (where the same card works) is the second "ADDRCONF(NETDEV_UP): wlan0: link is not ready" message I'm still clueless and stuck with voyage 0.6pre for now... Cheers, Fabian _______________________________________________ Voyage-linux mailing list [email protected] http://list.voyage.hk/mailman/listinfo/voyage-linux
