• Recent
  • Unsolved
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login
  • Recent
  • Unsolved
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login

WOL Assistance?

Scheduled Pinned Locked Moved
General
2
3
433
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • A
    AisleWay
    last edited by Jan 26, 2024, 8:41 PM

    Hi There,

    I’m new to FOG and I am trying to set-up WOL to work across multiple different computers. I am currently attempting to get WOL to work on one computer.

    I have been able to get the computer to Wake-Up using two applications (WakeOnLan & WakeMeOnLan). I want to get the WOL on fog to work however it isn’t. I was able to get it to work after adding the WOL Broadcast plugin but that requires the IP which won’t work when I need to do it across several computers with different IPs. Will I have to go through

    My Fog Server is running at 10.133.xxx.xx and the test computer is running at. 10.20.xxx.xxx. I would appreciate any tips or guidance. All the other computers I would like to wake will also be on the 10.20.xxx.xxx subnet.

    A 1 Reply Last reply Feb 29, 2024, 12:05 AM Reply Quote 0
    • A
      AisleWay @AisleWay
      last edited by Feb 29, 2024, 12:05 AM

      @AisleWay Just replying to see if anyone might have any ideas.

      T 1 Reply Last reply Feb 29, 2024, 11:17 AM Reply Quote 0
      • T
        Tom Elliott @AisleWay
        last edited by Feb 29, 2024, 11:17 AM

        @AisleWay The WOL Broadcast plugin is designed specifically for your use case.

        Seeing as fog server is running on 10.133.x.x, the WOL packets are restricted (by default) to that particular subnet.

        If you add the broadcast of 10.20.x.x to the plugin, it will send there.

        If you need it to go to 10.10.x.x, add it to the plugin and wol will send via that as well.

        Not sure what else we can provide.

        This seems, to me, to indicate that the other networks are separated.

        For example:

        10.x.x.x is generally the whole scope, (10.0.0.0/8) but you have your network broken into seperated subnets.

        For example:
        10.0.0.0/16
        10.1.0.0/16

        etc…

        If all systems in your network is in the 10.x.x.x scope, why the separation when you want not to have to worry about what network to send across?

        Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG! Get in contact with me (chat bubble in the top right corner) if you want to join in.

        Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

        Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

        1 Reply Last reply Reply Quote 0
        • 1 / 1
        1 / 1
        • First post
          1/3
          Last post

        266

        Online

        12.0k

        Users

        17.3k

        Topics

        155.2k

        Posts
        Copyright © 2012-2024 FOG Project