Please add a WOL function to the XR500 Menu

[xlr8r]

Whilst this has been discussed months ago ... as yet, nothing has appeared in any of the firmware updates....

i.e. 

http://forum.netduma.com/topic/24915-configuring-wake-over-internet-arp-issue/?hl=wol

http://forum.netduma.com/topic/24167-wake-on-lan-not-working-on-this-router/?p=174793

http://forum.netduma.com/topic/24165-xr500-os-requests/?p=174763

 

 

Can devs please include a WOL function, as many other routers have this as a "basic function".....

 

on my prev R7000 router i had a simple menu option like this, (image grabbed from Google, MAC and IP's are not real!)

 

 

 

This would be a really useful tool for those (like myself) who need to remote access the router to startup home devices.

 

in addition, Content Filtering needs improved so that multiple schedules can be setup for different groups of devices. ie. one rule setup for one child, and one for another with different timescales set.

[Netduma Fraser]

What was the result from your ticket? Did your WOL request make it to the Netgear development team? They would be the ones implementing it. If not I can chase them.

[xlr8r]

What was the result from your ticket? Did your WOL request make it to the Netgear development team? They would be the ones implementing it. If not I can chase them.

 

 

5 months later... i have yet to have a "sensible" reply from Netgear.... 

 

they just kept asking for answers to stupid questions like , whats my IP and whats my firmware version, nad can i upload pictures of teh problem ? wtf Netgear

 

ultimately, there was nobody at Netgear with a level of intelligence , able to deal with the question I was asking.... 

 

hence why I never bother asking them for anything anymore.....

[Netduma Fraser]

Okay I'll contact them

[AlainCh2]

I'm also interested in having the Wol on any internal address.

I need to wakeup some sleeping devices without using  power buttons.

it's 2020 and domotics are more and more using functions
that can be ignored  in the past .... 
like this one ignored two years ago.

PS: and a "Wakeup" button inside Netduma would be a luxury!!!!

[Netduma Fraser]

I'll remind the team of this and see if they can put it into 3.0 easily.

[Bderbi24]

Netduma Fraser, can you confirm if this feature has been implemented within 3.0?

[Netduma Fraser]

19 minutes ago, Bderbi24 said:

Netduma Fraser, can you confirm if this feature has been implemented within 3.0?

Hey, welcome to the forum!

No it's not in 3.0 currently. We've focused on getting the main features we wanted included, setting up of the Rapp store etc and basically making sure we could make changes very easily in future. So although it's not included right now we've made it easier to add in future.

[D_L]

Hi, I really want to get an R2 (especially while the launch discount is still on, 😉), but WOL is a requirement for me, so I have been waiting for an update on that front.

If dedicated WOL functionality or an Rapp is not there yet (but hopefully planned for the near future), is there a work-around for making sure devices are not frequently flushed from the router's arp table, thus becoming unreachable through port forwarding of magic packets (i.e. the same issue as the OP's first linked thread)?

I believe telenet access was(is?) not supported in DumaOS (at least in Netgear routers), so static entries could not (cannot?) be added manually to fix the issue.

There is an old feature request for WOL functionality to be implemented within the network map (assuming shutdown systems configured for WOL do not drop off said map): https://forum.netduma.com/topic/26604-wake-on-lan/?tab=comments#comment-194280 . Any update on this variety of implementation?

Does anyone have a successful WOL setup with DumaOS 3.0, ideally on the R2 so that I can place my order?

[Netduma Fraser]

5 hours ago, D_L said:

Hi, I really want to get an R2 (especially while the launch discount is still on, 😉), but WOL is a requirement for me, so I have been waiting for an update on that front.

If dedicated WOL functionality or an Rapp is not there yet (but hopefully planned for the near future), is there a work-around for making sure devices are not frequently flushed from the router's arp table, thus becoming unreachable through port forwarding of magic packets (i.e. the same issue as the OP's first linked thread)?

I believe telenet access was(is?) not supported in DumaOS (at least in Netgear routers), so static entries could not (cannot?) be added manually to fix the issue.

There is an old feature request for WOL functionality to be implemented within the network map (assuming shutdown systems configured for WOL do not drop off said map): https://forum.netduma.com/topic/26604-wake-on-lan/?tab=comments#comment-194280 . Any update on this variety of implementation?

Does anyone have a successful WOL setup with DumaOS 3.0, ideally on the R2 so that I can place my order?

Hey, welcome to the forum!

It is not available currently but is on our roadmap - I couldn't say specifically when this might be implemented. They shouldn't get flushed, they'll appear as either online/offline on the router until removed. Telnet/SSH is not enabled for users. I will add your request to the roadmap so it gets boosted and maybe implemented sooner.

[D_L]

On 9/3/2020 at 11:45 AM, D_L said:

Hi, I really want to get an R2 (especially while the launch discount is still on, 😉), but WOL is a requirement for me, so I have been waiting for an update on that front.

If dedicated WOL functionality or an Rapp is not there yet (but hopefully planned for the near future), is there a work-around for making sure devices are not frequently flushed from the router's arp table, thus becoming unreachable through port forwarding of magic packets (i.e. the same issue as the OP's first linked thread)?

I believe telenet access was(is?) not supported in DumaOS (at least in Netgear routers), so static entries could not (cannot?) be added manually to fix the issue.

There is an old feature request for WOL functionality to be implemented within the network map (assuming shutdown systems configured for WOL do not drop off said map): https://forum.netduma.com/topic/26604-wake-on-lan/?tab=comments#comment-194280 . Any update on this variety of implementation?

Does anyone have a successful WOL setup with DumaOS 3.0, ideally on the R2 so that I can place my order?

 

On 9/3/2020 at 5:22 PM, Netduma Fraser said:

Hey, welcome to the forum!

It is not available currently but is on our roadmap - I couldn't say specifically when this might be implemented. They shouldn't get flushed, they'll appear as either online/offline on the router until removed. Telnet/SSH is not enabled for users. I will add your request to the roadmap so it gets boosted and maybe implemented sooner.

 

 

I bought an R2 after all and am more than pleased with everything about it except the feared WOL behaviour: even though my PC does remain on the Network Map as offline, after a couple of minutes no magic packets reach it. I imagine the issue is not having a static entry on the arp table.

I shall eagerly wait for a dedicated WOL Rapp or added functionality to interact with the arp table.

PS: the port forwarding interface only allows rules by IP(v4) identification; of course, this works when partnered with a static IP setting, but as a purer alternative the ability to set rules by MAC (or IPv6) would be nice.

[Netduma Fraser]

1 hour ago, D_L said:

 

I bought an R2 after all and am more than pleased with everything about it except the feared WOL behaviour: even though my PC does remain on the Network Map as offline, after a couple of minutes no magic packets reach it. I imagine the issue is not having a static entry on the arp table.

I shall eagerly wait for a dedicated WOL Rapp or added functionality to interact with the arp table.

PS: the port forwarding interface only allows rules by IP(v4) identification; of course, this works when partnered with a static IP setting, but as a purer alternative the ability to set rules by MAC (or IPv6) would be nice.

It's definitely on our roadmap so hopefully we can get that implemented soon. Try giving it a reserved IP in Settings and see if that helps. I'll add that to our roadmap as well.