You do have two connections defined, but they are down for some reason. Within the output of these:
nmcli -f connection con show ens1f0np0
nmcli -f connection con show ens1f1np1
… should be field “autoconnect”. That field tells whether NetworkManager attempts to start connections automatically (on boot & on link).
You also have two devices (note, the nmcli device state or nmcli d s for short shows more compact version than the show).
They would not show up, if you had no driver. Without driver you see something only with lspci.
With lspci -nn there is also device ID (in brackets). The ID is precise description of the device.
connection settings autoconnect
Whether or not the connection should be automatically connected by NetworkManager when the resources for the connection are available. TRUE to automatically activate the connection, FALSE to require manual intervention to activate the connection.
ipv4 settings method
IP configuration method.
NMSettingIP4Config and NMSettingIP6Config both support “disabled”, “auto”, “manual”, and “link-local”. See the subclass-specific documentation for other values.
In general, for the “auto” method, properties such as “dns” and “routes” specify information that is added on to the information returned from automatic configuration. The “ignore-auto-routes” and “ignore-auto-dns” properties modify this behavior.
In other words:
connection.autoconnect says whether connection should start on boot, regardless of method. You want yes there
ipv4.method says how to configure IPv4 settings (auto = with DHCP, manual = static values)
The machine/port does not seem to be connected and the issue is not the IPv4 config.
What is the output of lspci -nn | grep -i net ? (The device ID that is in brackets?)
Now what I found out is that the assigned static IP cannot be pinged from the outside, which tells me that there is still something wrong in thte network configuration. Will try to investigate as much as possible…
On the contrary!
This is the solution.
The question is whether you know what is required for the network setup of this host in question.
Since you don’t say what you see and/or have set up in nmtui
Is there at least a default gateway set up?
Is there a specified DNS?
Is there a working firewall?
It is incorrect to say that you were not provided with documentation as you requested.
Please answer the question, do you know what is required and necessary for the network this host is running on.
For example: it is enough to enter a wrong mask and your host will never be accessible from outside.
For this, please help with correct information, we will also help you.
Looks like the host has trouble getting IP from DHCP. Remove the static IP and run dhclient ens1f0np0 command. If the interface no IP assigned then you need to check your LAN network for firewall or NAT issues.
Successful dhclient command will emit logs something like below output to /var/log/messages file :
messages:Jul 12 18:21:05 desktop dhclient: DHCPOFFER of 192.168.1.152 from 192.168.1.1
messages:Jul 12 18:21:05 desktop dhclient: DHCPREQUEST for 192.168.1.152 on enp4s0 to 255.255.255.255 port 67 (xid=0x26dbaa74)
messages:Jul 12 18:21:05 desktop dhclient: DHCPACK of 192.168.1.152 from 192.168.1.1 (xid=0x26dbaa74)
messages:Jul 12 18:21:07 desktop NET: /usr/sbin/dhclient-script : updated /etc/resolv.conf
messages:Jul 12 18:21:07 desktop dhclient: bound to 192.168.1.152 -- renewal in 3578 seconds.```
Let me add something for DHCP client of NetworkManager
The built-in DHCP client does not work correctly with relayed DHCP servers in to large network of ISP.
I highly recommend install dhclient - ISC DHCP
dnf install dhclient
Not forgetting to tell NetworkManager to use it.
Now I followed prasad’s advice and turned off static IP assignment. The nmtui screen displays as In the next post (I cannot post more than one attachment)
It changed nothing as far as I am concerned. However when I tried running the dhclient command like: dhclient ens1f0np0, the response was like in the second following post
I ran nmcli and this is what I saw I will post in the third post after this
Still, I cannot ping anything (both external addresses and the server itself from the outside).
Yes, theoretically the physical connection may be at fault (I will double-check it when in the office :)) but I am using a brand new cable and it is connected through a dump 4-port hub, all other ports of it work just fine…
# ip li sh dev ens7f3
5: ens7f3: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN mode DEFAULT group default qlen 1000
link/ether 00:19:99:8d:cc:aa brd ff:ff:ff:ff:ff:ff
# nmcli d show ens7f3
GENERAL.STATE: 30 (disconnected)
It has state 30 (disconnected), just like OP in one of the screenshots (but OP had carrieron).