Initializing network after system installation

In the screenshot shown with the static addresses, why is auto connect not enabled?

What works and what doesn’t?
Is routing, forwarding checked?
Is the firewall stopped?

cat /etc/NetworkManager/conf.d/dhcp-client.conf

For comparison, this port has no cable on it:

# 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
    altname enp2s0f3

# nmcli d show ens7f3
GENERAL.DEVICE:                         ens7f3
GENERAL.TYPE:                           ethernet
GENERAL.HWADDR:                         00:19:99:8D:CC:AA
GENERAL.MTU:                            1500
GENERAL.STATE:                          30 (disconnected)
GENERAL.CONNECTION:                     --
GENERAL.CON-PATH:                       --
WIRED-PROPERTIES.CARRIER:               off
IP4.GATEWAY:                            --
IP6.GATEWAY:                            --

It has state 30 (disconnected), just like OP in one of the screenshots (but OP had carrier on).

Hi Xino and jlehtone,
Thanks for response! Here is the thing.

  1. It seems like therefis no dhcp-client.conf file in the /etc/NetworkManager/conf.d - in fact this directory is empty :frowning:
  2. The screenshot with the responses to the suggested checks is presented below (note that the device state is 100 (connected)

    Best regards,
    Mike F.

Hi,

And which client does the connectivity then?

journalctl -b | grep -i error
journalctl -b | grep -i dhclient

What works and what doesn’t?
Is routing, forwarding checked?
Is the firewall stopped?

arp -a | grep “192.168.0.18”

Let me answer the questions so that the problem can be solved, please!
I don’t want to force the words out of your mouth!
If you’re uncomfortable answering the questions, do a clean install again.

If there is link, then what drops the packets?
What else could we query about the system?

# Any other machines seen by this machine:
arp
# or
ip neigh

# Information about the interface:
ethtool ens1f0np0
ethtool -i ens1f0np0

# Link statistics
ip -s ad

Hello Xino and jheltone, I am really sorry to sound incomplete and confusing: it is because this is my first-time experience with Linux, and that is why every step draws blood from me :frowning: - and there is no one around I could have possibly ask for help.
As of now I created the dhcp-client.conf file according to the link provided by Xino (thank you!) and then restarted NetworkManager. It seems like nothing changed. I judge by the fact I still cannot ping anything outside. Looking into the logs I can see that there is nothing received via the ens1f0np0, despite that there were a lot of sent packages.
I compiled the “combined” screenshot made of the responses to all commands you recommended to me:


Therefore it seems like the configuration matches the requirements, the physical layer is functional (I connected my laptop to the same cable I insert into the Linux server - and it connected to the network no problem), DHCP seems to be enabled - but it failes obtaining the lease and therefore, to establish connection. What can be the reason for that?

Thank you for your time and input,
Mike F.

systemctl status firewalld.service

systemctl stop firewalld.service

systemctl disable firewalld.service

systemctl mask firewalld.service

reboot

Status ?

The ip -s ad shows a massive amount of receive errors on both ports of the Broadcom card.
I can’t tell whether that is a driver or hardware issue.

Hello Xino,

I followed your recommendations and have the firewall service disabled. However this did not help. Moreover, upon rebooting the interface could not even formally get activated. When I switched back to the manual network configuration and hence the static IP, the connection activation showed successful - but I still observe thousands of receive errors and cannot ping anything outside…
Best regards,
Mike F.

Hello jheltone, actually the second Ethernet port stays disconnected and I do not even pay attention at the related information. For the first port - yes, there are lots of errors, and I do not know how to test (reinstall?) driver or how to test the network hardware. Would it be possible?
Thank you,
Mike F.