From BCCD 3.0

Revision as of 02:00, 14 May 2019 (view source) Skylar (Talk | contribs) (→Stage configuration) ← Older edit		Revision as of 02:12, 14 May 2019 (view source) Skylar (Talk | contribs) m (→Stage configuration) Newer edit →
Line 28:		Line 28:
	* Head node		* Head node
	** <code>/etc/systemd/network/10-dhcp-eth0.network</code>		** <code>/etc/systemd/network/10-dhcp-eth0.network</code>
-	<verbatim>	+	<pre>
	[Match]		[Match]
	Name=eth0		Name=eth0
Line 34:		Line 34:
	[Network]		[Network]
	DHCP=yes		DHCP=yes
-	</verbatim>	+	</pre>
	** <code>/etc/systemd/network/20-static-eth1.network</code>		** <code>/etc/systemd/network/20-static-eth1.network</code>
	<pre>		<pre>

---

Revision as of 02:12, 14 May 2019

Contents 1 Stages 1.1 Stage descriptions 1.2 Stage configuration 2 systemd notes 2.1 systemd commands 2.2 systemd tricks 3 Troubleshooting 3.1 RTNETLINK answers: File exists

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:

• Head node
  • /etc/systemd/network/10-dhcp-eth0.network

[Match]
Name=eth0

[Network]
DHCP=yes

• • /etc/systemd/network/20-static-eth1.network

[Match]
Name=eth1

[Network]
Address=192.168.3.1/24
DHCP=no

systemd notes

systemd commands

Restart networking 

systemctl restart systemd-networkd

Networking status 

networkctl

systemd tricks

• Move /etc/network/interfaces out of the way to ensure that regular network setup doesn't occur
• Interface files need to have a numeric prefix and a .network suffix (i.e. /etc/systemd/network/10-static-eth0.network

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