Set up the DoubleZero client¶
DoubleZero is a private fiber network that carries market data between regions, and TheHUB's DoubleZero device (DZD) is TheHUB's own node on it (see The DoubleZero device). Using DoubleZero is optional.
This page is for the engineer who runs the host of a tenant that uses DoubleZero: a venue's or trading firm's own host, or a computing provider's downstream customer's host. Here, "client" means only the DoubleZero client software, never a downstream customer.
Before you start¶
An access pass is DoubleZero's entitlement record, bound to one address. It lists the multicast groups the holder may publish to and subscribe to, each by its group code, DoubleZero's identifier for a multicast group.
You need these, from the tenant's allocation table except the pass. A computing provider's downstream customer gets all four from its provider.
- The tenant's DoubleZero client address: an address from the tenant's
block that the host sends DoubleZero traffic from,
<DoubleZero client address>in the commands below. The host must hold it, because the commands send from it; the /31 peering link is on the router that peers with TheHUB, not on the host. A host at a computing provider also has an address from the provider for its default route, and that one does not match the pass. - An access pass bound to that address, naming the group codes for the tenant's feeds, requested through your TheHUB contact: by you for your own tenant (see Request your access pass), or by a computing provider for its downstream customer (see Using DoubleZero).
- The DZD's device code, the identifier of TheHUB's DZD on DoubleZero.
<DZD device code>in the commands below. - The DZD's two user-tunnel endpoint addresses, where tenants' tunnels terminate on the DZD.
The DoubleZero client software builds a Generic Routing Encapsulation (GRE) tunnel, an ordinary unicast tunnel that carries the multicast inside it, from the host across TheHUB's fabric to one of the user-tunnel endpoints.
The Border Gateway Protocol (BGP) session, group membership, and the multicast all run inside the tunnel.
Set up the host¶
-
Check reachability to both user-tunnel endpoints from the tenant's DoubleZero client address. The endpoints are not reachable from the internet, only across TheHUB's network.
ping -I <DoubleZero client address> <user-tunnel endpoint 1> ping -I <DoubleZero client address> <user-tunnel endpoint 2>Verify
Both endpoints answer. They are in every tenant's received routes, whatever its role.
-
Install the DoubleZero client, version 0.43.0 or later, from DoubleZero's package repository, then restart its daemon. On Debian or Ubuntu, the repository is
dl.cloudsmith.io/public/malbeclabs/doublezero/(Malbec Labs is the company that develops DoubleZero).- If the repository is not already configured on the host, follow the manual Debian instructions on Cloudsmith's setup page for the repository, which install the signing key and add the repository's source list.
-
Install the client and restart the daemon:
Restart the daemon after every install or upgrade
An install or upgrade does not restart the daemon by itself, and a daemon left running from before the install or upgrade silently ignores the DoubleZero client address set in the next step.
Verify
doublezero --versionreports 0.43.0 or later, and the daemon's process start time is later than the install. -
Connect with the client pinned to TheHUB's DZD. To subscribe to a group:
doublezero connect multicast --subscribe <group code> \ --client-ip <DoubleZero client address> \ --device <DZD device code>--client-iptakes the DoubleZero client address. To publish, use--publish <group code>in place of--subscribe <group code>. Use a group code named on the access pass.Set both
--client-ipand--device- Why
--client-ip: without it, the daemon discovers the address of the host's default route, which is not the tenant's DoubleZero client address and does not match the access pass. - Why
--device: without it, the client picks the lowest-latency DoubleZero device. Other DoubleZero devices share the facility, so the tunnel can end on one of them and the tenant's DoubleZero traffic leaves TheHUB.
- Why
-
Verify the connection.
Verify
The tunnel is up and its BGP session is established, and the tunnel ends on one of the DZD's user-tunnel endpoints. A tunnel to any other address does not cross TheHUB.
Inside the tunnel
- Two separate BGP sessions. The BGP session that
doublezero statusreports runs inside the tunnel, between the DoubleZero client and the DZD. It belongs to DoubleZero and is separate from the tenant's external BGP (eBGP) session with TheHUB, which runs on the router that holds the tenant's connection to TheHUB. - No multicast configuration on either side. Neither the tenant nor TheHUB configures Internet Group Management Protocol (IGMP), Protocol Independent Multicast (PIM), or a rendezvous point, and no network between the host and TheHUB needs multicast support.
- Maximum Transmission Unit (MTU) through the tunnel. The effective multicast MTU through the tunnel is the standard 1500-byte path MTU less the GRE encapsulation overhead. Size frames to fit.
See also¶
- Onboarding: the onboarding guides.
Last reviewed 2026-11-19.