I understand and as well think that it is silly for them to argue that as well, but the two IP's shown below are not accessible from outside of AT&T's network. I have tried ping, trace and telnet from inside and outside their network and found that you receive destination unreachable when coming from the outside of their network. This would argue that they have a somewhat mixed LAN WAN environment that is their customer travel across before hitting the real world, which by the way does fall under the RFC guidelines.
Chris Freels IT Systems Administrator Gracenote (formerly CDDB) > Tracing route to www.securityfocus.com [66.38.151.10] > over a maximum of 30 hops: > > 1 10 ms 10 ms 10 ms 10.58.34.1 > 2 <10 ms 10 ms 20 ms 24.182.156.17 > 3 51 ms 50 ms 50 ms 24.18.95.65 > 4 40 ms 50 ms 40 ms 10.0.236.70 > 5 40 ms 50 ms 40 ms 24.7.76.189 > > This is, in many people's opinion, a violation of RFC1918. > The engineers of the networks who use them answer with the > equally valid point that their internal routers can have > whatever internal IPs they want, I shouldn't be trying to > connect directly to them anyway. One of those religious wars > you never really want to get into. That's a silly argument from them...if they set you up to be on the router, then how are you NOT supposed to connect to them???
