# Configuring an Ethernet connection by using control-center

<div class="center top initialized" id="bkmrk-copy-link" style="--_floating-content-translate: -22.46668243408203px -73px;"><div id="bkmrk-"><div aria-hidden="true" class=" ui " id="bkmrk--1"></div></div><div class=" dark " id="bkmrk-copy-link-1" role="status"><div class="section-link tooltip-content" slot="content"><span class="copy-link-text">Copy link</span></div></div></div>
If you connect a host to the network over Ethernet, you can manage the connection’s settings with a graphical interface by using the GNOME Settings menu.

Note that `control-center` does not support as many configuration options as the `nmcli` utility.

**Prerequisites**

<div class="itemizedlist" id="bkmrk-a-physical-or-virtua">- A physical or virtual Ethernet Network Interface Controller (NIC) exists in the server’s configuration.
- GNOME is installed.

</div>**Procedure**

<div class="orderedlist" id="bkmrk-press-the-super-key%2C">1. Press the <kbd class="keycap">Super</kbd> key, enter `Settings`, and press <kbd class="keycap">Enter</kbd>.
2. Select <span class="strong strong">**Network**</span> in the navigation on the left.
3. Choose whether to add a new connection profile or to modify an existing one:
    
    <div class="itemizedlist">
    - To create a new profile, click the <span class="guibutton">+</span> button next to the <span class="strong strong">**Ethernet**</span> entry.
    - To modify an existing profile, click the gear icon next to the profile entry.
    
    </div>
4. Optional: On the <span class="strong strong">**Identity**</span> tab, update the name of the connection profile.
    
    On hosts with multiple profiles, a meaningful name makes it easier to identify the purpose of a profile.
5. Depending on your environment, configure the IP address settings on the <span class="strong strong">**IPv4**</span> and <span class="strong strong">**IPv6**</span> tabs accordingly:
    
    <div class="itemizedlist">
    - To use DHCP or IPv6 stateless address autoconfiguration (SLAAC), select `Automatic (DHCP)` as method (default).
    - To set a static IP address, network mask, default gateway, DNS servers, and search domain, select `Manual` as method, and fill the fields on the tabs:
        
        <div class="informalfigure"><div class="mediaobject"><div class="image-block">[ ![Static IP address settings in `control-center`](https://access.redhat.com/webassets/avalon/d/Red_Hat_Enterprise_Linux-10-Configuring_and_managing_networking-en-US/images/b59bc0170ee2d2d60b426af3bc1b4d07/IP-settings-gnome-settings.png) ](https://access.redhat.com/webassets/avalon/d/Red_Hat_Enterprise_Linux-10-Configuring_and_managing_networking-en-US/images/b59bc0170ee2d2d60b426af3bc1b4d07/IP-settings-gnome-settings.png "Static IP address settings in `control-center`")</div></div></div>
    
    </div>
6. Depending on whether you add or modify a connection profile, click the <span class="guibutton">Add</span> or <span class="guibutton">Apply</span> button to save the connection.
    
    The GNOME `control-center` automatically activates the connection.

</div>**Verification**

<div class="orderedlist" id="bkmrk-display-the-ip-setti">1. Display the IP settings of the NIC:
    
    <div class="content-code-block-container" data-wrap-available="true"><div class="expandable truncated" style="column-gap: 50px;"><div tabindex="0"><div aria-hidden="true" id="bkmrk--4"></div></div></div></div>```plaintext
    # <strong>ip address show enp1s0</strong>
    2: enp1s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
        link/ether 52:54:00:17:b8:b6 brd ff:ff:ff:ff:ff:ff
        inet 192.0.2.1/24 brd 192.0.2.255 scope global noprefixroute enp1s0
           valid_lft forever preferred_lft forever
        inet6 2001:db8:1::fffe/64 scope global noprefixroute
           valid_lft forever preferred_lft forever
    ```
    
    <div class="content-code-block-container" data-wrap-available="true"><div class="expandable truncated" id="bkmrk--5" style="column-gap: 50px;"><div id="bkmrk--6" tabindex="0"></div><div id="bkmrk--7"></div></div><div class="content-code-block-container-actions"><div class=" center " id="bkmrk--8"><div id="bkmrk--9"></div></div><div class=" center " id="bkmrk--10"><div id="bkmrk--11"></div></div></div></div>
2. Display the IPv4 default gateway:
    
    <div class="content-code-block-container"><div class="  " style="column-gap: 50px;"><div tabindex="0"><div aria-hidden="true" id="bkmrk--12"></div></div></div></div>```plaintext
    # <strong>ip route show default</strong>
    default via 192.0.2.254 dev enp1s0 proto static metric 102
    ```
    
    <div class="content-code-block-container"><div class="  " id="bkmrk--13" style="column-gap: 50px;"><div id="bkmrk--14" tabindex="0"></div><div id="bkmrk--15"></div></div><div class="content-code-block-container-actions"><div class=" center " id="bkmrk--16"><div id="bkmrk--17"></div></div></div></div>
3. Display the IPv6 default gateway:
    
    <div class="content-code-block-container"><div class="  " style="column-gap: 50px;"><div tabindex="0"><div aria-hidden="true" id="bkmrk--18"></div></div></div></div>```plaintext
    # <strong>ip -6 route show default</strong>
    default via 2001:db8:1::fffe dev enp1s0 proto static metric 102 pref medium
    ```
    
    <div class="content-code-block-container"><div class="  " id="bkmrk--19" style="column-gap: 50px;"><div id="bkmrk--20" tabindex="0"></div><div id="bkmrk--21"></div></div><div class="content-code-block-container-actions"><div class=" center " id="bkmrk--22"><div id="bkmrk--23"></div></div></div></div>
4. Display the DNS settings:
    
    <div class="content-code-block-container"><div class="expandable truncated" style="column-gap: 50px;"><div tabindex="0"><div aria-hidden="true" id="bkmrk--24"></div></div></div></div>```plaintext
    # <strong>cat /etc/resolv.conf</strong>
    search example.com
    nameserver 192.0.2.200
    nameserver 2001:db8:1::ffbb
    ```
    
    <div class="content-code-block-container"><div class="expandable truncated" id="bkmrk--25" style="column-gap: 50px;"><div id="bkmrk--26" tabindex="0"></div><div id="bkmrk--27"></div></div><div class="content-code-block-container-actions"><div class=" center " id="bkmrk--28"><div id="bkmrk--29"></div></div></div></div>If multiple connection profiles are active at the same time, the order of `nameserver` entries depend on the DNS priority values in these profiles and the connection types.
5. Use the `ping` utility to verify that this host can send packets to other hosts:
    
    <div class="content-code-block-container"><div class="  " style="column-gap: 50px;"><div tabindex="0"><div aria-hidden="true" id="bkmrk--30"></div></div></div></div>```plaintext
    # <strong>ping <em><host-name-or-IP-address></em></strong>
    ```
    
    <div class="content-code-block-container"><div class="  " id="bkmrk--31" style="column-gap: 50px;"><div id="bkmrk--32" tabindex="0"></div><div id="bkmrk--33"></div></div><div class="content-code-block-container-actions"><div class=" center " id="bkmrk--34"><div id="bkmrk--35"></div></div></div></div>

</div>**Troubleshooting steps**

<div class="itemizedlist" id="bkmrk-verify-that-the-netw">- Verify that the network cable is plugged-in to the host and a switch.
- Check whether the link failure exists only on this host or also on other hosts connected to the same switch.
- Verify that the network cable and the network interface are working as expected. Perform hardware diagnosis steps and replace defective cables and network interface cards.
- If the configuration on the disk does not match the configuration on the device, starting or restarting NetworkManager creates an in-memory connection that reflects the configuration of the device. For further details and how to avoid this problem, see the Red Hat Knowledgebase solution [NetworkManager duplicates a connection after restart of NetworkManager service](https://access.redhat.com/solutions/3068421).

</div>