I had a similar problem with JSView, it stopped working recently. i unzipped it, fixed the bug (in a manner of speaking), zipped it again and now it works. With the signing I will not be able to do this again and that's a bummer.
It's not about a real domain, it's about dynamic IP. I have a "real" domain but I am still using no-ip.org to connect to some VPNs on ADSL with dynamic IP addresses.
I think you should apologize because you're wrong. What you see there is not the TTL set by your machine, it's the TTL set by the remote server. And it doesn't always starts from 255. For example, google.com sets the TTL to 64. Even though the usual values for TTL are 64, 128 and 255, you cannot be sure what the exact TTL value is unless you are the admin of the server server.
From linux ping(8) man page, section Ttl Details:
In normal operation ping prints the ttl value from the packet it receives. When a remote system receives a ping packet, it can do one of three things with the TTL field in its response:
Not change it; this is what Berkeley Unix systems did before the 4.3BSD Tahoe release. In this case the TTL value in the received packet will be 255 minus the number of routers in the round-trip path.
Set it to 255; this is what current Berkeley Unix systems do. In this case the TTL value in the received packet will be 255 minus the number of routers in the path from the remote system to the pinging host.
Set it to some other value. Some machines use the same value for ICMP packets that they use for TCP packets, for example either 30 or 60. Others may use completely wild values.
Slashdot Mirror
I had a similar problem with JSView, it stopped working recently. i unzipped it, fixed the bug (in a manner of speaking), zipped it again and now it works.
With the signing I will not be able to do this again and that's a bummer.
Just checked now, dd-wrt knows about freedns.afraid.org and also it seems that my no-ip.org domains work again.
Thanks, I'll look into it, I have to see if I can do this on a dd-wrt router.
It's not about a real domain, it's about dynamic IP.
I have a "real" domain but I am still using no-ip.org to connect to some VPNs on ADSL with dynamic IP addresses.
I think you should apologize because you're wrong.
What you see there is not the TTL set by your machine, it's the TTL set by the remote server. And it doesn't always starts from 255. For example, google.com sets the TTL to 64.
Even though the usual values for TTL are 64, 128 and 255, you cannot be sure what the exact TTL value is unless you are the admin of the server server.
From linux ping(8) man page, section Ttl Details: