Results 1 to 11 of 11

Thread: a tutorial on how to mount/access a NAS please

  1. #1

    a tutorial on how to mount/access a NAS please

    I have a terastation (a NAS from Buffalo), but I am having difficulty mounting it from wl-500gp/oleg/samba3. I can access it via smbclient and see it via smbtree, but cannot mount it because the firmware does not have smbmount/smbmnt.

    In this post, http://www.wl500g.info/showthread.ph...mbmount&page=2, Oleg states that smbmount is NEVER going to be added to firmware, because mounting windows/samba is rarely used.

    I don't quite understand Oleg's statement. Does he mean there is a better way than smbmount to mount a NAS? If so, what is it?

    I've tried mount.cifs without success. I've also tried the method from newbiefan, http://www.wl500g.info/showpost.php?...0&postcount=24, but the files he provided seems to work only for samba2, but I want samba3 for its support international character support. I've also tried http://riot.org/seb/smbfs_0.0_mipsel.ipk, but it leads to error segmentation.

    Would someone please provide some guidance on how to mount a NAS from a wl-500gp with samba3 installed? Thanks.

  2. #2
    Not a real guide but some tips. I've tried this with Oleg's 1.9.2.7-10 but probably works also with the new firmware version as well.

    Most NASs support NFS (as their firmware is Linux based) and NFS is slightly faster than Samba so try to use NFS if you can. First check, if your NAS supports NFS. Read on if it can.

    Create NFS share in your NAS. As this varies NAS by NAS I cannot help you with this.

    Decide what directory in your router you'd like to mount the NAS. Let's assume it's /mnt.

    Enable NFS in the router's WEB interface (the router will probably restarted after this).

    Insert the NFS kernel module in your router.

    insmod nfs

    This is needed as by default, it's not loaded. The reason for having a separate kernel module that typically it's not used, so it would be just a waste of memory to have it there.

    Mount in your router the share of your NAS.

    In general the command
    mount -t nfs -o rsize=32768,wsize=32768,timeo=14,intr,proto=tcp <the IP address of your NAS>:/the_share_name /the_mount_point_in_your_router(have to exist)

    Let's assume that it's /nas, and your NAS has the IP address of 192.168.1.36 (you have to double check this)

    mount -t nfs -o rsize=32768,wsize=32768,timeo=14,intr,proto=tcp 192.168.1.36:/nas /mnt


    You can learn more about NFS (e.g. why proto=tcp is used, what are the other parameters) from sourceforge FAQ.

    If it works, put it into some script so that it runs automatically after the router starts.

    If there is some firewall between your NAS and the router you need to probably open couple of ports (e.g. in my case I was sharing one directory in Fedora and I had to configure the firewall).
    E.g. I had to open port 111 and 892 in addition to other NFS ports (like 2049).

    If you're unsure what port to open, you can check during the mount, what ports are tried to be opened via Wireshark.

    I hope it helps.
    Last edited by ecaddict; 25-09-2009 at 13:05. Reason: made more descriptive

  3. #3

    some problem

    ecaddict
    Thanks for your detailed reply, but I had two problems.
    1. I tried "insmod nfs" on w-500gp, but received an error message:
    insmod: unresolved symbol rpc_wake_up_task

    2. My NAS (a terastation) seems to have only samba. Is there a way to have smbmount on Asus/Oleg?

    Thanks.

  4. #4

    nfs problem

    Ok, I've enabled NFS from the web interface and got it running. But I am still unable to mount my NAS.

    This is what I have:

    "showmount -e 192.168.2.4"
    Export list for 192.168.2.4:
    /mnt/array1 <anon clnt>
    /mnt/array1/Buffalo 192.168.2.0/255.255.255.0

    but then
    "mount -t nfs -o nfsvers=2,rsize=32768,wsize=32768,timeo=14,intr,pr oto=tcp 192.168.2.4:/mnt/array1/Buffalo ./test"
    mount: mounting 192.168.2.4:/mnt/array1/Buffalo on ./test failed: No such device

    and this is my nfs "exports" file:
    "/mnt/array1/Buffalo 192.168.2.0/255.255.255.0(rw,no_root_squash,anonuid=65534,anon gid=65534)
    /mnt/array1 (ro,insecure,all_squash)"

    Could someone please help? Thanks.
    Last edited by onewiki; 25-09-2009 at 06:00.

  5. #5

    Problem solved and a tutorial available now

    tutorial on mounting a NAS from wl-500gp with samba3
    http://wl500g.info/showthread.php?p=161727#post161727

    now only the outstanding problem is to mount a NAS with nfs.
    Last edited by onewiki; 26-09-2009 at 17:51.

  6. #6
    Quote Originally Posted by onewiki View Post
    now only the outstanding problem is to mount a NAS with nfs.
    In the other thread I suggested to drop the -o cause you weren't using options, but in this thread you are.

    However the syntax for mount is : mount [flags] DEVICE NODE [-o OPT,OPT]

    So your command should be:

    mount -t nfs 192.168.2.4:/mnt/array1/Buffalo ./test -o nfsvers=2,rsize=32768,wsize=32768,timeo=14,intr,pr oto=tcp

    But, I doubt that nfsvers, rsize, wsize, timeo and proto are valid options for "mount", I would just use:

    mount -t nfs 192.168.2.4:/mnt/array1/Buffalo ./test

  7. #7

    no such device

    Thanks, but I did try
    mount -t nfs 192.168.2.4:/mnt/array1/Buffalo ./test
    but the same result.

  8. #8
    I think I found the problem

    nfs.o needs 2 other kernelmodules: sunrpc.o and lockd.o

    So first insmod sunrpc, then insmod lockd and finally insmod nfs

    now it should work...

  9. #9
    DcChair,
    Thanks for helping. But the two modules were already running. If you follow this link to the other thread I mentioned the same problem, you can see the modules that were running on my wl-500gp/oleg.

    http://wl500g.info/showthread.php?p=161727#post161727

    Thanks again.

  10. #10
    hmmm you're right, I didn't completely read that last post.
    I only saw insmod: unresolved symbol rpc_wake_up_task and that's exactly the error you get, when you try to load nfs.o without the other 2 modules.

    Did you mention the firmware version you are running?
    Perhaps a newer firmware is the solution?

    I tried to mount a nfs-share on my laptop running Leopard -> I didn't get the error, but instead i the mount-command hung...
    But then again this might also be a problem on the laptop.

  11. #11
    I have the newest firmware running, (build 617). I am giving up. Thanks for trying.

Similar Threads

  1. Владельцы NAS Qnap TS-*09, есть пара вопросов
    By sda in forum Russian Discussion - РУССКИЙ (RU)
    Replies: 19
    Last Post: 23-01-2015, 06:20
  2. NAS: Create your own caching proxy
    By vinyols in forum WL-500gP Tutorials
    Replies: 8
    Last Post: 24-09-2009, 20:38
  3. NAS Trouble
    By Anonincog in forum WL-500w Q&A
    Replies: 6
    Last Post: 24-07-2009, 21:20
  4. Replies: 2
    Last Post: 02-03-2009, 22:04

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •