Attached are the files for Preliminary Network objectives, completed by
Michael B. Weiner.
Please review to see if the tasks are best suited in these two objectives
(or if perhaps another one or two would be appropriate). Please review for
technical accuracy and and completeness.
When reviewing that a topic should be included within an objective that
isn't specifically stated in the task, please review the current
objectives for Level 1 (http://www.lpi.org/p-obj-101.html and
p-obj-102.html).
Great work Michael!
--
Kara Pritchard Phone: 618-398-7360
Author, RHCE Exam Cram
Director of Exam Development http://www.lpi.org/
Site Manager http://www.LinuxUsersGroups.org/
--
---------- Forwarded message ----------
Date: Thu, 7 Jun 2001 12:02:25 -0500 (CDT)
From: [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Preliminary Web Objectives
Attached are some preliminary objectives for Web Services. There is a
*lot* of content we must address here for Apache, and thus these
definitely need flushed out. I'd rather not have just one objective to
cover all the apache related issues, so I attempted to organize into two,
server install/configuration specifics and customization, options, and
such like that. (Though I didn't do a good job, and it needs
re-addressing).
Please review, provide technical detail, and otherwise comment on these.
Again, I'd like us to start filtering out the ambiguity of these
objectives and fill in the gaps.
Thanks.
-Kara
---------- Forwarded message ----------
Date: Mon, 4 Jun 2001 12:45:34 -0500 (CDT)
From: [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Preliminary Kernel Objectives
In order to assist in speedy objective development, I've tried to start
developing some preliminary objectives for our tasks, based on the most
recent organizational structure. (I've only received one response to the
last thread on organizing!)
The objectives are definitely not complete in current form, nor are they
the concrete foundation we're forced to work with. The tasks are our
foundation (also attached). The goal is to create objectives which cover
these tasks and fill in the technical gaps and details.
Our Level 1 objectives
(http://www.lpi.org/http://www.lpi.org/p-obj-101.html and p-obj-102.html)
should provide a good outline for what form and style objectives should be
written in. I've modified slightly (including bullets for specified files
and tools covered) but the rest should be developed in the same fashion as
the current Level 1 objectives. There's no need to obsess over this step
at this stage, as I plan to have this completed in a stage of formal
review.
I would like either comments, changes, and additions as well as assistance
completing (technically) the objectives I've posted; your comments and
submissions for replacement or additional objectives; and your comments
for supplementary objectives (if any).
Please begin by reviewing the current objectives for Level 1 at the URLs
listed above. Next review the task file for this group. Finally, review
the preliminary objectives file and comment. Please note that the
preliminary objectives file associates the current task numbers with the
affiliated objective. Please continue to refer to these task IDs when
commenting, reorganizing, etc. objectives.
I will continue submitting preliminary objective files for various
categories today and tomorrow. I would like good discussion and progress
toward finalizing objectives in progress by Wednesday. By Friday, those of
you interested in the contract positions to finalize objectives should be
able to begin review. By next week, I would like to publish our objectives
for public review and begin collecting preliminary items.
The next 10 days are going to be crazy, and I greatly appreciate your time
and dedication to development. We are moving extremely quickly, and
everyone is very excited about our current developments!
Please contact me if you are available 6/8 - 6/12 for contract objective
review and development. I apologize that this will encompass a weekend,
but it is necessary for succeeding with our current development schedule.
Slots are filling for the Item Writing session planned for the week of
June 18. If you had hoped to participate in this event, please contact me
to discuss availability, expenses, etc. It is likely that a two team
approach (6/18 - 6/20, 6/20 - 6/22) will be used, allowing for flexible
travel arrangements.
--
Kara Pritchard Phone: 618-398-7360
Author, RHCE Exam Cram
Director of Exam Development http://www.lpi.org/
Site Manager http://www.LinuxUsersGroups.org/
--
[3.2.3 3.4.6 3.5.1 3.10.4 3.10.5 3.10.12 3.10.13 3.10.14 3.17.5]
Obj: Basic network configuration.
The candidate should be able to: configure a network device to be
able to connect to a local network, connect to a wide-area network,
communicate between various subnets within a single network, and
configure logging.
Includes tools and files such as:
* /sbin/route
* /sbin/ifconfig
* /sbin/arp
* /usr/sbin/arpwatch
* /etc/sysconfig/network
* /etc/sysconfig/static-routes
* /etc/sysconfig/network-scripts/ifcfg-eth0
[3.10.3 3.11.4 3.16.7 3.16.9 3.17.4]
Obj: Advanced network configuration and trouble shooting
The candidate should be able to: configure a network device to
implement various network authentication schemes, configure a multi-
homed network device, and determine and resolve networking and
communication problems.
Includes tools and files such as:
* /sbin/route
* /sbin/ifconfig
* /bin/netstat
* /bin/ping
* /sbin/arp
* /usr/sbin/tcpdump
* /usr/sbin/lsof
* /usr/bin/nc
3.2.3 lo Disable path MTU discovery
3.4.6 hi Delete routes using 'route del'
3.5.1 Determine the number of addresses in a /0, /1, /2 through /32 network
block
3.10.3 Monitor bandwidth utilization using tcpdump.
3.10.4 Install ippl or other ip-logging tools
3.10.5 Check ippl-log or appropriate logfiles for portscans
3.10.12 Manually define MAC addresses in the ARP cache using 'arp -s'
3.10.13 lo Use 'arpwatch' to get notified automatically when a new host gets
connected to the subnet
3.10.14 Set up a static ARP entry.
3.11.4 Edit /etc/nsswitch.conf to implement different networked system
databases, such as LDAP or NIS; ensure that the PAM configuration is consistent with
the NSS configuration where necessary.
3.15.2 L1 Set up PPP with special user account called PPP
3.16.7 You need to do some network debugging. Use TCPdump to trace packets
between to hosts.
3.16.9 Use telnet or nc to simulate a network protocol connection (such as
SMTP or HTTP) to diagnose problems
3.17.4 Define virtual network devices (eth0:1) using 'ifconfig' to route more
than one subnet through one network device
3.17.5 Setup a Linux server to operate as a gateway between two subnets
