You are not logged in.

#1 2022-01-17 09:45:56

Marvix
Member
Registered: 2013-10-08
Posts: 146

[SOLVED] Network Manager can't connect to wired connection

I can't connect to wired connection.

Only wireless connection works fine.

All it started three days ago when I was trying to set wired connection with VPN to auto-connect on login, and not have manually select it.

I used to use the dnsmasq DNS resolver, which I uninstalled it and stopped all connections.

I manage and use the network connections through Network Manager and `nm-editor` .

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp1s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT group default qlen 1000
    link/ether ***** brd ff:ff:ff:ff:ff:ff
3: wlp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP mode DORMANT group default qlen 1000
    link/ether ***** brd ff:ff:ff:ff:ff:ff
6: tun0: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UNKNOWN mode DEFAULT group default qlen 500
    link/none 
nmcli general

STATE      CONNECTIVITY  WIFI-HW  WIFI     WWAN-HW  WWAN    
connected  full          enabled  enabled  enabled  enabled 
systemctl --list-unit-files --state=enabled

UNIT FILE                          STATE   VENDOR PRESET
cups.path                          enabled disabled     
cronie.service                     enabled disabled     
cups.service                       enabled disabled     
getty@.service                     enabled enabled      
NetworkManager-dispatcher.service  enabled disabled     
NetworkManager-wait-online.service enabled disabled     
NetworkManager.service             enabled disabled     
ntpd.service                       enabled disabled     
systemd-timesyncd.service          enabled enabled      
cups.socket                        enabled disabled     
remote-fs.target                   enabled enabled 
# /etc/resolv.conf
# Latest update: 2022-01-17

nameserver 91.239.100.100
systemctl status NetworkManager
● NetworkManager.service - Network Manager
     Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled; vendor preset: disabled)
    Drop-In: /usr/lib/systemd/system/NetworkManager.service.d
             └─NetworkManager-ovs.conf
     Active: active (running) since Mon 2022-01-17 11:12:12 EET; 51min ago
       Docs: man:NetworkManager(8)
   Main PID: 3816 (NetworkManager)
      Tasks: 3 (limit: 4526)
     Memory: 4.2M
        CPU: 1.785s
     CGroup: /system.slice/NetworkManager.service
             └─3816 /usr/bin/NetworkManager --no-daemon

Jan 17 12:03:13 archie NetworkManager[3816]: <info>  [1642413793.8592] dhcp4 (enp1s0): activation: beginning transaction (timeout in 45 seconds)
Jan 17 12:03:58 archie NetworkManager[3816]: <warn>  [1642413838.7283] dhcp4 (enp1s0): request timed out
Jan 17 12:03:58 archie NetworkManager[3816]: <info>  [1642413838.7283] dhcp4 (enp1s0): state changed unknown -> timeout
Jan 17 12:03:58 archie NetworkManager[3816]: <info>  [1642413838.7284] device (enp1s0): state change: ip-config -> failed (reason 'ip-config-unavailable', sys-iface-state: 'managed')
Jan 17 12:03:58 archie NetworkManager[3816]: <info>  [1642413838.7292] manager: NetworkManager state is now DISCONNECTED
Jan 17 12:03:58 archie NetworkManager[3816]: <warn>  [1642413838.7298] device (enp1s0): Activation: failed for connection 'Wired - Unsafe'
Jan 17 12:03:58 archie NetworkManager[3816]: <info>  [1642413838.7303] device (enp1s0): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
Jan 17 12:03:58 archie NetworkManager[3816]: <info>  [1642413838.7483] dhcp4 (enp1s0): canceled DHCP transaction
Jan 17 12:03:58 archie NetworkManager[3816]: <info>  [1642413838.7484] dhcp4 (enp1s0): state changed timeout -> terminated
Jan 17 12:03:58 archie NetworkManager[3816]: <info>  [1642413838.7501] device (enp1s0): set-hw-addr: reset MAC address to ****** (deactivate)

---

Edit: All it was from the modem-router. I reset it and now I'm back to where I was before, where I wanted to.

Last edited by Marvix (2022-01-17 21:44:47)

Offline

#2 2022-01-17 11:53:20

-thc
Member
Registered: 2017-03-15
Posts: 485

Re: [SOLVED] Network Manager can't connect to wired connection

The (error) messages from NM are unambiguous: No DHCP server answers to the DHCP request from your ethernet port.

Under my circumstances (german) those symptoms point to the cable connection and/or the router.

Because your DNS server is in Denmark this probably means you are too. At least some danish ISPs provide ISP-based DHCP - you just plug your machine into the ISP wall socket and start surfing.

Either way - the connectivity between your ethernet port and the DHCP server is broken.

I would boot your machine from an Arch installation media - if the wired connection works your Arch network setup is broken.

Offline

#3 2022-01-17 19:17:14

HalosGhost
Forum Moderator
From: Twin Cities, MN
Registered: 2012-06-22
Posts: 2,089
Website

Re: [SOLVED] Network Manager can't connect to wired connection

A post from Marvix was deleted from this thread at their request.

All the best,

-HG

Offline

#4 2022-01-17 19:20:17

Marvix
Member
Registered: 2013-10-08
Posts: 146

Re: [SOLVED] Network Manager can't connect to wired connection

-thc wrote:

The (error) messages from NM are unambiguous: No DHCP server answers to the DHCP request from your ethernet port.

Under my circumstances (german) those symptoms point to the cable connection and/or the router.

Will I need to reconfigure my router?

-thc wrote:

Because your DNS server is in Denmark this probably means you are too. At least some danish ISPs provide ISP-based DHCP - you just plug your machine into the ISP wall socket and start surfing.

No, I'm from Greece, and I don't trust and also I'm not satisfied with ISP's DNS providers, so I use a few from a list I collected.

-thc wrote:

Either way - the connectivity between your ethernet port and the DHCP server is broken.

I would boot your machine from an Arch installation media - if the wired connection works your Arch network setup is broken.

You mean to use the arch-chroot? And if yes, then what to do next?

Offline

#5 2022-01-17 19:25:15

-thc
Member
Registered: 2017-03-15
Posts: 485

Re: [SOLVED] Network Manager can't connect to wired connection

No - you don't need to use arch-chroot.

Just plug in the network cable and boot the Arch installation ISO or Pendrive.

At the prompt try to ping "www.google.com" or "8.8.8.8".

Offline

#6 2022-01-17 19:46:13

Marvix
Member
Registered: 2013-10-08
Posts: 146

Re: [SOLVED] Network Manager can't connect to wired connection

Oh, yes, I've already done it, and returns "Temporary failure in name resolution".

ping -c example.com
ping: example.com: Temporary failure in name resolution

Last edited by Marvix (2022-01-17 20:11:24)

Offline

#7 2022-01-17 21:46:26

Marvix
Member
Registered: 2013-10-08
Posts: 146

Re: [SOLVED] Network Manager can't connect to wired connection

All it was from the modem-router. I reset it and everything are solved. Thank you for everything.

Offline

Board footer

Powered by FluxBB