Talk:Network Environment

From BCCD 3.0

Revision as of 02:16, 14 May 2019 by Skylar (Talk | contribs)
Jump to: navigation, search

Contents

Stages

Stage descriptions

BCCD goes through the following network configuration stages:

  1. Live mode
    1. Initial boot:
      1. Try to obtain an IP address from a BCCD DHCP server
      2. If no BCCD DHCP servers are available, obtain an IP address from any DHCP server
    2. Head node: Upon user request, start DHCP server that will answer requests only from other BCCD systems
  2. Liberated mode
    1. Initial boot:
      1. Try to obtain an IP address from a BCCD DHCP server
      2. If no BCCD DHCP servers are available, obtain an IP address from any DHCP server
    2. Diskless boot: Upon user request, start DHCP server that will answer requests from diskless BCCD systems on only a given interface

Open questions:

  1. Should we continue using bccd-identifier or switch to using the standard vendor-class-identifier that can be provided via systemd.network?
  2. Can bccd-reset-network be rewritten to produce systemd.network configuration files via templates for each stage?
  3. How do we detect that a BCCD DHCP server has not responded to a client, and obtain an address from any DHCP server?

Stage configuration

Current testing files:

[Match]
Name=eth0

[Network]
DHCP=yes
[Match]
Name=eth1

[Network]
Address=192.168.3.1/24
DHCP=no
[Match]
Name=eth0

[Network]
DHCP=yes

[DHCP]
VendorClassIdentifier=bccd-client

systemd notes

systemd commands

Restart networking 
systemctl restart systemd-networkd
Networking status 
networkctl

systemd tricks

Troubleshooting

RTNETLINK answers: File exists

If you get an error like this:

RTNETLINK answers: File exists
Failed to bring up eth1.

Try flushing that interface and replumbing it:

$ sudo ip addr flush dev eth1
Personal tools
Namespaces
Variants
Actions
Navigation
Toolbox