config.yaml 6.5 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160
  1. # This is the nebula example configuration file. You must edit, at a minimum, the static_host_map, lighthouse, and firewall sections
  2. # PKI defines the location of credentials for this node. Each of these can also be inlined by using the yaml ": |" syntax.
  3. pki:
  4. ca: /etc/nebula/ca.crt
  5. cert: /etc/nebula/host.crt
  6. key: /etc/nebula/host.key
  7. #blacklist is a list of certificate fingerprints that we will refuse to talk to
  8. #blacklist:
  9. # - c99d4e650533b92061b09918e838a5a0a6aaee21eed1d12fd937682865936c72
  10. # The static host map defines a set of hosts with with fixed IP addresses on the internet (or any network).
  11. # A host can have multiple fixed IP addresses defined here, and nebula will try each when establishing a tunnel.
  12. # The syntax is:
  13. # "{nebula ip}": ["{routable ip/dns name}:{routable port}"]
  14. # Example, if your lighthouse has the nebula IP of 192.168.100.1 and has the real ip address of 100.64.22.11 and runs on port 4242:
  15. static_host_map:
  16. "192.168.100.1": ["100.64.22.11:4242"]
  17. lighthouse:
  18. # am_lighthouse is used to enable lighthouse functionality for a node. This should ONLY be true on nodes
  19. # you have configured to be lighthouses in your network
  20. am_lighthouse: false
  21. # serve_dns optionally starts a dns listener that responds to various queries and can even be
  22. # delegated to for resolution
  23. #serve_dns: false
  24. # interval is the number of seconds between updates from this node to a lighthouse.
  25. # during updates, a node sends information about its current IP addresses to each node.
  26. interval: 60
  27. # hosts is a list of lighthouse hosts this node should report to and query from
  28. # IMPORTANT: THIS SHOULD BE EMPTY ON LIGHTHOUSE NODES
  29. hosts:
  30. - "192.168.100.1"
  31. # Port Nebula will be listening on. The default here is 4242. For a lighthouse node, the port should be defined,
  32. # however using port 0 will dynamically assign a port and is recommended for roaming nodes.
  33. listen:
  34. host: 0.0.0.0
  35. port: 4242
  36. # Sets the max number of packets to pull from the kernel for each syscall (under systems that support recvmmsg)
  37. # default is 64, does not support reload
  38. #batch: 64
  39. # Configure socket buffers for the udp side (outside), leave unset to use the system defaults. Values will be doubled by the kernel
  40. # Default is net.core.rmem_default and net.core.wmem_default (/proc/sys/net/core/rmem_default and /proc/sys/net/core/rmem_default)
  41. # Maximum is limited by memory in the system, SO_RCVBUFFORCE and SO_SNDBUFFORCE is used to avoid having to raise the system wide
  42. # max, net.core.rmem_max and net.core.wmem_max
  43. #read_buffer: 10485760
  44. #write_buffer: 10485760
  45. # Local range is used to define a hint about the local network range, which speeds up discovering the fastest
  46. # path to a network adjacent nebula node.
  47. #local_range: "172.16.0.0/24"
  48. # Handshake mac is an optional network-wide handshake authentication step that is used to prevent nebula from
  49. # responding to handshakes from nodes not in possession of the shared secret. This is primarily used to prevent
  50. # detection of nebula nodes when someone is scanning a network.
  51. #handshake_mac:
  52. #key: "DONOTUSETHISKEY"
  53. # You can define multiple accepted keys
  54. #accepted_keys:
  55. #- "DONOTUSETHISKEY"
  56. #- "dontusethiseither"
  57. # sshd can expose informational and administrative functions via ssh this is a
  58. #sshd:
  59. # Toggles the feature
  60. #enabled: true
  61. # Host and port to listen on, port 22 is not allowed for your safety
  62. #listen: 127.0.0.1:2222
  63. # A file containing the ssh host private key to use
  64. # A decent way to generate one: ssh-keygen -t ed25519 -f ssh_host_ed25519_key -N "" < /dev/null
  65. #host_key: ./ssh_host_ed25519_key
  66. # A file containing a list of authorized public keys
  67. #authorized_users:
  68. #- user: steeeeve
  69. # keys can be an array of strings or single string
  70. #keys:
  71. #- "ssh public key string"
  72. # Configure the private interface. Note: addr is baked into the nebula certificate
  73. tun:
  74. # Name of the device
  75. dev: nebula1
  76. # Toggles forwarding of local broadcast packets, the address of which depends on the ip/mask encoded in pki.cert
  77. drop_local_broadcast: false
  78. # Toggles forwarding of multicast packets
  79. drop_multicast: false
  80. # Sets the transmit queue length, if you notice lots of transmit drops on the tun it may help to raise this number. Default is 500
  81. tx_queue: 500
  82. # Default MTU for every packet, safe setting is (and the default) 1300 for internet based traffic
  83. mtu: 1300
  84. # Route based MTU overrides, you have known vpn ip paths that can support larger MTUs you can increase/decrease them here
  85. routes:
  86. #- mtu: 8800
  87. # route: 10.0.0.0/16
  88. # TODO
  89. # Configure logging level
  90. logging:
  91. # panic, fatal, error, warning, info, or debug. Default is info
  92. level: info
  93. # json or text formats currently available. Default is text
  94. format: text
  95. #stats:
  96. #type: graphite
  97. #prefix: nebula
  98. #protocol: tcp
  99. #host: 127.0.0.1:9999
  100. #interval: 10s
  101. #type: prometheus
  102. #listen: 127.0.0.1:8080
  103. #path: /metrics
  104. #namespace: prometheusns
  105. #subsystem: nebula
  106. #interval: 10s
  107. # Nebula security group configuration
  108. firewall:
  109. conntrack:
  110. tcp_timeout: 120h
  111. udp_timeout: 3m
  112. default_timeout: 10m
  113. max_connections: 100000
  114. # The firewall is default deny. There is no way to write a deny rule.
  115. # Rules are comprised of a protocol, port, and one or more of host, group, or CIDR
  116. # Logical evaluation is roughly: port AND proto AND ca_sha AND ca_name AND (host OR group OR groups OR cidr)
  117. # - port: Takes `0` or `any` as any, a single number `80`, a range `200-901`, or `fragment` to match second and further fragments of fragmented packets (since there is no port available).
  118. # code: same as port but makes more sense when talking about ICMP, TODO: this is not currently implemented in a way that works, use `any`
  119. # proto: `any`, `tcp`, `udp`, or `icmp`
  120. # host: `any` or a literal hostname, ie `test-host`
  121. # group: `any` or a literal group name, ie `default-group`
  122. # groups: Same as group but accepts a list of values. Multiple values are AND'd together and a certificate would have to contain all groups to pass
  123. # cidr: a CIDR, `0.0.0.0/0` is any.
  124. # ca_name: An issuing CA name
  125. # ca_sha: An issuing CA shasum
  126. outbound:
  127. # Allow all outbound traffic from this node
  128. - port: any
  129. proto: any
  130. host: any
  131. inbound:
  132. # Allow icmp between any nebula hosts
  133. - port: any
  134. proto: icmp
  135. host: any
  136. # Allow tcp/443 from any host with BOTH laptop and home group
  137. - port: 443
  138. proto: tcp
  139. groups:
  140. - laptop
  141. - home