The local network

It looks like we have similar tasks. True, I have already set up a network in the class :) Tasks, however, can be different: we have something like a peer-to-peer network, but there is no server with a storage of user profiles. Therefore, I describe my experience.

1. In order for computers to communicate with each other, it is really necessary for everyone to register their IP address (if, of course, there is no strict condition for the dynamic allocation of these addresses from the provider or someone else). I recommend giving the teacher’s computer IP, ending in 0, and the rest with numbers, respectively, of each computer in the classroom.
2. To control access and prevent "left" network walking, configure each computer to access the external network through a teacher. You can put Squid on the teacher’s desk (to optimize and control the network output) and bind (especially if the external channel is skinny). You can also put a ftp server (like vsftpd) and a proxy (like Apache) on the teacher’s desk. It makes sense to install a proxy if you want to deploy a site in a local class :) Of course, all student computers need to be configured to go through the teacher’s: browser settings, nameservers (if bind is set), etc.
3. Set up on each student computer ftp access to it and sshd - not to run around the class, but work from the teacher’s place. Very convenient - even the computer can be immediately chopped off by violators :)
4. Pupils are different. We, for example, like to change all sorts of settings, change the background, fonts, etc. or remove applets from cde. To prohibit deleting everything from the desktop, you can arrange the desktop in the desired form and put a ban on the rights to write to the folder / home / school / desktop (school is the login name for students). I did this: I made the icons of the programs I needed for the students on the screen, and for the student files I created links to the folders from Documents on the desktop "7th grade", "8th grade", etc.
5. In the case of KDE (possibly in other systems), it makes sense to lock the desktop and lock the menu bar (prevent changes). However, in some cases it does not help much, but in most cases it is able to stop the attacker :) I think that you can copy the “standard” (or rather, the settings you made as standard) to restore them when you boot, but there are some problems with this (KDE does not always reacts to it adequately). I understand yet.
6. Samba can also be customized. But I had problems with her, so I don’t share my experience yet. In principle, you can do without it (if there is no huge need) :)

Well, there is still a lot of all the little things - setting up each computer for faster work. I think you can find information online on this topic :)

1. It is not clear which operating systems are present in the class ?;
2. If a network of Linux machines for what is recommended Samba? For Linux network it is better to use its native nfs .;
3. Provide more detailed information about the network and the desired results.

• Setting up a LAN connection in Ubuntu Linux
• Local Area Network under Ubuntu 10.04
• Local network in Ubuntu. We connect computers

It would be better to put Samba and less problems!

Connect them to the subnet. Register IPs, etc.