Unable to connect to internet after enabling wake on lan on Debian 9












0















I've enabled Wake-On-Lan on my debian machine with this tutorial. I didn't have the option to try it out or reboot, and went to sleep. The next day, a power surge happened, and rebooted my computer, for the first time in 15 days.



After that, I didn't have any connection on my computer.



I started to troubleshoot :




  • Rebooted the computer.

  • Rebooted the router.

  • Changed the Ethernet cable.

  • Tried to connected via Wi-Fi with a USB key ( Edimax EW-7811Un )

  • Tried to connect via connection sharing from my Android Phone.

  • Connected the same cable and router to another computer running Ubuntu 18.04, and it worked with no issues. So the issue must be coming from my computer.


That didn't change anything. I looked up the Arch Linux wiki ( props btw, it's really nice. ) and suggested to check my Network Manager config.



I linked the output of /var/log/messages, and diverse config files here :



https://0bin.net/paste/Jcp8j30r6NXBS95K#rPQVHP5oFqdWLyO51F-keBGlRwtSSn7wDD2bh4Tv9U7



And more ...



I set the nameserver of the /etc/resolv.conf to nameserver 8.8.8.8 for testing, but it didn't change anything. I also tried with FDN's DNS



When I remove the comments of the /etc/network/interfaces file, and setup the connection by hand, it doesn't change anything, I'm still unable to connect to anything.



I also tried connecting to a IPv6 directly, as well as an IPv4 address.



I also tried to boot on a Ubuntu 18.10 live usb, which worked, but didn't yield anything.
I also tried to boot on a Debian 9 live USB in rescue mode, which worked, but didn't yield anything.



PINGing localhost works, but not LAN computers or others.



I also tried to install the r8168-dkms-8.043.02-1_all.deb package from the Debian repo with dpkg and a USB key, and rebooted. Many times. Sadly.



I've also followed the advice found on the Arch Linux forum about Realtek no link / WOL problem. And tried to activate and deactivate several times the Intel Virtualization Technology. I even updated the BIOS to it's last version ( dated 2014 ).










share|improve this question









New contributor




N07070 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.





















  • It feels like this is missing a critical number of details.  Can you ping your router? If not, stuff like changing nameservers has no chance of having any effect.

    – G-Man
    31 mins ago
















0















I've enabled Wake-On-Lan on my debian machine with this tutorial. I didn't have the option to try it out or reboot, and went to sleep. The next day, a power surge happened, and rebooted my computer, for the first time in 15 days.



After that, I didn't have any connection on my computer.



I started to troubleshoot :




  • Rebooted the computer.

  • Rebooted the router.

  • Changed the Ethernet cable.

  • Tried to connected via Wi-Fi with a USB key ( Edimax EW-7811Un )

  • Tried to connect via connection sharing from my Android Phone.

  • Connected the same cable and router to another computer running Ubuntu 18.04, and it worked with no issues. So the issue must be coming from my computer.


That didn't change anything. I looked up the Arch Linux wiki ( props btw, it's really nice. ) and suggested to check my Network Manager config.



I linked the output of /var/log/messages, and diverse config files here :



https://0bin.net/paste/Jcp8j30r6NXBS95K#rPQVHP5oFqdWLyO51F-keBGlRwtSSn7wDD2bh4Tv9U7



And more ...



I set the nameserver of the /etc/resolv.conf to nameserver 8.8.8.8 for testing, but it didn't change anything. I also tried with FDN's DNS



When I remove the comments of the /etc/network/interfaces file, and setup the connection by hand, it doesn't change anything, I'm still unable to connect to anything.



I also tried connecting to a IPv6 directly, as well as an IPv4 address.



I also tried to boot on a Ubuntu 18.10 live usb, which worked, but didn't yield anything.
I also tried to boot on a Debian 9 live USB in rescue mode, which worked, but didn't yield anything.



PINGing localhost works, but not LAN computers or others.



I also tried to install the r8168-dkms-8.043.02-1_all.deb package from the Debian repo with dpkg and a USB key, and rebooted. Many times. Sadly.



I've also followed the advice found on the Arch Linux forum about Realtek no link / WOL problem. And tried to activate and deactivate several times the Intel Virtualization Technology. I even updated the BIOS to it's last version ( dated 2014 ).










share|improve this question









New contributor




N07070 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.





















  • It feels like this is missing a critical number of details.  Can you ping your router? If not, stuff like changing nameservers has no chance of having any effect.

    – G-Man
    31 mins ago














0












0








0








I've enabled Wake-On-Lan on my debian machine with this tutorial. I didn't have the option to try it out or reboot, and went to sleep. The next day, a power surge happened, and rebooted my computer, for the first time in 15 days.



After that, I didn't have any connection on my computer.



I started to troubleshoot :




  • Rebooted the computer.

  • Rebooted the router.

  • Changed the Ethernet cable.

  • Tried to connected via Wi-Fi with a USB key ( Edimax EW-7811Un )

  • Tried to connect via connection sharing from my Android Phone.

  • Connected the same cable and router to another computer running Ubuntu 18.04, and it worked with no issues. So the issue must be coming from my computer.


That didn't change anything. I looked up the Arch Linux wiki ( props btw, it's really nice. ) and suggested to check my Network Manager config.



I linked the output of /var/log/messages, and diverse config files here :



https://0bin.net/paste/Jcp8j30r6NXBS95K#rPQVHP5oFqdWLyO51F-keBGlRwtSSn7wDD2bh4Tv9U7



And more ...



I set the nameserver of the /etc/resolv.conf to nameserver 8.8.8.8 for testing, but it didn't change anything. I also tried with FDN's DNS



When I remove the comments of the /etc/network/interfaces file, and setup the connection by hand, it doesn't change anything, I'm still unable to connect to anything.



I also tried connecting to a IPv6 directly, as well as an IPv4 address.



I also tried to boot on a Ubuntu 18.10 live usb, which worked, but didn't yield anything.
I also tried to boot on a Debian 9 live USB in rescue mode, which worked, but didn't yield anything.



PINGing localhost works, but not LAN computers or others.



I also tried to install the r8168-dkms-8.043.02-1_all.deb package from the Debian repo with dpkg and a USB key, and rebooted. Many times. Sadly.



I've also followed the advice found on the Arch Linux forum about Realtek no link / WOL problem. And tried to activate and deactivate several times the Intel Virtualization Technology. I even updated the BIOS to it's last version ( dated 2014 ).










share|improve this question









New contributor




N07070 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.












I've enabled Wake-On-Lan on my debian machine with this tutorial. I didn't have the option to try it out or reboot, and went to sleep. The next day, a power surge happened, and rebooted my computer, for the first time in 15 days.



After that, I didn't have any connection on my computer.



I started to troubleshoot :




  • Rebooted the computer.

  • Rebooted the router.

  • Changed the Ethernet cable.

  • Tried to connected via Wi-Fi with a USB key ( Edimax EW-7811Un )

  • Tried to connect via connection sharing from my Android Phone.

  • Connected the same cable and router to another computer running Ubuntu 18.04, and it worked with no issues. So the issue must be coming from my computer.


That didn't change anything. I looked up the Arch Linux wiki ( props btw, it's really nice. ) and suggested to check my Network Manager config.



I linked the output of /var/log/messages, and diverse config files here :



https://0bin.net/paste/Jcp8j30r6NXBS95K#rPQVHP5oFqdWLyO51F-keBGlRwtSSn7wDD2bh4Tv9U7



And more ...



I set the nameserver of the /etc/resolv.conf to nameserver 8.8.8.8 for testing, but it didn't change anything. I also tried with FDN's DNS



When I remove the comments of the /etc/network/interfaces file, and setup the connection by hand, it doesn't change anything, I'm still unable to connect to anything.



I also tried connecting to a IPv6 directly, as well as an IPv4 address.



I also tried to boot on a Ubuntu 18.10 live usb, which worked, but didn't yield anything.
I also tried to boot on a Debian 9 live USB in rescue mode, which worked, but didn't yield anything.



PINGing localhost works, but not LAN computers or others.



I also tried to install the r8168-dkms-8.043.02-1_all.deb package from the Debian repo with dpkg and a USB key, and rebooted. Many times. Sadly.



I've also followed the advice found on the Arch Linux forum about Realtek no link / WOL problem. And tried to activate and deactivate several times the Intel Virtualization Technology. I even updated the BIOS to it's last version ( dated 2014 ).







debian networking ethernet wake-on-lan






share|improve this question









New contributor




N07070 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.











share|improve this question









New contributor




N07070 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









share|improve this question




share|improve this question








edited 2 mins ago









Rui F Ribeiro

41.7k1483142




41.7k1483142






New contributor




N07070 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









asked 1 hour ago









N07070N07070

1




1




New contributor




N07070 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.





New contributor





N07070 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.






N07070 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.













  • It feels like this is missing a critical number of details.  Can you ping your router? If not, stuff like changing nameservers has no chance of having any effect.

    – G-Man
    31 mins ago



















  • It feels like this is missing a critical number of details.  Can you ping your router? If not, stuff like changing nameservers has no chance of having any effect.

    – G-Man
    31 mins ago

















It feels like this is missing a critical number of details.  Can you ping your router? If not, stuff like changing nameservers has no chance of having any effect.

– G-Man
31 mins ago





It feels like this is missing a critical number of details.  Can you ping your router? If not, stuff like changing nameservers has no chance of having any effect.

– G-Man
31 mins ago










0






active

oldest

votes











Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});






N07070 is a new contributor. Be nice, and check out our Code of Conduct.










draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f508623%2funable-to-connect-to-internet-after-enabling-wake-on-lan-on-debian-9%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























0






active

oldest

votes








0






active

oldest

votes









active

oldest

votes






active

oldest

votes








N07070 is a new contributor. Be nice, and check out our Code of Conduct.










draft saved

draft discarded


















N07070 is a new contributor. Be nice, and check out our Code of Conduct.













N07070 is a new contributor. Be nice, and check out our Code of Conduct.












N07070 is a new contributor. Be nice, and check out our Code of Conduct.
















Thanks for contributing an answer to Unix & Linux Stack Exchange!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f508623%2funable-to-connect-to-internet-after-enabling-wake-on-lan-on-debian-9%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

CARDNET

Boot-repair Failure: Unable to locate package grub-common:i386

濃尾地震