Selfhosted

39435 readers

6 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago

MODERATORS

[email protected]

Send WoL signal though Opnsense networks (lemmy.ml)

submitted 6 months ago by [email protected] to c/[email protected]

9 comments fedilink hide all child comments

So i dont know what im doing wrong. I have 3 interfaces on opnsense

1:Server=192.168.40.0 2:Wlan=192.168.20.0 3:wireguard=192.168.60.0

And lastly the Wan with its default configuration.

I want to be able to Send a WOL packet though the Wlan network to wake up my PC that is inside Server network.

In Firewall>rules>Wlan I made a new rule like this: Action=Pass Interface=Wlan Direction=in TCP/IP=ipv4 Protocol=UDP Source=any Destination=Server address Destination port range=from 7 to 7

When i try sending a wol signal when my pc went to sleep a few minutes later i think the firewall rule goes though, but when i try to send from another device after lots of time later it doesn't go though i think.

Im using Moonlight to send its signal, does anyone have been thought this problem. Thank you

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

[–] [email protected] 11 points 6 months ago (1 children)

WoL packets are usually sent to the ip broadcast address for the network as they’re not ip based. I don’t know if this would ever work well across networks. Can you do send the wol packet from the opnsense router instead? Does it work then?

If you’re sending it to the IP of the server, it likely works soon after your turn the machine off because the ARP entry hasn’t timed out yet, but once it times out it won’t work anymore. The router doesn’t know how to get to the machine. You may be able to add a static arp mapping to get it to work long term.

[–] [email protected] 2 points 6 months ago (1 children)

Never heard of that phrase ARP thanks i will look into that

[–] [email protected] 3 points 6 months ago (1 children)

Update: I have installed the wol plugin from opnsense into my machine, you asked if i can send a wol packet though the router and so in my thinking i was able to do it via the plugin. The problem starts on the ARP, i found what it is and what it do but i dont know how i can insert the MAC address into the firewall rule that i created above, if you dont mind could you help me on how can i do it? And if i do that will i be able to send the wol signal though the Wlan or Wireguard in the future? Thanks

[–] [email protected] 1 points 6 months ago

From a Linux command line it would be the command called arp, you need to add a static arp entry. I don’t know how that works on sense, but on Linux it would be something like arp -s IP MAC

Maybe there’s a module in opnsense to help. The way I’ve done this before is using a machine connected to the same network at my target to wake up by logging into that machine and issuing the wake command.