talos/networkd.md at b9b9aa9104c19815929b64a77a6a522f8f46baf4

mirror of https://github.com/siderolabs/talos.git synced 2025-08-19 13:41:13 +02:00

Timothy Gerla f59620473e docs: add 0.5 pre-release docs, add linkable anchors, other fixes

- add 0.5 docs branched from 0.4
- add intro page and "get help" pages
- moved Docker and Firecracker into a "Local Clusters" category
- switch to markdown-it from markd for consistency between corp site and docs site
- use markdown-it-anchor to create linkable anchors to sections within a page
- improve urls to use / instead of # for docs pages (WARNING: this breaks old links)
- continue to simplify handling in the Content.vue component
- update JS deps

Signed-off-by: Timothy Gerla <tim@gerla.net>

2020-05-04 16:04:53 -07:00

2.4 KiB

Raw Blame History

title

title
networkd

Networkd handles all of the host level network configuration. Configuration is defined under the networking key.

By default, we attempt to issue a DHCP request for every interface on the server. This can be overridden by supplying one of the following kernel arguments:

talos.network.interface.ignore - specify a list of interfaces to skip discovery on
ip - ip=<client-ip>:<server-ip>:<gw-ip>:<netmask>:<hostname>:<device>:<autoconf>:<dns0-ip>:<dns1-ip>:<ntp0-ip> as documented in the kernel here
- ex, ip=10.0.0.99:::255.0.0.0:control-1:eth0:off:10.0.0.1

Examples

Documentation for the network section components can be found under the configuration reference.

Static Addressing

Static addressing is comprised of specifying cidr, routes ( remember to add your default gateway ), and interface. Most likely you'll also want to define the nameservers so you have properly functioning DNS.

machine:
  network:
    hostname: talos
    nameservers:
    - 10.0.0.1
    time:
      servers:
        - time.cloudflare.com
    interfaces:
    - interface: eth0
      cidr: 10.0.0.201/8
      mtu: 8765
      routes:
        - network: 0.0.0.0/0
          gateway: 10.0.0.1
    - interface: eth1
      ignore: true

Additional Addresses for an Interface

In some environments you may need to set additional addresses on an interface. In the following example, we set two additional addresses on the loopback interface.

machine:
  network:
    interfaces:
    - interface: lo0
      cidr: 192.168.0.21/24
    - interface: lo0
      cidr: 10.2.2.2/24

Bonding

The following example shows how to create a bonded interface.

machine:
  network:
    interfaces:
    - interface: bond0
      dhcp: true
      bond:
        mode: 802.3ad
        lacprate: fast
        hashpolicy: layer3+4
        miimon: 100
        updelay: 200
        downdelay: 200
        interfaces:
        - eth0
        - eth1

VLANs

To setup vlans on a specific device use an array of VLANs to add. The master device may be configured without addressing by setting dhcp to false.

machine:
  network:
    interfaces:
    - interface: eth0
      dhcp: false
      vlans:
      - vlanId: 100
        cidr: "192.168.2.10/28"
        routes:
        - network: 0.0.0.0/0
          gateway: 192.168.2.1

2.4 KiB Raw Blame History