12
8
Here is a log of tracert superuser.com
from my computer:
Tracing route to superuser.com [198.252.206.16] over a maximum of 30 hops: 1 2 ms 2 ms 2 ms 192.168.1.1 2 11 ms 17 ms 9 ms 10.216.128.1 3 12 ms 17 ms 14 ms 89-75-22-81.infra.chello.pl [89.75.22.81] 4 23 ms 17 ms 17 ms 84.116.192.102 5 18 ms 18 ms 15 ms pl-krk01a-rd4-ae0-2183.aorta.net [84.116.253.70] 6 20 ms 16 ms 15 ms pl-waw04a-rd1-ae12-2158.aorta.net [84.116.252.225] 7 15 ms 15 ms 15 ms 84.116.135.225 8 17 ms 19 ms 24 ms henet.plix.pl [195.182.218.197] 9 34 ms 44 ms 49 ms 10ge1-2.core1.prg1.he.net [184.105.213.241] 10 33 ms 44 ms 34 ms 10ge15-3.core1.fra1.he.net [184.105.213.233] 11 45 ms 51 ms 48 ms 100ge5-2.core1.par2.he.net [72.52.92.13] 12 161 ms 163 ms 156 ms 10ge15-1.core1.ash1.he.net [184.105.213.93] 13 131 ms 124 ms 124 ms 100ge7-1.core1.nyc4.he.net [184.105.223.166] 14 121 ms 121 ms 121 ms 10ge4-1.core1.nyc5.he.net [184.105.213.218] 15 122 ms 120 ms 121 ms lightower-fiber-networks.10gigabitethernet3-2.core1.nyc5.he.net [216.66.50.106] 16 122 ms 123 ms 121 ms ae12.nycmnyzrj91.lightower.net [64.72.64.110] 17 122 ms 120 ms 122 ms ae2-jrcynj67j41.lightower.net [72.22.160.175] 18 123 ms 123 ms 122 ms 69.46.229.98.lightower.net [69.46.229.98] 19 124 ms 123 ms 123 ms stackoverflow.com [198.252.206.16] Trace complete.
The first entry (192.168.1.1
) is my router, which does not surprise me. What is weird is the second entry, 10.216.128.1
, which shows even when doing the traceroute from my router or when the computer is directly connected to the internet. My router has a public IP — is my ISP violating the IP standard? Would such configuration prevent me from using the 10.216.128.x
range in my own network?
There is a diagram in an answer to a related question which does not really answer mine — my router knows nothing of the 10.216.128.x
network, and the hop shows even when tracert
ing another hosts on its subnet, which the router should theoretically be able to contact directly:
Tracing route to 89-66-132-2.dynamic.chello.pl [89.66.132.2] over a maximum of 30 hops: 1 2 ms 2 ms 2 ms 192.168.1.1 2 27 ms 11 ms 10 ms 10.216.128.1 3 18 ms 21 ms 18 ms 89-66-132-2.dynamic.chello.pl [89.66.132.2] Trace complete.
What is funny is that this private IP does not show up when tracert
ing the gateway:
Tracing route to 89-66-132-1.dynamic.chello.pl [89.66.132.1] over a maximum of 30 hops: 1 3 ms 2 ms 2 ms 192.168.1.1 2 10 ms 11 ms 11 ms 89-66-132-1.dynamic.chello.pl [89.66.132.1] Trace complete.
while tracert
ing an address which is not even in the same network it shows up again, while the gateway seemingly disappears:
Tracing route to 89-69-109-1.dynamic.chello.pl [89.69.109.1] over a maximum of 30 hops: 1 2 ms 2 ms 2 ms 192.168.1.1 2 12 ms 14 ms 12 ms 10.216.128.1 3 16 ms 15 ms 21 ms 89-69-109-1.dynamic.chello.pl [89.69.109.1] Trace complete.
1
possible duplicate of private address in traceroute results
– kinokijuf – 2014-07-07T10:34:38.950You say you have a public IP. When you do ipconfig on your computer does it show a public IP? Is your "router" set to "bridge mode"(that might be a requirement for having a public IP) – barlop – 2014-07-07T10:42:49.367
@barlop i have a public IP on my router, not my computer. – kinokijuf – 2014-07-07T10:43:13.270
Perhaps you should reword your title to Why do I have a private IP directly after router, in tracert results? That makes it a different question to http://superuser.com/questions/611736/private-address-in-traceroute-results There is a diagram in the answer to that question but it doesn't really answer yours.
– barlop – 2014-07-07T10:51:27.463Can you http to 10.216.128.1 ? – barlop – 2014-07-07T10:54:48.687
@barlop no, nothing — not even ping or tracert it. – kinokijuf – 2014-07-07T11:00:27.057
OR, you could word it as "how can I be going straight from my private IP, to my ISP's private IP?" Your question as it is, looks like a duplicate but isn't really. And because of that - looking like a duplicate, it has 2 votes to close it. You could also point to that quesiton and say it's not the same 'cos your one has a private IP directly after, so for example, the diagram in the answer to that question doesn't seem to apply to you. – barlop – 2014-07-07T11:01:32.373
There is absolutely nothing stopping there being an interim private network between the internet and a public IP. It is just being routed across a privately addressed segment. – Paul – 2014-07-07T11:04:17.447
@Paul yes, i already know it, but router should be able to access
89.66.132.x
directly according to the netmask – kinokijuf – 2014-07-07T11:05:30.863What evidence do you have that your router has a public IP assigned to it? – David Schwartz – 2014-07-07T11:05:56.890
@DavidSchwartz Try to RDP into
89.66.132.177
;) – kinokijuf – 2014-07-07T11:13:56.503@kinokijuf That proves that traffic to that IP address reaches your router, but it doesn't prove that that IP address is assigned to your router. It could be assigned to a device ahead of your router. (Compare a forward traceroute from your network with a traceroute to your network from the outside.) – David Schwartz – 2014-07-07T11:15:36.763
@DavidSchwartz um, my router reports it as its IP address… – kinokijuf – 2014-07-07T11:17:08.217
@DavidSchwartz ok, now try to tracert to me and report whether you see anything weird – kinokijuf – 2014-07-07T11:17:58.413
@DavidSchwartz I suppose his router interface and www.whatismyip.com report 89.66.132.177 as his public IP since one can RDP. It's clearly his isn't it - and port forwarding he must have set up. Unless perhaps you think all the devices between him and that are private.. But then.. wouldn't that be the ISP using a private IP, over a WAN? Aren't Private IPs only meant to be used on LANs.. WANS are I suppose (at least in this case), internet infrastructure? – barlop – 2014-07-07T12:23:51.697
@DavidSchwartz If one accepts what appears to be your suggestion that his router's public IP might not be that 89 address. If his router is R1 and his WAN side IP is 10.x.y.1 there's a cable from that to his ISP's R1 at interface i1 I guess you think that's also a 10.x.y.1 address. But can an ISP use a private IP on a WAN? – barlop – 2014-07-07T12:38:17.070
@kinokijuf Here are the results of a tracert to your IP The last IPs to you are- 84.116.192.101, 89.75.22.82, , 89.66.132.177. So, no private IPs there. Maybe you have a very funny router and it affects traffic going out. Try another router and you may find the 10 address goes. – barlop – 2014-07-07T12:39:30.353
@barlop Yes, they can. This is not particularly uncommon. One annoying side-effect is that ICMP errors may have a private source address (as seen here). Cisco addressed this by giving you a specific command to set the source address of ICMP errors, but not everyone uses it or uses devices that support it. – David Schwartz – 2014-07-07T12:43:25.317
@DavidSchwartz When they do it, using a private IP publicly, is it not abiding by / is it breaking, RFCs/TCP/IP guidelines/rules? (Note, I still think it may just be a funny router he has(and should try with another router) 'cos tracert to him showed no privates) – barlop – 2014-07-07T12:47:32.680
@barlop They don't use it publicly -- only to their own customers. His link to his ISP is part of his ISP's network. It's perfectly fine to use local address space with your own customers. (And many ISPs do so.) – David Schwartz – 2014-07-07T12:49:39.130