Public IPs
A public IP without moving your server
Keep your server in place with an assessed public IP delivery path. Compare direct assignment and gateways, then verify firewall rules and reply routing.
The Fibmesh blog
The article library.
Practical writing on private access, public reachability and the routes in between. For the people building and looking after their own infrastructure.
Explore the library
Public IPs
Make infrastructure reachable. Work through addressing, firewall rules, port mappings and the route replies take.
10 articles in Public IPs
Public IPs
Moving an application between providers: which connection assumptions change?
Before moving an application between providers, check public addresses, outbound allowlists, DNS caches, private dependencies and a workable rollback plan.
Public IPs
ERP on customer premises: keeping the server where the business needs it
Keep an ERP server on customer premises while assessing public IP delivery, service exposure, full-tunnel effects, ownership and recovery checks.
Public IPs
One gateway, several servers: planning public port mappings
Plan one gateway’s public port mappings to multiple servers. Define protocol and external port, restrict callers, and verify each target’s return route.
Public IPs
An IPv6-only public address: who can actually reach your service?
An IPv6-only service needs clients with working IPv6 or a supported intermediary. Check DNS, application behavior and firewall policy before hosting.
Public IPs
A public IP from your ISP—or delivered to your server?
Compare an ISP public IP with an address delivered over a tunnel. Review routing, address retention, support ownership and connection-change costs.
Public IPs
Port forwarding is configured. Why is your server still unreachable?
Port forwarding can fail at the server, upstream NAT or reply route. Test the listener, public WAN address and full connection without opening every port.
Public IPs
A public address and a routed subnet solve different problems
One public IP can serve mapped services; a routed subnet gives workloads separate addresses. Compare routing duties, usable counts and IPv4 or IPv6 needs.
Public IPs
Public IP return routing: where does your server’s reply go?
When public requests arrive but connections time out, inspect the reply. Check source identity, NAT state and routing policy through the server and gateway.
Keep up with Fibmesh
Good questions deserve a closer look.
New guides on connectivity, access and infrastructure, delivered to your feed reader.