Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

pages/static-ip-config: reorganize and delete some obsolete information #111

Merged
merged 3 commits into from
Jul 27, 2020
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 4 additions & 15 deletions modules/ROOT/pages/static-ip-config.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,9 @@ By default, an FCOS instance will attempt to grab a DHCP address from the local

As with any custom configuration on FCOS, you can write specific files in the xref:ign-storage.adoc[`storage` node] of the Ignition file.

The following snippet shows how to assign the following to enp1s0:
The following snippet shows how to assign a static configuration to `enp1s0`:

NOTE: FCOS uses https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/[predictable interface names] by https://lists.fedoraproject.org/archives/list/[email protected]/thread/6IPTZL57Z5NLBMPYMXNVSYAGLRFZBLIP/[default]. Please take care to use the correct interface name for your hardware.

* static IP: `192.0.2.10/24`
* gateway: `192.0.2.1`
Expand Down Expand Up @@ -38,17 +40,4 @@ storage:
dns=192.168.124.1;1.1.1.1;8.8.8.8
dns-search=redhat.com
----
NOTE: During the initramfs portion of the boot process, dracut will attempt to grab a DHCP address. When it times out, Ignition will take over and write the above configuration into the filesystem.

If the interface does not come up correctly on first boot (see https://github.com/coreos/fedora-coreos-tracker/issues/358[tracker issue 358]), you have two possible workarounds.

. If you configured a username and password in your Ignition configuration, you can log in to the
host via the console and issue the following commands to force the static IP to take effect:

nmcli connection down enp1s0
nmcli connection up enp1s0

. If you are not able to access the host via the console, you can reboot the host and the static IP configuration will take effect.

Also, interfaces should be named based on the `predictable interface names`, if a user try to configure an interface using for intance `eth0` this change might not be taken into account.
Additional parameters can be found in the https://developer.gnome.org/NetworkManager/stable/settings-connection.html[NetworkManager] documentation.
NOTE: Additional parameters for NetworkManager key files can be found in the https://developer.gnome.org/NetworkManager/stable/settings-connection.html[NetworkManager documentation].