We have been experiencing some problems with our server, and
we suspect it might be due to routing issues within our ISPs network.
When we did a traceroute from our server, this is what we got:
traceroute to freefall.freebsd.org (204.216.27.21), 30 hops max, 40 byte
packets
1 10.128.4.13 (10.128.4.13) 12.350 ms 79.670 ms 12.336 ms
2 10.128.3.2 (10.128.3.2) 12.904 ms 12.847 ms 12.983 ms
3 tac02-enet0.rtr.agt.net (161.184.255.225) 13.098 ms 13.684 ms 13.814
ms
4 local1-atm0-0-111.tac.net (207.229.15.25) 18.424 ms 17.902 ms 17.792
ms
5 REGIONAL1-fe2-1-0.tac.net (205.233.111.39) 17.904 ms 21.189 ms 19.104
ms
...etc...
as you will notice, our provider is using non-routable addresses (as seen in
hop 1
and 2), and then they are using another wierd one (161.184.255.255) in hop 3
before
it gets back out in to real world addresses. I don't understand everything
about
internet addressing, but is what they are doing a valid scheme, or is it
looking for
disaster? Any thoughts (and if you could point me to an RFC) on this would
be appreciated.
Thanks.
Damien Tougas
Converging Technology Solutions, Inc.
10148 - 73 Street
Edmonton, Alberta T6A 2W9
Phone: (780) 469-1679
Fax: (780) 461-5127
mailto:dtougas@converging.net
http://www.converging.net
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message