Hi,
I'm running Debian 9 for a few weeks and today when I, today, booted my computer I had no access to the wired internet.
As I had seen some error messages during boot I went to see what they were, and found this.

First Error Message

sh[486]: ifquery: /etc/network/interfaces:1: misplaced option
sh[486]: ifquery: couldn't read interfaces file "etc/network/interfaces"
ifup[492]: ifup: /etc/network/interfaces:1: misplaced option
ifup[492]: ifup: couldn't read interfaces file "etc/network/interfaces"
systemd[1]: networking.service: Main process kernell: r8169 0000:03.00.0:exited, code=exited, status=1/FAILURE
systemd[1]: Failed to start Raise network interfaces
systemd[1]: networking.service: Unit entered failed state
systemd[1]: networking.service: Failed with result "exit code"

Second Error Message

kernell: r8169 0000:03.00.0: firmware: failed to load rtl_nic/rtl8168e-2.fw (-2)
kernell: r8169 0000:03.00.0: Direct firmware load for rtl_nic/rtl8168e-2.fw failed with error -2
kernell: r8169 0000:03.00.0: enp3s0: unable to load firmware patch rtl_nic/rtl8168e-2.fw
kernell: r8169 0000:03.00.0: enp3s0: link down
kernell: r8169 0000:03.00.0: enp3s0: link down
kernell: IPv6: ADDRCONF (NETDEV UP): enp3s0: link is not ready
NetworkManager[530]: <warn> [1521747206.5819] Error: failed to open /run/network/ifstate
NetworkManager[530]: <info> [1521747206.5819] ModemManager available in the bus
ModemManager[536]: <info> Couldn't check support for device at "/sys/devices/pci0000:00/0000:00:05.0/0000:03:00.0" not supported by any plugin

My /etc/network/interfaces file is this:

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopack

Sorry in advance for any errors, but I wrote the error messages by hand, as I have no internet in that computer.

Thanks in advance for all the help given.

Missing firmware package?
https://unix.stackexchange.com/quest...tl8168g-3-fw-2

Do you have a way to connect this machine via a wired ethernet connection? If so, do

If not, you should be able to download the required file via another machine using something like

or via a browser

https://packages.debian.org/stretch/...altek/download

then transfer via memory stick and install the required .deb package.

1 members found this post helpful.

Thank you Ferrari for the help.

The firmware problem is solved but it musn't have been linked to the internet problem, as I, after a reboot, still don't have access to it.

Below goes a more thourough list of error messages:


sh[486]: ifquery: /etc/network/interfaces:1: misplaced option
sh[486]: ifquery: couldn't read interfaces file "etc/network/interfaces"
ifup[492]: ifup: /etc/network/interfaces:1: misplaced option
ifup[492]: ifup: couldn't read interfaces file "etc/network/interfaces"
systemd[1]: networking.service: Main process kernell: r8169 0000:03.00.0:exited, code=exited, status=1/FAILURE
systemd[1]: Failed to start Raise network interfaces
systemd[1]: networking.service: Unit entered failed stateavahi-daemon[509]: chroot.c: open() failed: No such file or directory
systemd[1]: Started Avahi mDNS/DNS-SD Stack.
avahi-daemon[504]: Failed to open /etc/resolv.conf: Invalid argument

NetworkManager[532]: <warn> [1521756175.7357] dhcp4 (enp3s0): request timed out
NetworkManager[532]: <info> [1521756175.7358] dhcp4 (enp3s0): state changed unknown -> timeout
NetworkManager[532]: <info> [1521756175.7524] dhcp4 (enp3s0): canceled DHCP transaction, DHCP client pid 1344
NetworkManager[532]: <info> [1521756175.7525] dhcp4 (enp3s0): state changed timeout -> done
NetworkManager[532]: <info> [1521756175.7532] device (enp3s0): state change: ip-config -> failed (reason 'ip-config-unavailable') [70 120 5]
NetworkManager[532]: <info> [1521756175.7536] manager: NetworkManager state is now DISCONNECTED
NetworkManager[532]: <warn> [1521756175.7563] device (enp3s0): Activation: failed for connection 'Wired connection 1'

NetworkManager[532]: <info> [1521756082.6825] settings: hostname: using hostnamed
NetworkManager[532]: <info> [1521756082.6826] settings: hostname changed from (none) to "archiso"
NetworkManager[532]: <warn> [1521756082.6831] dhcp-init: DHCP client 'dhcpcd' not available

kernel: r8169 0000:03:00.0: firmware: direct-loading firmware rtl_nic/rtl8168e-2.fw
kernel: r8169 0000:03:00.0 enp3s0: link down
kernel: r8169 0000:03:00.0 enp3s0: link down
kernel: IPv6: ADDRCONF(NETDEV_UP): enp3s0: link is not ready
NetworkManager[532]: <warn> [1521756083.3116] Error: failed to open /run/network/ifstate

NetworkManager[532]: <warn> [1521756610.7264] dhcp4 (enp3s0): request timed out
NetworkManager[532]: <info> [1521756610.7265] dhcp4 (enp3s0): state changed unknown -> timeout
NetworkManager[532]: <info> [1521756610.7430] dhcp4 (enp3s0): canceled DHCP transaction, DHCP client pid 2098
NetworkManager[532]: <info> [1521756610.7431] dhcp4 (enp3s0): state changed timeout -> done
NetworkManager[532]: <info> [1521756610.7436] device (enp3s0): state change: ip-config -> failed (reason 'ip-config-unavailable') [70 120 5]
NetworkManager[532]: <info> [1521756610.7439] manager: NetworkManager state is now DISCONNECTED
Mar 22 22:10:10 archiso NetworkManager[532]: <warn> [1521756610.7445] device (enp3s0): Activation: failed for connection 'Wired connection 1'
NetworkManager[532]: <info> [1521756610.7454] device (enp3s0): state change: failed -> disconnected (reason 'none') [120 30 0]
avahi-daemon[504]: Withdrawing address record for fe80::8d37:ee95:22ce:867f on enp3s0.
NetworkManager[532]: <info> [1521756610.7648] policy: auto-activating connection 'Wired connection 1'
avahi-daemon[504]: Leaving mDNS multicast group on interface enp3s0.IPv6 with address fe80::8d37:ee95:22ce:867f.
NetworkManager[532]: <info> [1521756610.7702] device (enp3s0): Activation: starting connection 'Wired connection 1' (babb41ed-ce86-393f-9d27-6d4a8d1cf06d)
avahi-daemon[504]: Interface enp3s0.IPv6 no longer relevant for mDNS.
NetworkManager[532]: <info> [1521756610.7851] device (enp3s0): state change: disconnected -> prepare (reason 'none') [30 40 0]
NetworkManager[532]: <info> [1521756610.7871] manager: NetworkManager state is now CONNECTING
NetworkManager[532]: <info> [1521756610.7908] device (enp3s0): state change: prepare -> config (reason 'none') [40 50 0]
NetworkManager[532]: <info> [1521756610.7927] device (enp3s0): state change: config -> ip-config (reason 'none') [50 70 0]
NetworkManager[532]: <info> [1521756610.7937] dhcp4 (enp3s0): activation: beginning transaction (timeout in 45 seconds)
NetworkManager[532]: <info> [1521756610.7977] dhcp4 (enp3s0): dhclient started with pid 2180
dhclient[2180]: DHCPDISCOVER on enp3s0 to 255.255.255.255 port 67 interval 5
avahi-daemon[504]: Joining mDNS multicast group on interface enp3s0.IPv6 with address fe80::8d37:ee95:22ce:867f.
avahi-daemon[504]: New relevant interface enp3s0.IPv6 for mDNS.
avahi-daemon[504]: Registering new address record for fe80::8d37:ee95:22ce:867f on enp3s0.*.
dhclient[2180]: DHCPDISCOVER on enp3s0 to 255.255.255.255 port 67 interval 8
dhclient[2180]: DHCPDISCOVER on enp3s0 to 255.255.255.255 port 67 interval 8
dhclient[2180]: DHCPDISCOVER on enp3s0 to 255.255.255.255 port 67 interval 9
sudo[1462]: pam_unix(sudo:session): session closed for user root
dhclient[2180]: DHCPDISCOVER on enp3s0 to 255.255.255.255 port 67 interval 10
dhclient[2180]: DHCPDISCOVER on enp3s0 to 255.255.255.255 port 67 interval 11
NetworkManager[532]: <warn> [1521756655.7266] dhcp4 (enp3s0): request timed out

Well it definitely would have contributed the problem - No firmware, no working wifi! Now wifi is working, but your NetworkManager log shows an issue with getting a DHCP address...a router restart required perhaps?

I am not on wifi, it is a cable connection.

Sorry, ignore that. However the DHCP comment still applies. Did you try restarting the router you connect to?

You're not connecting to a cable modem by chance are you? Not a PPPoE service?

If you have a PPPoE internet connection , you'll need to configure (via NM connection editor) a DSL connection instead.

I restarted the modem but it didnt change anything.
Yes, I'm using a cable modem
How can I know if I'm using a PPoE connection?

No, and that's because I had originally assumed an internet router with VDSL/ADSL type service.
Almost for sure it will be a PPPoE connection, but your service provider can confirm. Usually, you will be given authentication credentials needed to activate such a connection. Open the NetworkManager connection editor and add the required DSL connection.

1 members found this post helpful.

I found the problem.
What I am going to say I will say with red on my cheeks. It was the ethernet cable that was connected in the router to the wrong socket.
Thanks Ferrari for all the help, and I hope next time I wont waste yours or anyone's time

Glad to read of your resolution! Opportunities to get "under the hood" are always good for the learning. Glad that it was something simple anyway.