Need to remember not to reply from the wrong address, again...
Actually the default would be ICMP usually, ICMP type 8 echo-request
return ICMP type 9 echo-reply.
Sometimes trying a TCP traceroute can work better though it wont
generally show up info on hops that don't have the same port open,
combining the information can provide some insight though.
Heh, Peter totally agree with you there, about the only time I can see
it making any sense is on a pure client with 0 open ports and all
stealth so it doesn't reveal it's presence to probes at all, for servers
it seems completely dumb to me as a port probe will show you up anyway.
As for the idea of firewalling it to reduce potential for flooding etc
also makes no sense to me, rate limiting is possible without crippling
basic functionality. Personally would at least say any host providing a
service should be capable of basic reachability diagnostics (Routers,
Servers etc) though some issues can be the result of NAT just breaking
reachability as usual, such as if several servers are behind one NAT
router, about time we got on with IPv6 and got rid of it xD.
On 01/10/12 15:33, [email protected] wrote:
Maybe Ask doesn't lik UDP packets (traceroute default). ;-)
Regards,
Vladimir
Dne 1.10.2012 15:50, Thomas Rieschl napsal(a):
same here:
traceroute to manage.ntppool.org (207.171.3.5), 30 hops max, 60 byte
packets
[...]
8 xe-0.equinix.snjsca04.us.bb.gin.ntt.net (206.223.116.12) 194.416
ms 183.367 ms 187.229 ms
9 ae-7.r20.snjsca04.us.bb.gin.ntt.net (129.250.5.52) 184.352 ms
179.428 ms 188.666 ms
10 ae-4.r21.lsanca03.us.bb.gin.ntt.net (129.250.6.10) 197.169 ms
195.248 ms 191.073 ms
11 ae-2.r04.lsanca03.us.bb.gin.ntt.net (129.250.5.70) 197.040 ms
200.920 ms 196.621 ms
12 ge-0-7-0-11.r04.lsanca03.us.ce.gin.ntt.net (198.172.90.74) 191.631
ms 194.173 ms 218.542 ms
13 xe9-1.hr01.lax2.phyber.com (207.171.30.26) 221.596 ms 218.599 ms
188.342 ms
14 netblk-207-171-3-5.phyber.com (207.171.3.5) 188.307 ms !X 196.916
ms !X 192.961 ms !X
seems like Ask doesn't like Hungarians and Austrians anymore ;)
Regards,
Thomas
On 01.10.2012 15:17, Kiss Gábor wrote:
From here it works too ...
2012/10/1 Ralf Hildebrandt <[email protected]>
* Kiss Gábor <[email protected]>:
Dear Ask,
FYI:
Page https://manage.ntppool.org/manage is unreachable.
Works for me.
Well.
Traceroute says:
[...]
13 phyber.losangeles.savvis.net (208.173.55.226) 189.680 ms 189.636
ms 189.605 ms
14 xe6-2.cr02.lax1.phyber.com (207.171.30.213) 200.096 ms 200.126
ms 200.090 ms
15 xe9-4.hr01.lax2.phyber.com (207.171.30.42) 200.342 ms 200.199
ms 200.262 ms
16 netblk-207-171-3-5.phyber.com (207.171.3.5) 196.637 ms !X
196.484 ms !X 196.537 ms !X
!X means: Communication administratively prohibited
So it seems to be some filtering issue.
Gabor
_______________________________________________
pool mailing list
[email protected]
http://lists.ntp.org/listinfo/pool
_______________________________________________
pool mailing list
[email protected]
http://lists.ntp.org/listinfo/pool
_______________________________________________
pool mailing list
[email protected]
http://lists.ntp.org/listinfo/pool
_______________________________________________
pool mailing list
[email protected]
http://lists.ntp.org/listinfo/pool
