ad19

Members
  • Content Count

    14
  • Joined

  • Last visited

Community Reputation

0 Neutral

About ad19

  • Rank
    Newbie

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Thanks for this tutorial - i've followed it but haven't been able to upgrade from 6.1.7 to 6.2 on my HP Gen8. Even after copying across the extra files to the second partition (zlmage, rd.gz etc) i get a PXE-E53 no boot file error when booting up the Gen8
  2. Thanks for this ed_co - it allowed me to copy across the zImage and rd.gz files. Like you mention, I have problems ejecting/unmounting for some reason. Unfortunately, i can't get Jun's DS3615xs v1.03b loader up and running. When booting up my Gen8, i get a PXE-E53 no boot file error
  3. - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.1.6-15266 Update 1 - Loader version and model: Jun's Mod V1.02b - DS3615xs - Using custom extra.lzma: NO - Installation type: HP Proliant MicroServer Gen8 - Additional comments: REBOOT REQUIRED
  4. - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.1.6-15266 - Loader version and model: JUN'S LOADER v1.02b - DS3615xs - Using custom extra.lzma: NO - Installation type: HP Gen8 Microserver - Additional comments: NO REBOOT REQUIRED
  5. - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.1.5 update 1 - Loader version and model: JUN'S LOADER v1.02b - DS3617xs - Using custom extra.lzma: NO - Installation type: BAREMETAL - Microserver Gen8 - Additional comments: REBOOT REQUIRED
  6. - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.1.5-15254 - Loader version and model: Jun's Loader v1.02b - DS3615xs - Installation type: HP Microserver Gen8 - Additional comments: No reboot required (reboot tested, working fine)
  7. - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.1.4 15217 Update 5 - Loader version and model: Jun's Loader v1.02b - DS3617xs - Installation Type: HP Gen 8 - Additional comments: Reboot required
  8. - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.1.4 15217 Update 2 - Loader version and model: Jun's Loader v1.02b - DS3617xs - Installation type: Baremetal (HPEMicroserver Gen8) - Additional comments: Requires reboot
  9. @Polanksiman, you're right - after having closed port 1194 and rebooting the Diskstation, i could no longer connect from outside. The only way to reconnect was to open port 1194 in the firewall and reboot to allow the changes to take effect
  10. I closed port 1194 on the Diskstation firewall and the connection still worked so i'll keep it closed permanently. Thanks again!
  11. Thanks sbv3000, it's up and running! One point which i neglected in the steps above was opening port 1194 within the Diskstation's firewall.
  12. Thanks sbv3000 and Polanskiman, your responses are much appreciated - i'm trying to implement your 'neat' recommendation by utilising the router's DDNS functionality and forwarding the VPN server's port by following the steps below: 1. I’ve enabled the DDNS client on my router and assigned a host name 2. Port forwarding is setup on the router (1194 | UDP) 3. OpenVPN is running within the Diskstation’s VPN Server package (port 1194 | UDP) 4. I’ve exported the configuration file and imported it to the VPN client The VPN client is asking for the public IP of the Diskstation to enable connection. Would this be a combination of the DDNS host name ('your DDNS') and the dynamic IP address within the OpenVPN section of the Diskstation’s VPN server package?
  13. A very useful guide, thanks. You mention that the best way to make things very safe is to only forward VPN ports. Could you expand on this a bit more please? I'm keen to access the services needed (DS Cam, a few file folders) through a secure VPN connection (e.g. VPN connection setup on Xpenology box and then access the relevant services remotely from my laptop through a secure VPN connection). Is this possible? Any help would be much appreciated.
  14. Thanks for the guide and all your efforts with the bootloader, the update worked a treat!