DSM-G600, DNS-3xx and NSA-220 Hack Forum

Unfortunately no one can be told what fun_plug is - you have to see it for yourself.

You are not logged in.

Announcement

#1 2011-02-22 01:52:09

neerav
Member
Registered: 2011-01-16
Posts: 15

Can the DNS-321 "mount" a share found on the network?

After much research, I bought the DNS-321 but before I truly understood the power of fun_plug and the DNS-323's ability to mount external USB drives.

Would it be possible for the DNS-321 to "mount" shares/drives found elsewhere in the home network through SMB and/or AFP?  Why?  So that my entire network's shares are accessible at one location.  Administering the shares, controlling access, setting Rsync backups of important files would be easier.  I would also be able to have one drive appear as a directory in another.  External access to my files are also simplified as they would appear to be in one location.

As servers, I have the DNS-321 and a Mac OS X 10.4 which has three external USB drives.  All drives/shares accessible through both AFP and SMB.  I access these servers from multiple other Macs and Windows machines in the network.  I was thinking that one protocol would be just for communicating drives/shares between the servers.  The other protocol would be for the network machines to access the shares.  So there wouldn't be doubled shares visible.

Is this doable?


Neerav
DNS-321 • 2 x 2TB WD20EADS in standard mode • ffp 0.5

Offline

 

#2 2011-02-22 09:44:28

Uriens
Member
Registered: 2008-05-17
Posts: 13

Re: Can the DNS-321 "mount" a share found on the network?

Hi,

with your installed ffp 0.5 you can simply mount a network share over SMB via "mount -t smbfs -o username=XXX //10.0.01/test /mnt/share".
If you want to have that persistent, copy the line to the start procedure...

Cheers

Offline

 

#3 2011-02-22 18:16:28

neerav
Member
Registered: 2011-01-16
Posts: 15

Re: Can the DNS-321 "mount" a share found on the network?

Code:

root@Dlink-NAS:~# mkdir /mnt/M3FA750
root@Dlink-NAS:~# mount -t smbfs -o username=user //192.168.3.102/M3_FA_750 /mnt/M3FA750
mount: mounting //192.168.3.102/M3_FA_750 on /mnt/M3FA750 failed: No such device

I KNOW the SMB share exists because I can see and browse it in Windows.  I can also mount it on the Mac through the Go -> Connect to Server... menu option, entering smb://192.168.3.102 and choosing the M3_FA_750 share. And through the Mac terminal:

Code:

> mkdir /Volumes/M3FA750
> mount -t smbfs //user:password@192.168.3.102/M3_FA_750 /Volumes/M3FA750

However, the same thing on the NAS:

Code:

root@Dlink-NAS:~# mkdir /mnt/M3FA75
root@Dlink-NAS:~# mount -t smbfs //user:password@192.168.3.102/M3_FA_750 /mnt/M3FA75
mount: mounting //user:password@192.168.3.102/M3_FA_750 on /mnt/M3FA750 failed: No such device

Further investigating: Something screwy in ping-land:
1) Mac laptop to Mac server, NAS and Windows: ok
2) Mac server to NAS, Mac Laptop, Windows: ok
3) Windows to Mac server, mac laptop, NAS: ok
4) NAS to Mac laptop, Windows: ok
5) NAS to Mac server: FAIL

Huh, what, why?  Any suggestions as to why the NAS cannot see only the Mac server?

Update, after doing even more forum searches:

Code:

root@Dlink-NAS:~# /bin/mount -o username=user,password=pass -t smbfs //192.168.3.102/M3_FA_750 /mnt/M3FA750
mount: unknown filesystem type 'smbfs'
root@Dlink-NAS:~# cat /proc/filesystems
nodev    sysfs
nodev    rootfs
nodev    bdev
nodev    proc
nodev    sockfs
nodev    usbfs
nodev    pipefs
nodev    anon_inodefs
nodev    futexfs
nodev    tmpfs
nodev    inotifyfs
nodev    devpts
    ext3
    ext2
    squashfs
nodev    ramfs
    minix
nodev    nfs
nodev    rpc_pipefs

A search in the forum show a person using a cifs kernel on a DNS-323 to "fix" the problem.  I'm afraid to try it on the DNS-321 without guidance and knowing more about consequences or even hope that cifs will "mount" a smb share.

Another update:

Code:

root@Dlink-NAS:/ffp/lib/modules# wget http://dns323.kood.org/forum/attachment.php?item=467
root@Dlink-NAS:/ffp/lib/modules# mv attachment.php\?item\=467 cifs.1.50.ko
root@Dlink-NAS:/ffp/lib/modules# chmod 755 cifs.1.50.ko 
root@Dlink-NAS:/ffp/lib/modules# insmod cifs.1.50.ko
insmod: cannot insert 'cifs.1.50.ko': invalid module format

So I guess that answers the question of whether that solution would work on my DNS-321.

Last edited by neerav (2011-02-22 19:46:36)


Neerav
DNS-321 • 2 x 2TB WD20EADS in standard mode • ffp 0.5

Offline

 

Board footer

Powered by PunBB
© Copyright 2002–2010 PunBB