Sign In
Create Account
Conexiune la 100 mbps FL1000...
Last Updated: Feb 02 2017 02:35, Started by
iullius
, Dec 24 2016 17:09
·
0
0
#19
Posted 10 January 2017 - 21:57
|
OK am pus un switch intre mine is RDS si.. merge in gigabit.
Concluzia este clara: De vina este echipamentul RDS, switch-ul banuiesc. |
Back to top
#20
Posted 29 January 2017 - 13:11
|
Asa e merge la toata lumea numai pe o basina de echipament nu si problema este de la ISP. Minunat. De fapt s-a zis pe prima pagina ca e vorba de o problema de negociere link intre 2 echipamente, al tau si a lor. Adica daca o luam asa vinovat e si echipamentul tau si a lor. Ai incercat sa iti fortezi placile tale alea 4 in diverse moduri de negociere sa vezi ce se petrece? Nop e ca e vina nenorocitul de ISP. Problema nu e niciodata de la client.
|
#21
Posted 29 January 2017 - 19:31
|
Asa le place la unii sa se bage in seama aiurea, mama mama...
Care o fi urmatoarea intrebare daca am verificat cablul? Normal ca am incercat fortarea in Gigabit, nu isi mai ia link neam, nici una din cele patru placi de retea. Ca sa elimin problema calculatorului am montal placa mpcie cu cele 2 LAN-uri Intel I350 cu adaptor mPCIe la PCIe in alt PC si la fel 100 Megabit link. Din moment ce aceleasi 4 placi de retea isi iau link gigabit si merg in gigabit conectate la RDS prin switch sau router cum poti spune ca este vina echipamentului meu? Plus ca ele merg conectate la orice altceva fara probleme, adica in opinia ta ce ar trebui sa faca clientul sa-si schimbe calculatorul sau RDS ar trebui sa rezolve un caz rar prin inlocuirea unui rahat de switch cu probleme? Uite cu ce dau ei FL1000...: 
Routere_RDS.jpg 316.88K
46 downloads
|
#22
Posted 29 January 2017 - 20:08
|
Ai fi uimit cat de bine isi fac treaba TP-Link-urile alea. Si unii mai stiu una alta de asta se si baga in seama nu ca altii care concluzioneaza direct ca e de la ISP. I-a baga o cupla UTP in loc de un switch si un patch din cupla pana la jucaria ta si vezi face link? In una bucata mie evident. Eu zic ca sunt placile alea mai ciufute adica sunt mai sensibile si cand simnt ceva pe cablu fac fallback la 100FD.
Quote
2.1 Specification Clarifications 1. SerDes: AN_TIMEOUT Only Works When Link Partner Idle Clarification: The auto-negotiation time-out mechanism (PCS_LCTL.AN_TIMEOUT_EN) only works if the SerDes partner is sending idle code groups continuously for the duration of the time-out period (the usual case). If the partner is transmitting packets in auto-negotiation, time-out will not occur since auto-negotiation is restarted at the beginning of each packet. If the partner has an application that indefinitely transmits data in spite of the lack of response, it is possible that link will not be established. Workaround: If this is a concern, the auto-negotiation time-out mechanism may be considered unreliable and an additional software mechanism can be used to disable auto-negotiation (if sync is maintained without a link being established (PCS_LSTS.SYNC_OK=1 and PCS_LSTS.LINK_OK=0) for an extended period of time). |
#23
Posted 29 January 2017 - 20:26
|
Ar trebui sa am si cupla UTP...
Plus ca m-am rugat de cel de la RDS care a venit in locatie, hai mai sa vedem direct in switch, il bagam acolo si macar lamurim daca este o problema de cablu/traseu, nimic, nu a vrut neam, o tinea mortis ca ii merge pe laptopul lui de test, de parca eu aveam laptopul lui... Uite aici modelul de LAN RTL8168E PCI-E Gigabit Ethernet NIC: +-1c.0-[01]----00.0 Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] +-1c.1-[02]----00.0 Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] +-1c.2-[03-04]--+-00.0 Intel Corporation I350 Gigabit Network Connection [8086:1521] | \-00.1 Intel Corporation I350 Gigabit Network Connection [8086:1521] Edited by iullius, 29 January 2017 - 20:28. |
#24
Posted 29 January 2017 - 20:54
|
Ca exemplu: stiu pe cineva care a patit-o cu un archer c2 sau nu mai stiu cu ce router care nici de-al dracu nu negocia in 1000 pe sarma venita de la cutia redese desi cand baga in laptop si in wan la router ii facea link pe 1000. Solutia eleganta sau nu a fost sa bage o cupla UTP pe traseu si sa ii negocieze router-ul in 1000 cu redese-ul. Astea sunt din categoria fenomene paranormale. Pentru mine ca nu am cum sa reproduc fenomenul sa vad ce se intampla defapt.
PS: Uite un topic interesant de citit, nu cred ca ajuta dar merita citit: https://arstechnica.com/civis/viewtopic.php?f=10&t=50247 Mda nu gasesc ceva foarte relevant legat de modelul ala de cip Realtek. |
#25
Posted 29 January 2017 - 21:20
|
Pai problema mea este ca nu vreau sa bag router intre mine si RDS ci vreau sa pun firewall intre mine si RDS/restul lumii.
|
#26
Posted 29 January 2017 - 21:24
|
Router/ switch / firewall same shit tot echipament de retea e. Eu ti-am dat exemplu ca s-a mai intamplat si cu alt tip de echipament acelasi lucru si ca s-a rezolvat cu o cupla UTP. Poti incerca sa pui o cupla si un patch in jucaria ta, efectiv prelungesti sarma redese cu 1 metru de exemplu cat e patch-ul si vezi daca asa iti negociaza in 1000 cu echipamentul ala.
|
#27
Posted 29 January 2017 - 21:42
|
Eu sunt mai "japones" adica intreb de 10 ori ca sa pricep 100% bine, cupla UTP am idee ce este insa nu am idee ce este acel patch, inca un cablu UTP, la asta te referi?
Are importanta daca cupla este cat5/6 ecranata sau nu? |
#28
Posted 29 January 2017 - 23:51
|
cupla UTP:
[ https://conectica.ro/fisiere/produse/principala/2/21.17.3043M.jpg - Pentru incarcare in pagina (embed) Click aici ] Patchcord, o bucata de cablu UTP deja mufat: [ http://infocityonline.com/ebayimage/cat6lancable02.jpg - Pentru incarcare in pagina (embed) Click aici ] Eu port la mine 3 cuple utp din cele mai ieftine posibile, m-au ajutat de 2 - 3 ori pana acum cand am avut nevoie sa prelungesc un cablu pana la laptop. Astea ale mele sunt cred ca 1 - 2 Lei, cel de care am zis mai sus ca a folosit o cupla si a rezolvat cu negocierea tot de asta ieftina a folosit. Mai ai posibilitatea sa incerci sa convingi pe cei de la redese sa schimbe cablul de la cutie pana la tine. Sorry de formatare dar nu le am cu atasamentul pozelor. Edited by MembruAnonim, 29 January 2017 - 23:54. |
|
#29
Posted 30 January 2017 - 21:20
|
@Kagaroth Am testat cu cupla UTP si patch cum ai zis, rezultatul:
Placile Intel nici o schimbare tot 100 Mbit. Placile Realtek, la fel ca si cand pun cablul crossover, se conecteaza/deconecteaza de cateva ori(in gigabit) apoi raman conectate in gigabit dar viteza de transfer este de mizerie: http://beta.speedtes...sult/6011033876 |
#30
Posted 31 January 2017 - 13:14
|
Cat de mare e jucaria aia pe care vrei sa o folosesti ca firewall? Cat de departe e cutia RDS? Poti incerca sa faci o sesizare sa vina la tine si sa mergi cu jucaria la cutie sa pui un patch in ea si in switch si elimini asa si problema cablului. Eventual incerci si in alt port din switch. Eu tot la problema de incompatibilitate hardware ma gandesc. Desi as vrea sa pot intra pe switch sa vada si ochiul meu ce raporteaza respectivul switch cand conectezi jucaria la el.
PS: Baga un distro Linux, daca ai alt OS pe jucarie, si da ethtool -S $ethConectatLaRDS. Posteaza aici output. |
#31
Posted 31 January 2017 - 15:49
|
Jucaria este foarte mica cat doua harduri de 3.5 inch puse unul langa altul.
Am incercat ce zici tu si am scris aici: https://forum.softpe.../#entry20453115 , cel care s-a deplasa sa constate ce spusesem eu in sesizare nu a vrut neam sa mearga la cutie care este un etaj mai sus... Am bagat eu un ochi la cutie(de acolo si poza) sa vad ce saracii au acolo, insa nu m-am bagat sa-mi conectez eu echipamentul pentru ca pot vede acest lucru si nu am chef sa ma cert cu redese pe amanunte de genul asta.. Am testat fiecare NIC pe linux cum ai cerut: Realtek#1: Settings for enp1s0: Supported ports: [ TP MII ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Supported pause frame use: No Supports auto-negotiation: Yes Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Advertised pause frame use: Symmetric Receive-only Advertised auto-negotiation: Yes Link partner advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full Link partner advertised pause frame use: No Link partner advertised auto-negotiation: Yes Speed: 100Mb/s Duplex: Full Port: MII PHYAD: 0 Transceiver: internal Auto-negotiation: on Supports Wake-on: pumbg Wake-on: d Current message level: 0x00000033 (51) drv probe ifdown ifup Link detected: yes NIC statistics: tx_packets: 103 rx_packets: 50 tx_errors: 0 rx_errors: 0 rx_missed: 0 align_errors: 0 tx_single_collisions: 0 tx_multi_collisions: 0 unicast: 23 broadcast: 27 multicast: 0 tx_aborted: 0 tx_underrun: 0 Realtek#2: Settings for ens1: Supported ports: [ TP MII ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Supported pause frame use: No Supports auto-negotiation: Yes Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Advertised pause frame use: Symmetric Receive-only Advertised auto-negotiation: Yes Link partner advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full Link partner advertised pause frame use: No Link partner advertised auto-negotiation: Yes Speed: 100Mb/s Duplex: Full Port: MII PHYAD: 0 Transceiver: internal Auto-negotiation: on Supports Wake-on: pumbg Wake-on: d Current message level: 0x00000033 (51) drv probe ifdown ifup Link detected: yes NIC statistics: tx_packets: 154 rx_packets: 116 tx_errors: 0 rx_errors: 0 rx_missed: 0 align_errors: 0 tx_single_collisions: 0 tx_multi_collisions: 0 unicast: 31 broadcast: 83 multicast: 2 tx_aborted: 0 tx_underrun: 0 Intel#1: Settings for enp3s0f0: Supported ports: [ TP ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Supported pause frame use: Symmetric Supports auto-negotiation: Yes Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Advertised pause frame use: Symmetric Advertised auto-negotiation: Yes Speed: 100Mb/s Duplex: Full Port: Twisted Pair PHYAD: 1 Transceiver: internal Auto-negotiation: on MDI-X: off (auto) Supports Wake-on: pumbg Wake-on: g Current message level: 0x00000007 (7) drv probe link Link detected: yes NIC statistics: rx_packets: 30 tx_packets: 136 rx_bytes: 6432 tx_bytes: 22750 rx_broadcast: 30 tx_broadcast: 25 rx_multicast: 0 tx_multicast: 111 multicast: 0 collisions: 0 rx_crc_errors: 0 rx_no_buffer_count: 0 rx_missed_errors: 0 tx_aborted_errors: 0 tx_carrier_errors: 0 tx_window_errors: 0 tx_abort_late_coll: 0 tx_deferred_ok: 0 tx_single_coll_ok: 0 tx_multi_coll_ok: 0 tx_timeout_count: 0 rx_long_length_errors: 0 rx_short_length_errors: 0 rx_align_errors: 0 tx_tcp_seg_good: 0 tx_tcp_seg_failed: 0 rx_flow_control_xon: 0 rx_flow_control_xoff: 0 tx_flow_control_xon: 0 tx_flow_control_xoff: 0 rx_long_byte_count: 6432 tx_dma_out_of_sync: 0 tx_smbus: 0 rx_smbus: 0 dropped_smbus: 0 os2bmc_rx_by_bmc: 0 os2bmc_tx_by_bmc: 0 os2bmc_tx_by_host: 0 os2bmc_rx_by_host: 0 tx_hwtstamp_timeouts: 0 rx_hwtstamp_cleared: 0 rx_errors: 0 tx_errors: 0 tx_dropped: 0 rx_length_errors: 0 rx_over_errors: 0 rx_frame_errors: 0 rx_fifo_errors: 0 tx_fifo_errors: 0 tx_heartbeat_errors: 0 tx_queue_0_packets: 15 tx_queue_0_bytes: 930 tx_queue_0_restart: 0 tx_queue_1_packets: 92 tx_queue_1_bytes: 15954 tx_queue_1_restart: 0 tx_queue_2_packets: 29 tx_queue_2_bytes: 5322 tx_queue_2_restart: 0 tx_queue_3_packets: 0 tx_queue_3_bytes: 0 tx_queue_3_restart: 0 rx_queue_0_packets: 14 rx_queue_0_bytes: 840 rx_queue_0_drops: 0 rx_queue_0_csum_err: 0 rx_queue_0_alloc_failed: 0 rx_queue_1_packets: 16 rx_queue_1_bytes: 5472 rx_queue_1_drops: 0 rx_queue_1_csum_err: 0 rx_queue_1_alloc_failed: 0 rx_queue_2_packets: 0 rx_queue_2_bytes: 0 rx_queue_2_drops: 0 rx_queue_2_csum_err: 0 rx_queue_2_alloc_failed: 0 rx_queue_3_packets: 0 rx_queue_3_bytes: 0 rx_queue_3_drops: 0 rx_queue_3_csum_err: 0 rx_queue_3_alloc_failed: 0 Intel#2: Settings for enp3s0f1: Supported ports: [ TP ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Supported pause frame use: Symmetric Supports auto-negotiation: Yes Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Advertised pause frame use: Symmetric Advertised auto-negotiation: Yes Speed: 100Mb/s Duplex: Full Port: Twisted Pair PHYAD: 1 Transceiver: internal Auto-negotiation: on MDI-X: off (auto) Supports Wake-on: pumbg Wake-on: g Current message level: 0x00000007 (7) drv probe link Link detected: yes NIC statistics: rx_packets: 27819 tx_packets: 1841 rx_bytes: 40382443 tx_bytes: 184425 rx_broadcast: 561 tx_broadcast: 51 rx_multicast: 23 tx_multicast: 184 multicast: 23 collisions: 0 rx_crc_errors: 0 rx_no_buffer_count: 0 rx_missed_errors: 0 tx_aborted_errors: 0 tx_carrier_errors: 0 tx_window_errors: 0 tx_abort_late_coll: 0 tx_deferred_ok: 0 tx_single_coll_ok: 0 tx_multi_coll_ok: 0 tx_timeout_count: 0 rx_long_length_errors: 0 rx_short_length_errors: 0 rx_align_errors: 0 tx_tcp_seg_good: 4 tx_tcp_seg_failed: 0 rx_flow_control_xon: 0 rx_flow_control_xoff: 0 tx_flow_control_xon: 0 tx_flow_control_xoff: 0 rx_long_byte_count: 40382443 tx_dma_out_of_sync: 0 tx_smbus: 0 rx_smbus: 0 dropped_smbus: 0 os2bmc_rx_by_bmc: 0 os2bmc_tx_by_bmc: 0 os2bmc_tx_by_host: 0 os2bmc_rx_by_host: 0 tx_hwtstamp_timeouts: 0 rx_hwtstamp_cleared: 0 rx_errors: 0 tx_errors: 0 tx_dropped: 0 rx_length_errors: 0 rx_over_errors: 0 rx_frame_errors: 0 rx_fifo_errors: 0 tx_fifo_errors: 0 tx_heartbeat_errors: 0 tx_queue_0_packets: 67 tx_queue_0_bytes: 11743 tx_queue_0_restart: 0 tx_queue_1_packets: 135 tx_queue_1_bytes: 13523 tx_queue_1_restart: 0 tx_queue_2_packets: 440 tx_queue_2_bytes: 47090 tx_queue_2_restart: 0 tx_queue_3_packets: 1199 tx_queue_3_bytes: 103262 tx_queue_3_restart: 0 rx_queue_0_packets: 22752 rx_queue_0_bytes: 33301765 rx_queue_0_drops: 0 rx_queue_0_csum_err: 0 rx_queue_0_alloc_failed: 0 rx_queue_1_packets: 2638 rx_queue_1_bytes: 3669552 rx_queue_1_drops: 0 rx_queue_1_csum_err: 0 rx_queue_1_alloc_failed: 0 rx_queue_2_packets: 172 rx_queue_2_bytes: 37008 rx_queue_2_drops: 0 rx_queue_2_csum_err: 0 rx_queue_2_alloc_failed: 0 rx_queue_3_packets: 2257 rx_queue_3_bytes: 3262842 rx_queue_3_drops: 0 rx_queue_3_csum_err: 0 rx_queue_3_alloc_failed: 0In linux spre deosebire de Windows NIC-urile Realtek isi iau link cand sunt conectate la RDS foarte greu. dmesg si xmesg: https://www.dropbox....redese.txt?dl=0 https://www.dropbox....redese.txt?dl=0 BTW ce vezi in log "enp3s0f1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX" este conectat prin router pana sa schimb pe direct. Edited by iullius, 31 January 2017 - 15:52. |
#32
Posted 31 January 2017 - 16:57
|
La o prima privire, o problema, switch-ul RDS anunta doar 10 / 100 HD / FD, vad ca placile tale anunta si 1000 ca mod supportat. BS cu intel care nu arata si ce primeste de la partener. Si I217-V face la fel
 .iullius, on 31 ianuarie 2017 - 15:49, said:
Link partner advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full PS: Dropbox-ul nu e accesibil de la mine cel mai probabil, cred ca filtrez ceva ce nu trebuie si trebuie sa verific firewall-ul. |
#33
Posted 31 January 2017 - 20:53
|
Le-am pus pe pastebin: http://pastebin.com/B9rbYs22 si http://pastebin.com/GM1qSPYi
O sa incerc maine ce ai zis, chiar sunt curios ce raspunde switch-ul RDS. |
|
#35
Posted 01 February 2017 - 19:17
|
OK am incercat ce ai zis tu si acum sunt si mai rau in ceata...
Pe NIC-urile Intel nici o schimbare, nu vrea neam gigabit. Pe NIC-urile Realtek iata ce ciudatenii: Realtek#1 este "hotarat" pe 100 mbit: autoneg on: Settings for ens1: Supported ports: [ TP MII ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Supported pause frame use: No Supports auto-negotiation: Yes Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Advertised pause frame use: Symmetric Receive-only Advertised auto-negotiation: Yes Link partner advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full Link partner advertised pause frame use: No Link partner advertised auto-negotiation: Yes Speed: 100Mb/s Duplex: Full Port: MII PHYAD: 0 Transceiver: internal Auto-negotiation: on Supports Wake-on: pumbg Wake-on: d Current message level: 0x00000033 (51) drv probe ifdown ifup Link detected: yes autoneg off: Settings for ens1: Supported ports: [ TP MII ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Supported pause frame use: No Supports auto-negotiation: Yes Advertised link modes: Not reported Advertised pause frame use: No Advertised auto-negotiation: No Speed: 100Mb/s Duplex: Full Port: MII PHYAD: 0 Transceiver: internal Auto-negotiation: off Supports Wake-on: pumbg Wake-on: d Current message level: 0x00000033 (51) drv probe ifdown ifup Link detected: yes Realtek#2 insa: autoneg on: Settings for enp1s0: Supported ports: [ TP MII ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Supported pause frame use: No Supports auto-negotiation: Yes Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Advertised pause frame use: Symmetric Receive-only Advertised auto-negotiation: Yes Link partner advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Link partner advertised pause frame use: No Link partner advertised auto-negotiation: Yes Speed: 1000Mb/s Duplex: Full Port: MII PHYAD: 0 Transceiver: internal Auto-negotiation: on Supports Wake-on: pumbg Wake-on: d Current message level: 0x00000033 (51) drv probe ifdown ifup Link detected: yes autoneg off: Settings for enp1s0: Supported ports: [ TP MII ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Supported pause frame use: No Supports auto-negotiation: Yes Advertised link modes: Not reported Advertised pause frame use: No Advertised auto-negotiation: No Speed: 10Mb/s Duplex: Half Port: MII PHYAD: 0 Transceiver: internal Auto-negotiation: off Supports Wake-on: pumbg Wake-on: d Current message level: 0x00000033 (51) drv probe ifdown ifup Link detected: yes Sa mor de mai inteleg ceva(LOL) Cu autoneg isi ia link in gigabit insa conexiunea nu este stabila(in loop se conecteaza/deconecteaza) incat nu am reusit sa ma conectez cu pppoe. Cu autoneg off isi ia link de 10 mbit... Pe Intel am incercat si utilitarele UEFI de aici: http://www.helpjet.n...76-extract.html Insa nu am reusit sa scot nimic detaliat din debug: -------------------------- Begin Diagnostic Testing --------------------------- Intel Network Adapter in bus/device/function: 3/0/1 Pass 1 at 16:25 Register Tests Passed Pass 1 at 16:25 EEPROM Tests Passed Pass 1 at 16:25 Interrupt Tests Passed Pass 1 at 16:27 Loopback Tests Passed Pass 1 at 16:28 Link Tests Failed Pass 1 at 16:28 Network Tests Failed -------------------------- Tests Completed - Errors ---------------------------
IMG_20170201_184441.jpg 291.12K
14 downloads
IMG_20170201_185013.jpg 259.3K
14 downloadsP.S. Conectat la router sau switch toate testele sunt OK. IMHO este, cum am mai zis, saracia aia de switch RDS de vina. Problema este ce fac eu, cum ii pot determina pe cei de la RDS sa verifice/corecteze problema? Pana acum toate incercarile mele au fost un mare esec! Edited by iullius, 01 February 2017 - 19:20. |
#36
Posted 02 February 2017 - 02:03
|
Nu stiu de unde au scos switch-urile alea TP LINK, RDS folosea switch-uri ZTE dar pe 100 mbps. La 1000 mbps acum se trece pe FTTH de apartament, de fapt cam la orice abonament.
Inca odata vedem ce probleme tampite are marca asta de Tembel Link, routerele lor m-au enervat la culme. |
Anunturi
Bun venit pe Forumul Softpedia!
▶ 0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users
-
- Change Theme
- English
- Mark Community Read
- Termene & conditii
- Confidentialitate
- Consimtamant
- Cookies
- Help
© 2001-2024 Softpedia. All rights reserved. Softpedia® and the Softpedia logo are registered trademarks of SoftNews Net SRL.
Ora implicita a Forumului Softpedia este ora standard a Romaniei (GMT+2). Mai multe informatii →
⚠ Postarile afisate pe Forumul Softpedia reprezinta o opinie subiectiva a membrilor care le-au publicat si nu a SoftNews Net SRL.