Jump to content
XPEnology Community

chege

Member
  • Posts

    143
  • Joined

  • Last visited

Everything posted by chege

  1. If you need s/n only to fix problem with random IP then its easier way to do this. Just setup static IP under DSM. If your server works then better dont try to mess with loader that someone else "burned" into it, like you said, you dont even know how server is prepared to work with synology. Only issue you have atm is that you cant migrate to dsm 6.x, and you have to turn off auto update options.
  2. Maybe something is changed lately, but few months ago, when synology released dsm 6.1.1 i could use push notification w/o problems and i didnt need sn/mac other than used in xpeno loader. My setup was on esxi 6.02, and notifications received on android phone. I did nothing more than turn it on.
  3. Sorry for the form im posting in here. Those 2 images are part of synology mail from mailing list about WannaCry, which was sent as images not plain text. Generally is said that WannaCry targets only windows systems, so DSM users are safe.
  4. If you properly setup up virtual host by name then all could work as intended. Try to set up with different port than 5000 and try access it with http://www.mydomain.com:port/. Also try http://www.mydomain.com/mydomain to see if the folder is accessible.
  5. During loader startup did you switch to ESXI option? Its the last one in grub menu. Also you can try to build new VM from scratch, just use hard drive from OVF template.
  6. When loader ends to load and you see something like: "Diskstation>", then you need to use synology assistant or try to find it from web assistant find.synology.com. My advice is to use synology assistant. Then open in browser http://xpenoIP and go thru initialization process.
  7. Its not exactly true. On dsm 5.x loader you can login with credentials like thru ssh.
  8. Agree. Thats why, i think, loader is prepared to emulate both hardware. Thanks to jun
  9. I aint Rhubarb so maybe only he can answer exactly. But I am making a guess here that it really doesn't matter if you go for DS3615XS or DS3617XS because you need to create a new usb drive to boot the DSM 6.1 or later iteration anyway. Moreover latest Jun's loader for DS3615XS is v1.02a whereas the latest is v1.02a2 for DS3617XS, which is a later revised version. Although I remember v1.02a2 only contains very minor change, it still make sense to go for the later version if you were to try something new. Having said all above, neither of the two loader work for my setup with both error 13, which really is a bomber. 1. jun's loader v1.02.a2 is a fixed loader for ds3617xs, v1.02a has "time bomb" 2. ds3617xs is compiled for new cpu architecture, with new set of instructions, hardware acceleration etc. if you use it on old cpu then it can cause problems on some part of dsm and packages, but users will blame xpeno loaders. for sake of safety and peace of mind its highly recommended to use emulation of ds3615xs
  10. chege

    DSM 6.1.x Loader

    You cant switch from ds3615xs to ds3617xs without fresh install. Those hardware are not compatible, different architecture.
  11. chege

    DSM 6.1.x Loader

    As far as i know there is n problem with clean install. My test vm with DSM 6.1.1 on esxi 6.0 worked with no problem few weeks. (jun's loader 1.02a2, ds3617xs)
  12. A VPN is something I have been wanting to setup for a while, but never seem to be able to get it to work. Is there a guide available somewhere? - I've looked through the GUIDES section on here and can't find anything. Did you check synology instructions? https://www.synology.com/en-global/know ... /vpn_setup
  13. chege

    DSM 6.1.x Loader

    I dont advise to migrate to DSM 6.1.1. There is problem with migration on esxi vm. Before you do that with live system do some tests with migration first. As far as i know all users doing migration on esxi reported brick system, including me.
  14. Ive got problem to find my dsm 5.2 with find.synology.com, it is up and running for years, but i can find it with synology assistant app.
  15. There is issue when you upgrade DSM 6.x to 6.1.1 on esxi vm. Basically system is bricked.
  16. chege

    DSM 6.1.x Loader

    VI is part of DSM, dont need to be installed. There is not many packages yet since they are not prepared for DSM 6.1.
  17. chege

    DSM 6.1.x Loader

    You can't do tunnel without external server with white IP Maybe, i dont know. Im using to tunnel from PS's with windows meshcentral.com. There is also client for linux but i never tried it.
  18. chege

    DSM 6.1.x Loader

    You are right, but QC - like a single easy way accsess to storage when ISP do not give white dynamic IP. QC = tunnel to storage that do not matter about your IP / ISP / Network / Etc problems. If someone know services or easy way to acsses to storage (without buying wps, wds, hostings) and gives QC functional - pm me please Im not sure this is exactly what you need but good start i think: https://dnstunnel.de/
  19. You cant lock out completely cause DSM wont allow you to turn off/delete all accounts with admin priviledges. At least 1 account has to be active. Maybe you just has blocked IP?
  20. chege

    Web assistant

    Just for info. Dont trust web assistant. Today i found out that web assistant find.synology.com didnt found my baremetal xpeno with DSM 5.2. It is strange since this box could be found some time ago and it can be found with synology assistant for windows.
  21. chege

    DSM 6.1.x Loader

    Why dont you try to create test VM with, let say, 20GB hard drive. Install some packages, add fake data and then change hdd size. Best lessons comes from practice. It takes about 1 hour or less.
  22. Try both mac to be odd or even last hex, dont remember. But since you said its 87 then i think its odd. The original MAC from Lun's loader is xxxxx85. I installed a second machine for test and need to change it, because same MAC at same network doesn't work. That was the reason why I count it up. Is there a relationship between MAC and Serial number? I don't want to use quickconnect. Can I use that way? Then use mac xxxxxx89 instead 86. But IMO best option is to use hardware mac address, just change in grub.cfg to mac1= and mac2=. That should be enough. You can use same serial on all xpeno you have or just change 1 number in it.
  23. Try both mac to be odd or even last hex, dont remember. But since you said its 87 then i think its odd.
×
×
  • Create New...