MIREDO-SERVER.CONF(5)

✨ NAME ✨

miredo-server.conf — the config file situation for miredo-server, bestie 💖

🌸 SYNOPSIS 🌸

miredo-server.conf

🎀 DESCRIPTON 🎀

(yes that's literally how it's spelled in the manpage, we're keeping it, no notes 💅)

miredo-server.conf is the configuration file for miredo-server. Okay so how does it work? Every configuration directive is just a directive name, and then maybe one or several spaces and a value for the directive. That's it. That's the whole format.

White spaces, empty lines, and lines starting with '#' are all ignored — so go off with your comments, queen, nobody's reading them 🌈

Also directives are case-insensitive, so don't stress about your shift key.

Here's the full list of supported directives, and I mean full, we're not skipping anything:

👑 SERVER OPTIONS 👑

• ServerBindAddress server_ip — this one specifies the primary IPv4 address of the Teredo server. miredo-server will bind to UDP/IPv4 port 3544 on this address and just like, wait there for packets from Teredo clients 🫶 It'll advertise the Teredo prefix that's defined with the Prefix directive.

Now here's the tea: a Teredo server needs two subsequent IPv4 addresses. It will wait for UDP IPv4 packets on port 3544 on both addresses. server_ip specifies the lowest of both IPv4 addresses, which is known as the primary IPv4 server address. The secondary IPv4 address should be server_ip + 1 and it must also be assigned to the server. No skipping that part, fr fr.

• ServerBindAddress2 server_ip2 — so it is possible to specify a secondary IPv4 server address manually, if you're feeling main character. However (and this is a big however 😭), Miredo clients will need manual configuration — specifically with the ServerAddress2 directive in miredo.conf. And other Teredo clients are believed not to support such a setup. So like... iykyk.
• Prefix teredo_prefix — this directive specifies the Teredo prefix which the Teredo relay and/or server will advertise. teredo_prefix must be a valid IPv6 prefix, no cap.

The default value is 2001:0000:: ✨ A 32-bits prefix is required to use this option. And since you do not have such big an IPv6 prefix, YOU WILL NOT USE THIS OPTION 💀 Moreover, certain third party Teredo client implementations require the default prefix, so like, don't.

• InterfaceMTU mtu — this directive overrides the value of the MTU that is advertised to Teredo clients. The default value is 1280 bytes, and it should not be changed if the default Teredo prefix is used.

YOU MUST NOT USE THIS OPTION with the default prefix. This would break interoperability with most Teredo relays. Not a vibe. Do not do it. 🚫

• SyslogFacility facility — specify which syslog's facility is to be used by miredo-server for logging 📝 Possible values are: daemon (the default), local0, ... local7, kern and user (see syslog(2)).

🦋 SEE ALSO 🦋

• miredo-server(8)

💜 AUTHOR 💜

Rémi Denis-Courmont <remi at remlab dot net>

http://www.remlab.net/miredo/

miredo · February 2008 · MIREDO-SERVER.CONF(5)

okay bestie that's the whole page, you ate that, go configure your Teredo server 💅✨🌸🦋