[DSM 5.0-4493 Update 4 Complete Install Guide]

Hi, thanks for the reply, push was previously being handled by SS.

 

Unfortunately it seems as though the SS notifications are not showing up in DSM, I am assuming this is not normal or I have missed a setting somewhere?

 

I'm still working through settings, seems alot more to setup compare to DSM 4, unless I didnt really look into DSM 4 settings properly lol.

[DSM 5.0-4493 Update 4 Complete Install Guide]

Just installed DSM 5.0-4493 Update 3 on My N54L after having the security messages about the ransomware having ran DSM 4.3 for the past year.

 

Now having spent the best part of 2 days backing up and getting DSM 5.0 setup I have come across a stumbling block with the push notifications. I understand from the above posts that this is not working. Yup I should have read the vast amount of posts on the forums prior to install but then again the forums aren't the most user friendly in terms of ease of use for the less experienced amongst us It confused me and took me long enough to decide on which bootloader to use, started with gynoboot but struggled to update to 4493 Update 3 with any updates saying they weren't for my NAS so then I tried with nanoboot and updated successfully which is where I am at now.

 

I use the push notifications in conjunction with surveillance station to alert me when the camera detects motion when I am not home. Is there a work around for this? as I am not sure how to interpret Polanskiman comment a few posts up.

So far, the only things that do not work (but this is registration related) is the QuickConnect functionality but it can easily be overcome by setting up a custom DDNS and the Push Notification to the DS Finder app. Those two can only work if the product is purchased and properly registered on Synology's website with a valid serial number.

 

Any help would be appreciated.

 

Neil

[[SOLVED]Wake On LAN (WOL)]

Hello,

I use WinSCP to have the access to system files.

At the first log with SCP protocol, I have a first error message "-sh: groups: not found , but after OK I have the access to the folder.

But when I want to save the synoinfo.conf file after modification I have the same message and scp: /etc/synoinfo.conf: Permission denied.

If someone could help me

Thanks a lot

 

Did you find your answer and get it working?

 

You need to login with SCP using the username "root" and not the name used to login to DSM, password remains the same as you created at setup.

[Guide: Change serial number and MAC address]

If we're talking about the N54L Microserver, then you can see the MAC address on the first page in BIOS setup.

 

Your hex edit is missing the 69 after your first mac address. Every mac address is 7 characters long. That's why it isn't working for you.

 

Seems as though the 69 has been added by the ver2.xlsb calc. When you say every MAC address is 7 characters long I assume you mean 7 pairs of alpha/numerical.

 

The MAC address on every system on my lan is 6 pairs.

 

I'm even more confused now.

[Guide: Change serial number and MAC address]

I have Xpenology running fine on a micro server I am trying out before buying but having issues with the MAC address.

 

Am i right in saying that the server uses the mac address's listed in the vendor file?

Is there anywhere else that it can read the mac addresses from as each time I reboot my N54L I have a different mac and none of them are listed in the vendor file.

 

On another note when editing the vendor file in hex edit and adding the serial number hex code I always end up with extra characters on the serial number. When I boot up it lists all as invalid mac addresses

 

 

I am following this guide but somewhere I must be missing something. Any help would be much appreciated.

 

Thanks