Quote from: astor on July 03, 2013, 08:12 pmWhen you send a packet, it gets stamped with the number 127, and each router that it passes through decreases it by one. When it reaches zero, the Time To Live has expired and the packet is no longer forwarded anywhere. This feature was implemented because people thought internet packets might get stuck in loops, so if they don't reach their destination in 128 hops, they are killed.I've seen TTL expired errors when there's a routing issue, like when two routers keep sending the packets back and before between each other until the TTL expires. Not sure what would be causing it for you.Your statement does sound pretty generic. Not that it would really do that much harm for people to think so in this instance though. Now didn't somebody else around here make that same mistake lately? Hmmmmm, who could that be... :P If you didn't realize, it's not always 127. It's actually user configurable (as in programmer configurable, as opposed to only the kernel being able to do it).Anyway, it's being caused by a/some poor relay(s), I should think. Either deliberately malicious or just incompetently configured/modified. There's a lot more than just the Tor hops between you & Silk Road -- there's all the hops of the "normal" network we call the internet that Tor uses to implement its own network :)