Talk to a specialist

VLSM.io SOLUTIONS

IPv4 subnet leasing

IPv4 prefixes from /24 through /16, with delivery and capacity sized for your project infrastructure.

IPv4-only egressConnectivity and intelligence
Globe with IPv4-only outbound connections
IPv4-only egress203.0.113.24Illustrative addresses
Estimated reading time: 7 min7 sections
01

Address space to organize your operation

IPv4 subnet rental provides an addressing foundation for projects that need to organize multiple applications, environments, or outbound groups. VLSM.io works with prefixes from /24 through /16, subject to availability and technical assessment. Block selection should reflect how addresses will be used, the number of services, and expected growth. Renting a subnet does not, by itself, define bandwidth, connection counts, or permission to access external destinations. Those aspects need to be specified separately so the project has clear technical and operational boundaries.

The service can be discussed for infrastructure hosted in the data centers and for external environments. In each scenario, the handoff point and responsibility for routing, servers, and applications must be documented. A project that only configures a proxy requires a different integration from one that receives a network over a tunnel. Making this distinction at the beginning helps size effort, capacity, and support, preventing the team from discovering connectivity requirements only after it has started migrating its workflows into the new environment.

CONNECTIONS IN MOTIONThe path of your connection
ApplicationJob or integration
ConnectivityIPv4-only egress
DestinationSystem or service
Example of a service with IPv4-only Internet egress. IPv6 egress belongs to a separate service. The animation does not represent live traffic.
02

How to interpret IPv4 prefixes

An IPv4 address contains 32 bits. In prefix notation, the number after the slash indicates how many bits identify the network. A /24 contains 256 total addresses, while a /16 contains 65,536. A /20, as an intermediate reference, contains 4,096. These totals describe the mathematical size of the block; the number actually available to applications depends on architecture and necessary reservations. Do not automatically apply one usable-address rule to proxies, links, routed interfaces, and local networks, because these are different deployment situations.

Start sizing with an inventory of applications and groups that genuinely require distinct addresses. Separate production, staging, and temporary operations, reserving room for justified growth. Also consider how long configuration changes would take if the pool expands in the future. A simple distribution plan with owners and purposes for each range is often more useful than a large block without usage criteria. Periodically reviewing that plan identifies unused addresses and reduces unnecessary changes to services that already operate reliably under an established configuration.

03

Choose the delivery method

Delivery possibilities include HTTP IP Proxy, SOCKS5, proxy-side name resolution identified as SOCKS5H in compatible clients, SOCKS5 with UDP, VXLAN, GRE, cross-connect, virtual machines, and bare-metal servers. The method depends on the project and contracted availability. SOCKS5H is not an independent protocol; it indicates a name-resolution choice in the integration. Likewise, UDP traffic requires specific support in both the service and the client. The list of possibilities should become a concrete specification before activation, with the selected method explicitly documented for the project.

When the goal is to integrate an application that already supports proxies, that delivery method may reduce changes to the customer network. Tunnels and physical connections address other needs, such as infrastructure integration or routing control. Virtual machines and bare-metal servers add decisions about operating systems, updates, and administrative ownership. Compare alternatives by the effort required to operate the service and by workflow requirements. The best handoff is one your team can maintain, diagnose, and expand consistently throughout the operating life of the project.

TRAFFIC AND ADDRESSINGObserve the source and track responses.
Source203.0.113.24
Destination198.51.100.20
Return203.0.113.24
Addresses reserved for examples. Track bidirectional traffic together with latency, failures, and application results.
04

Routing, tunnels, and continuity

VXLAN and GRE add encapsulation to the path and require attention to packet size, endpoint connectivity, and rules on intermediate equipment. Configuration should cover both outbound and return paths, avoiding asymmetric routes that disrupt sessions or troubleshooting. These mechanisms should not be treated as automatic encryption. When additional transport confidentiality is required, that protection must be designed explicitly. Acceptance testing needs to observe actual application traffic rather than relying only on the successful response of a simple reachability test between the configured endpoints.

Define how a link maintenance event, equipment restart, or handoff outage affects operations. If the project requires redundancy, specify the covered components and the criteria for changing paths. Two connections do not guarantee independence when they share the same physical or logical constraint. Document the recovery procedure and the people responsible for performing it. This planning supports a discussion of continuity based on the actual design, without confusing the number of contracted addresses with the availability of the entire infrastructure supporting the service.

05

Scalability from 1 Mbps to multiple 100 Gbps

The network capacity range envisioned for projects extends from 1 Mbps to multiple 100 Gbps, subject to sizing and agreement. It does not mean that each address receives that capacity individually. Analyze transferred volume, response size, connection duration, and the distribution of execution times. An operation involving large files has a different profile from thousands of small queries. The metrics should make it possible to identify whether the constraint is bandwidth, processing, connection counts, or the destination being queried by the application.

Plan gradual tests with task-completion targets and agreed limits. Increasing concurrency without observing destination responses can expand queues, errors, and repeated work. Compare useful results before and after every adjustment, including resource consumption in the customer environment. Maintain operational headroom for predictable peaks and define the process for requesting expansion. This approach turns scalability into a managed capability, with evidence about what needs to grow and criteria for determining whether the change produced a practical benefit for the business workflow.

06

Inventory, access, and ownership

Maintain a record of allocated prefixes, delivery methods, associated applications, and responsible contacts. Separate credentials by environment whenever the integration allows it, and avoid publishing them in repositories, screenshots, or execution logs. Delegating a block does not remove the need for access controls. Inbound, outbound, and administrative rules should follow the project purpose, reducing exposure of services that do not need to be reachable from the internet or from networks that do not participate in the operation and its support processes.

Address use also needs to be internally traceable. When an incident is reported, the team should be able to identify the application and time period involved without unnecessarily retaining sensitive content. Define log retention, request handling, and the process for suspending a problematic integration. Traceability helps troubleshooting and support organization alike. It does not require recording every transmitted detail, but it does require planning which events are necessary to understand operations and respond accurately to a concrete issue reported by an affected party.

FROM CONNECTION TO RESULTTurn requirements into an observable operation.
Plan
Connect
Monitor
Destination planning, connectivity configuration, and result validation are complementary steps. The animation represents this workflow.
07

From technical assessment to activation

To begin the assessment, provide the project purpose, estimated address requirements, main destinations, infrastructure location, and desired delivery method. Add bandwidth, protocol, and continuity requirements. These details support discussion of a suitable prefix and the work required to activate it. Validate the service first in a controlled environment with written acceptance criteria. Only then expand migration while monitoring indicators that represent complete application behavior, rather than merely the isolated availability of the new outbound address or of one component in the delivery path.

Planning should consider coexistence with IPv6 when that makes sense for the destinations involved. The IPv4 subnet continues serving systems that depend on that family, while an IPv6 solution can be contracted separately. IPv4 subnet rental does not include IPv6 egress. There is no need to mix compatibility criteria: each path should be tested and identified. Discuss addressing, delivery, and capacity with VLSM.io around your actual operation, using a proposal that explicitly identifies resources, responsibilities, and the next steps required to implement and validate the selected service.