Posted: Wed Jan 01, 2014 15:26 Post subject: CIFS - GUI / CLI not working.
Dear folks,
First of all: happy new year to everybody and my best wishes to all of you from Barcelona.
I want to ask if CIFS isn't working in Kong builds, because I'm not able to make it happen from the GUI or CLI.
I have been trying a lot of different options, let me post here some of them and the errors obtained, that not necessary are in the same order, but after a lot of tries I can't remeber the order... (sorry mates)
Option-1 wrote:
insmod cifs
nvram set samba_user="Myuser"
nvram set samba_password="Mypassword"
nvram set samba_domain="Mydomain"
cd /tmp/
mkdir -m 777 /mnt
cd /mnt/
mkdir -m 777 /my-main-shared
cd /my-main-shared/
mkdir -m 777 /Public
mkdir -m 777 /Properties
mount.cifs //myserverpath.mydomain.com/public /tmp/mnt/my-main-shared/Public/ -o
username=$(nvram get samba_user),password=$(nvram get samba_password)
mkdir /tmp/mnt/smbshares/my-main-shared/Properties/
mount.cifs //myserverpath.mydomain.com/properties /tmp/mnt/my-main-
shared/Properties -o username=$(nvram get samba_user),password=$(nvram get
samba_password),domain=$(nvram get samba_domain)
More or less applying the same as the latest above, but adding the port 137, 138, 139, 445
Option-5 (asuming folders are created) wrote:
Trying to upgrade cfis.ko, mount.cifs, nls_base.ko also adding -t at the beginning of the script and many other options.
Outcomes are as follows: wrote:
mount error(22): Invalid argument
Refer to the mount.cifs( manual page (e.g.man mount.cifs)
mount error(2): No such file or directory
Refer to the mount.cifs( manual page (e.g.man mount.cifs)
mount error: cifs filesystem not supported by the system
Refer to the mount.cifs( manual page (e.g.man mount.cifs)
So, does anyone have any suggestion on this matter ?
The builds that I'm using are the mentioned below in my signature. Taking in consideration that for this scenario mainly I'm using the AC66U, because the path of the desired file-server is located in a company POP on where I'm connecting to this POP by VPNC using the DD-WRT as well.
Also as I said at the beginning with the GUI isn't working neither. The configuration there it's so simple and I did follow some post for people that make this happen without any issue.
Many thanks and looking forward for your advices.
Best regards. _________________ 7 x Broadcom BCM5300 chip rev 1 - Asus RT-AC66U ----> v3.0-r31899 giga (04/24/17)
1 x Marvel Armada 385 - LinkSys WRT1900ACS ---------> v3.0-r31899 std (04/24/17)
1 x Marvel Armada 370/XP - LinkSys WRT1900AC -------> v3.0-r31899 std (04/24/17)
1 x QCA IPQ806X - Linksys EA8500 -------------------> v3.0-r31899 std (04/24/17)
1 x Broadcom BCM4709 - Asus RT-AC3200 --------------> v3.0-r30880 std (11/14/16)
1 x ARMv7 Processor rev 0 (v7l) - Asus RT-AC68U ----> v3.0-r30880 std (11/14/16)
1 x ARMv7 Processor rev 0 (v7l) - Linksys EA6900 ---> v3.0-r30880 std (11/14/16)
1 x ARM Cortex-A9 Processor - Net Gear R7000 -------> v3.0-r30880 std (11/14/16)
5 x Broadcom BCM4716 chip rev 1 - Linksys E4200 ----> v24-sp2 (06/07/14) kingkong
1 x Broadcom BCM5300 chip rev 1 - Asus RT-AC66U ----> v24-sp2 (04/01/13) giga
Last edited by Bronk-S on Sat Jan 04, 2014 17:50; edited 1 time in total
I don’t even use dd-wrt, let alone a Kong build. I’m a tomato guy. So all I can add is that the following works for me under tomato:
Code:
mount -t cifs “\\\\<server>\\<share>” -o “username=<username>,password=<password>” “/tmp/somedir”
Granted, mount.cifs should generate the same results, but you just never know how small differences might have negative effects.
Also, note the use of backslashes rather than forward slashes for shares, and the need to escape those backslashes. Should forward slashes work w/ Windows? Beats me, but I avoid them if it’s something that’s going to be passed to a Windows environment.
Hi eibgrad,
Thank you so much for your input here and it surprise to me that you aren't a DD-WRT user...
Well, in any case isn't working neither and I don't know what can I do more, but I'm waiting for Kong to integrate VPNC to my new AC68U and I will test from there and see if I'm luck or not...
Many thanks as I said above and I will keep you posted around the outcomes.
Best regards. _________________ 7 x Broadcom BCM5300 chip rev 1 - Asus RT-AC66U ----> v3.0-r31899 giga (04/24/17)
1 x Marvel Armada 385 - LinkSys WRT1900ACS ---------> v3.0-r31899 std (04/24/17)
1 x Marvel Armada 370/XP - LinkSys WRT1900AC -------> v3.0-r31899 std (04/24/17)
1 x QCA IPQ806X - Linksys EA8500 -------------------> v3.0-r31899 std (04/24/17)
1 x Broadcom BCM4709 - Asus RT-AC3200 --------------> v3.0-r30880 std (11/14/16)
1 x ARMv7 Processor rev 0 (v7l) - Asus RT-AC68U ----> v3.0-r30880 std (11/14/16)
1 x ARMv7 Processor rev 0 (v7l) - Linksys EA6900 ---> v3.0-r30880 std (11/14/16)
1 x ARM Cortex-A9 Processor - Net Gear R7000 -------> v3.0-r30880 std (11/14/16)
5 x Broadcom BCM4716 chip rev 1 - Linksys E4200 ----> v24-sp2 (06/07/14) kingkong
1 x Broadcom BCM5300 chip rev 1 - Asus RT-AC66U ----> v24-sp2 (04/01/13) giga
Joined: 14 Jan 2009 Posts: 406 Location: AB, Canada
Posted: Wed Aug 20, 2014 8:52 Post subject:
This problem seems to be fixed in latest kong builds, however they have a rebooting problem so I have been looking for a solution myself (in my case with 24345 build). After hours of research I found that there should be an option passed to mount: sec=ntlm. There is no way to pass this option to the "Automount cifs" found under Administration -> Management, so I disabled it altogether. Here's what I ended up with in Startup script:
[BEWARE: the last 2 line are actually 1 line; this forum decided otherwise]
I don't have any username or passwor on my shares at home, but the options are required and AFAIK if share doesn't require username or password it will take any. _________________
Nethear R6300 v2 - Latest Kong dd-wrt always
Linksys E3000 - Latest dd-wrt always
Asus RT-N56U - OpenWRT trunk
This problem seems to be fixed in latest kong builds, however they have a rebooting problem so I have been looking for a solution myself (in my case with 24345 build). After hours of research I found that there should be an option passed to mount: sec=ntlm. There is no way to pass this option to the "Automount cifs" found under Administration -> Management, so I disabled it altogether. Here's what I ended up with in Startup script:
[BEWARE: the last 2 line are actually 1 line; this forum decided otherwise]
I don't have any username or passwor on my shares at home, but the options are required and AFAIK if share doesn't require username or password it will take any.
Hi m00nman,
I'm on holidays and I will return back on Sunday, then Monday I will post the outcomes from your script.
I have in the AC68/7U the build created arpund 14-17 of April 23900M so as per the number that you mentioned should be close to yours.
Many thanks for your help, much appreciated.
Best regards. _________________ 7 x Broadcom BCM5300 chip rev 1 - Asus RT-AC66U ----> v3.0-r31899 giga (04/24/17)
1 x Marvel Armada 385 - LinkSys WRT1900ACS ---------> v3.0-r31899 std (04/24/17)
1 x Marvel Armada 370/XP - LinkSys WRT1900AC -------> v3.0-r31899 std (04/24/17)
1 x QCA IPQ806X - Linksys EA8500 -------------------> v3.0-r31899 std (04/24/17)
1 x Broadcom BCM4709 - Asus RT-AC3200 --------------> v3.0-r30880 std (11/14/16)
1 x ARMv7 Processor rev 0 (v7l) - Asus RT-AC68U ----> v3.0-r30880 std (11/14/16)
1 x ARMv7 Processor rev 0 (v7l) - Linksys EA6900 ---> v3.0-r30880 std (11/14/16)
1 x ARM Cortex-A9 Processor - Net Gear R7000 -------> v3.0-r30880 std (11/14/16)
5 x Broadcom BCM4716 chip rev 1 - Linksys E4200 ----> v24-sp2 (06/07/14) kingkong
1 x Broadcom BCM5300 chip rev 1 - Asus RT-AC66U ----> v24-sp2 (04/01/13) giga
This problem seems to be fixed in latest kong builds, however they have a rebooting problem so I have been looking for a solution myself (in my case with 24345 build). After hours of research I found that there should be an option passed to mount: sec=ntlm. There is no way to pass this option to the "Automount cifs" found under Administration -> Management, so I disabled it altogether. Here's what I ended up with in Startup script:
[BEWARE: the last 2 line are actually 1 line; this forum decided otherwise]
I don't have any username or passwor on my shares at home, but the options are required and AFAIK if share doesn't require username or password it will take any.
Hi m00nman,
Confirmed it works in the build 23900 in a AC68U model.
Right now I need to leave, but I will test if works in the AC66U.
I see a good thing that appears in the Samba tab to be added as a disc which is exactly what I want.
Many thanks for your input it's really much appreciated.
Best regards. _________________ 7 x Broadcom BCM5300 chip rev 1 - Asus RT-AC66U ----> v3.0-r31899 giga (04/24/17)
1 x Marvel Armada 385 - LinkSys WRT1900ACS ---------> v3.0-r31899 std (04/24/17)
1 x Marvel Armada 370/XP - LinkSys WRT1900AC -------> v3.0-r31899 std (04/24/17)
1 x QCA IPQ806X - Linksys EA8500 -------------------> v3.0-r31899 std (04/24/17)
1 x Broadcom BCM4709 - Asus RT-AC3200 --------------> v3.0-r30880 std (11/14/16)
1 x ARMv7 Processor rev 0 (v7l) - Asus RT-AC68U ----> v3.0-r30880 std (11/14/16)
1 x ARMv7 Processor rev 0 (v7l) - Linksys EA6900 ---> v3.0-r30880 std (11/14/16)
1 x ARM Cortex-A9 Processor - Net Gear R7000 -------> v3.0-r30880 std (11/14/16)
5 x Broadcom BCM4716 chip rev 1 - Linksys E4200 ----> v24-sp2 (06/07/14) kingkong
1 x Broadcom BCM5300 chip rev 1 - Asus RT-AC66U ----> v24-sp2 (04/01/13) giga
Confirmed it works in the build 23900 in a AC68U model.
Right now I need to leave, but I will test if works in the AC66U.
I see a good thing that appears in the Samba tab to be added as a disc which is exactly what I want.
Many thanks for your input it's really much appreciated.
Best regards.
Hi m00nman,
In the AC66U build: 23900M the module: fscache isn't loaded well and it appears the following message:
insmod: fscache.ko: module not found
I don't have idea how to add this module. From there I have been trying to add the share disc anyway and it keeps waiting, but never implemented.
In a E900 all the modules are being added well, but the disc aren't loaded although that it finishes well the script. I'm looking after a df -h or in the GUI - Samba and nothing appears at all.
Many thanks and if you have any option to load the module not working in AC66U will be much appreciated.
Best regards. _________________ 7 x Broadcom BCM5300 chip rev 1 - Asus RT-AC66U ----> v3.0-r31899 giga (04/24/17)
1 x Marvel Armada 385 - LinkSys WRT1900ACS ---------> v3.0-r31899 std (04/24/17)
1 x Marvel Armada 370/XP - LinkSys WRT1900AC -------> v3.0-r31899 std (04/24/17)
1 x QCA IPQ806X - Linksys EA8500 -------------------> v3.0-r31899 std (04/24/17)
1 x Broadcom BCM4709 - Asus RT-AC3200 --------------> v3.0-r30880 std (11/14/16)
1 x ARMv7 Processor rev 0 (v7l) - Asus RT-AC68U ----> v3.0-r30880 std (11/14/16)
1 x ARMv7 Processor rev 0 (v7l) - Linksys EA6900 ---> v3.0-r30880 std (11/14/16)
1 x ARM Cortex-A9 Processor - Net Gear R7000 -------> v3.0-r30880 std (11/14/16)
5 x Broadcom BCM4716 chip rev 1 - Linksys E4200 ----> v24-sp2 (06/07/14) kingkong
1 x Broadcom BCM5300 chip rev 1 - Asus RT-AC66U ----> v24-sp2 (04/01/13) giga
Joined: 14 Jan 2009 Posts: 406 Location: AB, Canada
Posted: Tue Sep 09, 2014 9:52 Post subject:
It may have the module built into the kernel. I don't know. I only did it on the R7000.
The way to find out is to disable cifs mount feature in the GUI. Login to ssh and run "lsmod". Enable the CIFS in the gui and run "lsmod" again. Compate the two outputs and see which modules need to be loaded.
Also while you have it enabled in the gui try mounting manually in an ssh session with:
You might just want to enable CIFS in the gui so all the modules are loaded automatically and just have the mount in the script. Just make sure to have enough delay (say 30 sec?) _________________
Nethear R6300 v2 - Latest Kong dd-wrt always
Linksys E3000 - Latest dd-wrt always
Asus RT-N56U - OpenWRT trunk
manual page (e.g.man mount.cifs)
So all I can add is that the following works for me under tomato:
