Latenta UPC

tifreaf, on 13 februarie 2016 - 21:57, said:

Dar tu ai scris asta:

tifreaf, on 13 februarie 2016 - 21:10, said:

Eu doar am vrut sa stiu cum ti-ai dat tu seama ca daca UPC-RDS merge prost, atunci sigur e problema la UPC
Si de ce daca UPC-RDS merge prost dar UPC-restul merge bine, atunci UPC are un serviciu de proasta calitate

Edited by 654321, 13 February 2016 - 22:06.

654321, on 13 februarie 2016 - 22:02, said:

Am postat niste log-uri mai la inceput, daca te uiti pe ele o sa-ti dai seama,
Apropo al cui e serverul rds-peer.astralnet.ro [83.103.173.34] ?

UPC RO

tifreaf, on 13 februarie 2016 - 22:17, said:

IP-ul este al UPC dar nu pot ajunge la el...

 
C:\WINDOWS\system32>tracert 83.103.173.34
Tracing route to RDS-peer.astralnet.ro [83.103.173.34]
over a maximum of 30 hops:
  1	<1 ms	<1 ms	<1 ms  192.168.1.1
  2	 *	   10 ms	 8 ms  10.190.0.1
  3	 *		*		*	 Request timed out.
  4	 *		*		*	 Request timed out.
  5	 *		*		*	 Request timed out.
  6	 *		*		*	 Request timed out.
  7	 *		*		*	 Request timed out.
  8	 *		*		*	 Request timed out.
  9	 *		*		*	 Request timed out.
10	 *		*		*	 Request timed out.
11	 *		*		*	 Request timed out.
12	 *		*		*	 Request timed out.
13	 *		*		*	 Request timed out.
14	 *		*		*	 Request timed out.
15	 *		*		*	 Request timed out.
16	 *		*		*	 Request timed out.
17	 *		*		*	 Request timed out.
18	 *		*		*	 Request timed out.
19	 *		*		*	 Request timed out.
20	 *		*		*	 Request timed out.
21	 *		*		*	 Request timed out.
22	 *		*		*	 Request timed out.
23	 *		*		*	 Request timed out.
24	 *		*		*	 Request timed out.
25	 *		*		*	 Request timed out.
26	 *		*		*	 Request timed out.
27	 *		*		*	 Request timed out.
28	 *		*		*	 Request timed out.
29	 *		*		*	 Request timed out.
30	 *		*		*	 Request timed out.
Trace complete.

654321, on 13 februarie 2016 - 22:25, said:

Pe prima pagina este un log de la mine;
eu pe acolo ies din UPS spre RDS si  seara am peste 100ms latenta pana la RDS-peer.astralnet.ro
Am pus si un log din RDS spre RDS-peer.astralnet.ro si am latenta 19 ms
Deci puse cap la cap a cui e vina ? ce zici UPC sau RDS?

Pai si eu ti-am pus trace spre RDS si eu nu ies pe acolo dar tot peste 100ms am doar cu RDS.
Si mai mult... ti-am pus trace si cu Telekom si ies spre Telekom prin acelasi hop prin care ies spre RDS si ce sa vezi....

Edited by 654321, 13 February 2016 - 22:37.

RDS-peer ala e in RDS, altfel nu as fi avut 1ms in el.

IP apartine UPC, e peeringul lor.

 rdspeer.png   5.9K   24 downloads

654321, on 13 februarie 2016 - 22:35, said:

Pai tocmai ti-am zis ca din RDS (cealalta parte a conexiuni) pana la RDS-peer.astralnet.ro am latenta 19 ms, a cui e vina? clar UPC

MembruAnonim, on 13 februarie 2016 - 22:38, said:

Eu nici macar nu am ruta spre el...

Ai, dar e cu firewall si nu raspunde la ICMP.

Adica mie din UPC nu imi raspunde dar iti raspunde tie din RDS? Si in 1ms... si mai ziceai de peering....

Edited by 654321, 13 February 2016 - 22:43.

Da, pai pare a fi in RDS. Depinde de cum e setat firewallul, banuiesc ca nu raspunde extern. Nici astora nu le raspunde:

http://lg.alsysdata.net/

Query: traceroute Layer4 83.103.173.34
TTL LFT trace to RDS-peer.astralnet.ro (83.103.173.34):80/tcp
1  [25409] [ALSYSDATA] ns.alsys.ro (93.190.144.1) 0.2ms
2  [25409] [ALSYSDATA] als-r-border.alsysdata.eu (93.190.151.147) 0.3ms
3  [39737] [NETVISION-AS] 193.120.37.89.in-addr.arpa (89.37.120.193) 0.9ms
**  [80/tcp no reply from target]  Try advanced options (use -VV to see packets).

Pai raspunde in 1ms ca nu e in UPC ci la RDS, nu ajunge sa se atinga de peering.

Edited by MembruAnonim, 13 February 2016 - 22:45.

Deci ala clar e in RDS, nu?

1 1 ms 1 ms 4 ms  hitronhub.home [10.0.0.1]
  2    14 ms    16 ms    14 ms  INTEL_CE_LINUX [82.210.172.1]
  3    24 ms    21 ms    17 ms  INTEL_CE_LINUX [95.77.37.81]
  4    42 ms    31 ms    29 ms  INTEL_CE_LINUX [84.116.217.61]
  5    26 ms    26 ms    29 ms  ro-buh01a-ri1-ae2-v1558.upcnet.ro [84.116.224.17
4]
  6    30 ms    28 ms    29 ms  ro-hr02a-rd2-v1625.upcnet.ro [84.116.225.186]
  7    33 ms    22 ms    29 ms  ro-bv01a-rc1-v1577.upcnet.ro [84.116.224.249]
  8    32 ms    49 ms    29 ms  ro-buh01a-ri1-ae1-v1684.upcnet.ro [84.116.216.16
6]
  9    92 ms    94 ms   109 ms  rds-peer.astralnet.ro [83.103.173.34]
10   118 ms   103 ms   104 ms  bb01.timisoara.rdsnet.ro [213.154.121.130]
11   101 ms   109 ms   102 ms  qr12.timisoara.rdsnet.ro [213.154.121.149]
12 * * * Request timed out.
13   102 ms   109 ms   101 ms  x.x.x.x static.brasov.rdsnet.ro [x.x.x.x]
Trace complete.

Asta e un traceroute de acasa (UPC) la un IP din RDS

Aici ro-buh01a-ri1-ae1-v1684.upcnet.ro [84.116.216.166] ai iesit din UPC pentru ca tot pe acolo ies si eu.

tracert 83.103.173.34
Tracing route to rds-peer.astralnet.ro [83.103.173.34]
over a maximum of 30 hops:
  1 <1 ms <1 ms <1 ms  192.168.1.1
  2 1 ms 1 ms 1 ms  86-120-37-1.static.brasov.rdsnet.ro [86.120.37.1
]
  3 9 ms 10 ms 9 ms  10.220.131.13
  4 9 ms 10 ms 10 ms  10.220.131.13
  5 10 ms 10 ms 10 ms  10.220.131.9
  6 19 ms 19 ms 19 ms  rds-peer.astralnet.ro [83.103.173.34]
Trace complete.

Asta e un traceroutedin RDS spre rds-peer.astralnet.ro

654321, on 13 februarie 2016 - 22:50, said:

si ma intorc tot in UPC, de ce?

Asta pare a fi prin peeringul direct UPC-RDS (daca n-o fi vreo manevra la hop-ul 8 unde si creste latenta), ping mare pentru ca e depasita capacitatea demult

LE: penultimul. Ultimul e local RDS.

Edited by MembruAnonim, 13 February 2016 - 22:57.

tifreaf, on 13 februarie 2016 - 22:52, said:

Pentru ca urmatorul nu mai este UPC. Nu cred ca w21 ar avea 1ms in el daca ar fi UPC.