Find me:

Using Tunnelbroker to make Lavalink balance its requests over many IPv6 addresses

When scraping metadata with Lavalink, it may be useful to have a large block of IPv6 addresses available. Allocating a large prefix of addresses to a machine can be difficult, as this is dependent on the configuration of the IP addresses, which is generally out of your control if you are renting a server.

We can use the free Tunnelbroker service from Hurricane Electric to get a routed IPv6 prefix. This can also work if your server does not even have an IPv6 address to begin with.

Acquiring a /48 block

  1. Register an account at
  2. Create a new (regular) tunnel
  3. Enter your IPv4 IP address and select a nearby region. Your IPv4 must be pingable.
  4. Request a new /48. We could use a /64, however a /64 is much more likely to be blocked.

Configuring your block

The first thing you will need to do is enable IPv6 binding in Linux. This enables Lavalink (and other programs) to bind to local addresses that would otherwise be considered illegal:

# Enable now
sysctl -w net.ipv6.ip_nonlocal_bind=1
# Persist for next boot
echo 'net.ipv6.ip_nonlocal_bind = 1' >> /etc/sysctl.conf

Next you will need to configure your network system. This diverges a lot depending on your distribution. Hurricane Electric provides a lot of examples. Common for them all is that you need to take two extra steps:

ip -6 route replace local YOUR_48_BLOCK dev lo

Test your configuration

Before setting up Lavalink, you can test if your IPv6 configuration actually works.

# Test that IPv6 works in the first place

# If you have the IPv6 block 1234:1234:1234::/48
# You should be able to use any of the IPs within that block
ping6 -I 1234:1234:1234::
ping6 -I 1234:1234:1234::1
ping6 -I 1234:1234:1234:dead::beef

# Make sure your /48 block appears when running this command
ip -6 route

This is the easy part. Add the ratelimit block to your config:

    # ...
      ipBlocks: ["1234:1234:1234::/48"]
      strategy: "LoadBalance"
      searchTriggersFail: true

You can read more about the different strategies in

When using docker

If you use Docker, you will need to set your network mode to "host". This will let your container use the network as if it was not in a container.


Ubuntu: Editing /etc/network/interfaces on a Netplan system

Don't edit /etc/network/interfaces if your system relies on a /etc/netplan/ configuration. See the Netplan example on the Tunnelbroker website.

Using the /64 block instead of the /48 block

Make sure the /64 block is not being used in your config. You must replace it in the examples that Tunnelbroker provides.

You probably haven't configured your routes properly. See the “Test your configuration” section.

You did not enable net.ipv6.ip_nonlocal_bind as described above.

You're using a nano strategy for a block larger than a /64 block. This doesn't work. The other strategies still pick out random values for the last 64 bits, so there would be no point anywaysIndex out of bounds for the CombinedBlock.

“Help, I've tried everything!”

If you've followed this entire guide and you have a problem not listed here, you are welcome to contact me. Please provide the following info: