Router D-link DI-524

Cablul de alimentare inlocuit cu unul imprumutat sau posibil ca routerul sa se fi stricat, ai incercat un reset ?

da. cum as putea sa fac update la ultima versiune de firmware?

http://forum.softped...-d-link-di-524/

Salutare.
Nu pot face sa-mi mearga internetul prin router. In momentul cand conectez cablul de la internet direct la laptop merge, in cazul in care il pun pe router mi se conecteaza dar nu primesc semnal de internet. Mufa e in portul de wan, acum 2 zile mergea pur si simplu a cazut deodata. Va atasez ce imi apare la logul de pe router.
Multumesc.
-------------------------------------------------
  System Logs
-------------------------------------------------
Sun Jan 06 13:09:40 2013 Associated:  7C-C3-A1-08-F0-09 st=0
Sun Jan 06 13:09:43 2013 DOD:triggered internally
Sun Jan 06 13:09:43 2013 DHCP:discover()
Sun Jan 06 13:09:44 2013 Associated:  00-17-C4-4E-36-2F st=0
Sun Jan 06 13:09:47 2013 DHCP:discover()
Sun Jan 06 13:09:55 2013 DHCP:discover()
Sun Jan 06 13:10:11 2013 DHCP:discover()
Sun Jan 06 13:10:43 2013 DOD:UDP trigger from 192.168.0.103:16403 to 17.173.254.222:16384
Sun Jan 06 13:10:43 2013 DHCP:discover()
Sun Jan 06 13:10:47 2013 DHCP:discover()
Sun Jan 06 13:10:55 2013 TX TCP reset for 192.168.0.118(2459) -> 192.168.0.1(80)
Sun Jan 06 13:10:55 2013 TX TCP reset for 192.168.0.118(2460) -> 192.168.0.1(80)
Sun Jan 06 13:10:55 2013 TX TCP reset for 192.168.0.118(2462) -> 192.168.0.1(80)
Sun Jan 06 13:10:55 2013 DHCP:discover()
Sun Jan 06 13:11:11 2013 DHCP:discover()
Sun Jan 06 13:11:13 2013 TX TCP reset for 192.168.0.118(2507) -> 192.168.0.1(80)
Sun Jan 06 13:11:13 2013 TX TCP reset for 192.168.0.118(2508) -> 192.168.0.1(80)
Sun Jan 06 13:11:13 2013 TX TCP reset for 192.168.0.118(2509) -> 192.168.0.1(80)
Sun Jan 06 13:11:46 2013 DOD:triggered internally
Sun Jan 06 13:11:46 2013 DHCP:discover()
Sun Jan 06 13:11:49 2013 TX TCP reset for 192.168.0.118(2550) -> 192.168.0.1(80)
Sun Jan 06 13:11:49 2013 TX TCP reset for 192.168.0.118(2552) -> 192.168.0.1(80)
Sun Jan 06 13:11:49 2013 TX TCP reset for 192.168.0.118(2553) -> 192.168.0.1(80)
Sun Jan 06 13:11:49 2013 TX TCP reset for 192.168.0.118(2554) -> 192.168.0.1(80)
Sun Jan 06 13:11:49 2013 TX TCP reset for 192.168.0.118(2555) -> 192.168.0.1(80)
Sun Jan 06 13:11:49 2013 TX TCP reset for 192.168.0.118(2556) -> 192.168.0.1(80)
Sun Jan 06 13:11:49 2013 TX TCP reset for 192.168.0.118(2558) -> 192.168.0.1(80)
Sun Jan 06 13:11:49 2013 TX TCP reset for 192.168.0.118(2552) -> 192.168.0.1(80)
Sun Jan 06 13:11:49 2013 TX TCP reset for 192.168.0.118(2553) -> 192.168.0.1(80)
Sun Jan 06 13:11:49 2013 TX TCP reset for 192.168.0.118(2554) -> 192.168.0.1(80)
Sun Jan 06 13:11:50 2013 DHCP:discover()
Sun Jan 06 13:11:58 2013 DHCP:discover()
Sun Jan 06 13:12:07 2013 Set Device Time to: Sun Jan 06 13:15:00 2013
Sun Jan 06 13:12:10 2013 TX TCP reset for 192.168.0.118(2582) -> 192.168.0.1(80)
Sun Jan 06 13:12:10 2013 TX TCP reset for 192.168.0.118(2583) -> 192.168.0.1(80)
Sun Jan 06 13:12:10 2013 TX TCP reset for 192.168.0.118(2584) -> 192.168.0.1(80)
Sun Jan 06 13:12:10 2013 TX TCP reset for 192.168.0.118(2585) -> 192.168.0.1(80)
Sun Jan 06 13:12:10 2013 TX TCP reset for 192.168.0.118(2586) -> 192.168.0.1(80)
Sun Jan 06 13:12:10 2013 TX TCP reset for 192.168.0.118(2587) -> 192.168.0.1(80)
Sun Jan 06 13:12:10 2013 TX TCP reset for 192.168.0.118(2588) -> 192.168.0.1(80)
Sun Jan 06 13:12:11 2013 TX TCP reset for 192.168.0.118(2585) -> 192.168.0.1(80)
Sun Jan 06 13:12:11 2013 TX TCP reset for 192.168.0.118(2586) -> 192.168.0.1(80)
Sun Jan 06 13:12:11 2013 TX TCP reset for 192.168.0.118(2588) -> 192.168.0.1(80)
Sun Jan 06 13:12:14 2013 DHCP:discover()
Sun Jan 06 13:12:42 2013 TX TCP reset for 192.168.0.118(2636) -> 192.168.0.1(80)
Sun Jan 06 13:12:43 2013 TX TCP reset for 192.168.0.118(2637) -> 192.168.0.1(80)
Sun Jan 06 13:12:53 2013 TX TCP reset for 192.168.0.118(2647) -> 192.168.0.1(80)
Sun Jan 06 13:13:01 2013 DOD:triggered internally
Sun Jan 06 13:13:01 2013 DHCP:discover()
Sun Jan 06 13:13:05 2013 DHCP:discover()
Sun Jan 06 13:13:13 2013 DHCP:discover()
Sun Jan 06 13:13:29 2013 DHCP:discover()
Sun Jan 06 13:14:01 2013 DOD:TCP trigger from 192.168.0.118:2696 to 92.83.160.213:16917
Sun Jan 06 13:14:01 2013 DOD:TCP trigger from 192.168.0.118:2699 to 109.96.195.109:39557
Sun Jan 06 13:14:01 2013 DOD:TCP trigger from 192.168.0.118:2702 to 188.241.229.170:41356
Sun Jan 06 13:14:01 2013 DOD:TCP trigger from 192.168.0.118:2701 to 188.25.78.243:27168
Sun Jan 06 13:14:01 2013 DHCP:discover()
Sun Jan 06 13:14:02 2013 DHCP:offer(192.168.1.254)
Sun Jan 06 13:14:02 2013 DHCP:request(192.168.1.198)
Sun Jan 06 13:14:06 2013 DHCP:request(192.168.1.198)
Sun Jan 06 13:14:14 2013 DHCP:request(192.168.1.198)
Sun Jan 06 13:14:18 2013 Disassociated:  00-17-C4-4E-36-2F because RX deauth req
Sun Jan 06 13:14:27 2013 Associated:  00-17-C4-4E-36-2F st=0
Sun Jan 06 13:14:30 2013 DHCP:request(192.168.1.198)
Sun Jan 06 13:14:33 2013 DOD:prot 2 trigger from 192.168.0.118 to 224.0.0.22
Sun Jan 06 13:14:33 2013 DOD:prot 2 trigger from 192.168.0.118 to 224.0.0.22
Sun Jan 06 13:14:33 2013 DHCP:discover()
Sun Jan 06 13:14:37 2013 DHCP:discover()
Sun Jan 06 13:14:45 2013 DHCP:discover()
Sun Jan 06 13:15:00 2013 Set Device Time to: Sun Jan 06 13:15:00 2013
Sun Jan 06 13:15:00 2013 DOD:UDP trigger from 192.168.0.118:37716 to 188.26.94.208:46400
Sun Jan 06 13:15:00 2013 DOD:UDP trigger from 192.168.0.118:37716 to 94.24.41.131:39746
Sun Jan 06 13:15:00 2013 DOD:UDP trigger from 192.168.0.118:37716 to 188.25.135.50:51697
Sun Jan 06 13:15:00 2013 DOD:UDP trigger from 192.168.0.118:37716 to 86.120.221.227:59738
Sun Jan 06 13:15:00 2013 DOD:UDP trigger from 192.168.0.118:37716 to 93.114.227.103:59043
Sun Jan 06 13:15:00 2013 DOD:UDP trigger from 192.168.0.118:37716 to 197.2.19.12:59733
Sun Jan 06 13:15:00 2013 DOD:UDP trigger from 192.168.0.118:37716 to 188.26.135.250:37617
Sun Jan 06 13:15:00 2013 DOD:UDP trigger from 192.168.0.118:37716 to 195.8.194.202:47100
Sun Jan 06 13:15:00 2013 DOD:UDP trigger from 192.168.0.118:37716 to 195.135.193.170:14784
Sun Jan 06 13:15:00 2013 DHCP:discover()
Sun Jan 06 13:15:01 2013 DHCP:discover()
Sun Jan 06 13:15:03 2013 TX TCP reset for 192.168.0.118(2820) -> 192.168.0.1(80)
Sun Jan 06 13:15:04 2013 DHCP:discover()
Sun Jan 06 13:15:12 2013 DHCP:discover()
Sun Jan 06 13:15:28 2013 DHCP:discover()
Sun Jan 06 13:15:28 2013 DHCP:offer(192.168.1.254)
Sun Jan 06 13:15:28 2013 DHCP:request(192.168.1.198)
Sun Jan 06 13:15:32 2013 DHCP:request(192.168.1.198)
Sun Jan 06 13:15:33 2013 DOD:UDP trigger from 192.168.0.118:37716 to 5.15.166.183:50762
Sun Jan 06 13:15:33 2013 DHCP:discover()
Sun Jan 06 13:15:34 2013 DOD is disabled
Sun Jan 06 13:15:34 2013 DOD is disabled
Sun Jan 06 13:15:34 2013 DOD is disabled
Sun Jan 06 13:15:34 2013 DOD is disabled
Sun Jan 06 13:15:34 2013 DOD is disabled
Sun Jan 06 13:15:34 2013 DOD is disabled
Sun Jan 06 13:15:34 2013 DOD is disabled
Sun Jan 06 13:15:34 2013 DOD is disabled
Sun Jan 06 13:15:34 2013 DOD is disabled
Sun Jan 06 13:15:34 2013 DOD is disabled
Sun Jan 06 13:15:34 2013 DOD is disabled
Sun Jan 06 13:15:34 2013 DOD is disabled
Sun Jan 06 13:15:34 2013 DOD is disabled
Sun Jan 06 13:15:34 2013 DOD is disabled
Sun Jan 06 13:15:34 2013 DOD is disabled
Sun Jan 06 13:15:34 2013 DOD is disabled
Sun Jan 06 13:15:34 2013 DOD is disabled
Sun Jan 06 13:15:34 2013 DOD is disabled
Sun Jan 06 13:15:34 2013 DOD is disabled
Sun Jan 06 13:15:34 2013 DOD is disabled
Sun Jan 06 13:15:34 2013 DOD is disabled
Sun Jan 06 13:15:34 2013 DOD is disabled
Sun Jan 06 13:15:34 2013 DOD is disabled
Sun Jan 06 13:15:35 2013 Restarted by 192.168.0.118
Sun Jan 06 13:15:36 2013 Associated:  00-17-C4-4E-36-2F st=0
Sun Jan 06 13:15:36 2013 DOD:triggered internally
Sun Jan 06 13:15:36 2013 DHCP:discover()
Sun Jan 06 13:15:36 2013 ADPM ep 37716 ipa 118 ip 37716 UNo0
Sun Jan 06 13:15:36 2013 ADPM ep 37716 ipa 118 ip 37716 UNo1
Sun Jan 06 13:15:38 2013 Associated:  7C-C3-A1-08-F0-09 st=0
Sun Jan 06 13:15:40 2013 DHCP:discover()
Sun Jan 06 13:15:48 2013 DHCP:discover()
Sun Jan 06 13:15:48 2013 TX TCP reset for 192.168.0.118(2910) -> 192.168.0.1(80)
Sun Jan 06 13:16:04 2013 DHCP:discover()
Sun Jan 06 13:16:10 2013 TX TCP reset for 192.168.0.118(2951) -> 192.168.0.1(80)
Sun Jan 06 13:16:36 2013 DOD:UDP trigger from 192.168.0.118:37716 to 86.124.178.100:25232
Sun Jan 06 13:16:36 2013 DOD:UDP trigger from 192.168.0.118:37716 to 95.76.149.41:39393
Sun Jan 06 13:16:36 2013 DOD:UDP trigger from 192.168.0.118:37716 to 89.136.168.38:16327
Sun Jan 06 13:16:36 2013 DOD:UDP trigger from 192.168.0.118:37716 to 109.98.227.107:24500
Sun Jan 06 13:16:36 2013 DOD:UDP trigger from 192.168.0.118:37716 to 109.99.143.68:23851
Sun Jan 06 13:16:36 2013 DHCP:discover()
Sun Jan 06 13:16:40 2013 DHCP:discover()
Sun Jan 06 13:16:48 2013 DHCP:discover()
Sun Jan 06 13:17:04 2013 DHCP:discover()
Sun Jan 06 13:17:13 2013 TX TCP reset for 192.168.0.118(3094) -> 192.168.0.1(80)
Sun Jan 06 13:17:19 2013 TX TCP reset for 192.168.0.118(3106) -> 192.168.0.1(80)
Sun Jan 06 13:17:36 2013 DOD:triggered internally
Sun Jan 06 13:17:36 2013 DHCP:discover()
Sun Jan 06 13:17:40 2013 DHCP:discover()
Sun Jan 06 13:17:45 2013 DPM ep 37716
Sun Jan 06 13:17:47 2013 DPM ep 37716
Sun Jan 06 13:17:48 2013 DHCP:discover()
Sun Jan 06 13:18:04 2013 DHCP:discover()
Sun Jan 06 13:18:36 2013 DOD:triggered internally
Sun Jan 06 13:18:36 2013 DHCP:discover()
Sun Jan 06 13:18:40 2013 DHCP:discover()
Sun Jan 06 13:18:48 2013 DHCP:discover()
Sun Jan 06 13:19:04 2013 DHCP:discover()
Sun Jan 06 13:19:50 2013 DOD:triggered internally
Sun Jan 06 13:19:50 2013 DHCP:discover()
Sun Jan 06 13:19:54 2013 DHCP:discover()
Sun Jan 06 13:19:54 2013 TX TCP reset for 192.168.0.118(3297) -> 192.168.0.1(80)
Sun Jan 06 13:19:54 2013 TX TCP reset for 192.168.0.118(3298) -> 192.168.0.1(80)
Sun Jan 06 13:19:54 2013 TX TCP reset for 192.168.0.118(3299) -> 192.168.0.1(80)
Sun Jan 06 13:19:54 2013 TX TCP reset for 192.168.0.118(3300) -> 192.168.0.1(80)
Sun Jan 06 13:19:54 2013 TX TCP reset for 192.168.0.118(3301) -> 192.168.0.1(80)
Sun Jan 06 13:19:54 2013 TX TCP reset for 192.168.0.118(3302) -> 192.168.0.1(80)
Sun Jan 06 13:19:54 2013 TX TCP reset for 192.168.0.118(3303) -> 192.168.0.1(80)
Sun Jan 06 13:19:54 2013 TX TCP reset for 192.168.0.118(3304) -> 192.168.0.1(80)
Sun Jan 06 13:19:54 2013 TX TCP reset for 192.168.0.118(3305) -> 192.168.0.1(80)
Sun Jan 06 13:19:54 2013 TX TCP reset for 192.168.0.118(3301) -> 192.168.0.1(80)
Sun Jan 06 13:19:54 2013 TX TCP reset for 192.168.0.118(3302) -> 192.168.0.1(80)
Sun Jan 06 13:19:54 2013 TX TCP reset for 192.168.0.118(3303) -> 192.168.0.1(80)
Sun Jan 06 13:19:54 2013 TX TCP reset for 192.168.0.118(3304) -> 192.168.0.1(80)
Sun Jan 06 13:19:54 2013 TX TCP reset for 192.168.0.118(3305) -> 192.168.0.1(80)
Sun Jan 06 13:19:55 2013 TX TCP reset for 192.168.0.118(3305) -> 192.168.0.1(80)
Sun Jan 06 13:20:02 2013 DHCP:discover()
Sun Jan 06 13:20:12 2013 TX TCP reset for 192.168.0.118(3326) -> 192.168.0.1(80)
Sun Jan 06 13:20:12 2013 TX TCP reset for 192.168.0.118(3327) -> 192.168.0.1(80)
Sun Jan 06 13:20:12 2013 TX TCP reset for 192.168.0.118(3328) -> 192.168.0.1(80)
Sun Jan 06 13:20:12 2013 TX TCP reset for 192.168.0.118(3329) -> 192.168.0.1(80)
Sun Jan 06 13:20:12 2013 TX TCP reset for 192.168.0.118(3330) -> 192.168.0.1(80)
Sun Jan 06 13:20:12 2013 TX TCP reset for 192.168.0.118(3331) -> 192.168.0.1(80)
Sun Jan 06 13:20:12 2013 TX TCP reset for 192.168.0.118(3332) -> 192.168.0.1(80)
Sun Jan 06 13:20:12 2013 TX TCP reset for 192.168.0.118(3330) -> 192.168.0.1(80)
Sun Jan 06 13:20:12 2013 TX TCP reset for 192.168.0.118(3331) -> 192.168.0.1(80)
Sun Jan 06 13:20:12 2013 TX TCP reset for 192.168.0.118(3332) -> 192.168.0.1(80)
Sun Jan 06 13:20:18 2013 DHCP:discover()
Sun Jan 06 13:21:04 2013 TX TCP reset for 192.168.0.118(3378) -> 192.168.0.1(80)
Sun Jan 06 13:21:04 2013 TX TCP reset for 192.168.0.118(3379) -> 192.168.0.1(80)
Sun Jan 06 13:21:04 2013 TX TCP reset for 192.168.0.118(3380) -> 192.168.0.1(80)
Sun Jan 06 13:21:04 2013 TX TCP reset for 192.168.0.118(3381) -> 192.168.0.1(80)
Sun Jan 06 13:21:04 2013 TX TCP reset for 192.168.0.118(3382) -> 192.168.0.1(80)
Sun Jan 06 13:21:04 2013 TX TCP reset for 192.168.0.118(3383) -> 192.168.0.1(80)
Sun Jan 06 13:21:05 2013 TX TCP reset for 192.168.0.118(3383) -> 192.168.0.1(80)
Sun Jan 06 13:21:13 2013 DOD:triggered internally
Sun Jan 06 13:21:13 2013 DHCP:discover()
Sun Jan 06 13:21:17 2013 DHCP:discover()
Sun Jan 06 13:21:22 2013 TX TCP reset for 192.168.0.118(3402) -> 192.168.0.1(80)
Sun Jan 06 13:21:22 2013 TX TCP reset for 192.168.0.118(3403) -> 192.168.0.1(80)
Sun Jan 06 13:21:22 2013 TX TCP reset for 192.168.0.118(3404) -> 192.168.0.1(80)
Sun Jan 06 13:21:22 2013 TX TCP reset for 192.168.0.118(3405) -> 192.168.0.1(80)
Sun Jan 06 13:21:25 2013 DHCP:discover()
Sun Jan 06 13:21:41 2013 DHCP:discover()
Sun Jan 06 13:22:23 2013 DOD:triggered internally
Sun Jan 06 13:22:23 2013 DHCP:discover()
Sun Jan 06 13:22:24 2013 Disassociated:  7C-C3-A1-08-F0-09 because idle 300 seconds
Sun Jan 06 13:22:27 2013 DHCP:discover()
Sun Jan 06 13:22:35 2013 DHCP:discover()
Sun Jan 06 13:22:51 2013 DHCP:discover()
Sun Jan 06 13:23:27 2013 DOD:triggered internally
Sun Jan 06 13:23:27 2013 DHCP:discover()
Sun Jan 06 13:23:31 2013 DHCP:discover()
Sun Jan 06 13:23:39 2013 DHCP:discover()
Sun Jan 06 13:23:55 2013 DHCP:discover()
Sun Jan 06 13:24:32 2013 DOD:triggered internally
Sun Jan 06 13:24:32 2013 DHCP:discover()
Sun Jan 06 13:24:36 2013 DHCP:discover()
Sun Jan 06 13:24:44 2013 DHCP:discover()
Sun Jan 06 13:25:00 2013 DHCP:discover()
Sun Jan 06 13:25:33 2013 DOD:triggered internally
Sun Jan 06 13:25:33 2013 DHCP:discover()
Sun Jan 06 13:25:37 2013 DHCP:discover()
Sun Jan 06 13:25:45 2013 DHCP:discover()
Sun Jan 06 13:26:01 2013 DHCP:discover()
Sun Jan 06 13:26:34 2013 DOD:triggered internally
Sun Jan 06 13:26:34 2013 DHCP:discover()
Sun Jan 06 13:26:38 2013 DHCP:discover()
Sun Jan 06 13:26:46 2013 DHCP:discover()
Sun Jan 06 13:27:02 2013 DHCP:discover()
Sun Jan 06 13:27:40 2013 DOD:triggered internally
Sun Jan 06 13:27:40 2013 DHCP:discover()
Sun Jan 06 13:27:44 2013 DHCP:discover()
Sun Jan 06 13:27:52 2013 DHCP:discover()
Sun Jan 06 13:28:08 2013 DHCP:discover()

Poti incepe prin a ne spune modelul echipamentelor, versiuni firmware, hardware, retea de internet, setari facute pe router.

Pai am laptop Dell Vostro A860,Router  Firmware Version: V2.07 , Tue, Mar 18 2008, o placa wireless atheros updata la zi, iar pe router nu am facut nici o configuratie, deoarece internetul imi este dat de o firma fara nici un fel de parola, adica in momentul in care conectez cablul la laptop imi merge automat netul. Am lasat conexiunea pe dynamic ip pe router, si o parola. La setarile de internet de pe laptop am lasat sa-si ia automat adresele. Am sa incerc sa mai vad ca poate se bate ceva cap in cap prin software ca tare e pacatos laptopul asta.

de router ce ne poti spune?

gumball3000, on 06 ianuarie 2013 - 19:23, said:

La ce te referi ?

Am rezolvat pana la urma. Acum o ora l-am facut. Aveam instalat sp3 pe xp. L-am dezinstalat, i-am dat reset, si a mers netul. Sincer habar n-am avut ce avea, din ce-am vazut eu routerul trimitea date dar laptopul nu le receptiona.

salutare,

dupa 4 ani in care m-a servit cu mandrie mi s-a ars si mie routerul un di 524 - nu am incercat sa ii schimb inca alimentatorul, dar am sa incerc zilele urmatoare.
l-am schimbat cu un tp link 1043nd

Buna alegere!

Nu reusesc sa updatez routerul din topic D-Link Dl-524 versiune b4 neam.

Se blocheaza cand incerc sau nu se restarteaza si ramane asa cu versiune V 2.04 din 2006.

Sugestii, sfaturi ?

Edited by asda, 14 November 2013 - 09:41.

Bineinteles ca n-a mai trecut mult si a murit curentul ceea ce se intampla la 2-3 luni o data si router-ul nu mai da semnal wifi nici internet prin cablu...

Am tot incercat sa-l resetez si pornit si oprit cu butonul din spate si n-am reusit sa-i fac mare lucru.

Iarasi, sugestii ?

Edited by asda, 14 November 2013 - 14:26.

cosul de gunoi sau un service specializat (costurile nu se justifica)

Si eu am un batran DI-524, Rev. B4 (cel mai prost din cate am inteles). Mi-a facut tot felul de probleme de-a lungul timpului, de la a nu mai functiona wireless-ul, pana la viteze foarte mici de transfer, chiar si pe porturile LAN. Ultimul firmware pentru el e 2.07, insa nu mai merge functia de port forwarding deloc (nici DMZ-ul). Asa ca, din dorinta de a nu-l arunca la gunoi, am cautat si am gasit mai multe variante de firmware-uri mai vechi. Dupa mai multe teste, am constatat ca firmware-ul optim este 2.04 patch 5. Nu mai pica wireless-ul, viteza de download e in regula (6MB/s - am abonament Fiberlink 1 de la RDS). In caz ca mai are cineva router de genul si face probleme, puteti descarca firmware-ul de aici: ftp://203.126.164.142/DI-524/2.04/beta-please%20do%20not%20send/20070226_524_V204Patch05(0313114011).zip (ATENTIE!!! Doar pentru REV B4).

i-am schimbat o data toti conzii (de pe placa) vreo 13 de 47uF unu de 100 si unu de 680. erau umflati, crapati. aproape nu mai mergea nici pe cablu. a mers bine 1-2 ani. (nonstop in priza - cu alte surse..ca originalul l-am aruncat de mult)

acu incepe sa deconecteze wifi-ul. semne ca iar s-au dus din conzi.  treaba e cam asa: intai face figuri pe wifi (deconectari etc)..apoi pe masura ce crapa mai mult conzii...incepe sa faca figuri si pe cablu.

acest model sta extrem de prost pe etajul de alimentare. are un IC ce converteste pana la 15VDC intrare in ce are el nevoie...3.3V

Eu am unul (la parinti) care merge din 2008... nu mai prea face fata cerintelor (traficului) de azi dar merge, trebuie sa ai rabdare cu el

probabil il baga in priza din cand in cand. daca il lasi in priza 24/24 crapa in 2-3 ani maxim.

Edited by christig, 08 August 2016 - 23:16.

Nu, e folosit din 2008 fara mari intreruperi (1-2 zile max)