rolf wroteI know because I have a public IP from my ISP, but it is on the router. My computer has a private IP (192...). When I do a traceroute to google, I see the IP of my router, but the private IP which is connected to me, not the public IP that the ISP gave me.
Ohhh ohhh I get what you're saying. If one has a real IP address, which is assigned to his modem / router, that router has two IP addresses. The real IP address, on the WAN side, and a private IP address, on the LAN side. It routes from one interface to another. In that case, a traceroute would show you your private IP address of the router and not the real IP address from WAN side.
However, one can traceroute, and if he finds an ISP's IP that he also gets in
www.whatismyip.com, then he could verify that this is not a real IP address. Because if it was, then it would not show in the traceroute.
NuclearVision wroteA question was playing my head.
Let's say i'm seeding a unique torrent, and i give it to you guys to download. When you click peer list, you will see my host address, what will it look like? My internal ip, my ISP's ip, or what?
if somebody can help me with this please reply.
Your ISP's IP. The last IP that is reachable over the internet is the IP address that represents you on the internet. If you have only an internal IP, then your ISP's IP would show, because this is the last real IP that is available and visible before the data enters the ISP's private network and routes to your modem / router.
If you had a real IP, then that data would route over your ISP, but would ultimately reach your modem / router as designated to reach your real IP address. When you send data, its headers indicate that it originates from your own real IP address, and is not modified to show that it ultimately originates from your ISP rather than your real IP (transparent proxy).
This was a bit complex to explain. If you did not get what I said, then I will try to explain it in a different way.