Wake on LAN over different VLANS
-
Can you provide the output of this?
ip link show -
@Tom-Elliott Take your time Tom! I am very patient and have any time you need so whenever you are free.
-
@Wayne-Workman This is the result
-
I’ll try to “schedule” it for tonight then, if that’s okay? I’m on EDT (New York).
-
@szecca1 said:
@Wayne-Workman This is the result
Make sure that ens32 is set as the interface for that server’s storage node.
-
@Tom-Elliott I work from 8-4 every day during the week, but if you are only available at night I can make it work. I’m in NY as well so time wise will be the same
-
@Wayne-Workman If you’re talking about on the fog server where the storage node is, right now it is set to ‘bond0’ You’re saying to change that to ens32? and that should fix the wake on lan?
-
@Wayne-Workman I tried that and still the computer is not turning on. It has the same settings as before I switched to Fedora when the wake on lan worked with Ubuntu. Just confused haha
-
@Developers Where is package / code that actually sends the WOL ?
-
Please try updating to the latest. I altered some more of the code and things should work. Again, as I told you in chat, I don’t have physical systems for testing WOL on, so most of the time I’m just working blind and hoping for the best. Every once in a while I can test where I work, but this time of year, as I hope you all understand, it’s pretty unrealistic. Please let me know if it is working now.
Thank you,
-
Okay, so I was an idiot when working with things. @szecca1 is using a NAS. I set Wake on lan to get all nodes to try waking up hosts. NAS cannot wake up hosts because the links that wake them up is not installed. Fixed this by adding the FOG_WEB_HOST as a starting point for WOL as well.
It appears all is now working.
-
Glad to see this is fixed. I helped to the extent of my abilities via forum chat but I came to a dead end basically. And Tom’s post explains why. Good to see a solution is found.
