Asus AC87U ARP requests waking Synology NAS

[vanq69er]

Hi all,

After much investigation I have found that my AC87U is waking my DS413 NAS every hour with an ARP broadcast;

5689 60.171866 AsustekC_92:d3:20 Broadcast ARP 60 Who has 192.168.1.113? Tell 192.168.1.1

Apparently the NAS is hardcoded to wake and reply however, I was wondering if it is possible to change the ARP broadcast timing to say 4 hours or disable it for the NAS IP/MAC? The NAS has a static ARP set (PERM).

Thanks, any help is much appreciated!

 

[GSpock]

Hi,
check this one: http://www.snbforums.com/threads/ntp-service-wakes-my-nas-hdds-from-sleep-every-hour.29063/
and also this one: http://www.snbforums.com/threads/router-hourly-scans-lan-web-server.29516/

But so far no solution to this repetitive wake of NAS HDD (except to downgrade FW ...)

Rgds,
GS

 

[vanq69er]

Hi GSpock, thanks mate this was exactly what I was after. I might try downgrade to 378.54_2 and see if it fixes the problem.

 

[vanq69er]

GSpock you are an absolute champion! Downgraded to 378.54_2 and it sleeps like a baby!

 

[GSpock]

Thanks, but the one who found out is here: http://www.snbforums.com/threads/37...ork-attached-printer.26529/page-2#post-222389

Really a pitty that Rmerlin cannot (at this time) provide a fix (or work-around) for this in more recent FW (the cause has alredy been identified: new networkmap process), because we see more and more people complaining here about this repetitive useless wake-up of NAS HDD, and also printers .... and who knows what else ....

 

[Iwakan]

Same problem here with Synology and 380.57. According to your experience I'm going to revert to 378.54_2 but I have a question. It's possible to perform the downgrade directly or I have to reset configuration after downgrade?

 

[Savell Martin]

Ye we really need a fix especially for new routers that need the new firmware.

 

[GSpock]

Same problem here with Synology and 380.57. According to your experience I'm going to revert to 378.54_2 but I have a question. It's possible to perform the downgrade directly or I have to reset configuration after downgrade?

I have not performed the downgrade myself (yet), still hoping for a fix or workaround. May be vanq69er could tell us ... ?

 

[vanq69er]

Same problem here with Synology and 380.57. According to your experience I'm going to revert to 378.54_2 but I have a question. It's possible to perform the downgrade directly or I have to reset configuration after downgrade?

No config reset however, I would recommend backing up the config anyway. For me it was as simple as upgrading the firmware normally but just load the old version, no config changed that I could find.

 

[Iwakan]

No config reset however, I would recommend backing up the config anyway. For me it was as simple as upgrading the firmware normally but just load the old version, no config changed that I could find.

Thank you. I downgraded my router and Synology continues waking up. Not as often as before but I think that not more than three or four hours hibernating. I have just unplugged network cable to check and I'm going to enable log to see what's happening. Meanwhile any idea?

 

[GSpock]

Thank you. I downgraded my router and Synology continues waking up. Not as often as before but I think that not more than three or four hours hibernating. I have just unplugged network cable to check and I'm going to enable log to see what's happening. Meanwhile any idea?

... well, at least you know that it is not waken-up anymore by the router/networkmap .... for the rest, it can be a little bit of anything on your LAN that for whatever reason tries to access your NAS ..... DLNA clients, windows client, ... the NAS itself updaing its DDNS record ... and/or checking for an update of DSM, and so on ....

 

[Iwakan]

Thank you. I'm still testing but I have a question. This is a problem of the stock firmware, Merlin or both?

 

[sfx2000]

Thank you. I downgraded my router and Synology continues waking up. Not as often as before but I think that not more than three or four hours hibernating. I have just unplugged network cable to check and I'm going to enable log to see what's happening. Meanwhile any idea?

ARP requests/broadcasts are actually required - so I'm not surprised that the Synology is still waking up...

Doing some quick google-fu, it looks more like a Synology bug with the Freescale board support package, in that ARP can wake up the processor from deep sleep mode - see here:

http://forum.synology.com/enu/viewtopic.php?f=83&t=59081&start=75

and slide 49 here - http://www.nxp.com/files/training/doc/dwf/AMF_NET_T0610.pdf

So I'm thinking Asus shouldn't try to fix this, or put in workarounds, as this can break other things..

 

[GSpock]

Thank you. I'm still testing but I have a question. This is a problem of the stock firmware, Merlin or both?

Hi, I only use Merlin .... sorry !

 

[GSpock]

ARP requests/broadcasts are actually required - so I'm not surprised that the Synology is still waking up...

Doing some quick google-fu, it looks more like a Synology bug with the Freescale board support package, in that ARP can wake up the processor from deep sleep mode - see here:

http://forum.synology.com/enu/viewtopic.php?f=83&t=59081&start=75

and slide 49 here - http://www.nxp.com/files/training/doc/dwf/AMF_NET_T0610.pdf

So I'm thinking Asus shouldn't try to fix this, or put in workarounds, as this can break other things..

Well, since the issue was not present in previous/older FW, one could expect that a fix is provided in most recent FW
(and it has been identified the issue is within the "new" networkmap process).

 

[sfx2000]

Well, since the issue was not present in previous/older FW, one could expect that a fix is provided in most recent FW
(and it has been identified the issue is within the "new" networkmap process).

Well, since the Syno does deep sleep, and that's fine perhaps, but it's doing deep sleep - the NAS wakes up, and spins up the drives as a result. Check the settings for the NAS - spinning down drives vs. sleep/hibernation...

Anyways - sending out ARP's is how the router is mapping IP addresses on the LAN to MAC addresses of the devices - this is how things work for all vendors.

killing off ARP isn't a good thing...

 

[Iwakan]

Question here is why with older firmwares, hibernation of Synology and other devices are working fine and with newer ones not. Not upgrading router's firmware is a problem specially when critical vulnerabilities are discovered and not pached and continuos NAS waking up is not good for the HDs. I think we must inform Asus about that. If stock firmware is updated with a solution Merlin will be updated too.

 

[GSpock]

Well, since the Syno does deep sleep, and that's fine perhaps, but it's doing deep sleep - the NAS wakes up, and spins up the drives as a result. Check the settings for the NAS - spinning down drives vs. sleep/hibernation...

Anyways - sending out ARP's is how the router is mapping IP addresses on the LAN to MAC addresses of the devices - this is how things work for all vendors.

killing off ARP isn't a good thing...

... I do not say we should kill ARP .... and we know it is needed to do wol. As mentioned by Iwakan, the point is that it was OK in previous version of Merlin, so .... and the issue is clearly identified in the new networkmap process ....

 

[sfx2000]

No, we don't change ARP, as this is a vital IPv4 management protocol...

Looks like the Synology perhaps has issues with Magic Packet on the ethernet interface - they should be implementing MPEN before going into suspended mode on the Freescale SoC - if they do it correctly, then the ARP packets are discarded, and no problem with the NAS staying in sleep mode until the Magic Packet is received by the NAS...

If they set MPEN to true, they first need to ensure that graceful stop transmit and receive is completed, otherwise MPEN is cleared - then, any addressed frame to the NAS can wake it up...

The Freescale chipset is very particular about this, moreso than other SoC's...

 

[GSpock]

Dear sfx2000,
I do not want to continue a polemic with you on the matter ..... it seems you keep on forgetting that the issue we are having was not present in older Merlin firmware ... and you seem to believe there is a bug in Synology FW and freescale chipset which BTW is not the chipset in my Synology ; if this is your point, fair enough, I have another one.
Rgds,
GS