Wizard needs food bad.. er, I need help w/ wpa_supplicant. (Solvedish)

Question

Edit- As it turns out, even though I see a message stating that my WG311V3 supports WPA2 via ndiswrapper, that doesn't appear to be the case in practice. I guess WPA and a 20+ character random passworrd will do.
After bring down then up wlan0, I associate it w/ my AP and use wpa_supplicant. When I try to reconnect, I always timeout. W/ my router, I have WPA2 selected, using PSK and whatever passphase. There's a part for cipher type, and I've tried leaving it blank as well as selecting TKIP. Does anyone see anything wrong w/ the wpa_supplicant output/config, or anything else I'm missing? I'm totally in the dark w/ configuring this stuff.
#wpa_supplicant -dd -B -Dwext -i wlan0 -c/etc/wpa_supplicant.conf
Initializing interface 'wlan0' conf
'/etc/wpa_supplicant.conf' driver 'wext'
ctrl_interface 'N/A' bridge 'N/A'
Configuration file '/etc/wpa_supplicant.conf'
-> '/etc/wpa_supplicant.conf'
Reading configuration file
'/etc/wpa_supplicant.conf'
Line: 1 - start of a new network block
ssid - hexdump_ascii(len=5):
64 6c 69 6e 6b
dlink
proto: 0x2
key_mgmt: 0x2
pairwise: 0x18
group: 0x18
PSK - hexdump(len=32): [REMOVED]
Priority group 0
id=0 ssid='dlink'
Initializing interface (2) 'wlan0'
Interface wlan0 set UP - waiting a second for
the driver to complete initialization
SIOCGIWRANGE: WE(compiled)=22 WE(source)=18
enc_capa=0xf
capabilities: key_mgmt 0xf enc 0xf flags 0x0
WEXT: Operstate: linkmode=1, operstate=5
Own MAC address: 00:18:4d:70:43:04
wpa_driver_wext_set_wpa
wpa_driver_wext_set_key: alg=0 key_idx=0
set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=1
set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=2
set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=3
set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_countermeasures
wpa_driver_wext_set_drop_unencrypted
RSN: flushing PMKID list in the driver
Setting scan request: 0 sec 100000 usec
WPS: UUID based on MAC address -
hexdump(len=16): f4 d2 ce 7e 1d 74 52 56 a9 8b
8b 47 79 c1 7f 7b
WPS: Build Beacon and Probe Response IEs
WPS: * Version
WPS: * Wi-Fi Protected Setup State (0)
WPS: * Version
WPS: * Wi-Fi Protected Setup State (0)
WPS: * Response Type (2)
WPS: * UUID-E
WPS: * Manufacturer
WPS: * Model Name
WPS: * Model Number
WPS: * Serial Number
WPS: * Primary Device Type
WPS: * Device Name
WPS: * Config Methods (0)
WPS: * RF Bands (3)
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: KEY_RX entering state NO_KEY_RECEIVE
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
Added interface wlan0
Daemonize..
Last edited by omgwtfbyobbq (2009-12-07 05:52:32)

Answer 1

With the URL of the feed one can check it in iTunes and submit it to FeedValidator as a first-line method of locating problems. It's nearly impossible to read right through a long feed's text looking for the one tiny error which may have borked it. With both URLs it's much easier to check things - including whether iTunes is using the feed the originator thinks it is (not always the case).
If you've been getting quick updates in the Store you've been lucky; the Store checks feeds in some sort of rotation and so it depends where you happen to be in the cycle when you upload a change.