| |
| |
| |
|
Page: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18
Comments:
<0> I add ~40ms in Level 3 between Dallas and LA...
<1> my traffic goes through lots of hops
<1> wtf is wvfiber?
<0> Looks like a reasonable 40-50ms ping to the destination from here...
<1> 13 34 ms 45 ms 34 ms ny60-a00-pos-7-0.OC48-ash-c00-pos-1-37-1.wvfiber
<1> .net [63.223.28.13]
<1> 14 107 ms 115 ms 101 ms nyc-c00-pos-1-35-1.OC48-nyc60-a00-pos-4-0.wvfibe
<1> r.net [63.223.28.9]
<0> 50-60ms, that is.
<1> some kind of OC48 that adds a **** load of lag
<0> Saturation somewhere?
<1> dunno
<1> im 98-115 ms after that
<1> 113ms on the final hop
<2> i should tell them to restart their routers on that entire netblock
<1> why would nyc-nyc add 60ms
<1> on oc48's
<0> Well, that's not likely to happen.
<1> i thought they fixed the congestion issues
<2> :(
<0> Since there's probably a thousand customers or more going through them.
<2> yeah
<2> i bet
<2> all these ip's are static
<1> hm
<2> so i can't even change
<2> if i wanted to
<1> ill trace it from bafserv
<0> I don't really see anything that looks wrong right now.
<0> What problems are you experiencing?
<3> routing
<0> Just some extra latency?
<1> hmm
<0> OggyX2, don't talk out your ***.
<1> i cant get to 66.159.240.94 from bafserv
<0> pls k thx
<3> Night he has to call some dumb*** DSL TECH and tell em to fix my **** ****ER
<1> that wont get you far
<0> It's not a problem with his end connection.
<3> routing problems
<1> http://pastebin.bafserv.com/2923
<1> for some reason bafserv can't get past hop 10
<1> i can ping them though
<1> ICMP
<1> so
<1> its weird :P
<3> lol
<1> but it looks fine
<3> its always a routing problem on their end
<1> im under 1ms right up to when i jump from NYC to LA on level3
<1> OggyX2, not always
<3> Night is getting extremely Bigheaded lately
<3> im gonna have to put a stop to this
<1> ?
<0> Heh.
<3> talking out of my arse eh
<3> alright then
<0> What else do you do, Oggy?
<3> talk out of my arse
<3> hehe
<3> hey you dont have to listen to me you know
<2> i wonder if it may be T1
<2> i dunno
<3> there is always 8ball
<2> yeh
<0> No, it's not your T1.
<2> k
<3> !8ball is Night a MOROOON
<4> OggyX2, Not bloody likely.
<3> !8ball sure he is
<4> OggyX2, I'm busy.
<0> !8ball Is this the result of possible saturation between AS19817 and AS19151?
<4> Night, It would take a disturbed person to even ask.
<3> Night = Disturbed
<0> Deeply, in fact.
<0> My diagnosis is that it is between the DSL provider and one of their peers. It is not an issue with any end connection.
<0> Anyway.
<0> What problems is this causing for you?
<0> Are you dropping packets or is it just increased latency?
<3> I like it when , DSL technicians give up a large logical technical excuse for something as simple as some tech getting off their dumb*** and rebooting something
<3> hehe
<0> Heh.
<2> Night: the users in the buildings are complaining about very slow programs
<2> we use citrix
<2> so the applications got real slow
<2> and they "freeze
<2> " up
<0> 40 sites connecting to a single T1?
<2> bonded
<2> T1
<0> How many?
<0> Two?
<2> yeah
<0> Packet loss might cause apparent freezes...
<0> There's none evidenced in your traces.
<0> Are all sites complaining?
<2> yeah
<3> just call your provider and have them look into it
<3> its not hard
<3> stfu already night you are giving me a headache damit
<3> :P
<2> im on the phone with provider
<2> he says he doesn't see anything wrong
<2> :/
<2> dsl extreme is "still wokring on it"
<2> i don't thin thye know iether
<2> im going crazy
<0> Normal provider techs will just look at your line and say it's fine.
<2> so any conclusion?
<2> do you tihnk its dsl extreme forsure
<2> do you see any packet loss on that ip?
<0> None yet.
<3> ah they are still working on it
<5> http://www.stagmatech.com/index3.htm
<2> hrmm
<2> so if its not dsl extreme, and not my T1
<2> i wonder what it could be
<2> man
<2> this is bad
<6> !ping what-man
<4> PiNG THiNGiE - What-Man's ping reply took seconds
<5> http://www.stagmatech.com/images/19-103-562-01_JPG.jpg
<5> http://www.madshrimps.be/?action=getarticle&number=1&artpage=1596&articID=399
<5> look at this beast hsf
<5> phear
<2> ok
<2> found out the problem
<2> ****ing router went out in LAX Airport
<2> they just replaced it
<2> everything is quick now.
<2> damn hippies
<2> can you believe that ****?
<5> well if Im not mistaken i was the first one to mention that it was a routing problem
<2> yea
<2> you wre
<2> were*
<2> but dsl extreme didn't even tell me that
<2> crazy
<2> it took them 2 days to fix it
<2> over at LAX airport
<5> <2> they are all high
<5> <esd_> looking at it Oggy
<5> <5> port problem on their end
<5> <5> maybe the routing is bad
<5> <5> or messed up somehow
<5> * Joins: Sinistor (sinistor@dhcp-191-23.office.miscg.com)
<5> <2> who's end?
<2> i should now work on spliting the ****ing netblock for my buildings so if 1 router goes bad, my company is still up
<5> see so Night can spend all day giving up a technical answer for something as simple as a messed up routing
<2> lol
Return to
#dsl
or
Go to some related
logs:
AM37-L DRIVER
#linuxhelp
hittest quirksmode
#winxp
#politics
#windowsxp
#windowsxp
teenkelly sparta
avlive updates
Jephey
|
|
