This log totally sucks though it's an incroyable relief to have performed the exploit of killing this sneaky bastard after a hundred of fruitless attempts. I'm sure that those who have been deceived by the rumpled stinking scum of MT, will thank me. I'd rate it a 2, but considering the average mediocrity of the other logs, I can't possibly feel guilty.
WOO!! Go Necsi!! Nice solo!!
That's one schmuck that had it coming for a long time now!
Wasach
ps. if he reports you for it, I'll chip in for fines!!
it was a Router problem most likly.
Keller, DNS is working fine.
Yeah, looks like a looping DNS problem. That means MUDs probably still up, which means we all idled out probably. Wonderful.
Yee Haw its a MUD crash!
traceroute to towers (38.117.144.98), 30 hops max, 38 byte packets
18 p15-0.core01.jfk01.atlas.cogentco.com (66.28.4.9) 232.245 ms 154.158 ms 193.126 ms
19 g7.ba21.b001353-0.jfk01.atlas.cogentco.com (66.250.13.206) 131.711 ms 172.242 ms 137.802 ms
20 Pilosoft.demarc.cogentco.com (38.112.1.42) 231.887 ms 148.678 ms 156.183 ms
21 g1.ba21.b001353-0.jfk01.atlas.cogentco.com (38.112.1.41) 208.332 ms 167.588 ms 183.688 ms
22 Pilosoft.demarc.cogentco.com (38.112.1.42) 139.076 ms 195.840 ms 137.327ms
23 g1.ba21.b001353-0.jfk01.atlas.cogentco.com (38.112.1.41) 172.747 ms 146.101 ms 183.278 ms
24 Pilosoft.demarc.cogentco.com (38.112.1.42) 148.375 ms 159.055 ms 180.011ms
25 g1.ba21.b001353-0.jfk01.atlas.cogentco.com (38.112.1.41) 208.823 ms 178.653 ms 203.176 msSmells like a loop to me.
Its just you.
Nope, you're not the only one, Hobbe. Is it just me, or was the mud a hell of a lot more stable before they switched ISPs?
Am i the only one that cant connect to t2t?
well actually you can't kill him, he usually send you out when he is near death, so after the tenth attempt he finally fall under my wrath (or rather under my deadly headbutt :P)
HAHAHAHA Dident know you could kill him.. I hate him i got somthing went wrong 4 times in a row and when i finally got somthing he gave me GOLD... Shrug