23.7. Setting the Hostname
Figure 23.23. Setting the hostname
23.7.1. Editing Network Connections
system-config-networkcommand in a shell prompt to launch the Network Administration Tool. If you are not root, it prompts you for the root password to continue.
Figure 23.24. Network Connections
eth0(OSA, LCS), or
hsi0(HiperSockets). Note that on System z you cannot add a new connection here. To modify an existing connection, select a row in the list and click the Edit button. A dialog box appears with a set of tabs appropriate to wired connections, as described below.
18.104.22.168. Options common to all types of connection
22.214.171.124. The Wired tab
Figure 23.25. The Wired tab
126.96.36.199. The 802.1x Security tab
- Choose one of the following methods of authentication:
- TLS for Transport Layer Security
- Tunneled TLS for Tunneled Transport Layer Security, otherwise known as TTLS, or EAP-TTLS
- Protected EAP (PEAP) for Protected Extensible Authentication Protocol
- Provide the identity of this server.
- User certificate
- Browse to a personal X.509 certificate file encoded with Distinguished Encoding Rules (DER) or Privacy Enhanced Mail (PEM).
- CA certificate
- Browse to a X.509 certificate authority certificate file encoded with Distinguished Encoding Rules (DER) or Privacy Enhanced Mail (PEM).
- Private key
- Browse to a private key file encoded with Distinguished Encoding Rules (DER), Privacy Enhanced Mail (PEM), or the Personal Information Exchange Syntax Standard (PKCS#12).
- Private key password
- The password for the private key specified in the Private key field. Select Show password to make the password visible as you type it.
Figure 23.26. The 802.1x Security tab
188.8.131.52. The IPv4 Settings tab
SEARCHDNS(Refer to Section 26.3, “Installation Network Parameters”).
- Automatic (DHCP)
- IPv4 parameters are configured by the DHCP service on the network.
- Automatic (DHCP) addresses only
- The IPv4 address, netmask, and gateway address are configured by the DHCP service on the network, but DNS servers and search domains must be configured manually.
- IPv4 parameters are configured manually for a static configuration.
- Link-Local Only
- A link-local address in the 169.254/16 range is assigned to the interface.
- Shared to other computers
- The system is configured to provide network access to other computers. The interface is assigned an address in the 10.42.x.1/24 range, a DHCP server and DNS server are started, and the interface is connected to the default network connection on the system with network address translation (NAT).
- IPv4 is disabled for this connection.
Figure 23.27. The IPv4 Settings tab
184.108.40.206.1. Editing IPv4 routes
Figure 23.28. The Editing IPv4 Routes dialog
220.127.116.11. The IPv6 Settings tab
- IPv6 is ignored for this connection.
- NetworkManager uses router advertisement (RA) to create an automatic, stateless configuration.
- Automatic, addresses only
- NetworkManager uses RA to create an automatic, stateless configuration, but DNS servers and search domains are ignored and must be configured manually.
- Automatic, DHCP only
- NetworkManager does not use RA, but requests information from DHCPv6 directly to create a stateful configuration.
- IPv6 parameters are configured manually for a static configuration.
- Link-Local Only
- A link-local address with the fe80::/10 prefix is assigned to the interface.
Figure 23.29. The IPv6 Settings tab
18.104.22.168.1. Editing IPv6 routes
Figure 23.30. The Editing IPv6 Routes dialog
22.214.171.124. Restart a network device
ONBOOT=yesis set. Refer to the Red Hat Enterprise Linux 6.9 Deployment Guide available from https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/index.html for more information about interface configuration files.
- Press Ctrl+Alt+F2 to switch to virtual terminal
- Move the interface configuration file to a temporary location:
mv /etc/sysconfig/network-scripts/ifcfg-device_name /tmpwhere device_name is the device that you just reconfigured. For example,
ifcfg-eth0is the ifcfg file for
eth0.The device is now disconnected in anaconda.
- Open the interface configuration file in the vi editor:
- Verify that the interface configuration file contains the line
ONBOOT=yes. If the file does not already contain the line, add it now and save the file.
- Exit the vi editor.
- Move the interface configuration file back to the
mv /tmp/ifcfg-device_name /etc/sysconfig/network-scripts/The device is now reconnected in anaconda.
- Press Ctrl+Alt+F6 to return to anaconda.