NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
ReadyNAS Add-ons for Legacy ReadyNAS
1113 Topics
SMTP server addon for ReadyNAS Ultra?
Hi all, I have searched a bit but not found any suitable threads and my question is fairly straightforward: Is there an SMTP server addon for the ReadyNAS Ultra (4)? I would like a single place to point all of my clients and devices locally in order to send mail, and thus only 1 place to edit the public SMTP settings if I change ISP or mail provider. The alerts from the ReadyNAS work just fine, but 2 webcams seem to have a problem using the same SMTP server settings when it comes to sending alert mails so I want to try using a local relay instead. Ideally there would be an addon with a simple interface or config file to specify: - the listening port - whether TLS needs to be enabled or not - the next hop server - the credentials to use for the next hop server I am not looking for a full-blown mail server, just a simple SMTP relay (not reachable from the Internet). Any advice greatly appreciated! Cheers, Mr Snrub
[Request] Sickbeard + Couchpotato + Python (Sparc)
Hi Everyone, I don't normally ask for anything on these forums, and have quietly enjoyed the community. With the recent changes to Usenet and losing of some websites. I am now looking at finally configuring SickBeard/Couchpotato on my ReadyNasDuo V1 (Sparc) However, I find it kind of silly to have to pay for a download of Both modules when the software is free if you were to simply download it for your computer. Especially for the older ReadyNas's So, my request is if anyone has these modules; I would very much like to 'bum' them off of you. I would very much appreciate it.
New Transmission 2.84 add-on for ReadyNAS Duo/NV+ (sparc)
This is a newly compiled version for the Duo straight from source. It has been configured with "--disable-nls --enable-lightweight --enable-utp" and the default web interface port of 9091. If it doesn't work after installation, try rebooting. Not sure if it can be install over the top of super-poussin's version, but if you are planning on uninstalling super-poussin's version then remember to save the torrent files somewhere else first. To quote myself: tarobun wrote: It looks like upgrading from Transmission 2.42 to this Transmission add-on is a no-no. Sounds like there are conflicting configuration that screws up both installs. :( (eg. /c/addons-config) It seems the best approach is to fully uninstall the old, delete the config directory, and then install this add-on. Once you're on this add-on, updating is straightforward and can be done over the existing version. Just a fyi - the default download dir is /var/local/Downloads and there is no username and password with this add-on. If you are prompted for them then the old version was not fully uninstalled. Thanks to super-poussin for the original Transmission add-ons. Enjoy! Transmission_2.73.bin - http://www.mediafire.com/?ajpyyc7ujv54o37 no-utp Transmission_2.75.bin - http://www.mediafire.com/?gbmbhu3hrabf9fe Transmission_2.76.bin - http://www.mediafire.com/?389i53w9w9rtosm Transmission_2.77.bin - http://www.mediafire.com/?pm420vuajaim9bz Transmission_2.80.bin* - http://www.mediafire.com/?5s7dag8ko72doj1 Transmission_2.81.bin* - http://www.mediafire.com/?x4pvvidrgb36df2 Transmission_2.82.bin* - http://www.mediafire.com/?rbctsdae000zoav Transmission_2.83.bin* - http://www.mediafire.com/?31iul25i0t12qda Transmission_2.84.bin* - http://www.mediafire.com/?rh5fge4mc8ahzw4 *if the "Upload" button doesn't work or the "Destination folder" field is blank, reload the webpage.
btsync don't remember settings after reboot.
Hi, I did install btsync and it did work perfect, I did intall the latest version from the dropbox of the dev. Did run it for 2-3 days, then I rebooted the NAS and after reboot btsync forgets the settings. Do some one know how to fix it? I have tried Factory reset, I have tried it with 6.1.5 and 6.1.6 but the same issue is still there. I have a ReadyNAS rn1020 with R6 I guess.
subversion newbie questions
Hi, At the moment I am trying to set up a subversion server on my ReadyNAS312. I have in installed "subversion" 1.6.12 from Steve-O from the "Available Apps" tab on my Readynas. I have a "Projects" directory on my hard disk that I want to store on my SVN server. This directory has multiple projects (let's call them "Project1", "Project2", etc). The first step is to make an exact copy of my project map on the SVN server so I can submit my updates on my NAS. Where can I read detailed information about a step by step guide to get this working? I also want 1 of the project directories to become available to someone that works with me on this project. So he will get access to "Projects\Project3". He should not be able to get access to the other projects. I will only sync my Projects map (with this Project3 map). How can I easily set this up? Sorry for the newbie questions, but I would be very grateful to you if I would get this working. I don't mind reading the how-to guides, but I can't find the how-to guide for the subversion plug-in. Kind regards, Mark Ps. I am using TortoiseSVN on my x64 Win7 computer and I was able to log in with putty into my readynas and I have used "svnadmin" and "chown". Didn't do the apache commands (enabled http on the SVN dir).Mail server add-on for ReadyNAS?
I've looked around a bit but can't seem to locate a mail server add-on for ReadyNAS. It looks like all the components are available, from MySQL for the back-end, to PHP to run a web-based front-end, but nothing to tie it all together. Am I the only one interested in using my ReadyNAS as a mail server?How to update RAIDiator 4.2.28 Virtual Machine to 4.2.31
I use a RAIDiator 4.2 Virtualbox virtual machine to help answer questions that come from here. ( See RAIDiator-x86-4-2-28-VirtualBox-image-notsupported). In that thread, Chirpa stated that "Firmware upgrades via FrontView won't work, would have to copy new root.tlz to boot flash then do an OS re-install." I can confirm that's the case. It will appear to be updating, but will fail and come up with 4.2.28 again. And while there are probably few differences from 4.2.28 to 4.2.31 that would ever make a difference in my usage, I decided to figure out just how to do that, and I succeeded. If anyone is still out there developing apps for 4.2, this could be helpful. I won't go through the trial-failure-try again cycle it took to figure this out, just what did ultimately work. Once I got there, it was that typical Homer Simpson "Doh" moment. I did the work in a Windows 10 environment, but the basics of the process could be performed in another OS, including Linux, if you have suitable tools.. The first thing you need to do is extract the contents of the 4.2.31 update file. After unzipping, the file with no extension is a tarball with a 4000(Hex) byte header. I used a hex editor to remove the header (UltraEdit is my tool of choice for such things, but it is a paid program). Basically, you remove everything down to the first file name csums.md5, then save with the extension .tar. Next, use your tool of choice (mine is 7Zip) to extract the contents of the .tar file. Before you do anything else, make a copy of the entire VM folder, just in case you mess up and need to go back. Next, you need to be able to work with the RAIDiator-x86-4.2.28-disk1.vmdk file, which serves as the "flash memory" of the virtual NAS. I converted it to a .vhd using VMDK2VHD (Google it, it's available from several sites). Then, Windows 10 can mount the .vhd as a drive (right-click and mount). Before you do that and go any farther, though, I recommend that you change Disk1 in your VM to use the converted .vhd and verify is still boots. Using a .vhd file is easier, but another way (maybe more useful for those working outside Windows) would be to mount the .vhdk as an additional drive in a Windows or other virtual machine. VirtualBox will complain that it has already registered that drive's UUID, so you have to change it. Go to your VirtualBox installation folder in a command window and execute vboxmanage internalcommands sethduuid "<fully qualified path to the Disk1 .vhdk>", which will change the UUID to a different random one. After you have mounted it in the Windows VM, you'll need to change the UUID again so the NAS VM will not complain, and you may have to remove and re-attach the file to the NAS VM (I didn't go far enough down this path to see). The "flash memory" is DOS formatted, so you don't need to have any special tools to view or change the content if you have mounted it in Windows using one of these methods. So, now that it's a virtual drive on your Windows machine or VM, it's time to do the magic. You need to delete the old root.tlz and put in the new one from the update file. (That's the OS in an .lzma file, BTW.) You also need to edit csums.md5 and replace the hash code for root.tlz with the one in the cums.md5 from 4.2.31. As always when working with Linux files in a Windows environment, use an editor that doesn't mess with the formatting (again, I use UltraEdit). Don't just copy csums.md5 or any other files from the update into the flash image -- I think they are actually from OS6, not OS4.2, so the ones from OS4.2 will make your VM not boot. Next, you need to edit syslinux.cfg and change default Normal to default OSReinstall. Note that this is likely case sensitive. Now, just unmount the .vmdk or .vhd from Windows and boot the NAS VM (note above instructions on re-assigning UUID again if you used that method). If you've set up RAIDar to be able to see the VM, you should see it shows the NAS status as "Updating". Then, the VM will go offline. I think that's where it's supposed to re-boot, but it doesn't. Which is good, because it would just update again. So, forcibly shut down (not reboot) the VM with Virtualbox. If you don't have RAIDar up to see the NAS status, make sure you wait long enough for an update. Unfortunately, there is no indication of what's going on on the VM's display. Now, using the same process to edit the contents of the "flash", go back and change the default in syslinux.cfg back to Normal. Boot the VM, and you are running OS4.2.31. Note that like all OS re-installs, network configuration is changed to DHCP and the admin password is reset. It turns out it is reset to "password", not the typical "netgear1" for OS4.2. I'm not sure if Netgear finally changed that or if it's because the boot kernel and initrd.gz in flash are actually from OS6. This took me a bit to figure out (I ultimately just guessed correctly that it happened), so remember it. Note that before I figured this process out, I tried replacing the disk2 .vmdk with an empty one to force a Factory Default. It seemed to work, but no volume was created and none could be created (at least via Frontview). I suspect that's either because of the OS6/OS4.2 hybrid system or a safeguard Netgear has in the OS to prevent a VM's use as a real NAS with suitably large virtual drives. The OS definately recognizes that it's running in VirtualBox (just as it recognizes it's running on real ReadyNAS hardware from the motherboard bios, most likely). So, don't try that. If you have never had a 4.2 VM, make sure you have one running 4.2.28 before moving to the update.
