[f3lxo]

posseggo un DSL-G624T e ho seguito per bene il forum, fw spagnolo, apertura porte, offuscamento....e infatti va tutto bene finke c'e il cavo.
eppure connesso tramite l'AP (in wifi), non si riesce ad avere un collegamento stabile, la connessione si blocca e bisogna ripristinarla tramite windows o resettando il router
ecco il log di quando si presenta il problema
************************************
Oct 17 19:57:39> DSL in Sync
Oct 17 19:58:58> Receive assoc failed from wpa,station index 1.
Oct 17 20:11:21> DSL out of sync
Oct 17 20:11:21> DSL in Sync
Oct 17 20:11:22> DSL out of sync
Oct 17 20:11:22> DSL in Sync
Oct 17 20:11:22> DSL out of sync
Oct 17 20:11:22> DSL in Sync
Oct 17 20:11:23> DSL out of sync
Oct 17 20:11:23> DSL in Sync
Oct 17 20:16:36> Receive assoc failed from wpa,station index 1.
Oct 17 20:18:05> failed to wait for MBOX command completion: curr command 0x2, failed cmd 0xA
Oct 17 20:18:06> failed to wait for MBOX command completion: curr command 0x1, failed cmd 0x2
Oct 17 20:18:06> failed to wait for MBOX command completion: curr command 0x2, failed cmd 0xA
Oct 17 20:18:06> failed to wait for MBOX command completion: curr command 0x2, failed cmd 0x1
Oct 17 20:18:06> failed to wait for MBOX command completion: curr command 0x2, failed cmd 0x1
Oct 17 20:18:06> failed to wait for MBOX command completion: curr command 0x1, failed cmd 0x2
Oct 17 20:18:06> The mailbox queue is full, drop current command: 0x1
Oct 17 20:18:06> The mailbox queue is full, drop current command: 0x2
Oct 17 20:18:06> The mailbox queue is full, drop current command: 0x2
Oct 17 20:18:06> The mailbox queue is full, drop current command: 0x2
Oct 17 20:18:06> failed to wait for MBOX command completion: curr command 0x2, failed cmd 0xA
Oct 17 20:18:06> The mailbox queue is full, drop current command: 0x2
Oct 17 20:18:06> failed to wait for MBOX command completion: curr command 0x2, failed cmd 0x2
Oct 17 20:18:06> The mailbox queue is full, drop current command: 0x2
Oct 17 20:18:07> failed to wait for MBOX command completion: curr command 0x1, failed cmd 0xA
Oct 17 20:18:07> The mailbox queue is full, drop current command: 0x1
Oct 17 20:18:07> The mailbox queue is full, drop current command: 0x2
Oct 17 20:18:07> The mailbox queue is full, drop current command: 0x2
Oct 17 20:18:07> The mailbox queue is full, drop current command: 0x2
Oct 17 20:18:07> failed to wait for MBOX command completion: curr command 0x2, failed cmd 0x2
Oct 17 20:18:07> failed to wait for MBOX command completion: curr command 0x2, failed cmd 0xA
Oct 17 20:18:07> The mailbox queue is full, drop current command: 0x2
Oct 17 20:18:07> The mailbox queue is full, drop current command: 0x2
Oct 17 20:18:07> failed to wait for MBOX command completion: curr command 0x2, failed cmd 0x1
Oct 17 20:18:07> @@@@@@@@@@@@ @@@@@@@@@@@@
Oct 17 20:18:07> wdrv_DDA_restart_setEvent ..........
Oct 17 20:18:07> deleting timer 0xc006cc74
Oct 17 20:18:07> deleting timer 0xc006e93c
Oct 17 20:18:07> deleting timer 0xc0073af4
Oct 17 20:18:07> deleting timer 0xc007377c
Oct 17 20:18:07> @@@@@@@@@@@@ TIME SINCE BOOT: 0[d]:2[h]:59[m]:12 @@@@@@@@@@@@
Oct 17 20:18:07> Preparing for vlynq tearing down....
Oct 17 20:18:07> Resetting the remote device.
Oct 17 20:18:07> Un-resetting the remote device.
Oct 17 20:18:07> Preparing the VLYNQ, now the Link is up.
Oct 17 20:18:07> Freed MSDUs count = 32
Oct 17 20:18:07> Freed MSDUs count = 0
Oct 17 20:18:07> Preparing for vlynq tearing down....
Oct 17 20:18:07> Resetting the remote device.
Oct 17 20:18:07> Un-resetting the remote device.
Oct 17 20:18:07> Preparing the VLYNQ, now the Link is up.
Oct 17 20:18:07> AcxRegAddr = 0xA4040000, AcxMemAddr = 0xA4000000
Oct 17 20:18:07> whal_acxProcInitiate: found DEVICE_VENDOR ID = 0x9066104c
Oct 17 20:18:07> whal_acxProcInitiate: Cpu halt -} download code
Oct 17 20:18:07> whal_acxProcLoadFwImage: 0xa4000000, 0x0
Oct 17 20:18:07> whal_acxProcLoadFwImage() -- Loading FW image107526: Compiled for RADIA (bg) radio
Oct 17 20:18:07> whal_acxProcLoadFwImage: 1, pBuf=0xc00a5000, len=0x15564. Extra pBuf=0x0, len=0x3
Oct 17 20:18:07> whal_acxProcLoadFwImage: 2, pBuf=0xc00a5000, len=0x15564. Extra pBuf=0x0, len=0x3
Oct 17 20:18:07> whal_acxProcLoadFwImage: 3, pBuf=0xc00a5000, len=0x15564, DataLen=0x1555c
Oct 17 20:18:07> whal_acxProcLoadFwImage: 4, pBuf=0xc00a5000, len=0x15564
Oct 17 20:18:07> whal_acxProcLoadFwImage: Checksum, calc=0x71e76f, file=0x71e76f
Oct 17 20:18:07> whal_acxProcInitiate: run
Oct 17 20:18:07> whal_acxProcWaitInitComplete:
Oct 17 20:18:08> whal_acxMboxInit: pCmdMbox=0xa401dd00, pInfoMbox=0xa401de88
Oct 17 20:18:08> ----------------------------------------------------------------
Oct 17 20:18:08> ACX Firmaware Version = Rev 1.6.0.24
Oct 17 20:18:08> ----------------------------------------------------------------
Oct 17 20:18:08> whal_acxProcConfigure: templates (beacon, probe response, tim) for

• Network

Oct 17 20:18:08> whal_acxProcConfigure: Host Queue is in 0x9574E020
Oct 17 20:18:08> TxQueue[0] NumDesc = 32
Oct 17 20:18:08> TxQueue[0] Priority = 0
Oct 17 20:18:08> TxQueue[1] NumDesc = 32
Oct 17 20:18:08> TxQueue[1] Priority = 129
Oct 17 20:18:08>
Oct 17 20:18:08> whal_acxConfigMemory() --
Oct 17 20:18:08> HostRxDescriptorsAddr = 1574e020
Oct 17 20:18:08> RxQueue NumDesc = 32
Oct 17 20:18:08> RxQueue Priority = 0
Oct 17 20:18:08> RxQueue type = 7
Oct 17 20:18:08> whal_acxProcConfigure: read queue heads
Oct 17 20:18:08> whal_acxConfigRead_QueueHead() -
Oct 17 20:18:08> RxMemBlkQ - 00016960
Oct 17 20:18:08> RxQueueHead - 00013f54
Oct 17 20:18:08> TxMemBlkQ - 0001b360
Oct 17 20:18:08> TxMemBlkQ[0]- 000145d4
Oct 17 20:18:08> TxMemBlkQ[1]- 00014c54
Oct 17 20:18:08> 107536: whal_acxProcConfigure: configure RxQueue/TxQueue objects
Oct 17 20:18:08> whal_txQueue_Init: [Qid=0] HwBaseAddr=0xa40145d4, NumDesc=32
Oct 17 20:18:08> Write EDCF-IE: TxQueue = 0, trafficType 1 AIFSN = 2, CWmin = 15, CWmax = 1023
Oct 17 20:18:08> MSDULifetime 512 ,rxTimeout 0 ,ackPolicy 0, shortRetryLimit 7
Oct 17 20:18:08> longRetryLimit 2 , retryPremption 0 , txopLimit 3000 , txopContinuation 1
Oct 17 20:18:08> whal_txQueue_Init: [Qid=1] HwBaseAddr=0xa4014c54, NumDesc=32
Oct 17 20:18:08> whal_ParamsPrintMemMap:
Oct 17 20:18:08> Code (0x00000000, 0x0001250c)
Oct 17 20:18:08> Wep (0x00012830, 0x00012940)
Oct 17 20:18:08> Sta (0x00012940, 0x00013f28)
Oct 17 20:18:08> Tmpl (0x00012524, 0x000125df)
Oct 17 20:18:08> Queue (0x00013f54, 0x000152d4)
Oct 17 20:18:08> Pool (0x00016960, 0x0001c760)
Oct 17 20:18:08> whal_apiConfig: beaconInterval = 200
Oct 17 20:18:08> WATCH_DOG_TIMER_VAL = 520
Oct 17 20:18:08> wd_beacon_limiter = 1
Oct 17 20:18:08> whal_apiStartBss: Enable Tx, Rx and Start the Bss
Oct 17 20:18:08> ----------------------------------------------------------------
Oct 17 20:18:08> ----------------------------------------------------------------
Oct 17 20:18:08> START BSS, SSID=ROME_WIRELESS, BSSID=00-17-9A-1E-73-C2
Oct 17 20:18:08> ----------------------------------------------------------------
Oct 17 20:18:08> ----------------------------------------------------------------
Oct 17 20:18:08> AP Power Level = 1
Oct 17 20:18:08> Regulatory Domain = ETSI
Oct 17 20:18:08> Net[0] : Channel=10
Oct 17 20:18:08> ----------------------------------------------------------------
Oct 17 20:18:08> FW Watchdog is Enabled

*****************************************************************
mi sembra di capire che ci sia un problema con la crittografia WPA:

Oct 17 20:16:36> Receive assoc failed from wpa,station index 1.

una serie di inetrminabili notifiche di errore:

Oct 17 20:18:05> failed to wait for MBOX command completion: curr command 0x2, failed cmd 0xA

e poi qualcosa vada in overflow:

Oct 17 20:18:07> The mailbox queue is full, drop current command: 0x2

poi non capisco se é solo l'AP che si reinizializza o tutto il router, dai led non riesco a trovare sempre lo stesso schema
se qualcuno avesse idea di cosa significhino queste 3 stringhe.....

-con netstumbler per la connessione wifi leggo
SNR: 38 Signal: -64 Noise: -100

-la velocitą non scende mai sotto i 48Mbps
-I dati della'ADSL son invece sopra la media , sia per SNR che per attenuazione (fonte www.dlinkpedia.com)
-la connessione su windows l'ho ottimizzata con TCPOptimizer (www.speedguide.net) per una connessione da 3mbps
-l'adsl é il 10mega di libero
-i 3computer connessi tramite wifi utilizzano tutti la Intel(R) PRO/Wireless 2200BG con gli ultimi driver ver. 9.0.4.17

per quanto rigurda i settaggi del router
HOME/WIRELESS
-Enable AP: on
-Channel: 10 (impostato a 10 su tutti i pc, anke se WPA dovrebbe trovare il canale con minor attenuazione automatucamente...)
-Security: WPA
-group key Interva: 3600
-PSK key: (WPA Password)

ADVaNCED/WIRELESS PERFORMANCE
Beacon interval: 200
DTIM: 2
Hidden SSID: Disabled
Antenna transmit power: 100%
RTS Threshold: 4096
Frag Threshold: 4096
b/g Mode: G+

potrei provare con questo fw?
DLinkEU-A_DSL-G624T_singleimage_kernel_fs_V3.00B01T02.EU-A.20060720

Cosa devo fare? non possiamo attaccarci tutti col cavo eternet e la cosa é insostenibile....di rimuovere la crittografia non se parla, visto ke sto in condominio di scrocconi. E preferirei non passare al WEP, ma se il problema riguarda la WPA mi metto l'anima in pace.fatemi sapere...grazie

[f3lxo]

A forza di passarci ore ed ore a scervellarmi del perkč di queste continue disconnessioni, lampo di genio: ke non sia l'altro lato della connessione il problema, ovvero la Intel(R) PRO/Wireless 2200BG ( a posteriori rivelatasi, dopo accurate ricerche, fetentissima nella sua categoria)?
presso intel ho trovato queste "interessantissime" note:
http://support.intel.com/support/wir.../cs-022509.htm
http://support.intel.com/support/wir.../cs-006205.htm
Ne conviene ke: in teoria non dovrei avere di questi problemi poichč la versione dei driver montata sulle 3 skede é la 9.0.4.17 che ha gia la fix per tali problemi, senza contare che il risparmio energetico era gia disattivato su tutte e 3 le skede. Ma allora?
Per eliminare ogni dubbio ho disinstallato manualmente i driver della PRO/Wireless 2200BG, riavviato il pc, re-installato manualmente i driver 9.0.4.17 (procedura consigliata da intel in caso di problemi)...ecco fatto dovrebbe essere tutto apposto...magari!
Preso dallo sconforto ormai sempre crescente, per non vedere ne sentire ho installato anke l'aggiornamento rapido mircosoft per la WPA2, ke in teoria non avrebbe rilevanza ma comunque non mi sento di escludere qualke correzione occulta al supporto WPA(spiego dopo il perchč):
http://support.microsoft.com/kb/893357/en-us
devo dire ke da qundo ho caricato la patch MS e installato in modo "corretto" nuovamente i drivers, il router sembri sopportare un numero maggiore di errori tipo:
Receive assoc failed from wpa,station index 1
prima di crashare e riavviarsi.(microsoft malandrina....)
il firmware EU menzionato nel 1o post l'ho caricato, ma va peggio di quello SP, almeno sembra, quindi ho rispristinato il fw SP con buona pace dei sensi.
Per quanto riguarda la solita stringa di errore:
Receive assoc failed from wpa,station index 1
in effetti sembra sia sempre lo stesso pc (ovvero la "station index 1") a fallire l'associazione all'AP, ma allora dove lo trovo un modo in questo maledetto router per capire di quale pc si tratta?
Dimenticavo i 3 pc sono:
2x Toshiba SATELLITE A80-111
1x Fujitsu-Siemens AMILO M1437G
vi aggiornero presto....