| Line 32: | Line 32: | ||
[Network] | [Network] | ||
DHCP=yes | DHCP=yes | ||
</pre> | |||
===Static address on a single interface=== | |||
For an interface <code>eth0</code>, a single <code>.network</code> file is needed: | |||
<pre> | |||
# cat /etc/systemd/network/eth0.network | |||
[Match] | |||
Name=eth0 | |||
[Network] | |||
Address=192.168.0.50/24 | |||
Address=2001:db8:dead:beef::/64 | |||
# These are optional but worth mentioning | |||
DNS=8.8.8.8 | |||
DNS=8.8.4.4 | |||
NTP=pool.ntp.org | |||
</pre> | |||
You can also split up the addresses into separate blocks: | |||
<pre> | |||
# cat /etc/systemd/network/eth0.network | |||
[Match] | |||
Name=eth0 | |||
[Network] | |||
DNS=8.8.8.8 | |||
DNS=8.8.4.4 | |||
NTP=pool.ntp.org | |||
[Address] | |||
Address=192.168.0.50/24 | |||
[Address] | |||
Address=2001:db8:dead:beef::/64 | |||
</pre> | |||
Or add static routes: | |||
<pre> | |||
# cat /etc/systemd/network/eth0.network | |||
[Match] | |||
Name=eth0 | |||
[Network] | |||
DNS=8.8.8.8 | |||
DNS=8.8.4.4 | |||
NTP=pool.ntp.org | |||
[Address] | |||
Address=192.168.0.50/24 | |||
[Address] | |||
Address=2001:db8:dead:beef::/64 | |||
[Route] | |||
Destination=10.0.10.0/24 | |||
Gateway=192.168.50.1 | |||
[Route] | |||
Destination=10.0.20.0/24 | |||
Gateway=192.168.50.1 | |||
</pre> | </pre> | ||
Revision as of 02:25, 29 September 2015
This is a placeholder page for the discussion of what the Cloud image (Base at first, Atomic to follow) requires from a networking stack on it's images.
- configure DHCP, renew dhcp leases
- configure with cloud-init
- configure with traditional RH-ecosystem ifcfg-eth0 file (log warnings for unsupported options)
Questions!
- Q: any need to support more than one interface? - Q: if single interface, should we standardize on "eth0"" - Q: dns configuration? - Q: support static IP (via cloud-init?)
Several use cases in EC2 involve instances with multiple network interfaces and occasionally multiple addresses on a single interface. I do not believe all of those need to be configured automatically, but it ought to remain possible for a user/script/etc to make network configuration changes that persist across reboots.
.png){kind=small}
mhayden is doing some rambling on systemd-networkd here since maxamillion asked so nicely.
systemd-networkd use cases
Here are some sample use cases for systemd-networkd and example configurations.
Simple DHCP on a single interface
For an interface eth0, a single .network file is needed:
# cat /etc/systemd/network/eth0.network [Match] Name=eth0 [Network] DHCP=yes
Static address on a single interface
For an interface eth0, a single .network file is needed:
# cat /etc/systemd/network/eth0.network [Match] Name=eth0 [Network] Address=192.168.0.50/24 Address=2001:db8:dead:beef::/64 # These are optional but worth mentioning DNS=8.8.8.8 DNS=8.8.4.4 NTP=pool.ntp.org
You can also split up the addresses into separate blocks:
# cat /etc/systemd/network/eth0.network [Match] Name=eth0 [Network] DNS=8.8.8.8 DNS=8.8.4.4 NTP=pool.ntp.org [Address] Address=192.168.0.50/24 [Address] Address=2001:db8:dead:beef::/64
Or add static routes:
# cat /etc/systemd/network/eth0.network [Match] Name=eth0 [Network] DNS=8.8.8.8 DNS=8.8.4.4 NTP=pool.ntp.org [Address] Address=192.168.0.50/24 [Address] Address=2001:db8:dead:beef::/64 [Route] Destination=10.0.10.0/24 Gateway=192.168.50.1 [Route] Destination=10.0.20.0/24 Gateway=192.168.50.1