Search the Community

Showing results for tags 'mac'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Information
    • Readers News & Rumours
    • Information and Feedback
    • The Noob Lounge
  • XPEnology Project
    • F.A.Q - START HERE
    • Loader Releases & Extras
    • DSM Updates Reporting
    • Developer Discussion Room
    • Tutorials and Guides
    • DSM Installation
    • DSM Post-Installation
    • Packages & DSM Features
    • General Questions
    • Hardware Modding
    • Software Modding
    • Miscellaneous
  • International
    • РУССКИЙ
    • FRANÇAIS
    • GERMAN
    • SPANISH
    • ITALIAN
    • KOREAN
    • CHINESE
    • HUNGARIAN

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


About Me

Found 6 results

  1. I've created an Ansible Playbook for creating an Xpenology USB. https://github.com/stevenhrabok/ansible-xpenology-usb Currently it's only written for Mac OSX. In future I may add the ability to create USB Devices in Linux if there is interest in using the tool. I wrote this to help automate the workflow and make the USB drive creation process more consistent. It also helps avoid forgetting a steps in the process. Features: Prompts for information serial number - changed in grub.cfg nic 1 mac address - changed in grub.cfg
  2. Recently I reinstalled my build (DS3617xs/6.1.7) using a set of serial/mac(starting with 02:11:32) generated by Docker/DDSM. Everything went smooth until I create a new host in VMM, the mac of the DSM was changed to another random address(#1). I rebooted the DSM and kept looking at the router, the DSM started with 02:11:32 but later when the VM started, the DSM mac was changed again to another random address different from #1. I checked the grub.cfg of the usb drive and it wasn't changed. Now I am sure the DSM mac was changed during either the creation of a new VM or the startup of an existing
  3. I have been able to get my Mac Mini Server 2012 model to boot with Jun's 6.1 3617 loader and it works great. I was able to see the NAS on the network using Synology Assistant and connect just fine. However, I have had no luck getting Jun's 6.2 beta loader to connect to the network. It appears to boot just fine, but I never see it on the network. I tried: Both the 3615 and 3517 loaders Set the PID/VID of the USB Tried 2 different USB drives; all boot, no network Set the mac1 to the actual NIC mac address. I assume the NIC chipset
  4. Firstly, my apologies if this has been answered already. Ive been unable to get a clear answer here for days. I have a valid serial number from a DS3615xs that had died, and I never got around to RMAing before it was lost for good. I have a DSM 6.1.5 Virtual machine on ESXI 6.0. I am trying to get a clear understanding of how a Mac addresses are derived from a Serial number. Ive gone over the discussions and tools out there for it, but it seems all of them assume a generated serial number, and not one that I already have. Any information you guys can
  5. I have got genuine serial + MAC from another/wrecked Synology device. Is it recomended to use it? If so, how to do that? Will there be any advantage? Thanks in advance.
  6. Bonjour à tous, un besoin d'aide j'ai deux N54L PROD: un en production avec la dernière version du DSM 5.2 TEST : un qui me sert de test donc je peux tout faire avec J'ai suivi scrupuleusement le tuto d'installation présent sur le site sur TEST pour une fraiche installation. Une fois tout suivi , a clef usb construite, je démarre. J'arrive sur le même écran que sur le tuto où il est demandé de lancer le Synology Assistant. Mais Synology Assistant ne trouve pas mon DSM6 SI je mets la clef USB DSM 5.2 de PROD sur TEST, le synology as