title
description
sections.overview.title
sections.overview.content
privateRanges.title
10.0.0.0 to 10.255.255.25510.0.0.110.1.1.110.200.50.100172.16.0.0 to 172.31.255.255172.16.0.1172.20.1.1172.31.255.254192.168.0.0 to 192.168.255.255192.168.1.1192.168.0.100192.168.100.50publicRanges.title
publicRanges.description
publicRanges.characteristics.title
- p
- u
- b
- l
- i
- c
- R
- a
- n
- g
- e
- s
- .
- c
- h
- a
- r
- a
- c
- t
- e
- r
- i
- s
- t
- i
- c
- s
- .
- i
- t
- e
- m
- s
publicRanges.examples.title
| publicRanges.examples.headers.publicIp | publicRanges.examples.headers.ownerService |
|---|---|
8.8.8.8 | Google Public DNS |
1.1.1.1 | Cloudflare DNS |
13.107.42.14 | Microsoft services |
151.101.193.140 |
natImplications.title
natImplications.privateToPublic.process.title
- n
- a
- t
- I
- m
- p
- l
- i
- c
- a
- t
- i
- o
- n
- s
- .
- p
- r
- i
- v
- a
- t
- e
- T
- o
- P
- u
- b
- l
- i
- c
- .
- p
- r
- o
- c
- e
- s
- s
- .
- s
- t
- e
- p
- s
natImplications.privateToPublic.benefits.title
- n
- a
- t
- I
- m
- p
- l
- i
- c
- a
- t
- i
- o
- n
- s
- .
- p
- r
- i
- v
- a
- t
- e
- T
- o
- P
- u
- b
- l
- i
- c
- .
- b
- e
- n
- e
- f
- i
- t
- s
- .
- i
- t
- e
- m
- s
natImplications.publicToPrivate.challenges.title
- n
- a
- t
- I
- m
- p
- l
- i
- c
- a
- t
- i
- o
- n
- s
- .
- p
- u
- b
- l
- i
- c
- T
- o
- P
- r
- i
- v
- a
- t
- e
- .
- c
- h
- a
- l
- l
- e
- n
- g
- e
- s
- .
- i
- t
- e
- m
- s
natImplications.publicToPrivate.solutions.title
- n
- a
- t
- I
- m
- p
- l
- i
- c
- a
- t
- i
- o
- n
- s
- .
- p
- u
- b
- l
- i
- c
- T
- o
- P
- r
- i
- v
- a
- t
- e
- .
- s
- o
- l
- u
- t
- i
- o
- n
- s
- .
- i
- t
- e
- m
- s
identification.title
| identification.headers.method | Description | identification.headers.privateIndicator | identification.headers.publicIndicator |
|---|---|---|---|
| IP Range Check | Look at first octets of IP address | 10.x.x.x, 172.16-31.x.x, 192.168.x.x | Any other address not in reserved ranges |
| Reachability Test | Try to reach from external network | Cannot be reached from internet | Can be reached from internet (if not firewalled) |
| Router Configuration | Check WAN vs LAN interface addresses | LAN interfaces use private addresses | WAN interface uses public address (unless CGNAT) |
tools.title
commonScenarios.title
troubleshooting.title
troubleshooting.labels.possibleCauses Server has private IP, No port forwarding, Firewall blocking
troubleshooting.labels.diagnosis Check if server IP is private, test port forwarding
troubleshooting.labels.solution Configure port forwarding or use public IP
troubleshooting.labels.possibleCauses Both using same private range, No routing configured
troubleshooting.labels.diagnosis Check for IP address conflicts, routing tables
troubleshooting.labels.solution Use different private ranges or configure routing
troubleshooting.labels.possibleCauses Private IP conflicts, NAT traversal issues
troubleshooting.labels.diagnosis Check for address space overlap
troubleshooting.labels.solution Reconfigure IP ranges or use different VPN protocol
security.title
- Private IPs provide security through obscurity
- Still need internal security measures
- Lateral movement possible within private networks
- Monitor internal network traffic
- Public IPs are constantly scanned and attacked
- Require robust firewall and security measures
- DDoS protection may be necessary
- Regular security updates and monitoring essential
bestPractices.title
- Use private IPs for internal networks
- Reserve public IPs for internet-facing services only
- Plan private IP ranges to avoid conflicts
- Document your IP addressing scheme
- Use DHCP for dynamic private IP assignment
- Implement proper firewall rules for public IPs
- Monitor public IP usage and costs