What should a novice Linux network administrator know?

I would not strongly separate the Linux administrator and the administrator. Networks are usually mixed (especially in Russia, Windows is loved for its "free": -) ).

We said above that for practical work, you need to know the commands. But in order to apply them, you need a little theory on general administration and on Linux administration.

Optional need to know:

1. Fundamentals of local area networks.

   Types of networks by size and purpose. Topologies: classification, application, distribution. Standardization of local networks.

2. Technical equipment of the local network.

   Network adapters: wired and wireless. Repeaters, hubs, switches, routers. IP cameras, IP phones, IP printers, access points. Gateways, bridges, firewalls, NAS, and RAID arrays.

3. Communication lines.

   Shielded and unshielded twisted pair. Fiber-optic communication line. Radio frequency devices. Practical work: installation of a communication line.

4. The logical structure of the network.

   Protocols of logical interaction in the local network. TCP/IP protocol v4 and v6. Class and classless addressing, subnet mask.

5. Building a peer-to-peer network.

   Basic methods of building a network. From workgroups to home groups. Manage the list of users. Separation resources in a peer-to-peer network.

6. Disk subsystem and print subsystem.

   Working with hard disks. Working with printers. Differentiation of access to network resources.

7. Building a wireless network.

   Basic methods of building wireless networks. Creating a wireless access point. Security protocols for forming a wireless network.

8. DNS.

   General information about DNS. Formation of a domain zone, connection. DNS server monitoring. Practical work: Configuring the DNS server.

9. DHCP.

   General information about DHCP. Installing and configuring the DHCP server. Manage the DHCP scopes, pool, lease, and reservation.

Linux software for novice administrators provides the following program:

1. Introduction.

   1. A brief history of UNIX and Linux. The GNU project.
   2. General information about the Linux system architecture.
   3. Basic concepts - operating system, shell, console, terminal.
   4. Overview of existing Linux distributions.

2. Install and get started.

   1. What you need to know before installing.
   2. Installing Debian GNU / Linux.
   3. Getting started on Linux.
   4. Local login. Virtual terminals.

3. Management basics in Linux.

   1. Command line interface lines.
   2. Bourne Shell Basics (sh).
   3. Bash: interactive shell.
   4. What are shell scripts.
   5. Process and task management.

4. Getting started.

   1. How to get help - man and info.
   2. Files and directories.
   3. Search for files.
   4. Text processing. Text editor vi.
   5. Manage files via Midnight Commander.

5. Installing and removing programs.

   1. Utilities make, diff, patch.
   2. Installing programs from the source code.
   3. RPM package management system and extension with YUM.
   4. APT package Management system.

6. Working with disks and file systems.

   1. Disk drives in Linux.
   2. Creating disk partitions: fdisk, cfdisk.
   3. File systems in the file: loop device.
   4. Virtual memory (swap).
   5. Linux file systems: Ext2, Ext3, Ext4, ReiserFS, XFS.
   6. Support for" non-native " file systems NTFS, FAT.
   7. Virtual file systems.

7. Administration of user and group accounts. Authorization in Linux.

   1. Access rights.
   2. Authorization users.
   3. User administration.
   4. Password management: passwd.

8. Logging and the Linux kernel.

   1. Logs, their location, and logging of system messages and events.
   2. Interaction with a running kernel-configuring the kernel.
   3. Access to the hardware.
   4. Bootloaders of LILO, GRUB systems.
   5. Managing kernel modules: modprobe, rmmod, lsmod and modinfo.

9. Backup and restore.

   1. General questions. Terminology.
   2. Backup strategies.
   3. Archiver tar.
   4. Direct access to devices - dd.
   5. Packers gzip, bzip2.

10. The Linux boot process and the X Window System graphics system.

    1. The loading sequence. Program init and its functions.
    2. Scenario rc and the SystemV initialization system.
    3. The concept of a service. Manage services.
    4. The architecture of the graphical interface.
    5. Setting up X.org.
    6. Starting X.
    7. Access to remote X servers.

11. Fundamentals of building networks.

    1. Equipment and network topology.
    2. Hierarchy of network protocols. ISO/OSI reference model.
    3. Protocol family TCP/IP. 11. 4 Basics of IP addressing, routing, classes, and subnet masks.

12. Linux network tools.

    1. Configuring network interfaces.
    2. Configuring static routing
    3. Diagnostic tools: ping, traceroute, netstat, tcpdump, lsof.
    4. Remote access - secure shell (OpenSSH).
    5. Syncing files using the utility RSync.

And in general, take the program of an educational course and read about these topics on the Internet. You can also watch a couple of webinars.

Let the copperheads peck me, but I must know this from and to: unixtoolbox.

What will they kill you for? That's right, I couldn't express it so succinctly. Yes, and the RFC is for a beginner-a friend walks wide. Basic commands, a built-for-yourself kernel, installing mc-and go ahead. The main thing is to understand what it is necessary for. If it is purely for self-education, then for a start, it is probably easier to build a network of 2-3 machines, at least on virtualbox.For a very novice administrator, it is still important to understand how the network works - what is a mask, gateway, DNS, nat, bridge, firewall, proxy.

From my experience, I will say that you need to know the tc, because it will be desirable to cut the traffic. Samba, because no one canceled the file server, and backup there is safer. Many people want mail, but everything is simple there. I usually raise SNMP for my subnet. And the above is for my friends-we read all about IPTABLES and SQUID. And the main thing is to know the phone number, ICQ and email of a friend who is ready to help you figure it out, spend your time and effort. For books, this is good, and direct transfer of experience (supported by books) is irreplaceable.

All of the above, especially about the book with the teams-credit. To become a network administrator, you need to start with a Linux enikeyshchik. The command line is the main tool, then you will get tired of doing everything with your hands, you will start writing scripts and automating. There are a lot of services and projects, and the complexity can grow indefinitely (for example, clustering some services). Build a virtual laboratory type so that you can break everything and not get upset. About a friend - very accurately, it will help you not to walk on the street. a rake. The more convenient and good free systems are, the more dangerous they are - what you ask, she will do. The entry threshold is not small.