asked on

Router IP addresses???

Forgive another newbie question. I was refered to the website www.samspade.org in an earlier post, great site. Anyway out of curiosity I entered my companies website address in the DO STUFF box, the tracert section return an 10.4.xx.xx address before getting our address. This IP has a MAC address for a Linksys device. At first I didn't catch that the 10.4.xx.xx (which is similiar to our internal static address) was between our ISP and our router. So I used GFI LANguard to check that range of IP addresses, wondering if we had something undocumented on the network. LAnguard returned tons of Cisco machines within this range. Should 10.4.xx.xx be reserved and not used internally? any clarification would help. maybe some easy points for someone
Thanks,
Doie

Les Moore

G'day, doie30286

Interesting. You should never see any 10.x.x.x addresses in the internet. See RFC 1918. I know that many ISP's use them internally, but NAT should give them all a public address for anything traversing the Internet.

Another great site (don't laugh) = Church of the Swimming Elephant http://www.cotse.com
And http://www.dnsreport.com (plug in your domain)

Cheers!

SunBow

So who is it started trace?

Note, unit starting a trace typically begins on local intranet.

stevenlewis

>Should 10.4.xx.xx be reserved and not used internally?
it should only be used internally

ASKER CERTIFIED SOLUTION

TheAmigo

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

TheAmigo

As an example, putting www.netscape.com into Sam Spade's traceroute tool, has this at the end:

10 66.185.143.233 75.169 ms pop2-mtc-P2-0.atdn.net (DNS error) [AS1668] AOL Transit Data Network
11 66.185.151.162 75.109 ms ow2-mc3.atdn.net (DNS error) [AS1668] AOL Transit Data Network
12 172.20.149.54 77.139 ms DNS error
13 64.12.151.211 77.066 ms main-v1.netscape.aol.com (DNS error) [AS1668] AOL Transit Data Network

Note that 172.20.x.x falls in the same private IP category as 10.x.x.x (RFC 1918). This isn't a problem, just means that they're using private IPs between routers rather than waste real IPs when they aren't needed.

Netman66

It's very possible your ISP is providing you with private addressing to their network and NAT'ing from their internal network to the internet.

What you're seeing is likely devices they are using to segment their internal addressing.

doie30286

ASKER

here is a copy of the tracert from Samspade.org, the final hop (which I over looked at first) is correct. Thanks for all the great input. I think points will go to Amigo, my habits are to leave the question open for a few days just to get more input, which is what this site is all about.
Again, thanks to all.
Should I at least report this to our ISP?

3 130.152.80.30 8.836 ms
4 198.32.146.21 14.734 ms mae-la.above.net
5 208.185.156.10 19.453 ms pos3-
6 208.185.156.125 16.298 ms pos2-
7 208.184.233.134 81.884 ms so-5-1-
8 208.184.233.126 80.631 ms so-6-0-
9 216.200.127.10 78.970 ms pos2-
10 64.124.112.29 85.640 ms
11 66.28.4.22 81.859 ms p15-
12 66.28.4.161 80.717 ms p14-
13 66.28.5.242 79.839 ms g49.ba01.b000173-
14 66.28.30.134 82.602 ms
15 66.35.174.109 77.344 ms DNS error [AS6983] ITC
16 66.35.162.126 78.031 ms pos8-0-DELTACOM
17 10.4.22.90 80.996 ms DNS error
18 66.0.117.83 82.829 ms DNS error [AS6983] ITC DELTACOM

Les Moore

It looks like internal addressing within deltacom, only between their internal routers, which is very typical. The only times you could see this address is through a traceroute, simply because of the way traceroute works as opposed to a ping or other browsing. It has no effect on your Internet use even if your were 10.4.22.x on the inside of your network