Timeline for What is the relationship between my public IP address and the address assigned to my NIC?
Current License: CC BY-SA 4.0
14 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Oct 4, 2022 at 6:08 | audit | Suggested edits | |||
Oct 4, 2022 at 6:09 | |||||
Sep 13, 2022 at 15:46 | vote | accept | StoneThrow | ||
Sep 13, 2022 at 4:41 | answer | added | grawity_u1686 | timeline score: 3 | |
Sep 13, 2022 at 4:24 | answer | added | Charles Burge | timeline score: 2 | |
Sep 13, 2022 at 4:07 | answer | added | Scottmeup | timeline score: 2 | |
Sep 13, 2022 at 0:18 | comment | added | Frank Thomas | no, not at all. NAT is a tool to use when and where you need it. Your ISP will have segmented their network, and are controlling the routing between those sub-networks as they require, which may or may not require NAT for their situation and design goals. Common consumer internet access routers commonly use Source NAT, as there is no value in making your entire home network directly reachable from the Internet, combined with the general scarcity of publicly routable IP addresses. | |
Sep 13, 2022 at 0:09 | comment | added | StoneThrow | @FrankThomas -- I think I get it: there are several layers of "internal networks" between the public IP address (24.253.65.208) and my modem. Is it correct, then, that each of these layers of "internal networks" implement a NAT (as in John's comment) so that inbound packets from the layer closer to the public get routed to the layer closer to my modem? (I'm hoping someone will put together One Answer To Rule Them All, but I think I am forming a piecemeal picture from everyone's helpful comments :)) | |
Sep 13, 2022 at 0:03 | comment | added | anon | That is how NAT generally works. Inbound packets from outside IP go to the appropriate inside IP. It has worked like this for a very long time (2 - 3 decades) | |
Sep 13, 2022 at 0:00 | comment | added | StoneThrow | @John - Does that mean something along the lines of: if my laptop issues a request for www.example.com, and my tablet issues a request for www.example.org, the "outside world" sees both requests as coming from my modem, and when responses reach my modem, they get forwarded to my router, who implements the logic of "10.0.0.2 requested www.example.com" and "10.0.0.4 requested www.example.org" and routes response packets accordingly? | |
Sep 13, 2022 at 0:00 | comment | added | Frank Thomas | No it is probably not your modem. your modem as a line device may not have an IP at all, and if it does, it is almost certainly an IP for your ISPs internal network, and traffic has to pass through several additional devices before it reaches the ISP's network periphery, and passes through a gateway where your public IP is assigned on the WAN. | |
Sep 12, 2022 at 23:51 | comment | added | StoneThrow | @Ramhound - when you say "24.253.65.208 is your public IP address", does that mean it's the IP address assigned to my modem by my ISP? | |
Sep 12, 2022 at 22:31 | comment | added | anon | The "piece of software" is NAT (Network Address Translation). This is in use in all home / very small business routers. Here is a decent explanation: techtarget.com/searchnetworking/definition/…. | |
Sep 12, 2022 at 22:22 | comment | added | Ramhound | 24.253.65.208 is your public internet IP address while 10.0.0.2 only exists within your own Intranet. "What would be different if the User Router as DHCP Server box was unchecked?" - You would have to assign each device a static intranet IP address. 10.0.0.1 and 24.253.65.208 is the same device, your modem provided by your router | |
Sep 12, 2022 at 22:17 | history | asked | StoneThrow | CC BY-SA 4.0 |