EgressPool.DependencyInjection 26.6.8.9060

EgressPool

EgressPool is a .NET library for sending outbound TCP, UDP, and HTTP traffic from a configured pool of source IP addresses.

Use it when an application needs its outbound connections to appear from different local addresses while keeping the calling code simple.

What You Can Do

• Configure one or more IPv4 or IPv6 prefixes.
• Automatically detect prefixes allocated on local interfaces.
• Create TCP, UDP, or HTTP clients that use addresses from those prefixes.
• Select prefixes by destination scope for TCP, HTTP, and destination-aware UDP clients.
• Reuse the same pool across many outbound requests.
• Release addresses by disposing the clients, sockets, leases, or pool you create.

Quick Start

using System.Net;
using Egress;

EgressPoolOptions options = new()
{
    Prefixes = [IPNetwork.Parse("127.0.0.0/8")],
};

await using EgressPool pool = await EgressPool.CreateAsync(options);
using HttpClient client = pool.CreateHttpClient();

string response = await client.GetStringAsync("http://127.0.0.1:5000/");

To add prefixes already allocated on local interfaces:

EgressPoolOptions options = new()
{
    AutoDetectPrefixes = true,
};

Detected prefixes are merged into the same pool as configured prefixes. Destination-aware TCP, HTTP, RentAddressAsync(IPAddress), and CreateUdpClient(IPAddress) calls prefer prefixes with the same address scope as the destination, then verify candidates with a UDP bind/connect probe before selecting one.

When a logger is supplied directly or through dependency injection, EgressPool writes trace logs for detected prefixes, candidate prefixes, rejected candidates, and the final selected prefix.

Expected Behavior

Each outbound connection receives a source address from the configured pool. When the connection, client, or pool is disposed, the address is no longer held by that caller.

Some configurations may require operating system support or elevated permissions. If the requested behavior is not available on the current machine, pool creation or connection creation fails with an exception.

Cleanup

Dispose the pool when the application is finished with it:

await pool.DisposeAsync();

If an application exits unexpectedly, release anything left behind by a previous process:

await EgressPool.CleanupStaleStateAsync();