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.
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
All articles
Start with the question in front of you. Find a guide, compare the choices and work through the details.
27 articles
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.
Networks
Access your NAS from outside the office: decide who should reach it first.
Plan remote NAS access around approved shares, separate administrator permissions and supported gateways. Test file operations, encryption and recovery.
Networks
Two offices use the same private subnet. What happens when you connect them?
Two sites using the same private range create ambiguous routes. Compare renumbering, direct enrollment and assessed translation before connecting them.
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.
Networks
Private workspace DNS: names your team can use without publishing them.
Private workspace DNS maps internal names to approved resources. Check record ownership, resolver selection, routes and application certificates together.
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.
Publish
Your webhook needs a public endpoint. Your admin panel doesn’t.
Expose the webhook receiver, keep admin routes private, validate signed deliveries and plan for retries, replay checks and separate outbound calls.
Keep up with Fibmesh
Good questions deserve a closer look.
New guides on connectivity, access and infrastructure, delivered to your feed reader.