THE PRACTICAL GUIDE · NORMANDIN SYSTEMS
Get more from IPv6 ULA generator
IPv6 ULA generator: Generate your own local, non-routable IP addresses for your network according to RFC4193. Unique Local Addresses support private IPv6 addressing plans while reducing the collision risk associated with independently chosen local networks. IP calculations describe address space; they do not tell you whether a host is online or whether a firewall permits traffic. Prefix lengths divide an address into network and host portions, and a one-bit prefix change can substantially change the number of included addresses. Confirm whether you are working with IPv4 or IPv6 and use the same family throughout a calculation. For network planning, record both the human-readable notation and the exact boundaries. This helps catch accidental overlap, oversized allowlists, and assumptions about which addresses are usable.
Guide updated October 13, 2026
How to use this tool
- Begin with a representative input. For a practical test, use: A new local ULA prefix generation request. Replace demonstration values only after you understand the output.
- Enter the address, range, or prefix in the syntax requested by the tool, using the correct IPv4 or IPv6 address family.
- Inspect the network boundaries and the size of the resulting address space, especially when a calculation broadens or subdivides a range.
- Compare the result with neighboring subnets and your intended allocation before applying it to a router, firewall, or configuration file.
SEE IT IN PRACTICE
A worked example
A new local ULA prefix generation request
An fd-prefixed unique-local allocation, typically with a generated global-ID portion
Keep the generated prefix stable once deployed and record it before interconnecting independently managed networks.
Keep prefix purpose visible
A globally routed allocation, a Unique Local Address prefix, and a link-local address serve different purposes. A ULA can support internal addressing without becoming globally routed. Document where the prefix came from and which child prefixes belong to each segment. When combining networks, compare complete prefix allocations rather than only the memorable leading groups.
Avoid importing IPv4 assumptions
IPv6 uses 128-bit addresses and different neighbor and group-communication mechanisms. There is no IPv4-style broadcast address to subtract from each subnet. Address assignment conventions and platform requirements still matter, especially for common /64 LAN designs. Keep the delegated parent prefix, chosen child size, and routing plan together so an address calculation does not become an isolated number without operational context.
When this tool is useful
- Plan internal IPv6 addressing
- Create a lab allocation
- Prepare a private-network design
Tips for a better result
- ULA generation does not make a network globally routable or configure routers and interfaces.
- An address being mathematically inside a subnet does not prove that the address is assigned, reachable, or authorized for access.
- Keep prefix lengths visible in documentation; an address without its prefix is insufficient to describe a subnet allocation.
Frequently asked questions
Why is IPv6 planning usually expressed as prefixes rather than individual addresses?
The address space is large enough that subnet allocation is usually the useful planning unit. Prefix hierarchy makes routing, delegation, and segment boundaries easier to manage than enumerating host addresses.
Why does the prefix length matter?
The prefix length controls how many bits identify the network. Increasing the prefix length makes the block smaller; decreasing it makes the block larger and can include addresses beyond your intended scope.
Can I paste the result directly into a firewall?
First verify the destination’s accepted syntax and the policy’s intended scope. A mathematically correct range can still grant too much access, overlap another rule, or behave differently because of rule ordering.
What happens to the information I enter?
The utility processes your input in this browser. Some tools retain field values in browser storage or the URL; avoid entering secrets in shareable fields. Page and asset requests still go to the hosting provider. Read the privacy and offline-use notes for details.