1. Understand the role of a network administrator (or a system administrator who must double as a network administrator); understand the job titles, common tasks, certifications, and soft skills required.
2. Describe networking concepts including: the use of protocols, addressing hosts, virtual circuits; packet switching; MTUs, simplex, half and full duplex; point-to-point, unicast, broadcast, and multicast; throughput and bandwidth; autonomous systems; NAT (or PAT or IP Masquerade); multi-homing; and VLANs
3. Describe the history of the Internet; Internet exchange points; common network technologies including Ethernet, TCP/IP, IPv4 and IPv6
4. Understand ISPs and tiers of service and how to pick ISPs
5. Describe additional network technologies and the issues (including uses, security, and cost) about them: ATM (and LANE), DSL, VPN, VoIP, and link aggregation (a.k.a. bonding, IP multipath, EtherChannel, ...)
6. Name network standards bodies (ISO, RFCs, IEEE) and describe their relevance
7. Understand network structures and classifications (and associated issues) including client-server and peer-to-peer (issues: design, security, privacy, naming, etc.), LANs, MANs, and WANs, network topology (physical and logical, token-ring, bus, star, mesh, point-to-point)
8. Use and explain the OSI and TCP/IP network models
9. Name and identify network hardware and their functions: NICs, serial ports, repeaters, bridges, hubs, switches, routers, firewalls
10. Describe the functions of an Ethernet NIC (duplex, bandwidth, promiscuous mode operation, auto-negotiation) and a NIC device driver (Layer 2 implementation (e.g., MAC address assignment), copy packets to/from host RAM, etc.)
11. Identify cabling types and their characteristics, including parallel, ribbon, serial and null-modem, CAT-5, fiber optics, infra-red, and wireless; Identify Ethernet patch cable types and their use: straight, cross-over, and roll-over; understand capacity naming: T# standards, OC# standards, and 802.3 standards' common names (e.g. 10BaseT)
12. Identify physical network layout standards (EIA/TIA 568), including common terminology (MDF, POP, demarc, vertical and horizontal wiring, and catchment area) and network transmission issues (including EMI, RMI, ESD, latency, and cross-talk)
13. Design networks for some common and simple situations; understand why a network expert is needed in most other situations; understand client and server network hardware requirements, including costing and ROI calculations
14. Understand, use, plan, and troubleshoot IPv4 addressing: using binary, hex, and dotted-decimal numbers, network and broadcast addresses, subnet masking (and CIDR)
15. Understand and describe static, dynamic, and zeroconf address assignment, special and reserved IP addresses, provider independent (PI) addresses and multi-homing (with BGP)
16. Understand the basics of IPv6 addressing
17. Install and use Wireshark (formally "Ethereal")
18. Understanding Ethernet: IEEE 802 standards; addressing, protocol limitations, ARP and RARP protocols, installing Ethernet NICs; identifying fields using Wireshark
19. Discuss and understand TCP/IP protocols and concepts: handshake, TCP, UDP, IP, ICMP, ARP, DHCP, and others; identify protocols and fields with Wireshark
20. Understand hostnames, domain names, and name servers, how to use WHOIS database, ICANN and IANA, DNS caching, in-addr.arpa, top-level domain names, root servers, reserved names, how to obtain and register hostnames and domain names
21. Locate, use, and maintain network documentation
22. Identify network service management and policy concepts (e.g., AUP, host naming policy, etc.)
23. Use common network (client) utilities, including ftp, tftp, sftp, scp, ssh, telnet, wget, and links (a non-GUI web browser)
24. Describe other network protocols (such as IPX/SPX and NetBIOS), NETBEUI, AppletTalk
25. Understand network services and port numbers: how they are used and assigned (by the IANA), well-known, registered, and private/dynamic port numbers, the use of the services file, relationship of port numbers to sockets; and identify some common port numbers including 20, 21, 22, 23, 25, 53, 80, 443, 110, 119, 137, 139, 143, 161, and 445 (993 and 995 too, but not for any certification exams I know); and understand RPC and the role of the portmapper daemon
26. Understand routing concepts including: IP forwarding, routing versus routed protocols, routable and non-routable protocols, static and dynamic routing, best path determination, routing tables, default routes, and ICMP redirects; and understand IP routing protocols including a basic understanding of distance-vector, link-state, and policy routing protocols such as RIP, RIP2, OSPF, EIGRP, and BGP; hop-count, TTL, and other route metrics
27. Describe network security concepts including common threats, the basics of IPSec, GRE tunneling, common VPN technologies, centralized (and wireless) access control with Kerberos, RADIUS, and TACACS, packet filtering, service proxies, SOCKS proxies, network intrusion detection and prevention
28. Identify remote access technologies including serial consoles, KVM, PC Anywhere, DS view, VNC, RDeskTop, and XDMCP
29. Describe the basic concepts and issues of Clusters (HA and HP) and grids; and NAS, SAN, AoE, and other storage network technologies
30. Start and stop service daemons; using and configuring inetd and xinetd; monitoring service daemon status with ps, log files, and other tools.
31. Configure NICs with ethtool, mii-tool; /etc/ethers (and related files)
32. Configure the DNS (domain name system) resolver: setting a DNS system in /etc/nsswitch.conf; configuring a default domain name, changing/viewing the hostname using hostname; name server IP address(es), and other options in /etc/resolv.conf; set hostnames and aliases for IPs in /etc/hosts and other OS-specific ways for Red Hat and Debian based Linux distributions, BSD and Solaris Unix; and using other resolver-related files such as /etc/networks, /etc/nodename (or hostname or HOSTNAME), etc.
33. Configure TCP/IP (and IPv6) for Unix/Linux workstations and servers: set NIC to use DHCP and over-ride DHCP server assigned settings, assign static IP to a NIC; use ifconfig; understand and configure IP Alias (virtual interfaces)
34. Configure routing for Unix/Linux workstations and servers; use the route command; configuring a default route; identification of common routing daemons: ripd, zebra, gated, quagga, xorp, in.routed (Solaris), routed (FreeBSD, which also supports gated and zebra); configure zeroconf networking
35. Configure network access controls using TCP Wrappers (libwrap), by using /etc/host.allow and host.deny files; set a mostly-closed policy; identify other ways to implement service access controls including service specific configuration, xinetd, PAM, and firewall rules
36. Troubleshoot TCP/IP network problems using log files, a trouble-shooting methodology, and some common tools including ping, traceroute, telnet, nc (netcat), openssl, netstat, route, ifconfig, Wireshark, tcpdump, and others.
37. Configure name servers including a caching-only server with nscd and BIND, and a primary server and a secondary server with BIND; editing BIND configuration files: named.conf, rndc.conf and rndc.key, zone files (including in-arpa zone); trouble-shooting DNS problems with named-checkconf, named-checkzone, nslookup, dig, and Internet tools such as DNSstuff.com
38. Understand and configure PPP and secure using CHAP, PAP, and MS-CHAPv2; Understand PPPoE and configure ADSL
39. Understand Wi-Fi concepts and configure (on Linux); identify Wi-Fi security issues and simple counter-measures (including captive portals); and describe Wi-Max
40. Modify a simple iptables firewall configuration to enable additional services (or disable services)
41. Understand and configure file sharing services using NFS and Samba
42. Understand and configure common network services such as DHCP, FTP (including anonymous FTP), a basic LDAP server, SSH and telnet
43. Monitor the system and network using various tools and utilities such as log files, netstat, nmap, snort, nagios, SNMP and RMON, and MRTG
44. Understand the basic concepts of and tools for network traffic management and traffic shaping in Linux; understand and configure multi-homing and load balancing without BGP in Linux

Grading scale:  A=90-100,   B=80-89,   C=70-79,   D=65-69,   F=0-64
(Or you can elect to audit the class during the add/drop period.)

• No makeup exams will be offered without the prior approval of the instructor.
• Exams will be closed book and closed note multiple choice exams.  While the exams are non-cumulative, each does build upon knowledge acquired earlier.  Exams are based mostly upon material presented in class however some questions may be from assigned readings (the textbook and on-line resources).
• Exams will never cover material not yet discussed in class.  Should the class fall behind the course schedule some topics shown on the syllabus due for an earlier exam will be tested on the following exam instead.
• Regular attendance is imperative for the successful completion of this class.  The textbook and on-line resources should be considered as required course supplements; in other words the course is not based on the text.
• All phones, pagers, and beepers must be turned off during class time, except with prior permission of the instructor.  No food or drink is permitted in HCC classrooms.
• Attendance will be taken within 5 minutes of the start of class; after 4 absences and/or lateness, the student will lose 2 points off the final grade for each additional occurrence.
• If you miss a class you are still responsible for the material covered in that class.  All students should exchange contact information (name, email address, phone number) with at least one other student in the class.  If you must miss a class, you should then contact another student and request they take class notes for you.  (Note Campus Cruiser has email and discussion board areas for our course.)
• Credit for class participation includes attendance, preparedness, and adding to class discussions by asking questions and participating in discussions.  Playing computer games, surfing the Internet, or working on assignments for this or other classes during class time will lose you credit.
• Additional time outside of class will be required to complete the material.  For typical students an average of between 8 and 12 hours each week outside of class are required for preparation, practice, and projects.
• Students are expected to prepare for each class by completing all reading assignments, reviewing examples and model solutions provided, and practicing outside of class.  This is important — you can't learn a skill such as Unix/Linux administration only by attending class and reading books.  You must practice several hours a few days each week!  If you won't have enough time available, consider auditing the course.
• Working together on individual assignments is considered as cheating!  Turning in someone else's work without giving them credit is also considered cheating (plagiarism).  Cheating will result in an automatic F (zero) for the project for all parties.  Note that some projects may be group projects, where each member of a small group works together on a project.  It is also OK to ask a fellow student for class notes (in the event you miss a class) or for help in understanding the text or material given to the class (e.g., examples on the class website).  It is encouraged to study together as well.
• You must follow the academic honesty policy for HCC.  A second cheating offense will result in an F for the course, and your name will be turned over to the Dean for further handling.  I take these matters very seriously.  You have been warned!
• Communications Policy:  I will respond to your emails within 48 hours or two business days.  HCC policy is that grades can only be discussed in person during office hours, or via email only if you use your assigned HCC HawkNet (or Campus Cruiser) email account.
• Every effort will be made to stick to the weekly schedule for our course.  However it may happen that we will fall behind the schedule at some point.  If so no topics will be skipped.  Instead we will attempt to catch up over the following weeks.
• Please be aware that if we fall behind on the weekly schedule, the topics discussed may not match what shows on the syllabus.  The weekly schedule may (but probably won't be) updated in this case.
• In the case we fall behind, the homework assignments are automatically postponed until we do discuss that topic in class (i.e., the next class).  Projects and in-class exams will not be automatically postponed.  Should your instructor deem it necessary, projects and exams may be rescheduled; this will be announced in class.
• Any changes to this syllabus or weekly schedule will be announced in class.  Additionally changes will be announced via the class RSS feed.
• Late Policies:  Late assignments ( homework assignments, projects, or exams) generally will not be accepted.  An assignment is late if not turned in by the start of class on the day it is due.

  Late assignments will be accepted late only if you obtain the instructor's permission prior to the due date of the assignment, or for a documented serious medical reason.  All late assignments are subject to a late penalty of at least one letter grade (10%) regardless of the reason for the delay.

  Projects and homework assignments later than one week will receive a more severe late penalty; very late assignments without adequate excuses will receive a grade of F (0).  However if you have a very good reason your instructor may waive any or all of the late penalty.  (Examples of good reasons include extended illness that prevents working, or being out of town for work reasons.  Remember documentation will be required.)

Projects will be assigned at various times.  You will have sufficient time to complete the projects.  Although there will be in-class group exercises you must work individually on the non-group projects, typically outside of regular class hours except if a project is designated as a group project.  You may work together in small groups on group projects, provided the names of all who worked together are listed.  Each student must still submit their own copy.

Projects are graded on the following scale:

A = 95% (Excellent: Good design with good comments, style, and extras)
B = 85% (Good: Good design, some comments, readable style, and it works)
C = 75% (Acceptable: Project objectives are met or are close to being met)
D = 65% (Unacceptable)
E = 10-64% (Variable credit: At least you tried)
F =  0% (Didn't hand in the project)

Minor extras worth +5 points, minor omissions or poor design worth -5.

Projects are not graded when turned in.  They are graded all at once, sometime after the project deadline has passed (usually the next weekend).  Further details will be provided with your first project.  (See also submitting assignments below.)