Wake on LAN not working on Ubuntu 16.04

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP











up vote
4
down vote

favorite
2












I'm trying to setup wake on LAN on my desktop which has Ubuntu 16.04 running.



I've tried a lot, following different manuals and troubleshooting, but with no luck.



When the computer is off or on suspend, one orange light is on the network card, occasionally slightly flickering. I need to resume or turn on computer via LAN if it is suspended or turned off respectively.



I believe I have wake on LAN enabled in the BIOS.



Some outputs that I think might be relevant,



$ sudo ethtool enp2s0 | grep Wake
Supports Wake-on: pumbg
Wake-on: g

$ sudo ethtool -i enp2s0 | grep bus
bus-info: 0000:02:00.0

$ cat /proc/acpi/wakeup | grep 0000:02:00.0
PXSX S4 *enabled pci:0000:02:00.0

$ lspci | grep Ethernet
02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 0c)

$ cat /etc/default/halt
# Default behaviour of shutdown -h / halt. Set to "halt" or "poweroff".
HALT=poweroff
NETDOWN=no

$ sudo tcpdump -i enp2s0 '(udp and port 7) or (udp and port 9)'
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on enp2s0, link-type EN10MB (Ethernet), capture size 262144 bytes
15:31:38.121365 IP <ip>.51603 > <broadcast_ip>.discard: UDP, length 102


I even tried the r8168 driver with no luck.



I'm sending WOL signal with the following command



$ wakeonlan -i <broadcast_ip> <mac_addr>


Any ideas?










share|improve this question





















  • Does the tcpdump output show that your network is allowing the packet to reach your system?
    – Vivek Ghaisas
    Oct 24 '16 at 11:35










  • I guess tcpdump shows packets that actually reached my system, that is network allowed it to reach my system. No?
    – nisargjhaveri
    Oct 24 '16 at 11:37











  • I wasn't sure what those parameters to tcpdump did, so I just wanted to confirm whether that was the intention of running that command. :)
    – Vivek Ghaisas
    Oct 24 '16 at 11:41














up vote
4
down vote

favorite
2












I'm trying to setup wake on LAN on my desktop which has Ubuntu 16.04 running.



I've tried a lot, following different manuals and troubleshooting, but with no luck.



When the computer is off or on suspend, one orange light is on the network card, occasionally slightly flickering. I need to resume or turn on computer via LAN if it is suspended or turned off respectively.



I believe I have wake on LAN enabled in the BIOS.



Some outputs that I think might be relevant,



$ sudo ethtool enp2s0 | grep Wake
Supports Wake-on: pumbg
Wake-on: g

$ sudo ethtool -i enp2s0 | grep bus
bus-info: 0000:02:00.0

$ cat /proc/acpi/wakeup | grep 0000:02:00.0
PXSX S4 *enabled pci:0000:02:00.0

$ lspci | grep Ethernet
02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 0c)

$ cat /etc/default/halt
# Default behaviour of shutdown -h / halt. Set to "halt" or "poweroff".
HALT=poweroff
NETDOWN=no

$ sudo tcpdump -i enp2s0 '(udp and port 7) or (udp and port 9)'
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on enp2s0, link-type EN10MB (Ethernet), capture size 262144 bytes
15:31:38.121365 IP <ip>.51603 > <broadcast_ip>.discard: UDP, length 102


I even tried the r8168 driver with no luck.



I'm sending WOL signal with the following command



$ wakeonlan -i <broadcast_ip> <mac_addr>


Any ideas?










share|improve this question





















  • Does the tcpdump output show that your network is allowing the packet to reach your system?
    – Vivek Ghaisas
    Oct 24 '16 at 11:35










  • I guess tcpdump shows packets that actually reached my system, that is network allowed it to reach my system. No?
    – nisargjhaveri
    Oct 24 '16 at 11:37











  • I wasn't sure what those parameters to tcpdump did, so I just wanted to confirm whether that was the intention of running that command. :)
    – Vivek Ghaisas
    Oct 24 '16 at 11:41












up vote
4
down vote

favorite
2









up vote
4
down vote

favorite
2






2





I'm trying to setup wake on LAN on my desktop which has Ubuntu 16.04 running.



I've tried a lot, following different manuals and troubleshooting, but with no luck.



When the computer is off or on suspend, one orange light is on the network card, occasionally slightly flickering. I need to resume or turn on computer via LAN if it is suspended or turned off respectively.



I believe I have wake on LAN enabled in the BIOS.



Some outputs that I think might be relevant,



$ sudo ethtool enp2s0 | grep Wake
Supports Wake-on: pumbg
Wake-on: g

$ sudo ethtool -i enp2s0 | grep bus
bus-info: 0000:02:00.0

$ cat /proc/acpi/wakeup | grep 0000:02:00.0
PXSX S4 *enabled pci:0000:02:00.0

$ lspci | grep Ethernet
02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 0c)

$ cat /etc/default/halt
# Default behaviour of shutdown -h / halt. Set to "halt" or "poweroff".
HALT=poweroff
NETDOWN=no

$ sudo tcpdump -i enp2s0 '(udp and port 7) or (udp and port 9)'
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on enp2s0, link-type EN10MB (Ethernet), capture size 262144 bytes
15:31:38.121365 IP <ip>.51603 > <broadcast_ip>.discard: UDP, length 102


I even tried the r8168 driver with no luck.



I'm sending WOL signal with the following command



$ wakeonlan -i <broadcast_ip> <mac_addr>


Any ideas?










share|improve this question













I'm trying to setup wake on LAN on my desktop which has Ubuntu 16.04 running.



I've tried a lot, following different manuals and troubleshooting, but with no luck.



When the computer is off or on suspend, one orange light is on the network card, occasionally slightly flickering. I need to resume or turn on computer via LAN if it is suspended or turned off respectively.



I believe I have wake on LAN enabled in the BIOS.



Some outputs that I think might be relevant,



$ sudo ethtool enp2s0 | grep Wake
Supports Wake-on: pumbg
Wake-on: g

$ sudo ethtool -i enp2s0 | grep bus
bus-info: 0000:02:00.0

$ cat /proc/acpi/wakeup | grep 0000:02:00.0
PXSX S4 *enabled pci:0000:02:00.0

$ lspci | grep Ethernet
02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 0c)

$ cat /etc/default/halt
# Default behaviour of shutdown -h / halt. Set to "halt" or "poweroff".
HALT=poweroff
NETDOWN=no

$ sudo tcpdump -i enp2s0 '(udp and port 7) or (udp and port 9)'
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on enp2s0, link-type EN10MB (Ethernet), capture size 262144 bytes
15:31:38.121365 IP <ip>.51603 > <broadcast_ip>.discard: UDP, length 102


I even tried the r8168 driver with no luck.



I'm sending WOL signal with the following command



$ wakeonlan -i <broadcast_ip> <mac_addr>


Any ideas?







ubuntu wake-on-lan






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Oct 22 '16 at 10:13









nisargjhaveri

146126




146126











  • Does the tcpdump output show that your network is allowing the packet to reach your system?
    – Vivek Ghaisas
    Oct 24 '16 at 11:35










  • I guess tcpdump shows packets that actually reached my system, that is network allowed it to reach my system. No?
    – nisargjhaveri
    Oct 24 '16 at 11:37











  • I wasn't sure what those parameters to tcpdump did, so I just wanted to confirm whether that was the intention of running that command. :)
    – Vivek Ghaisas
    Oct 24 '16 at 11:41
















  • Does the tcpdump output show that your network is allowing the packet to reach your system?
    – Vivek Ghaisas
    Oct 24 '16 at 11:35










  • I guess tcpdump shows packets that actually reached my system, that is network allowed it to reach my system. No?
    – nisargjhaveri
    Oct 24 '16 at 11:37











  • I wasn't sure what those parameters to tcpdump did, so I just wanted to confirm whether that was the intention of running that command. :)
    – Vivek Ghaisas
    Oct 24 '16 at 11:41















Does the tcpdump output show that your network is allowing the packet to reach your system?
– Vivek Ghaisas
Oct 24 '16 at 11:35




Does the tcpdump output show that your network is allowing the packet to reach your system?
– Vivek Ghaisas
Oct 24 '16 at 11:35












I guess tcpdump shows packets that actually reached my system, that is network allowed it to reach my system. No?
– nisargjhaveri
Oct 24 '16 at 11:37





I guess tcpdump shows packets that actually reached my system, that is network allowed it to reach my system. No?
– nisargjhaveri
Oct 24 '16 at 11:37













I wasn't sure what those parameters to tcpdump did, so I just wanted to confirm whether that was the intention of running that command. :)
– Vivek Ghaisas
Oct 24 '16 at 11:41




I wasn't sure what those parameters to tcpdump did, so I just wanted to confirm whether that was the intention of running that command. :)
– Vivek Ghaisas
Oct 24 '16 at 11:41










2 Answers
2






active

oldest

votes

















up vote
0
down vote














I believe I have wake on LAN enabled in the BIOS.




Make sure you have it enabled in BIOS, because it is a pre-requisite of WoL working.




Wake-on: g



Magic packet setting must be persistent. If it is not after power cycle, you might want to try setting in the following file:



/etc/netctl/profile


as follows:



ExecUpPost='/usr/bin/ethtool -s interface wol g'


Further reading on ArchWiki.






share|improve this answer



























    up vote
    -1
    down vote













    Set WOL_DISABLE=N in /etc/default/tlp and NETDOWN=no in /etc/default/halt






    share|improve this answer


















    • 2




      Welcome to Unix & Linux Stack Exchange.  Please don’t post answers that are just configuration settings and no explanation.  Please explain what these do.  This doesn’t have to be long but it is expected.
      – Scott
      Feb 6 '17 at 20:25






    • 1




      I have NETDOWN=no set in /etc/default/halt. It is already mentioned in the question. And tlp is not in use.
      – nisargjhaveri
      Feb 7 '17 at 6:23










    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',
    convertImagesToLinks: false,
    noModals: false,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: null,
    bindNavPrevention: true,
    postfix: "",
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    );



    );













     

    draft saved


    draft discarded


















    StackExchange.ready(
    function ()
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f318137%2fwake-on-lan-not-working-on-ubuntu-16-04%23new-answer', 'question_page');

    );

    Post as a guest






























    2 Answers
    2






    active

    oldest

    votes








    2 Answers
    2






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes








    up vote
    0
    down vote














    I believe I have wake on LAN enabled in the BIOS.




    Make sure you have it enabled in BIOS, because it is a pre-requisite of WoL working.




    Wake-on: g



    Magic packet setting must be persistent. If it is not after power cycle, you might want to try setting in the following file:



    /etc/netctl/profile


    as follows:



    ExecUpPost='/usr/bin/ethtool -s interface wol g'


    Further reading on ArchWiki.






    share|improve this answer
























      up vote
      0
      down vote














      I believe I have wake on LAN enabled in the BIOS.




      Make sure you have it enabled in BIOS, because it is a pre-requisite of WoL working.




      Wake-on: g



      Magic packet setting must be persistent. If it is not after power cycle, you might want to try setting in the following file:



      /etc/netctl/profile


      as follows:



      ExecUpPost='/usr/bin/ethtool -s interface wol g'


      Further reading on ArchWiki.






      share|improve this answer






















        up vote
        0
        down vote










        up vote
        0
        down vote










        I believe I have wake on LAN enabled in the BIOS.




        Make sure you have it enabled in BIOS, because it is a pre-requisite of WoL working.




        Wake-on: g



        Magic packet setting must be persistent. If it is not after power cycle, you might want to try setting in the following file:



        /etc/netctl/profile


        as follows:



        ExecUpPost='/usr/bin/ethtool -s interface wol g'


        Further reading on ArchWiki.






        share|improve this answer













        I believe I have wake on LAN enabled in the BIOS.




        Make sure you have it enabled in BIOS, because it is a pre-requisite of WoL working.




        Wake-on: g



        Magic packet setting must be persistent. If it is not after power cycle, you might want to try setting in the following file:



        /etc/netctl/profile


        as follows:



        ExecUpPost='/usr/bin/ethtool -s interface wol g'


        Further reading on ArchWiki.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Jun 22 at 4:53









        Vlastimil

        6,7331149123




        6,7331149123






















            up vote
            -1
            down vote













            Set WOL_DISABLE=N in /etc/default/tlp and NETDOWN=no in /etc/default/halt






            share|improve this answer


















            • 2




              Welcome to Unix & Linux Stack Exchange.  Please don’t post answers that are just configuration settings and no explanation.  Please explain what these do.  This doesn’t have to be long but it is expected.
              – Scott
              Feb 6 '17 at 20:25






            • 1




              I have NETDOWN=no set in /etc/default/halt. It is already mentioned in the question. And tlp is not in use.
              – nisargjhaveri
              Feb 7 '17 at 6:23














            up vote
            -1
            down vote













            Set WOL_DISABLE=N in /etc/default/tlp and NETDOWN=no in /etc/default/halt






            share|improve this answer


















            • 2




              Welcome to Unix & Linux Stack Exchange.  Please don’t post answers that are just configuration settings and no explanation.  Please explain what these do.  This doesn’t have to be long but it is expected.
              – Scott
              Feb 6 '17 at 20:25






            • 1




              I have NETDOWN=no set in /etc/default/halt. It is already mentioned in the question. And tlp is not in use.
              – nisargjhaveri
              Feb 7 '17 at 6:23












            up vote
            -1
            down vote










            up vote
            -1
            down vote









            Set WOL_DISABLE=N in /etc/default/tlp and NETDOWN=no in /etc/default/halt






            share|improve this answer














            Set WOL_DISABLE=N in /etc/default/tlp and NETDOWN=no in /etc/default/halt







            share|improve this answer














            share|improve this answer



            share|improve this answer








            edited Feb 6 '17 at 16:27









            Michael Mrozek♦

            58.7k27184207




            58.7k27184207










            answered Feb 6 '17 at 15:00









            guest

            1




            1







            • 2




              Welcome to Unix & Linux Stack Exchange.  Please don’t post answers that are just configuration settings and no explanation.  Please explain what these do.  This doesn’t have to be long but it is expected.
              – Scott
              Feb 6 '17 at 20:25






            • 1




              I have NETDOWN=no set in /etc/default/halt. It is already mentioned in the question. And tlp is not in use.
              – nisargjhaveri
              Feb 7 '17 at 6:23












            • 2




              Welcome to Unix & Linux Stack Exchange.  Please don’t post answers that are just configuration settings and no explanation.  Please explain what these do.  This doesn’t have to be long but it is expected.
              – Scott
              Feb 6 '17 at 20:25






            • 1




              I have NETDOWN=no set in /etc/default/halt. It is already mentioned in the question. And tlp is not in use.
              – nisargjhaveri
              Feb 7 '17 at 6:23







            2




            2




            Welcome to Unix & Linux Stack Exchange.  Please don’t post answers that are just configuration settings and no explanation.  Please explain what these do.  This doesn’t have to be long but it is expected.
            – Scott
            Feb 6 '17 at 20:25




            Welcome to Unix & Linux Stack Exchange.  Please don’t post answers that are just configuration settings and no explanation.  Please explain what these do.  This doesn’t have to be long but it is expected.
            – Scott
            Feb 6 '17 at 20:25




            1




            1




            I have NETDOWN=no set in /etc/default/halt. It is already mentioned in the question. And tlp is not in use.
            – nisargjhaveri
            Feb 7 '17 at 6:23




            I have NETDOWN=no set in /etc/default/halt. It is already mentioned in the question. And tlp is not in use.
            – nisargjhaveri
            Feb 7 '17 at 6:23

















             

            draft saved


            draft discarded















































             


            draft saved


            draft discarded














            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f318137%2fwake-on-lan-not-working-on-ubuntu-16-04%23new-answer', 'question_page');

            );

            Post as a guest













































































            Popular posts from this blog

            How to check contact read email or not when send email to Individual?

            Displaying single band from multi-band raster using QGIS

            How many registers does an x86_64 CPU actually have?