Internet Protocall (IP) question.

[ammo]

All right, this is somewhat OT, but I gotta ask:

where the hell does the spelling/pronounciation "protocall" come from??!? Is this some form of regionalism somewhere in the states or is it just from the same bunch of people who pronounce nuclear "nucular"?

[spamdies]

Want to get really confused. Add a buisness class proxy on port 80 to your advanced proxies for http. Your routers IP will no longer show up when you go to ipchicken. The proxy will show up instead of the routers ip.
Your router handers multiple IPs. The one assigned by your ISP (24.x.x.x) which is your internet ip address.
internally your router has an IP (looks like 192.168.0.1) which is the GATEWAY that computers on your LAN access to get access to the internet. Most routers even keep track of the INTERNAL IP's of the computers connected to them.

so simplictys sake lets put it like this with a router you have to have a ip to connect to the router so it can direct internet traffic to and from your NODE.
your compter (192.168.0.xx) sends traffic to router (192.168.0.1) which broadcasts the requests through the external ip (24.x.x.x or what ever your ISP assigned)

[Tiger Shark]

Let me try..... <sigh>

Every device on the internet has a LAN address and a WAN address..... really.... even your PC has a LAN address... it's 127.0.0.1.... It's WAN address may be 192.168.1.2 with a default gateway of 192.168.1.1. Now, the router at 192.168.1.1 has a LAN address of 192.168.1.1 but it's WAN address may be 10.0.0.2 with a default gateway of 10.0.0.1. Now that router will have a LAN address of 10.0.0.1 but have a WAN address of 68.23.125.2 and a default gateway of 68.23.125.1. Now the router it talks to, (default gateway), may have a LAN address of.......

See how it works yet?

Now, Tracert isn't always the most discerning with regard to the WAN or LAN address it returns to you. In fact, it may flip from WAN to LAN and back on each hop it takes through the network. So let's try to give an example.....

The pure path, and I mean _pure_ path may be....

127.0.0.1 (your computer LAN) ->
192.168.1.2 (your computer WAN) ->
192.168.1.1 (your router LAN and your PC's gateway) ->
10.0.0.2 (your router's WAN) ->
10.0.0.1 (your router's router's LAN and your router's gateway) (getting the picture) ->
68.121.1.2 ->
68.121.1.1 ->
etc....... (the 68.x.x.x adresses are both the same device just the LAN and WAN addresses of it.....)

Now your tracert may show a combination of the following depending on the way the route is set up.... NOTE: It ignores itself so you won't see 127.0.0.1 or 192.168.1.2.

192.168.1.1 OR 10.0.0.2
10.0.0.1 OR 68.121.1.2
68.121.1.1 or etc.

Now.... All that is quite clear in my mind.... However reading it is making me crosseyed.... If I have messed up please feel free to correct the paths etc..... anyone....

PS: Before anyone "jumps on" my _pure_ path - Yes, I know that it technically goes through 127.0.0.1 as it passes through each device...... But that's a mere technicality....

Hope this try helps you understand it.....

[mastacracka]

Originally posted here by spamdies
Want to get really confused. Add a buisness class proxy on port 80 to your advanced proxies for http. Your routers IP will no longer show up when you go to ipchicken. The proxy will show up instead of the routers ip.
Your router handers multiple IPs. The one assigned by your ISP (24.x.x.x) which is your internet ip address.
internally your router has an IP (looks like 192.168.0.1) which is the GATEWAY that computers on your LAN access to get access to the internet. Most routers even keep track of the INTERNAL IP's of the computers connected to them.

so simplictys sake lets put it like this with a router you have to have a ip to connect to the router so it can direct internet traffic to and from your NODE.
your compter (192.168.0.xx) sends traffic to router (192.168.0.1) which broadcasts the requests through the external ip (24.x.x.x or what ever your ISP assigned)

thank ya got it jnow