var img = document.createElement('img'); img.src = "https://matomo.0l.de/piwik.php?idsite=5&rec=1&url=https://cunicu.li" + location.pathname; img.style = "border:0"; img.alt = "tracker"; var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(img,s);
Skip to main content

Route Synchronization

The route synchronization feature keeps the kernel routing table in sync with WireGuard's AllowedIPs setting.

This synchronization is bi-directional:

  • Networks with are found in a Peers AllowedIP list will be installed as a kernel route.
  • Kernel routes with the peers link-local IP address as next-hop will be added to the Peers AllowedIPs list.

This rather simple feature allows user to pair cunicu with a software routing daemon like Bird2 while using a single WireGuard interface with multiple peer-to-peer links.

Configuration​

The following settings can be used in the main section of the configuration file or with-in the interfaces section to customize settings of an individual interface.

sync_routes
boolean (Route Synchronization)
Default: true

Enable route synchronization.

routing_table
integer (Kernel Routing Table)
Default: 254

Kernel routing table which is used. On Linux, see /etc/iproute2/rt_tables for table ids and names

watch_routes
boolean (Watch Routes)
Default: true

Keep watching the for changes in the kernel routing table via netlink multicast group.

{
  • "sync_routes": true,
  • "routing_table": 254,
  • "watch_routes": true
}