Linux/File Server - Revision history

Admin: /* Related */

2016-03-13T23:37:38Z

← Older revision		Revision as of 23:37, 13 March 2016
Line 195:		Line 195:

	Other related pages:		Other related pages:

			[[Linux/Networking]]

			[[Linux/SSH]]

	[[Linux/Samba]]		[[Linux/Samba]]
Line 203:		Line 207:
	{{NetworkingFlag}}		{{NetworkingFlag}}
	{{UnixFlag}}		{{UnixFlag}}
			{{LinuxNetworkingFlag}}

Admin: /* Related */

2016-03-13T20:03:30Z

← Older revision		Revision as of 20:03, 13 March 2016
Line 197:		Line 197:

	[[Linux/Samba]]		[[Linux/Samba]]

			[[Linux/Automount Network Shares]]


	{{NetworkingFlag}}		{{NetworkingFlag}}
	{{UnixFlag}}		{{UnixFlag}}

Admin: /* Mounting NFS */

2016-03-13T20:00:55Z

Mounting NFS

← Older revision		Revision as of 20:00, 13 March 2016
Line 178:		Line 178:
	<pre>		<pre>
	$ umount /mnt/docs		$ umount /mnt/docs
	</~~per~~>		</pre>

	==Mounting Samba==		==Mounting Samba==
Line 191:		Line 191:
	mount -t cifs // 10.5.5.5/documents -o username=dummy /mnt/samba/documents		mount -t cifs // 10.5.5.5/documents -o username=dummy /mnt/samba/documents
	</pre>		</pre>




	=Related=		=Related=

Admin: /* Related */

2016-03-13T20:00:37Z

← Older revision		Revision as of 20:00, 13 March 2016
Line 158:		Line 158:
	$ exportfs -a		$ exportfs -a
	</pre>		</pre>


			=Mounting Filesystems=

			==Mounting NFS==

			To mount an NFS share being shared by a server at 10.5.5.5, you would run:

			<pre>
			$ # if the NFS root is not set:
			$ mount -t nfs 10.5.5.5:/exports/docs /mnt/docs

			$ # if the NFS root is set:
			$ mount -t nfs 10.5.5.5:/docs /mnt/docs
			</pre>

			to unmount:

			<pre>
			$ umount /mnt/docs
			</per>

			==Mounting Samba==

			<pre>
			mount // 10.5.5.5/documents -o username=dummy /mnt/samba/documents
			</pre>

			We can also set options, like specifying the filesystem using the -f flag. For example, if we wanted to specify CIFS for the filesystem type:

			<pre>
			mount -t cifs // 10.5.5.5/documents -o username=dummy /mnt/samba/documents
			</pre>

Admin at 19:48, 13 March 2016

2016-03-13T19:48:24Z

← Older revision		Revision as of 19:48, 13 March 2016
Line 159:		Line 159:
	</pre>		</pre>


			=Related=

			Other related pages:

			[[Linux/Samba]]


	{{NetworkingFlag}}		{{NetworkingFlag}}
	{{UnixFlag}}		{{UnixFlag}}

Admin: /* mounting NFS */

2016-03-13T19:47:34Z

mounting NFS

← Older revision		Revision as of 19:47, 13 March 2016
Line 133:		Line 133:
	</pre>		</pre>

			===editing idmapd.conf===

			Now edit the <code>/etc/idmapd.conf</code> file to set some options:

			uncomment this line

			<pre>
			# Domain = local.domain
			</pre>

			Now start the nfs daemons:

			<pre>
			$ service nfs-kernel-server start
			</pre>

			the network shares should be shared and good to go.

			If you edit <code>/etc/exports</code>, you can restart the NFS daemon and it will share any new stuff that you've added.

			Alternatively, you can activate new exports wtihout restarting NFS (and potentially interrupting connections) by running the command:

			<pre>
			$ exportfs -a
			</pre>

Admin: /* mounting NFS */

2016-03-13T19:44:58Z

mounting NFS

← Older revision		Revision as of 19:44, 13 March 2016
Line 118:		Line 118:

	Once an NFS export is available to a local machine, it can be mounted by a user.		Once an NFS export is available to a local machine, it can be mounted by a user.

			Here, the remote machine running the NFS server is located at 10.5.5.5.

	If the server is created without the <code>*(ro,fsid=0)</code> option set, they must know the full path to the share on the remote machine, and mount it by executing the following command.		If the server is created without the <code>*(ro,fsid=0)</code> option set, they must know the full path to the share on the remote machine, and mount it by executing the following command.

	~~Here, the remote machine running the NFS server is located at 10.5.5.5.~~

	<pre>		<pre>
	$ mount 10.5.5.5:/exports/images /mnt/images		$ mount 10.5.5.5:/exports/images /mnt/images
	</pre>		</pre>

			If the <code>*(ro,fsid=0)</code> option is set, the user does not need to know the full path, and can mount the directory that is on the remote machine at <code>/exports/images</code> by just using the <code>images/</code> path.

	<pre>		<pre>

Admin: /* configuring nfs server */

2016-03-13T19:43:16Z

configuring nfs server

← Older revision		Revision as of 19:43, 13 March 2016
Line 26:		Line 26:
	</pre>		</pre>

	~~add~~ nfs to ~~list of startup services~~:		WARNING WARNING WARNING this will start NFS services immediately upon install.

			Disable NFS service:

			<pre>
			$ service nfs-kernel-server stop
			</pre>

			Disable the NFS startup script:

			<pre>
			$ update-rc.d -f nfs-kernel-server remove
			</pre>

			to re-enable it:

	<pre>		<pre>
	$ ~~systemctl enable~~ nfs-kernel-server		$ update-rc.d nfs-kernel-server defaults
	</pre>		</pre>

	warning: this will add nfs to the startup sequence. don't forget that you have added this, and then go visit a hostile environment and share all of your files accidentally.		warning: this will add nfs to the startup sequence. don't forget that you have added this, and then go visit a hostile environment and share all of your files accidentally.

	===making stuff to share===		===making stuff to share===

Admin: /* sharing with specific computers */

2016-03-13T19:41:43Z

sharing with specific computers

← Older revision		Revision as of 19:41, 13 March 2016
Line 83:		Line 83:
	Now it is accessible to computers on two networks.		Now it is accessible to computers on two networks.

	===sharing with specific computers===		===sharing files with specific computers===

	If you don't want to share your files with an entire network, you can be more specific - giving a single node or a list of nodes. Editing the <code>/etc/exports</code> file, you can do this:		If you don't want to share your files with an entire network, you can be more specific - giving a single node or a list of nodes. Editing the <code>/etc/exports</code> file, you can do this:
Line 101:		Line 101:
	</pre>		</pre>

			==mounting NFS==

			Once an NFS export is available to a local machine, it can be mounted by a user.

			If the server is created without the <code>*(ro,fsid=0)</code> option set, they must know the full path to the share on the remote machine, and mount it by executing the following command.

			Here, the remote machine running the NFS server is located at 10.5.5.5.

			<pre>
			$ mount 10.5.5.5:/exports/images /mnt/images
			</pre>

			<pre>
			$ mount 10.5.5.5:/images /mnt/images
			</pre>

Admin: /* basics of file servers */

2016-03-13T19:15:57Z

basics of file servers

← Older revision		Revision as of 19:15, 13 March 2016
Line 11:		Line 11:

	sshfs is mostly for sharing files between linux nodes. possible to use with windows. encrypted the same way ssh is encrypted. nothing to configure on the server except ssh. easy to create/drop connections.		sshfs is mostly for sharing files between linux nodes. possible to use with windows. encrypted the same way ssh is encrypted. nothing to configure on the server except ssh. easy to create/drop connections.

			==nfs==

			if you use NFS, you will want to use the latest, version 4. it moved to tcp only (no udp), and is stateful (old version are stateless). this means file locking is part of NFS itself, and not outsourced to another utility. This makes file locking more efficient (but still imperfect).

			If you need to connect to a node running an older protocol, edit the <code>/etc/exports</code> file and list exports. that is, declare the directories on the disk that you are making available (sharing) via NFS.

			===configuring nfs server===

			on debian based systems like ubuntu and kali:

			<pre>
			$ apt-get install nfs-kernel-server
			</pre>

			add nfs to list of startup services:

			<pre>
			$ systemctl enable nfs-kernel-server
			</pre>

			warning: this will add nfs to the startup sequence. don't forget that you have added this, and then go visit a hostile environment and share all of your files accidentally.

			===making stuff to share===

			now you will make a folder containing the files that you want to share over NFS. the recommended method is to create a dedicated directory in root for folders that will be shared via NFS.

			<pre>
			$ mkdir /exports
			$ cd /exports
			$ mkdir docs/
			$ mkdir images/
			</pre>

			===create /etc/exports file===

			Now you will create your list of shared directories in <code>/etc/exports</code>. Start by saving any existing exports file:

			<pre>
			$ mv /etc/exports /etc/exports.default
			</pre>

			Next, edit your export file. One line contains a directory and some options about how it is accessed and by whom.

			<pre>
			/exports/docs 10.5.5.0/24(ro,no_subtree_check)
			/exports/images 10.5.5.0/24(rw,no_subtree_check)
			</pre>

			This sets the directory we are sharing, the network address we are sharing it to, and some options in parentheses. <code>man exports</code> has more info on the options.

			We are sharing these files with any computers on the network 10.5.5.0/24 - which means that anyone outside of that network cannot mount any of these folders.

			Alternative notation:

			<pre>
			10.5.5.0/24
			10.5.5.0/255.255.255.0
			</pre>

			The first is known as CIDR notation (classless inter-domain routing).

			ro = read only, rw = read adn write

			If you need to make the network shares available to multiple networks:

			<pre>
			/exports/docs 10.5.5.0/24(ro,no_subtree_check), 192.168.1.0/24(ro,no_subtree_check)
			</pre>

			Now it is accessible to computers on two networks.

			===sharing with specific computers===

			If you don't want to share your files with an entire network, you can be more specific - giving a single node or a list of nodes. Editing the <code>/etc/exports</code> file, you can do this:

			<pre>
			/exports/docs 10.5.5.151/24(ro,no_subtree_check)
			</pre>

			This shares files with the specific device at ip address <code>10.5.5.151</code>.

			With version 4, NFS can treat a directory as its export root, and create the NFS pseudo-filesystem. This is done by setting <code>fsid=0</code> or <code>fsid=root</code> for the directory, which is done in the C<doe>/etc/exports</code> file.

			<pre>
			/exports *(ro,fsid=0)
			/exports/docs 10.5.5.0/24(ro,no_subtree_check)
			/exports/images 10.5.5.0/24(rw,no_subtree_check)
			</pre>