CSS NC II - Core Competencies - UC2
CSS NC II - Core Competencies - UC2
SERVICING NC II
ELECTRONICS SECTOR
Unit of Competency : SET-UP COMPUTER NETWORKS
The unit of competency “Set-up Computer Networks” contains knowledge, skills and attitudes
required for a Computer Systems Servicing NC II qualification.
You are required to go through a series of learning activities in order to complete each of the
learning outcomes of the module. In each learning outcome there are Information Sheets,
Operation Sheets, and Activity Sheets. Follow these activities on your own and answer the Self-
Check at the end of each learning activity.
If you have questions, don’t hesitate to ask your teacher for assistance.
If you can demonstrate to your teacher that you are competent in a particular skill or skills,
talk to him/her about having them formally recognized so you don’t have to do the same training
again. If you have a qualification or Certificate of Competency from previous trainings show it to
your teacher. If the skills you acquired are still current and relevant to this module, they may
become part of the evidence you can present for RPL. If you are not sure about the currency of your
skills, discuss it with your teacher.
After completing this module ask your teacher to assess your competency. Result of your
assessment will be recorded in your competency profile. All the learning activities are designed for
you to complete at your own pace.
Inside this module you will find the activities for you to complete followed by
relevant information sheets for each learning outcome. Each learning outcome may have
more than one learning activity.
MODULE DESCRIPTOR:
This module is designed to enhance the kowledge, skills and attitude of the trainees in
Setting-up Computer Networks.
1. Cable routes are determined and planned in accordance with network design and actual
installation site.
2. Network materials necessary to complete the work are identified and obtained in accordance
with established procedures and checked against systems requirements
3. Tools, equipment and testing devices needed to carry out the installation work are obtained in
accordance with established procedures and checked for correct operation and safety
4. Appropriate personal protective equipment is used and OHS policies and procedures are
followed
5. Copper cable splicing is performed based on Electronic Industries
Alliance/Telecommunications Industry Association (EIA/TIA) standards
6. Network cables and cable raceway are installed in accordance with established procedures and
installation requirements
7. Installation work is performed and is checked to ensure no unnecessary damage has occurred
and complies with requirements
8. OHS standards and 5S principles are followed according to enterprise requirements
9. Excess components and materials are disposed of based on WEEE directives and 3Rs waste
management program.
10. Network connectivity of each terminal is checked in accordance with network design.
11. Any fault or problem in the network system is diagnosed and remedied in line with the
standard operating procedures.
1. Workplace Location
2. Equipment, Tools, Accessories and Supplies
Desktop PC, Laptop and workstations
PPE
CSS NC II Date Developed: Doc. No.: CSS CBLM CORE 2
UC 2 June 2017
Issued by:
NMCCI Page 8 of 59
Setting-up
Developed by:
Computer Networks
JOSEFINO T. HAPITAN
Router / Wi-Fi / Wireless Access Point / Repeater
Software application/Program (CD/DVD)
Multi-Tester
Cables (fiber optic & copper)
Terminals and terminal box
Insulators
Fasteners
Cable raceway/duct
Clamps
Wire stripper with bolt cutter
Pliers (assorted)
Screw drivers (assorted)
Crimping tools
3. Training Materials
OH&S Policies and procedure manual
Practicing 3Rs manual
Network Topology Chart
Network Configuration Manual
Assessment Method:
1. Written exam
2. Practical exam
3. Practical Demonstration
Learning Outcome 1:
Install Network cables
Learning Activities Special Instructions
If you have some problem on the content of the
1. Read information sheet 2.1-1 Network information sheet don’t hesitate to approach
Design your facilitator.
If you feel that you are now knowledgeable on
the content of the information sheet, you can
now answer self-check provided in the
module.
Compare your answer to the answer key 2.1-1
2. Answer Self Check 4.2-1 If you got 100% correct answer in this self-
check, you can now move to the next
information sheet. If not review the
information sheet and go over the self-check
again.
Network Design
Learning Objective:
After reading this INFORMATION SHEET, YOU MUST be able to be familiar with
Computer Network Design.
TECHNICAL TERMS
Bluetooth - wireless connection use to send and received messages
Coverall - apparel suit won to protect the body
E-mail - electronic messages we received via internet
Fax - abbreviation of facsimile; the electronic transmission of copies of documents for
reproduction at a remote location.
PDA - abbreviation for Personal Digital Assistant; a tiny pen-based palm top computer that
combines fax, e-mail and simple word processing into an easy-to-use unit
that fits, into pocket.
Peer-to-peer network – a network architecture in which driver files and printers on every PC can be
available to every other PC on the network.
Server - any computer that makes access to files, printing, communications, or other
services available users of the network.
Computer Network
In general, the term network can refer to any interconnected group or system. More
specifically, a network is any method of sharing information between two systems (human or
mechanical).
In addition to reducing hardware costs by sharing expensive printers and other peripherals
among multiple users, networks provide additional benefits to the users.
Software and data files can be shared for access by multiple users
Electronic mail (email) can be sent and received
Collaboration features allow contributions by multiple users to a single document
Remote-control programs can be used to troubleshoot problems or show new users how to
perform a task
Virtually any storage or output device can be shared over a network, but the most common
devices to be used over a network include:
Printers
Disk drives
CD-ROM and optical drives
Modems
Fax
CSS NC II Date Developed: Doc. No.: CSS CBLM CORE 2
UC 2 June 2017
Issued by:
NMCCI Page 12 of 59
Setting-up
Developed by:
Computer Networks
JOSEFINO T. HAPITAN
Tape backup units
The staff computers (bright green) can get to the color printer, checkout records, and the
academic network and the Internet. All user computers can get to the Internet and the card catalog.
Each workgroup can get to its local printer. Note that the printers are not accessible from outside
their workgroup.
Workgroup of
Computers
Hub
Server
Local Area Network
Although every computer on a LAN is connected to every other, they do not necessarily
mean all communicate with each other. There are two basic types of LAN, based on communication
patterns between the machines, called client/server networks and peer-to-peer networks.
Client/Server Networks
Every computer has a distinct role, that of either a client or a server. A server is designed to
share its resources among client computers on the network. The Client/Server is composed of:
Servers
These are located in secured areas, such as locked closets and data centers, because they
hold the organization's most valuable data and do not have the accessed by operators on a
continuous basis.
The server runs a special network operating system such as: Windows NT Server, Windows
2000 or Novell Netware.
CSS NC II Date Developed: Doc. No.: CSS CBLM CORE 2
UC 2 June 2017
Issued by:
NMCCI Page 13 of 59
Setting-up
Developed by:
Computer Networks
JOSEFINO T. HAPITAN
Clients
- The rest of the computers on the network function as client. A client standard PC that is
running an operating system such as DOS or Windows.
Client
Hub
Server
Example of Client/Server
Peer-to-Peer Network
In a peer-to-peer network, every computer is equal and can communicate with other
computer on a network to which it has been granted access rights. Essentially, every computer in
this network functions as both server and client. Peer-to-peer network can be as small as two
computers as many as hundreds of units.
Internetwork
Two or more networks or network segments connected using devices that operate at layer 3
(the 'network' layer) of the OSI Basic Reference Model, such as a router. Any interconnection among
or between public, private, commercial, industrial, or governmental networks may also be defined as
an internetwork.
In modern practice, the interconnected networks use the Internet Protocol. There are at
least three variants of internetwork, depending on who administers and who participates in them:
Intranet
Extranet
Internet
Intranet
Extranet
An extranet is a network or internetwork that is limited
in scope to a single organization or entity but which also has
limited connections to the networks of one or more other
usually, but not necessarily, trusted organizations or entities (e.g.
a company's customers may be given access to some part of its
intranet creating in this way an extranet, while at the same time
the customers may not be considered 'trusted' from a security
standpoint). Technically, an extranet may also be categorized as
a CAN, MAN, WAN, or other type of network, although, by
definition, an extranet cannot consist of a single LAN; it must
have at least one connection with an external network.
Internet
A specific internetwork, consisting of a worldwide interconnection of
governmental, academic, public, and private networks based upon the
Advanced Research Projects Agency Network (ARPANET) developed by ARPA of
the U.S. Department of Defense – also home to the World Wide Web (WWW)
and referred to as the 'Internet' with a capital 'I' to distinguish it from other
generic internetworks.
SELF-CHECK 2.1-1
I. Identify the following. Choose your answer from the grid below. Use a separate sheet of paper in
answering.
1. Internet
2. Intranet
3. GAN
4. WAN
5. MAN
6. Topology
7. Network
8. LAN
9. Star topology
Conditions:
Cables
Fiber optics
copper
terminals
cable raceway/duct
clamps
fasteners
insulators
terminal box
Assessment Method:
Written exam
Practical examPractical Demonstration
Learning Outcome 1:
Install Network cables
Learning Activities Special Instructions
If you have some problem on the content of
3. Read information sheet 2.1-1 Basic the information sheet don’t hesitate to
Network Infrastructure approach your facilitator.
If you feel that you are now
knowledgeable on the content of the
information sheet, you can now answer
self-check provided in the module.
Compare your answer to the answer key
4. Answer Self Check 4.2-1 2.1-1 If you got 100% correct answer in
this self-check, you can now move to the
next information sheet. If not review the
information sheet and go over the self-
check again.
Let's review the basic network infrastructure on the modern Debian system.
The hostname resolution is currently supported by the NSS (Name Service Switch)
mechanism too. The flow of this resolution is the following.
127.0.0.1 localhost
127.0.1.1 <host_name>
Each line starts with a IP address and it is followed by the associated hostname.
The IP address 127.0.1.1 in the second line of this example may not be found on some other
Unix-like systems. The Debian Installer creates this entry for a system without a permanent
IP address as a workaround for some software (e.g., GNOME) as documented in the bug
#719621.
For a system with a permanent IP address, that permanent IP address should be used here
instead of 127.0.1.1.
For a system with a permanent IP address and a fully qualified domain name (FQDN)
provided by the Domain Name System (DNS), that canonical <host_name>.<domain_name>
should be used instead of just <host_name>.
The "/etc/resolv.conf" is a static file if the resolvconf package is not installed. If installed, it is
a symbolic link. Either way, it contains information that initialize the resolver routines. If the
DNS is found at IP="192.168.11.1", it contains the following.
nameserver 192.168.11.1
CSS NC II Date Developed: Doc. No.: CSS CBLM CORE 2
UC 2 June 2017
Issued by:
NMCCI Page 23 of 59
Setting-up
Developed by:
Computer Networks
JOSEFINO T. HAPITAN
The resolvconf package makes this "/etc/resolv.conf" into a symbolic link and manages its
contents by the hook scripts automatically.
For the PC workstation on the typical adhoc LAN environment, the hostname can be
resolved via Multicast DNS (mDNS, Zeroconf) in addition to the basic files and dns methods.
The hostname resolution via deprecated NETBios over TCP/IP used by the older Windows
system can be provided by installing the winbind package. The "/etc/nsswitch.conf" file
should have stanza like "hosts: files mdns4_minimal [NOTFOUND=return] dns mdns4 wins"
to enable this functionality. (Modern Windows system usually use the dns method for the
hostname resolution.)
Note
The expansion of generic Top-Level Domains (gTLD) in the Domain Name System is
underway. Watch out for the name collision when chosing a domain name used only
within LAN.
The network interface name, e.g. eth0, is assigned to each hardware in the Linux kernel
through the user space configuration mechanism, udev (see Section 3.3, “The udev
system”), as it is found. The network interface name is referred as physical interface in
ifup(8) and interfaces(5).
In order to ensure each network interface to be named persistently for each reboot using
MAC address etc., there is a rules file "/etc/udev/rules.d/70-persistent-net.rules". This file is
automatically generated by the "/lib/udev/write_net_rules" program, probably run by the
"persistent-net-generator.rules" rules file. You can modify it to change naming rule.
Caution
When editing the "/etc/udev/rules.d/70-persistent-net.rules" rules file, you must keep
each rule on a single line and the MAC address in lowercase. For example, if you find
"FireWire device" and "PCI device" in this file, you probably want to name "PCI device"
as eth0 and configure it as the primary network interface.
Let us be reminded of the IPv4 32 bit address ranges in each class reserved for use on the
local area networks (LANs) by rfc1918. These addresses are guaranteed not to conflict with
any addresses on the Internet proper.
Note
If one of these addresses is assigned to a host, then that host must not access the
Internet directly but must access it through a gateway that acts as a proxy for individual
services or else does Network Address Translation (NAT). The broadband router usually
performs NAT for the consumer LAN environment.
Although most hardware devices are supported by the Debian system, there are some
network devices which require DFSG non-free firmware to support them. Please see
Section 9.9.6, “Hardware drivers and firmware”.
Debian squeeze and newer can manage the network connection via management daemon
software such as NetworkManager (NM) (network-manager and associated packages) or
Wicd (wicd and associated packages).
They come with their own GUI and command-line programs as their user interfaces.
They come with their own daemon as their backend system.
They allow easy connection of your system to the Internet.
They allow easy management of wired and wireless network configuration.
They allow us to configure network independent of the legacy ifupdown package.
Note
Do not use these automatic network configuration tools for servers. These are aimed
primarily for mobile desktop users on laptops.
Note
Some features of these automatic network configuration tools may suffer regressions.
These are not as robust as the legacy ifupdown package. Check BTS of network-
manager and BTS of wicd for current issues and limitations.
1. Make desktop user, e.g. foo, belong to group "netdev" by the following
(Alternatively, do it automatically via D-bus under modern desktop environments
such as GNOME and KDE).
Note
Only interfaces which are not listed in "/etc/network/interfaces" are managed by NM
or Wicd to avoid conflict with ifupdown.
Tip
If you wish to extend network configuration capabilities of NM,
please seek appropriate plug-in modules and supplemental
packages such as network-manager-openconnect, network-
manager-openvpn-gnome, network-manager-pptp-gnome,
When the method described in Section 5.2, “The modern network configuration for
desktop” does not suffice your needs, you should use the legacy network connection and
configuration method which combines many simpler tools.
The legacy network connection is specific for each method (see Section 5.4, “The network
connection method (legacy)”).
There are 2 types of programs for the low level network configuration on Linux (see
Section 5.7.1, “Iproute2 commands”).
Old net-tools programs (ifconfig(8), …) are from the Linux NET-3 networking system.
Most of these are obsolete now.
New Linux iproute2 programs (ip(8), …) are the current Linux networking system.
Although these low level networking programs are powerful, they are cumbersome to use.
So high level network configuration systems have been created.
The ifupdown package is the de facto standard for such high level network configuration
system on Debian. It enables you to bring up network simply by doing , e.g., "ifup eth0". Its
configuration file is the "/etc/network/interfaces" file and its typical contents are the
following.
auto lo
iface lo inet loopback
auto eth0
iface eth0 inet dhcp
The resolvconf package was created to supplement ifupdown system to support smooth
reconfiguration of network address resolution by automating rewrite of resolver
configuration file "/etc/resolv.conf". Now, most Debian network configuration packages are
modified to use resolvconf package (see "/usr/share/doc/resolvconf/README.Debian").
CSS NC II Date Developed: Doc. No.: CSS CBLM CORE 2
UC 2 June 2017
Issued by:
NMCCI Page 27 of 59
Setting-up
Developed by:
Computer Networks
JOSEFINO T. HAPITAN
Helper scripts to the ifupdown package such as ifplugd, guessnet, ifscheme, etc. are created
to automate dynamic configuration of network environment such as one for mobile PC on
wired LAN. These are relatively difficult to use but play well with existing ifupdown system.
These are explained in detail with examples (see Section 5.5, “The basic network
configuration with ifupdown (legacy)” and Section 5.6, “The advanced network
configuration with ifupdown (legacy)”).
Caution
The connection test methods described in this section are meant for testing purposes. It
is not meant to be used directly for the daily network connection. You are advised to
use NM, Wicd, or the ifupdown package instead (see Section 5.2, “The modern network
configuration for desktop” and Section 5.5, “The basic network configuration with
ifupdown (legacy)”).
The typical network connection method and connection path for a PC can be summarized as
the following.
acronym meaning
POTS plain old telephone service
BB broadband
BB-service e.g., the digital subscriber line (DSL), the cable TV, or the fiber to the premises (FTTP)
BB-modem e.g., the DSL modem, the cable modem, or the optical network terminal (ONT)
LAN local area network
WAN wide area network
DHCP dynamic host configuration protocol
PPP point-to-point protocol
PPPoE point-to-point protocol over Ethernet
ISP Internet service provider
Note
The WAN connection services via cable TV are generally served by DHCP or PPPoE. The
ones by ADSL and FTTP are generally served by PPPoE. You have to consult your ISP for
exact configuration requirements of the WAN connection.
Note
When BB-router is used to create home LAN environment, PCs on LAN are connected to
the WAN via BB-router with network address translation (NAT). For such case, PC's
network interfaces on the LAN are served by static IP or DHCP from the BB-router. BB-
router must be configured to connect the WAN following the instruction by your ISP.
The typical modern home and small business network, i.e. LAN, are connected to the WAN
(Internet) using some consumer grade broadband router. The LAN behind this router is
usually served by the dynamic host configuration protocol (DHCP) server running on the
router.
Just install the isc-dhcp-client package for the Ethernet served by the dynamic host
configuration protocol (DHCP).
See dhclient.conf(5).
No special action is needed for the Ethernet served by the static IP.
Table 5.6. List of configuration files for the PPP connection with pppconfig
file function
/etc/ppp/peers/<isp_name> The pppconfig generated configuration file for pppd specific to <isp_name>
/etc/chatscripts/<isp_name> The pppconfig generated configuration file for chat specific to <isp_name>
/etc/ppp/options The general execution parameter for pppd
/etc/ppp/pap-secret Authentication data for the PAP (security risk)
/etc/ppp/chap-secret Authentication data for the CHAP (more secure)
Caution
The "<isp_name>" value of "provider" is assumed if pon and poff commands are
invoked without arguments.
You can test configuration using low level network configuration tools as the following.
See "/usr/share/doc/ppp/README.Debian.gz".
A different approach to using pppd(8) is to run it from wvdial(1) which comes in the wvdial
package. Instead of pppd running chat(8) to dial in and negotiate the connection, wvdial
does the dialing and initial negotiating and then starts pppd to do the rest.
The configuration script wvdialconf configures the PPP connection interactively just by
selecting the following.
Table 5.7. List of configuration files for the PPP connection with wvdialconf
file function
/etc/ppp/peers/wvdial The wvdialconf generated configuration file for pppd specific to wvdial
/etc/wvdial.conf The wvdialconf generated configuration file
/etc/ppp/options The general execution parameter for pppd
/etc/ppp/pap-secret Authentication data for the PAP (security risk)
/etc/ppp/chap-secret Authentication data for the CHAP (more secure)
You can test configuration using low level network configuration tools as the following.
$ sudo wvdial
...
$ sudo killall wvdial
When your ISP serves you with PPPoE connection and you decide to connect your PC
directly to the WAN, the network of your PC must be configured with the PPPoE. The PPPoE
stand for PPP over Ethernet. The configuration script pppoeconf configures the PPPoE
connection interactively.
Table 5.8. List of configuration files for the PPPoE connection with pppoeconf
file function
/etc/ppp/peers/dsl-provider The pppoeconf generated configuration file for pppd specific to pppoe
/etc/ppp/options The general execution parameter for pppd
/etc/ppp/pap-secret Authentication data for the PAP (security risk)
/etc/ppp/chap-secret Authentication data for the CHAP (more secure)
You can test configuration using low level network configuration tools as the following.
See "/usr/share/doc/pppoeconf/README.Debian".
The traditional TCP/IP network setup on the Debian system uses ifupdown package as a high
level tool. There are 2 typical cases.
For dynamic IP system such as mobile PCs, you should setup TCP/IP network with
the resolvconf package and enable you to switch your network configuration easily
(see Section 5.5.4, “The network interface served by the DHCP”).
For static IP system such as servers, you should setup TCP/IP network without the
resolvconf package and keep your system simple (see Section 5.5.5, “The network
interface with the static IP”).
These traditional setup methods are quite useful if you wish to set up advanced
configuration; find details in the following.
The ifupdown package provides the standardized framework for the high level network
configuration in the Debian system. In this section, we learn the basic network configuration
with ifupdown with simplified introduction and many typical examples.
The ifupdown package contains 2 commands: ifup(8) and ifdown(8). They offer high level
network configuration dictated by the configuration file "/etc/network/interfaces".
command action
ifup eth0 bring up a network interface eth0 with the configuration eth0 if "iface eth0" stanza exists
ifdown eth0 bring down a network interface eth0 with the configuration eth0 if "iface eth0" stanza exists
Warning
Do not use low level configuration tools such as ifconfig(8) and ip(8) commands to
configure an interface in up state.
Note
There is no command ifupdown.
stanza meaning
"auto <interface_name>" start interface <interface_name> upon start of the system
"allow-auto <interface_name>" ,,
start interface <interface_name> when the kernel detects a hotplug event from the
"allow-hotplug <interface_name>"
interface
Lines started with "iface <config_name> …" define the network configuration <config_name>
Lines started with "mapping
define mapping value of <config_name> for the matching <interface_name>
<interface_name_glob>"
A line starting with a hash "#" ignore as comments (end-of-line comments are not supported)
A line ending with a backslash "\" extend the configuration to the next line
For the basic configuration, the mapping stanza is not used and you use the network
interface name as the network configuration name (See Section 5.6.5, “The mapping
stanza”).
Warning
Do not define duplicates of the "iface" stanza for a network interface in
"/etc/network/interfaces".
auto lo
iface lo inet loopback
allow-hotplug eth0
iface eth0 inet dhcp
When the Linux kernel detects the physical interface eth0, the allow-hotplug stanza causes
ifup to bring up the interface and the iface stanza causes ifup to use DHCP to configure the
interface.
The network interface served by the static IP is configured by creating the configuration
entry in the "/etc/network/interfaces" file as the following.
allow-hotplug eth0
iface eth0 inet static
address 192.168.11.100
netmask 255.255.255.0
gateway 192.168.11.1
dns-domain example.com
dns-nameservers 192.168.11.1
When the Linux kernel detects the physical interface eth0, the allow-hotplug stanza causes
ifup to bring up the interface and the iface stanza causes ifup to use the static IP to
configure the interface.
When the resolvconf package is not installed, DNS related configuration needs to be done
manually by editing the "/etc/resolv.conf" as the following.
nameserver 192.168.11.1
domain example.com
Caution
The wireless LAN (WLAN for short) provides the fast wireless connectivity through the
spread-spectrum communication of unlicensed radio bands based on the set of standards
called IEEE 802.11.
The WLAN interfaces are almost like normal Ethernet interfaces but require some network
ID and encryption key data to be provided when they are initialized. Their high level
network tools are exactly the same as that of Ethernet interfaces except interface names are
a bit different like eth1, wlan0, ath0, wifi0, … depending on the kernel drivers used.
Tip
The wmaster0 device is the master device which is an internal device used only by
SoftMAC with new mac80211 API of Linux.
The actual choice of protocol is usually limited by the wireless router you deploy.
You need to install the wpasupplicant package to support the WLAN with the new
WPA/WPA2.
In case of the DHCP served IP on WLAN connection, the "/etc/network/interfaces" file entry
should be as the following.
allow-hotplug ath0
iface ath0 inet dhcp
CSS NC II Date Developed: Doc. No.: CSS CBLM CORE 2
UC 2 June 2017
Issued by:
NMCCI Page 35 of 59
Setting-up
Developed by:
Computer Networks
JOSEFINO T. HAPITAN
wpa-ssid homezone
# hexadecimal psk is encoded from a plaintext passphrase
wpa-psk 000102030405060708090a0b0c0d0e0f101112131415161718191a1b1c1d1e1f
See "/usr/share/doc/wpasupplicant/README.modes.gz".
You need to install the wireless-tools package to support the WLAN with the old WEP. (Your
consumer grade router may still be using this insecure infrastructure but this is better than
nothing.)
Caution
Please note that your network traffic on WLAN with WEP may be sniffed by others.
In case of the DHCP served IP on WLAN connection, the "/etc/network/interfaces" file entry
should be as the following.
allow-hotplug eth0
iface eth0 inet dhcp
wireless-essid Home
wireless-key1 0123-4567-89ab-cdef
wireless-key2 12345678
wireless-key3 s:password
wireless-defaultkey 2
wireless-keymode open
See "/usr/share/doc/wireless-tools/README.Debian".
You need to configure the PPP connection first as described before (see Section 5.4.3, “The
PPP connection with pppconfig”). Then, add the "/etc/network/interfaces" file entry for the
primary PPP device ppp0 as the following.
You need to configure the alternative PPP connection with wvdial first as described before
(see Section 5.4.4, “The alternative PPP connection with wvdialconf”). Then, add the
"/etc/network/interfaces" file entry for the primary PPP device ppp0 as the following.
CSS NC II Date Developed: Doc. No.: CSS CBLM CORE 2
UC 2 June 2017
Issued by:
NMCCI Page 36 of 59
Setting-up
Developed by:
Computer Networks
JOSEFINO T. HAPITAN
iface ppp0 inet wvdial
For PC connected directly to the WAN served by the PPPoE, you need to configure system
with the PPPoE connection as described before (see Section 5.4.5, “The PPPoE connection
with pppoeconf”). Then, add the "/etc/network/interfaces" file entry for the primary PPPoE
device eth0 as the following.
allow-hotplug eth0
iface eth0 inet manual
pre-up /sbin/ifconfig eth0 up
up ifup ppp0=dsl
down ifdown ppp0=dsl
post-down /sbin/ifconfig eth0 down
# The following is used internally only
iface dsl inet ppp
provider dsl-provider
The "/etc/network/run/ifstate" file stores the intended network configuration states for all
the currently active network interfaces managed by the ifupdown package. Unfortunately,
even if the ifupdown system fails to bring up the interface as intended, the
"/etc/network/run/ifstate" file lists it active.
Unless the output of the ifconfig(8) command for an interface does not have a line like
following example, it can not be used as a part of IPV4 network.
When you try to reconfigure the interface, e.g. eth0, you must disable it first with the "sudo
ifdown eth0" command. This removes the entry of eth0 from the
"/etc/network/run/ifstate" file. (This may result in some error message if eth0 is not active
or it is configured improperly previously. So far, it seems to be safe to do this for the simple
single user work station at any time.)
Then, you can reactivate eth0 with the "sudo ifup eth0" command.
Tip
You can (re)initialize the network interface simply by "sudo ifdown eth0;sudo ifup
eth0".
The ifupdown-extra package provides easy network connection tests for use with the
ifupdown package.
The network-test command frees you from the execution of cumbersome low level
commands to analyze the network problem.
The automatic scripts are installed in "/etc/network/*/" and perform the following.
This syslog record is quite useful for administration of the network problem on the remote
system.
Tip
The automatic behavior of the ifupdown-extra package is configurable with the
"/etc/default/network-test". Some of these automatic checks slow down the system
boot-up a little bit since it takes some time to listen for ARP replies.
The functionality of the ifupdown package can be improved beyond what was described in
Section 5.5, “The basic network configuration with ifupdown (legacy)” with the advanced
knowledge.
Caution
If you could not set up network connection by information in Section 5.5, “The basic
network configuration with ifupdown (legacy)”, you make situation worse by using
information below.
The ifplugd package is an older automatic network configuration tool which can manage
only Ethernet connections. This solves unplugged/replugged Ethernet cable issues for
mobile PC etc. If you have NetworkManager or Wicd (see Section 5.2, “The modern network
configuration for desktop”) installed, you do not need this package.
This package runs a daemon and replaces auto or allow-hotplug functionalities (see
Table 5.10, “List of stanzas in "/etc/network/interfaces"”) and starts interfaces upon their
connection to the network.
Here is how to use the ifplugd package for the internal Ethernet port, e.g. eth0.
Tip
The arguments for the ifplugd(8) command can set its behaviors such as the delay for
reconfiguring interfaces.
CSS NC II Date Developed: Doc. No.: CSS CBLM CORE 2
UC 2 June 2017
Issued by:
NMCCI Page 39 of 59
Setting-up
Developed by:
Computer Networks
JOSEFINO T. HAPITAN
5.6.2. The ifmetric package
The ifmetric package enables us to manipulate metrics of routes a posteriori even for DHCP.
The following sets the eth0 interface to be preferred over the wlan0 interface.
The metric 0 means the highest priority route and is the default one. The larger metric value
means lower priority routes. The IP address of the active interface with the lowest metric
value becomes the originating one. See ifmetric(8).
A single physical Ethernet interface can be configured as multiple virtual interfaces with
different IP addresses. Usually the purpose is to connect an interface to several IP
subnetworks. For example, IP address based virtual web hosting by a single network
interface is one such application.
A single Ethernet interface on your host is connected to a Ethernet hub (not to the
broadband router).
The Ethernet hub is connected to both the Internet and LAN network.
The LAN network uses subnet 192.168.0.x/24.
Your host uses DHCP served IP address with the physical interface eth0 for the
Internet.
Your host uses 192.168.0.1 with the virtual interface eth0:0 for the LAN.
The ifupdown package offers advanced network configuration using the network
configuration name and the network interface name. I use a terminology being slightly
different from the one used in ifup(8) and interfaces(5).
Basic network configuration commands in Section 5.5.1, “The command syntax simplified”
require the network configuration name token of the iface stanza to match the network
interface name in the "/etc/network/interfaces".
command action
ifup eth0=config1 bring up a network interface eth0 with the configuration config1
ifdown eth0=config1 bring down a network interface eth0 with the configuration config1
ifup eth0 bring up a network interface eth0 with the configuration selected by mapping stanza
ifdown eth0 bring down a network interface eth0 with the configuration selected by mapping stanza
When the "<interface_name_glob>" matches "eth0", this execution produces the execution
of the following command to configure eth0 automatically.
Here, script input lines with "map" are optional and can be repeated.
Note
The glob for mapping stanza works like shell filename glob (see Section 1.5.6, “Shell
glob”).
Here is how to switch manually among several network configurations without rewriting the
"/etc/network/interfaces" file as in Section 5.5.13, “The basic network reconfiguration” .
For all the network configuration you need to access, you create a separate stanza in
"/etc/network/interfaces" file as the following.
auto lo
iface lo inet loopback
Please note the network configuration name which is the token after iface does not use the
token for the network interface name. Also, there are no auto stanza nor allow-hotplug
stanza to start the network interface eth0 automatically upon events.
Let's move your PC to a LAN served by the DHCP. You bring up the network interface (the
physical interface) eth0 by assigning the network configuration name (the logical interface
name) config1 to it by the following.
Let's move your PC to a LAN served by the static IP. You bring up the network interface eth0
by assigning the network configuration name config2 to it by the following.
The interface eth0 is up, configured with static IP and connected to LAN. The additional
parameters given as dns-* configures "/etc/resolv.conf" contents. This "/etc/resolv.conf" is
better manged if the resolvconf package is installed.
CSS NC II Date Developed: Doc. No.: CSS CBLM CORE 2
UC 2 June 2017
Issued by:
NMCCI Page 43 of 59
Setting-up
Developed by:
Computer Networks
JOSEFINO T. HAPITAN
$ sudo ifdown eth0=config2
...
Let's move your PC to a port on BB-modem connected to the PPPoE served service. You
bring up the network interface eth0 by assigning the network configuration name pppoe to
it by the following.
The interface eth0 is up, configured with PPPoE connection directly to the ISP.
Let's move your PC to a location without LAN or BB-modem but with POTS and modem. You
bring up the network interface ppp0 by assigning the network configuration name pots to
it by the following.
You should check the "/etc/network/run/ifstate" file for the current network configuration
state of the ifupdown system.
Warning
You may need to adjust numbers at the end of eth*, ppp*, etc. if you have multiple
network interfaces.
Here, each environment variable, "$IF_<OPTION>", is created from the name for the
corresponding option such as <option1> and <option2> by prepending "$IF_", converting
the case to the upper case, replacing hyphens to underscores, and discarding non-
alphanumeric characters.
Tip
See Section 5.5.2, “The basic syntax of "/etc/network/interfaces"” for
<address_family>, <method_name>, <option1> and <option2>.
The ifupdown-extra package (see Section 5.5.14, “The ifupdown-extra package”) uses these
environment variables to extend the functionality of the ifupdown package. The ifmetric
package (see Section 5.6.2, “The ifmetric package”) installs the "/etc/network/if-
up.d/ifmetric" script which sets the metric via the "$IF_METRIC" variable. The guessnet
package (see Section 5.6.8, “Mapping with guessnet”), which provides simple and powerful
framework for the auto-selection of the network configuration via the mapping mechanism,
also uses these.
Note
For more specific examples of custom network configuration scripts using these
environment variables, you should check example scripts in
"/usr/share/doc/ifupdown/examples/*" and scripts used in ifscheme and ifupdown-
scripts-zg2 packages. These additional scripts have some overlaps of functionalities with
basic ifupdown-extra and guessnet packages. If you install these additional scripts, you
should customize these scripts to avoid interferences.
You list test condition as the value for guessnet options for each network
configuration under iface stanza.
Mapping choses the iface with first non-ERROR result as the network configuration.
This dual usage of the "/etc/network/interfaces" file by the mapping script, guessnet-
ifupdown, and the original network configuration infrastructure, ifupdown, does not cause
negative impacts since guessnet options only export extra environment variables to scripts
run by the ifupdown system. See details in guessnet-ifupdown(8).
Note
When multiple guessnet option lines are required in "/etc/network/interfaces", use
option lines started with guessnet1, guessnet2, and so on, since the ifupdown package
does not allow starting strings of option lines to be repeated.
Table 5.15. Translation table from obsolete net-tools commands to new iproute2
commands
You may use low level network commands as follows safely since they do not change
network configuration.
command description
ifconfig display the link and address status of active interfaces
ip addr show display the link and address status of active interfaces
route -n display all the routing table in numerical addresses
ip route show display all the routing table in numerical addresses
arp display the current content of the ARP cache tables
ip neigh display the current content of the ARP cache tables
plog display ppp daemon log
ping yahoo.com check the Internet connection to "yahoo.com"
whois yahoo.com check who registered "yahoo.com" in the domains database
traceroute yahoo.com trace the Internet connection to "yahoo.com"
tracepath yahoo.com trace the Internet connection to "yahoo.com"
mtr yahoo.com trace the Internet connection to "yahoo.com" (repeatedly)
dig [@dns-server.com] example.com check DNS records of "example.com" by "dns-server.com" for a "a", "mx", or "any"
[{a|mx|any}] record
iptables -L -n check packet filter
netstat -a find all open ports
netstat -l --inet find listening ports
netstat -ln --tcp find listening TCP ports (numeric)
dlint example.com check DNS zone information of "example.com"
Tip
Some of these low level network configuration tools reside in "/sbin/". You may need to
issue full command path such as "/sbin/ifconfig" or add "/sbin" to the "$PATH" list in
your "~/.bashrc".
Generic network optimization is beyond the scope of this documentation. I touch only
subjects pertinent to the consumer grade connection.
The Maximum Transmission Unit (MTU) value can be determined experimentally with
ping(8) with "-M do" option which sends ICMP packets with data size starting from 1500
(with offset of 28 bytes for the IP+ICMP header) and finding the largest size without IP
fragmentation.
This process is Path MTU (PMTU) discovery (RFC1191) and the tracepath(8) command can
automate this.
Tip
The above example with PMTU value of 1454 is for my previous FTTP provider which
used Asynchronous Transfer Mode (ATM) as its backbone network and served its clients
with the PPPoE. The actual PMTU value depends on your environment, e.g., 1500 for
the my new FTTP provider.
In addtion to these basic guide lines, you should know the following.
Any use of tunneling methods (VPN etc.) may reduce optimal MTU further by their
overheads.
The MTU value should not exceed the experimentally determined PMTU value.
The bigger MTU value is generally better when other limitations are met.
Here are examples for setting the MTU value from its default 1500 to 1454.
For the DHCP (see Section 5.5.4, “The network interface served by the DHCP”), you can
replace pertinent iface stanza lines in the "/etc/network/interfaces" with the following.
For the static IP (see Section 5.5.5, “The network interface with the static IP”), you can
replace pertinent iface stanza lines in the "/etc/network/interfaces" with the following.
For the direct PPPoE (see Section 5.4.5, “The PPPoE connection with pppoeconf”), you can
replace pertinent "mtu" line in the "/etc/ppp/peers/dsl-provider" with the following.
mtu 1454
Note
The iptables(8) (see Section 5.9, “Netfilter infrastructure”) based optimization can
clamp packet size by the MSS and is useful for the router. See "TCPMSS" in iptables(8).
The TCP throughput can be maximized by adjusting TCP buffer size parameters as described
in "TCP Tuning Guide" and "TCP tuning" for the modern high-bandwidth and high-latency
WAN. So far, the current Debian default settings serve well even for my LAN connected by
the fast 1G bps FTTP service.
Netfilter provides infrastructure for stateful firewall and network address translation (NAT)
with Linux kernel modules (see Section 3.3.1, “The kernel module initialization”).
Main user space program of netfilter is iptables(8). You can manually configure netfilter
interactively from shell, save its state with iptables-save(8), and restore it via init script with
iptables-restore(8) upon system reboot.
Tip
Although these were written for Linux 2.4, both iptables(8) command and netfilter
kernel function apply for Linux 2.6 and 3.x kernel series.
Essay
1. What are the importance of network configuration?
Contents
Client Device systems
Local area network
Wide area network
Security/Firewall/Advance settings
Assessment Criteria
Assessment Method
Written exam
Practical exam
Direct observation
A client is part of a client–server model, which is still used today. Clients and servers may be
computer programs run on the same machine and connect via inter-process communication
techniques. Combined with Internet sockets, programs may connect to a service operating
on a possibly remote system through the Internet protocol suite. Servers wait for potential
clients to initiate connections that they may accept.
The term was first applied to devices that were not capable of running their own stand-
alone programs, but could interact with remote computers via a network. These dumb
terminals were clients of the time-sharing mainframe computer.
Ethernet over twisted pair cabling and Wi-Fi are the two most common transmission
technologies in use for local area networks. Historical technologies include ARCNET, Token
Ring, and AppleTalk.
Related terms for other types of networks are personal area networks (PANs), local area
networks (LANs), campus area networks (CANs), or metropolitan area networks (MANs)
which are usually limited to a room, building, campus or specific metropolitan area
respectively.
________________________________________________________________
________________________________________________________________
________________________________________________________________
________________________________________________________________
________________________________________________________________
________________________________________________________________
________________________________________________________________
________________________________________________________________
________________________________________________________________
________________________________________________________________
________________________________________________________________
________________________________________________________________
________________________________________________________________
________________________________________________________________
________________________________________________________________
________________________________________________________________
________________________________________________________________
________________________________________________________________
________________________________________________________________
________________________________________________________________
________________________________________________________________
________________________________________________________________
________________________________________________________________
________________________________________________________________
________________________________________________________________
________________________________________________________________
________________________________________________________________