An allocated IPv6 prefix is a range, not a ready-to-use proxy pool. Count only sources the host can actually use under the provider's allocation, routing and source-validation requirements.

First establish how the prefix is delivered: routed and on-link prefixes can require different arrangements. Local addresses and neighbour discovery must fit that model. Selecting suffixes from a /64 cannot create those prerequisites.

Squid's source-address directive and Dante external-source settings then choose among usable connection sources. They neither allocate the addresses nor establish the route.

An IPv6 source also needs a compatible IPv6 destination connection. Reaching the proxy over IPv4 does not give an IPv4-only website IPv6 connectivity; the entrance and onward connection are separate.

Start with a small usable set and document its selection and routing assumptions. Addresses in one prefix remain related network identities, not independently provisioned residential connections. There is no basis for promising that a website will treat their requests as unrelated people.

Allakkat attuumassuteqartut