| ; Example node configuration |
| |
| ; Optional directives are set to the default value but commented out. |
| |
| |
| node_address = 192.0.2.0 |
| |
| ;set_hostname = false |
| ;run_dns_server = false |
| ;replace_sysctl_conf = false |
| ;replace_resolv_conf = false |
| |
| ; External name server for using as a fallback before RNCN becomes operational |
| ; at this node |
| ;fallback_name_server = |
| |
| ; A private key for WireGuard can be generated by running 'wg genkey' |
| wg_private_key = |
| |
| ; The default router should be specified in either an IP address or a double |
| ; quoted interface name. |
| ; Same as BIRD configuration syntax, the literal double quotemarks in the |
| ; alternative 'ipv4_default_router' directive inducates that the default |
| ; router is on link of the quoted interface without a need of specifying its |
| ; IP address. |
| |
| ; Specify IPv4 default router using its IP address |
| ipv4_default_router = 198.51.100.1 |
| ; Or, specify an interface IPv4 default routes |
| ipv4_default_router = "eth0" |
| ; Same for IPv6 default router |
| ipv6_default_router = fe80::202d:25ff:fe26:c82b%eth0 |
| |
| ; URL to a remote configuration file for the DNS server |
| ;dns_config_update_url = |
| |
| |
| ; Example peer for waiting for the peer to initiate WireGuard handshake to |
| ; this node |
| [peer example-2] |
| ; The peer public key for WireGuard |
| public_key = |
| ; Peer IP address and port number for WireGuard |
| remote = example-2.rncn.net:15911 |
| ; Optional tunnel interface MTU to override default value of 1420; should be |
| ; specified if the underlaying default router (WAN) interface has a MTU |
| ; smalller than 1500; for example when using over PPPoE with MTU of 1492, the |
| ; WireGuard interface MTU should be set to 1412 (1492-80) |
| ;mtu = 1420 |
| ; In-tunnel IPv4 address (single address only) |
| ip4_addr = 10.100.0.0 |
| ; In-tunnel IPv6 addresses |
| ip6_addr = fd00:db8:100:0:: |
| ip6_addr = fe80:100:0:: |
| ; Adjustment value for calculating final metric for this peer |
| ;metric_offset = 0 |
| |
| ; Example peer for this node to initiate WireGuard handshake to the peer |
| [peer example-3] |
| public_key = |
| ; Local port number for receiving packet for this WireGuard tunnel; due to the |
| ; design limitation of WireGuard, it is not possible to specify bind address |
| ; or address family |
| bind_port = 15911 |
| ;mtu = 1420 |
| ip4_addr = 10.100.1.1 |
| ip6_addr = fd00:db8:100:1::1 |
| ip6_addr = fe80:100:1::1 |
| ;metric_offset = 0 |
| |
| ; The in-tunnel IP addresses use 1-bit host number; thus, the prefix lengths |
| ; are /23 and /127 for IPv4 and IPv6 address respectively. The remaining |
| ; address in this sub-network is used as peer's in-tunnel address implicitly; |
| ; take the local IPv4 address of peer example-3 configuration for example, |
| ; the peer's in-tunnel IPv4 address will be 10.100.1.0. |
| |
| |
| ; URLs for fetching address ranges for advertising routes for specified |
| ; networks from this node; can be empty |
| [ra-list] |
| ;https://api.rncn.net/example/routing-advertisements/all.area |
| ;https://api.rncn.net/example/routing-advertisements/eur.area |
| |
| ; Exclude these IPv4 address ranges from advertising; note the entries are |
| ; matched by text only, address prefix lengths are not considered |
| [ipv4-ra-exclusion] |
| ;216.239.32.0/24 |
| ;216.239.34.0/24 |
| ;216.239.36.0/24 |
| ;216.239.38.0/24 |
| ;1.1.1.0/24 |
| |
| ; Static IPv4 routes that uses the default router, and should be applied to, |
| ; as well as advertised from this node; |
| [wan-ipv4-route-targets] |
| ;1.1.1.1/32 |
| |
| ; Likewise, but for IPv6 routes |
| [wan-ipv6-route-targets] |
| ;2606:4700:4700::1111/128 |