Linux

58944 readers

935 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
No misinformation
No NSFW content
No hate speech, bigotry, etc

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 6 years ago

MODERATORS

AgreeableLandscape@lemmy.ml

nooter692@lemmy.ml

MarcellusDrum@lemmy.ml

cypherpunks@lemmy.ml

cyclohexane@lemmy.ml

d3Xt3r@lemmy.nz

[solved] Wake on LAN magic packet not reaching target (lemmy.world)

submitted 1 month ago* (last edited 1 month ago) by meekah@lemmy.world to c/linux@lemmy.ml

5 comments fedilink hide all child comments

I am trying to set up a simple home server with some old hardware, and since power is pretty expensive here I am trying to enable WoL so that I can turn it on whenever I need it, and automatically shut it down after a short time of inactivity.

I enabled WoL ("Power On By PME") in my BIOS, which then allowed me to enable WoL in my network device drivers using nmcli. It now reliably shows mode g selected after reboot, as reported by ethtool. I installed gWakeOnLan on another device to try waking my server, but to no avail.

When my server is shut down, the ethernet LEDs are still blinking, so I suppose the network device successfully stays turned on after shutdown. However, when I use netcat on my server to check that the magic packets get there, I can't see any output after sending the packets using gWakeOnLan. I tried both ports 9 and 40000.

I am using a router that was provided to me by my network provider, maybe I need to enable/unblock something there? No idea what it would be, though.

Any ideas on how to track this issue further down?

Edit: I am now using wol instead of gWakeOnLan. this command worked for me:

wol -p 9 -i 192.168.2.255 <server-mac-address>.

I got the IP from ip address :

inet 192.168.2.31/24 brd 192.168.2.255 scope global dynamic noprefixroute eno1

I'd like having a little GUI but apparently it's not possible to configure the IP in gWakeOnLan like this. I tried setting it to 'internet' mode (to allow me to enter my IP) but that didn't work. Oh well, a little script to double-click is fine, too, haha

you are viewing a single comment's thread
view the rest of the comments

[–] meekah@lemmy.world 2 points 1 month ago (1 children)

How would this explain the packet not reaching the server in a powered on state?

[–] Mihies@programming.dev 1 points 1 month ago (1 children)

Yeah, that won't but you could still try, just in case. Other than that, are both client and server on same IP segment? About router - I'd really suggest using your own router (also firewall) behind the provided one. Otherwise you are exposing your internal network to network provider which you might not want to do and at the same time you don't have a control over the core device in your network.

[–] meekah@lemmy.world 1 points 1 month ago

Thanks for the tip regarding the IP segment, that seemed to be it. I needed to use the correct broadcast IP for the subnet (I think? I'm bad with networks. I used 192.168.2.255 instead of 255.255.255.255, and now it works)

And yeah, I am looking to get a router at some point. Hard to make such a purchase when I'm struggling to make ends meet currently, though.