Package loss 60%

[moose]

Out of curiousity, where did you learn all this stuff?

I would love to have the power of understanding the inner workings of the net.

[tofri]

This morning the connection is perfect as never before.

Constant pings around 180ms, no packet losses.

But now I have to go to work  AAARRRGGGHHHHH

Cant HTC do anything against work, because of work I cant fly now in the Main;)


Thanks Skuzzy for your help!!!!

Tofri

[Alino]

Damn damn damn ;-)))))))) like Tofri said perfekt connect but we must go to work. I´m lucky that we can play this evening, hope we unlearned not to much.

Thank`s alot for your Help Skuzzy.
cya all

[Duedel]

Can't believe it. It works? Im at work so i cant test it. Skuzzy Alino Tofri many thx for ur help. Anybody knows where's the cause for the problem, Telekom?

BTW dtx heute wollen wir uns so ab 20:00 in der MA treffen.

[devious]

Sorry, bin bis Mittwochabend in München und ohne Kiste. Vielleicht kann ich ein I-Net Cafee auftreiben...

[blitz]

Hallo Leute,

no probs here since yesterday when nearly everybody in Main got bad connect.

If you german people wanna try out  something beside
Fu(&/()%§"!)=&/((%$§§ing Telekom go Q-dsl.de.
It's a bit more expensive ,59 Eu flat, but worth the price.

You may wanna get MTU-Speed too. It's a nice little programm that helps to optimize Win network. It's freeware, btw.


Normally gettin around 170ms This was taken Tuesday around 1 oc daytime



Host Name                        IP Address        Hop    Ping Time   Ping Avg   % Loss    Pkts r/s   Ping best/worst
tpl.hitechcreations.com          216.234.247.240          137ms       137ms      0%        30 / 30    137ms / 139ms


Host Name                        IP Address        Hop    Ping Time   Ping Avg   % Loss    Pkts r/s   Ping best/worst
* Unknown Host *                 212.202.222.33    2      3ms
* Unknown Host *                 62.67.36.73       3      3ms
ge-7-0-0.mp2.Berlin1.Level3.net  195.122.132.130   4      3ms
so-1-0-0.mp1.London2.Level3.net  212.187.128.49    5      24ms
so-1-0-0.mp1.Washington1.Level3.n212.187.128.138   6      96ms
gigabitethernet7-2.core1.Washingt64.159.18.133     7      97ms
above-level3-ds3.iad.above.net   209.244.219.150   8      97ms
acr1-loopback.Dallas.cw.net      208.172.130.61    9      135ms
aar2-loopback.Dallas.cw.net      208.172.130.7     10     135ms
internap.Dallas.cw.net           208.172.135.70    11     142ms
border3.ge3-1-bbnet1.ext1.dal.pna216.52.191.22     12     141ms
theplanet-2.border3.003.dal.pnap.216.52.189.222    13     141ms
tpl.hitechcreations.com          216.234.247.240   14     137ms


Host Name                        IP Address        Hop    Ping Time   Ping Avg   % Loss    Pkts r/s   Ping best/worst
* Unknown Host *                 212.202.222.33    2      3ms
* Unknown Host *                 62.67.36.73       3      4ms
ge-7-0-0.mp2.Berlin1.Level3.net  195.122.132.130   4      3ms
so-1-0-0.mp1.London2.Level3.net  212.187.128.49    5      25ms
so-1-0-0.mp1.Washington1.Level3.n212.187.128.138   6      97ms
gigabitethernet7-2.core1.Washingt64.159.18.133     7      98ms
above-level3-ds3.iad.above.net   209.244.219.150   8      98ms
acr1-loopback.Dallas.cw.net      208.172.130.61    9      135ms
aar2-loopback.Dallas.cw.net      208.172.130.7     10     135ms
internap.Dallas.cw.net           208.172.135.70    11     219ms
border3.ge3-1-bbnet1.ext1.dal.pna216.52.191.22     12     141ms
theplanet-2.border3.003.dal.pnap.216.52.189.222    13     141ms
tpl.hitechcreations.com          216.234.247.240   14     137ms


Blitz from Berlin

[fffreeze220]

For all u German dudes QSC rules the world. Fek the TELEKOM.

Got it sonce nearly a year and satisfied with it. it is worth every cent u pay for itQ-DSL

[moose]

glad you folks are back up and running. now come fight the bishrook hordes.

[Skuzzy]

Originally posted by moose
Out of curiousity, where did you learn all this stuff?

I would love to have the power of understanding the inner workings of the net.

Geez moose....just through experience I guess.  After doing this type of work for over 20 years, ya just pick up stuff.

I do spend a lot of time reading and researching though.  The Internet and the associated protocols are always changing, so in some sense I am always in school.
I do spend a bit of time and money at Barnes and Noble as well.

[Skuzzy]

I did some testing this morning and it does appear Telekom has corrected the routing problem.

Thank you to the guys that gave them the data to get this fixed.  We are all in this together and times like this is when we needed to bang from both ends to get it fixed.

A special thanks to those that posted the traces, which enabled me to find out what the problem (at least this one anyways) was.

[tofri]

AAAAAAAAAAARRRRRRRRRRRRGGGGGG GGGGGGGGGGGGGGGGGGHHHHHHHHHHH HHHHHHHHHHHHHH

Come home from work and the same SH#T as the last days

Tofri

[Skuzzy]

Dang it.  They fixed one problem and introduced another.  Here is a trace.

/usr/sbin/traceroute 217.237.156.110
traceroute to 217.237.156.110 (217.237.156.110), 30 hops max, 38 byte packets
 1  core0.dllstx.theplanet.com (216.234.234.1)  24.391 ms  4.018 ms  2.242 ms
 2  border3.fe5-1.theplanet-2.003.dal.pnap.net (216.52.189.221)  1.179 ms  1.776
 ms  3.622 ms
 3  core4.ge1-0-0-bbnet2.ext1.dal.pnap.net (216.52.191.99)  10.980 ms  6.967 ms
 13.668 ms
 4  so-1-2-0.a11.dllstx01.us.ra.verio.net (157.238.227.225)  6.334 ms  1.188 ms
 1.518 ms
 5  ge-6-0-0.r02.dllstx01.us.bb.verio.net (129.250.31.48)  1.300 ms  1.521 ms  1
.989 ms
 6  p16-2-0-0.r00.stngva01.us.bb.verio.net (129.250.5.35)  36.071 ms  33.998 ms
 36.544 ms
 7  p4-0.dt.stngva01.us.bb.verio.net (129.250.9.198)  40.303 ms  32.558 ms  32.4
44 ms
 8  Vienna-gw12.USA.net.DTAG.DE (62.156.131.173)  129.331 ms  130.004 ms  127.11
8 ms
 9  H-SA2.H.DE.net.DTAG.DE (62.156.131.181)  130.369 ms  131.999 ms  130.722 ms
10  H-SA1.H.DE.net.dtag.de (62.154.49.157)  134.790 ms  127.400 ms  128.544 ms
11  K-SA1.K.DE.net.dtag.de (62.154.0.118)  129.815 ms  128.461 ms  128.115 ms
12  BN-SA1.BN.DE.net.dtag.de (62.154.1.98)  126.760 ms  126.768 ms *
13  BN-EB1.BN.DE.net.dtag.de (62.154.66.38)  133.343 ms *  131.338 msace.

Notice where I was tracing to?  217.237.156.110, and notice where it stops.  The IP address is a router, which cannot be reached now.  Also, notice the dropped packets/timeouts in the last 2 routers.
Sigh,..someone please get this to dtag.de and make them aware there is still a problem.

[Monk]

Same ole same for me

connect to the MA

[Monk]

And one to the CT

[Alino]

Unbelievable this morning was everything ok, and now it`s the same like last 4 days. I hate it.


Routenverfolgung zu 216.234.247.240 über maximal 30 Abschnitte

  1    68 ms    55 ms    55 ms  217.5.98.143
  2   632 ms    55 ms    55 ms  217.237.156.110
  3   151 ms   151 ms   151 ms  Vienna-gw12.USA.net.DTAG.DE [62.156.131.182]
  4   151 ms   151 ms   137 ms  dt-gw.wswdc.ip.att.net [194.25.6.234]
  5   151 ms   151 ms   151 ms  gbr4-p50.wswdc.ip.att.net [12.123.9.54]
  6   165 ms   165 ms   151 ms  gbr4-p30.attga.ip.att.net [12.122.2.225]
  7   164 ms   165 ms   178 ms  gbr3-p20.dlstx.ip.att.net [12.122.2.89]
  8   179 ms   164 ms   179 ms  gbr5-p60.dlstx.ip.att.net [12.122.5.73]
  9   179 ms   178 ms   179 ms  gar2-p360.dlstx.ip.att.net [12.123.17.25]
 10   164 ms   179 ms   178 ms  gar1-p3100.dlrtx.ip.att.net [12.123.196.101]
 11   179 ms   192 ms   179 ms  12.119.136.22
 12   179 ms   178 ms   178 ms  border3.ge4-1-bbnet2.ext1.dal.pnap.net [216.52.1
91.83]
 13   178 ms   179 ms   178 ms  theplanet-2.border3.003.dal.pnap.net [216.52.189
.222]
 14   357 ms     *        *     216.234.247.240
 15   370 ms     *        *     216.234.247.240
 16   371 ms     *      370 ms  216.234.247.240

Ablaufverfolgung beendet.

Seems we joyed to early this morning. DAMN