Unfortunately no one can be told what fun_plug is - you have to see it for yourself.
You are not logged in.
Pages: 1
HELP - please. I am having problems with file permissions and I am not able to access fun plug by telnet, ssh, or removing associated files all access denied, connection refused, connection reset. I can ftp to DNS using the basic. Also I cannot add or delete files/folders or change file permissions - all denied. I can see files and read them, but cannot save to the DNS where ALL my files are and need to be able to. All was working great using Win7 x64 (prev upgraded from Vista SP2 x64) until I had upgraded dlink firmware to 1.09 from 1.07 then back to 1.07 having file access issues then having further issues after reverting back to original firmware and all is a disaster. I can't even see my drive(s) using a ext2/3 using a external USB drive adapter removing the drives from the NAS. Does any of the fun plug or assoc other programs reside in the firmware of the NAS, if so, how do I reset it or/and do I need to remove the files for fun plug and all which currently I am unable to do. I can make and create directories and transfer some files yet not always able to open them using Filezilla in ftp 21 mode. A variety of file attrib are present and I want at least to FORCE change somehow all permissions to 777.
Offline
create a new fun_plug with chmod -R 777 /mnt/* in it and restart?
resetting the firmware will not change any permissions on the disk.
Offline
I have downloaded fonz's simple fun plug and have managed to place it on the root of drive rebooting and the .tgz not being picked up and converted. I want to make sure is it that you mean or create something which I'll need a little help on. As of yet, I am not able to change any permissions as the SSH that as of late has been corrupted has taken over my drive and apparently permissions and performing chmod on the unit is not good now. What do you put in the *, is it the drive number. A bit rusty with all this. I was able to change the parent folder names of etch and ffp, but no subfolders. Do I try and do anything with the hidden root files .lpd and/or .system... that has samba related entries? Do you have a link or other? I believe nothing happens in the DNS firmware other than the software is initiated on boot. Was hoping an easy way to see the files and delete them with the drives apart from the DNS on a USB adapter yet has not worked out despite lengthy attempts. Sure do appreciate the reply all what you can offer.
Last edited by kawika6 (2010-10-07 23:00:56)
Offline
Type the "*" as is. It is a wildcard that will change all files and directories. The -R causes it to parse all subdirectories.
To be sure, I'd do both the following:
chmod -R 777 /mnt/HD_a2/*
chown -R nobody /mnt/HD_a2/*
Repeat for HD_b2 if a second disk is installed.
As mentioned in the next post, this will open up everything. Once you get access though, you can go about properly reconfiguring and turning off things that you do not need. Some of the services won't start unless configured anyway. Or, specify the directory names if you know them.
Last edited by FunFiler (2010-10-08 05:31:35)
Offline
This is not the greatest of ideas.
For one thing, making all the ffp/start files executable will start all the ffp services on the next reboot, which you may not want.
That command also would mess with files in /mnt/HD_a4, which is used by the firmware. There could easily be files in there that depend on the owner being other than nobody and/or the file permissions being set a certain way.
If the user has something else mounted in /mnt, you've just hosed that as well.
The user data volume is /mnt/HD_a2. I would first restrict any changes to there. And further, change the perms and ownership only in directories that hold user data, and not system files like ffp stuff, etch, and optware.
So,
cd /mnt/HD_a2
For each directory that you want to fix:
chmod -R 777 <directory name>
I suggest just picking one of your "user data" directories, run the chmod on that, and see if it helped.
Offline
Thanks to Funfiler and karlrado. karlrado what method you recommend the best way to perform as you suggested as currently I'm unable being 'locked' out having assess denied or that you do not have permission - see your administrator apparently by the working albeit corrupted login/pass-worded ssh.
I have tried Filezilla via ftp, unable to telnet being locked out by ssh not being able to log in and unable to perform by windows explorer or through command line to the drive.
If there was a way to view the drive being ext2/ext3 (yet viewable by the windows GUI apparently as NTFS files [or are they pseudo NTFS files]) apart from the DNS ... all the same, could I simply delete the files and all would be resolved needing to just reinstall ffp, or in your case fun_plug: utelnet + optware to restore telnet or would I damage something removing files affecting HD_a4 (what does HD-a4 refer to - a drive or partition or a location in the firmware.
BTW, is ffp (fonz) the same as fun_plug or different.
Thanks so much.
Offline
ffp = Fonz's Fun Plug - A specific package of software
fun_plug = generic name for a file that runs automatically as part of the firmware. This could be Fonz's code, your own code or something else.
Offline
kawika6 wrote:
Thanks to Funfiler and karlrado. karlrado what method you recommend the best way to perform as you suggested as currently I'm unable being 'locked' out having assess denied or that you do not have permission - see your administrator apparently by the working albeit corrupted login/pass-worded ssh.
I have tried Filezilla via ftp, unable to telnet being locked out by ssh not being able to log in and unable to perform by windows explorer or through command line to the drive.
If there was a way to view the drive being ext2/ext3 (yet viewable by the windows GUI apparently as NTFS files [or are they pseudo NTFS files]) apart from the DNS ... all the same, could I simply delete the files and all would be resolved needing to just reinstall ffp, or in your case fun_plug: utelnet + optware to restore telnet or would I damage something removing files affecting HD_a4 (what does HD-a4 refer to - a drive or partition or a location in the firmware.
BTW, is ffp (fonz) the same as fun_plug or different.
Thanks so much.
OK, so I gather that you are completely locked out, meaning that you cannot modify the files on the disk in any way.
The first step is to disable fun_plug and see if you can get it running without it.
Are you sure that you cannot telnet to the DNS? What happens when you try? Do you get the "busybox" shell that appears dead and does not accept keys? If so, there is a code that you have to type in to make the shell work. See the ffp howto in the wiki. If you can get in with telnet, skip ahead a bit.
The next thing I would try is checking your network access configuration (samba). Can you get to the admin web page? If so, go to Advanced->Network Access and look at the Network Access List. Make sure that there is an entry there that specifies a Share that is R/W. If there isn't one, then create one that is R/W for ALL users. This may let you access the drive R/W from a remote computer and make some modifications. Keep trying things here to see if you can get to the point where you can change the disks from the remote computer. Try changing the FTP configs too and try to get in via FTP. Try making new user accounts if you need to.
If adding a share or fixing FTP does not work, then you'll have to take the disk out and put it in another machine. Ideally, this would be a Linux box. You would just mount the disk so that you can modify it. If all you have is a Windows box, you can get one of those "live" Linux distros that you just boot from CD to run Linux just long enough to fix the disk. Another possibility is to find and install an ext2/ext3 driver for Windows, which I heard just became available. But I would go with the bootable distro. I suppose you can attach the disk via a USB enclosure or plug it in with the SATA cable, internally.
Once you have the ability to change the disk, I would first go in there and just rename the fun_plug script to anything but "fun_plug". That will keep the firmware from running the fun_plug script and doing whatever it was doing. You don't HAVE to delete anything else at this point, but I would probably just delete fun_plug and the ffp directory. If you have a lot of ffp configuration time invested, then just rename both ffp and fun_plug to something different so you can refer to these if you need to. Deleting or renaming these will help prevent permission-related re-installation problems later on. You want to get fun_plug and ffp/ out of the way so that fun_plug does not run and so you can reinstall ffp easily.
Then you might stick the disk back in the NAS and see if you can make shares on it. If you succeed in making a R/W share, you can reinstall ffp or whatever.
If that fails, try upgrading or reinstalling the firmware. This won't modify your data files in the HD_a2 partition. This is unlikely to make a difference unless you purposely wrote stuff back to the flash memory. You would know it if you did it, or if you used that store-password script mentioned in the wiki.
At this point, things should work - you should be able to get to the disk via a share or ftp. Then you can reinstall ffp or whatever.
If not, I would do whatever it takes to backup the data on my disk and then just stick the disk back in the DNS and have the DNS reformat it and start from scratch. But I don't know if I would do this, depending on what happened in the above steps. For example, if I could not get the root account to work due to a password problem, reformatting the disk may not help; the problem is with the password file in the flash. There may be some instructions on the wiki for recovering from this. It would probably involve using the "busybox" telnet which I think has a password-less root account.
If putting the DNS disk in another machine is really hard for you to do, you might try the firmware re-installation before taking the disk out.
That's about all I can offer. I am no expert, since I've never had to do this, but I would do something close to the above if I had to.
I'm a bit unclear on your problem description. Maybe you can write a CLEAR list of what works and what does not, as well as a better description of what happens when something fails. If all that is wrong is a lost/corrupted root password, then the path to repair could be different.
In any case, disabling fun_plug and then getting good root access back is important.
/mnt/HD_a4 is a small (485M on my system with a 1TB disk) partition that the firmware appears to use to store hidden temporary files. This partition is actually on your data hard disk and is set up when the DNS formats the drive. The files in the partition would include printer spool files and samba state files. You should just basically pretend that this partition is not there.
Offline
Hello karlrado - I have spent alot of time delving in all you suggested and nothing working to get the ffp folder off of the drive even when removing the drive and placing it in a windows machine with Sata connections using Ext2fsd.
I was able to mount the drive as ext2 using Ext2fsd, but access denied in deleting or modifying the files/folders even in Safe mode even trying to use Unlocker or FileAssassin. I was able to create a folder though, but how do I use it to reinstall ffp or the lite version of ffp?
BTW, I did find that my network access to the NAS was somehow changed to read-only and changed it back to read-write.
When I attempt to connect to Telnet or SSH, I get a blank 'busybox' shell screen that comes up then goes away stating connection refused not offering opportunity to put in a login or pw being unable to invoke a connection.
Do you know the link for the ffp howto in the wiki regarding the code that you have to type in to make the busybox shell work in reference to above?
Did not have any luck in using the live distros booting from CD for Ubuntu or PCLinusOS-KDE using external USB adapter as I apparently needed drivers for it not seeing the drive at all. I also was unable to mount or see the contents as an internal drive with Ubuntu distro CD only with the volume referred to simply as 'array' - unknown size, type, or volume.
This corrupted SSH folder literally has taken control of my drive and all of the data or most of it.
I have re-upgraded from 1.07 back to 1.09 to no avail.
I am really hesitant to format the drive and copy the files as you mentioned as I may copy and inherit the same problems including any anomaly disparity to format and convert the drive as ext2 outside the DNS unless format the 2nd drive in the DNS mounting it with Ext2fsd then copying the files from the 1st drive leaving out the ffp and associated files - does anyone have input on this?
The ftp access to the NAS does work, but only has limited commands and not able to perform the suggestions like 'chmod, chown, etc' from you and others.
In short, I simply need to get the folder off so I can regain control of my drive and reset all of my file permissions so I can get to and use them. In any case as you said, "... disabling fun_plug and then getting good root access back is important". If there is anything you or others can offer.
Last edited by kawika6 (2010-10-11 22:07:38)
Offline
You have quite a mess here.
The firmware telnet access code is here: http://dns323.kood.org/howto:ffp in the section about the Root User or Shells. You might try to get in that way. If you do, try to rename the fun_plug file or make it non-executable (chmod 666 fun_plug). No need to delete ffp/ unless you are going to reinstall. Since you got this screen to come up, this seems like your best shot. If you do manage to disable fun_plug, reboot and see if things are better.
Have you tried doing a factory reset?
http://dns323.kood.org/howto:hardware_reset
I'm not certain that all your problems are due to ffp. Try doing the hardware reset and then attempt accessing the drives afterwards via Windows shares and/or FTP. Keep in mind that if you do not have your FTP accounts and Network Shares set up correctly, you may have access problems, even if all the data files on your disk are 777. I think that you'll have to set up the shares and ftp access again after the reset anyway.
Are your disks part of a RAID 0 array? That one message you got about an array suggests so. I do not have any RAID experience, so I don't know what it would take to manipulate your disk(s) with another linux box or ext2fsd - it certainly is going to be tougher.
Another thing to consider is that if things are working properly, there should be no need to mess with the file permissions on the data disk. If you copy files from a Windows box to the DNS via the Remote Share, the files should be stored by samba on the disk with the right permissions and ownership. Any difficultly in accessing the files is probably due to the shares being configured incorrectly. Remember, this device is intended to be used WITHOUT the need to hack it or start a shell on it. So if you do all your file transfers via the shares, you shouldn't need to run chmod in a shell or anything like that.
The difficulty arises when people do hack into the box, start a shell, and then download a bunch of files using shell commands. For example, if you install fonz fun plug (ffp) and use wget to grab a bunch of files, the files will usually be owned by root and stored with permissions 644 for files and 755 for directories. Look up the "umask" command to understand why. If you want to let other machines access these files via the shares, you may have to adjust the owner/permissions.
So you might want to think carefully about why you might think you need to chmod/chown your files, if you get the box working again.
Offline
OH MY - oh my ... I did it with your help, all your help from everyone. It worked! Thank you bunches karlrado for you last post.
I had hardware reset the DNS with firmware 1.09 and re-entered all my settings, access, and all that. In doing so, it did force me to reformat and resync Volume_2 (no biggie). I formatted it to ext2 Raid 1 (mirroring) - the same as I had before.
I WAS able to place the 2 needed files (as mentioned previously I was able to place files/folders onto Volume_1 on the DNS) of the full version of ffp v0.5 being able to rename the original (corrupted) ffp folder as 'f' so I could see any changes as per instructions in the first 2 paragraphs at 'http://www.inreto.de/dns323/fun-plug/0.5/' ffp will "overwrite any previous versions including ssh files".
I then restarted the DNS and the new ffp INSTALLED with the new ffp folder being created! I then used 'putty' to telnet to the DNS and voila the telnet shell opened up!!!!!!!!!!
I continued and followed the instructions on 'http://nas-tweaks.net/CH3SNAS:Tutorials/fun_plug' to setup the new login and password for root.
I then followed the information from FunFiler to:
chmod -R 777 /mnt/HD_a2/*
chown -R nobody /mnt/HD_a2/*
replacing the '*' for specific <directories> as you suggested.
I did NOT do "Repeat for HD_b2 if a second disk is installed" ... I just simply reformatted and re-synced (the latter done automatically by the DNS) the Volume_2 disk.
I reset the ssh per instructions on the link above continuing from telnet and all is working.
... and there you have it, I now have full read/write access to all my files and folders - all is fixed! YEAH. Words cannot express.
Cheers to all and especially karlrado.
P.S. There are remnant folders from parent folder renamed 'f' that I seem to be unable to delete not affecting operation despite above - any input.
Last edited by kawika6 (2010-10-12 09:47:42)
Offline
Good Stuff.
I can't explain why you can't remove that 'f' directory. It may have something to do with RAID and what you did or didn't do to the two disks with respect to that directory. My only suggestion if you cannot delete it is to rename it to ".old_broken_ffp" or something so that it stays out of your sight. And check the owner and permissions of 'f' before giving up.
Offline
The permissions are '000' --- --- --- . Not sure how to work past that as file assassin , norton wipe, nor unlocker works. I renamed the file as you mentioned no problem. Sure do want to thank you again. If there is anything else you or someone you know can think of would be great. Not giving in, just it's not something I have to spend alot of time with for the moment.
Offline
Did you simply try
chmod 777 f
and then try to delete it?
Perhaps the 'f' dir was one of the ones you skipped when doing the chmod on the rest of the disk.
Offline
Hummm ... Ahhh my friend - it worked.
I was NOT initially able to remove the directory being in /mnt/HD_a2/ NOT seeing the change in ownership with 'ls -l' or through Windows explorer, yet it appeared as it worked in 'putty' doing:
chmod -R 777 f
chown -R nobody f
then making sure I was in /mnt/HD_a2/ directory after a little research, I did ...
rm -r f
... and it worked. Not sure if I needed to chmod or chown.
This is so cool. Curious where are you from - my being in Maryland USA. Appreciate your help.
Last edited by kawika6 (2010-10-13 06:22:21)
Offline
Pages: 1