USEFUL

PROTOCOLS I:
NAT
DNS
SMTP
DHCP
FTP/TFTP
SNMP
IPV6
Dr. Rigoberto Chinchilla
Eastern Illinois University
 Private non-routable (private)
addresses and addressing Schemas
Private Network
Hybrid Network
 NAT basics
 The original intention of NAT was to slow
the depletion of available IP addresses
space by allowing many private IP
addresses to be represented by some
smaller number of public IP addresses

 Since then, it’s been discovered that NAT

is also useful for
– Network migrations and mergers
– Security
NAT basics
NAT basics
 NAT uses
 Need to connect to the internet and your
hosts do not have globally unique IP
addresses

 When changing ISP’s: The new ISP

requires you to renumber your network

 Need to merge two INTRANETS with

duplicate addresses

 NAT is used typically in BORDER routers

 NAT's Pros(+) and Cons(-)
 Conserves legally registered addresses (+)

 Reduces address overlap occurrence (+)

 Increases flexibility when connected to the INTERNET

(+)

 Eliminates address renumbering as network changes

(+)

 Translation introduces path delays (-)

 Loss of end-to-end IP traceability (+/-)

 Certain application will not function with NAT

enabled(-)
 Types of NAT
 Static NAT : One-to-one mapping between local and
global addresses (No savings !)

 Dynamic NAT: Private IP addresses can be mapped

to a pool of Public (“real”) IP addresses (Some Savings)

 Overloading: Multiple Private addresses can be

mapped to ONE public (“real”) IP address (Port
Address Translation PAT)
– PAT is the real reason why INTERNET continues to
grow with the limited number of IP addresses we
have
 Next figures reference http://www.firewall.cx/networking-
topics/network-address-translation-nat/231-nat-dynamic-part-
1.html
 NAT TERMS
 “Inside Local”: INSIDE source address
BEFORE translation

 “Inside Global”: Inside host after

translation

 “Outside Global”: Outside global

destination host after translation

 “Outside local” :Outside local destination

host after translation
How NAT (static/dynamic) works?
How PAT works?
NAT basics
NAT basics
NAT basics
ISP’s and NAT
NAT Summary
Concerns about NAT

• End-to-end connectivity:
– NAT destroys universal end-to-end reachability of hosts on
the Internet.

– A host in the public Internet often cannot initiate

communication to a host in a private network.

– The problem is worse, when two hosts that are in a private

network need to communicate with each other.

27
NAT as Firewall
 Problems with NAT
 When a client program is using NAT to hide behind a
routing device on an internal network, when using
PORT the client tells a server on the external network
to connect to an address on the client's internal
network. I.e.:
– Client: PORT 192,168,1,2,7,138

 That almost always results in the routing device

denying the connection, or the connection to fail
completely if the IP address is a RFC 1918 compliant
reserved address (i.e. 192.168.x.x, 172.16.x.x,
10.x.x.x)

 In either case, the client user will typically experience

a discarded connection that is very frustrating since
the client program will just lock up until the
connection is considered permanently timed-out.
 Solution: Problems with NAT
 A solution is for the network administrator of
the client network is to use high-quality
network address translation software (NAT)

 Devices can keep track of data connections, and

when a client on a private network uses "PORT"
with an internal network address, the device
should dynamically rewrite the packet containing
the PORT and IP address and change the address
so that it refers to the external IP address of the
routing device

 The device would then have to route the

connection incoming from the remote server back
to the internal network address of the
client. I.e.:
– Client: PORT 192,168,1,2,7,138
 Solution: Problems with NAT
 When the packet containing this PORT
reaches the routing device, it should be
rewritten like this, assuming the external
address is 17.254.0.26:
– Client: PORT 17,254,0,26,7,138
– 1930 = 00000111 (7) 10001010 (138)

 The remote server would then attempt to

connect to 17.254.0.26:1930. The routing
device in this example would then forward
all traffic for this connection to and from
the client address at 192.168.1.2:1930.
 More potential problems with
NAT
Header Checksums
 http://www.ciscopress.com/articles/article.asp?p=25273&s
eqNum=3
The checksum of an IP packet is calculated over the entire
header. Therefore, if the source or destination IP address or
both change, the checksum must be recalculated. The same is
true of the checksum in the TCP header.

This number is calculated over the TCP header and data, and
also over a pseudo-header that includes the source and
destination IP addresses. Therefore, if an IP address or a port
number changes, the TCP checksum must also change. Cisco's
NAT performs these checksum recalculations.
 More potential problems with NAT
Fragmentation
 Recall from the section "NAT and Virtual Servers" that you can use NAT to
translate to different local addresses based on the destination port. A
packet with a destination port of 25 can be translated to a particular
address, for example, whereas a packet with some other destination port
numbers can be translated to other addresses.
– However, what if the packet destined for port 25 becomes fragmented at some point in the
network before it reaches the NAT? The TCP or UDP header, containing the source and
destination port numbers, is in the first fragment only. If that fragment is merely
translated and forwarded, the NAT has no way to tell whether the subsequent fragments
must be translated.
 IP makes no guarantees that packets are delivered in order. So it's quite
possible that the first fragment might not even arrive at the NAT before
later fragments. You must design NAT to handle such eventualities.

 Cisco's NAT keeps stateful information about fragments. If a first

fragment is translated, information is kept so that subsequent fragments
are translated the same way.
More potential problems with NAT
 Encryption
 Cisco's NAT can change the IP address information carried
within the data fields of many applications, as you will see
shortly. If the data fields are encrypted, however, NAT has
no way of reading the data. Therefore, for NAT to function,
neither the IP addresses nor any information derived from
them (such as the TCP header checksum) can be
encrypted.

 Another concern is virtual private networks (VPNs) using,

for example, IPSec. With certain modes of IPSec, if an IP
address is changed in an IPSec packet, the IPSec becomes
meaningless and the VPN is broken. When any sort of
encryption is used, you must place the NAT on the secure
side rather than in the encrypted path.
http://www.ciscopress.com/articles/article.asp?p=2
5273&seqNum=3
VPN basics
Basics of VPNs
Virtual Private Network
VPN basics
VPN Basics
VPN basics
Tunneling
Addressing in a VPN
VPN basics
VPN basics
VPN basics
VPN basics
VPN basics
VPN protocols
 VPN protocols
 IKE: Internet Key Exchange

 AH: Authentication Header

 ESP: Encapsulation Security Protocol

 The DNS server
 The DNS server is a device on a
network that responds to request
from clients to translate a Domain
name into the associated IP address

 If a local DNS server is capable of

translating a domain name into its
associated IP address, it does so and
returns the result to the client
 The DNS server
 If it can not translate the address, it passes the
request up to the next higher- level DNS server
on the system, which then tries to translate the
address

 If the DNS at this level is not capable to returns

positive results to the clients sends a request to
the next higher level server and so on

 If the name can not be found , then it is

considered an error and an error message is
returned
DNS basics
 Concept: Domains
 Domains are “namespaces”
 Everything below .com is in the “com”
domain
 Everything below ripe.net is in the ripe.net
domain and in the net domain
• com domain

net edu com

• • •
google
ripe.net domain ripe isi sun tislabs
•
moon •
www disi
net domain ftp • www
ws2 ws1
 Concept: Zones and Delegations
 Zones are “administrative spaces”
 Zone administrators are responsible for portion of a
domain’s name space
 Authority is delegated from a “parent and to a child” server

•
net zone
ne ed co
net domain m •
•t u
•
google
ripe.net zone rip is sun tislab
• e i moons •
ww dis
disi.ripe.net zone ww
w ft i
•
p ws ws w
2 1
 Concept: Name Servers
authoritative name server
 Give authoritative answers for one or
more zones
 The master server normally loads the data
from a zone file
 A slave server normally replicates the data
from the master via a zone transfer

slave

master
slave
 Concept: Resolving process &
Question: www.ripe.net
Cache
A
www.ripe.net A ? root-server
Ask net server @ X.gtld-servers.net
www.ripe.net A ?

Resolver Caching
192.168.5.10
forwarder www.ripe.net A ?

(recursive) gtld-server
Ask ripe server @ ns.ripe.net

Add to cache www.ripe.net A ?

192.168.5.10

ripe-server
 Network Applications
 DNS Function
 E-Mail Messages
 We select a network application based on
the type of network we need to
accomplish
 Each application program type is
associated with its own application
protocol
– WWW using HTTP (Chrome, explorer)
– Remote access programs using TELNET
– E-mail Programs supporting the POP3
application layer protocol.
 https://www.getmailbird.com/pop3-email-account/
 The DNS function
 Whenever e-mail clients send letters, they
request that a DNS server connected to
the network translate the domain names
into the associated IP address

 The part of the e-mail that contains the

recipient’s name becomes important at
the destination post office

 The server extracts it from the e-mail

message and checks to see if the recipient
is a member of its post office, otherwise
generates an error message
E-Mail and DNS (1 of 5)
E-Mail and DNS (2 of 5)
E-Mail and DNS (3 of 5)
A box for the user should be created previously
E-Mail and DNS (4 of 5)
E-Mail and DNS (5 of 5)
 What is SMTP
 SMTP (Simple Mail Transfer Protocol) is a TCP/IP
protocol used in sending and receiving e-mail.

– However, since it is limited in its ability to queue messages at

the receiving end, it is usually used with one of two other
protocols, POP3 or IMAP, that let the user save messages in a
server mailbox and download them periodically from the server
– Internet Mail Access Protocol
– Post Office Protocol version 3

 In other words, users typically use a program that uses

SMTP for routing e-mail and either POP3 or IMAP for
retrieving or deposit e-mail locally.

 A commercial package, Send mail, typically includes a

POP3 server
E-mail Servers
SMTP
 HTTP protocol used as a mail Access
 “The HTTP protocol is not a protocol dedicated for
email communications, but it can be used for
accessing your mailbox.

 Also called web based email, this protocol can be

used to compose or retrieve emails from an your
account. Hotmail is a good example of using
HTTP as an email protocol”
– reference http://www.emailaddressmanager.com/tips/protocol.html)

 Please read the following article (part of exam)

– http://www.howtogeek.com/99423/email-whats-the-
difference-in-pop3-imap-and-exchange/
 IMAP SUMMARY
http://www.emailaddressmanager.com/tips/protocol.html

 IMAP (Internet Message Access Protocol) – Is a

standard protocol for accessing e-mail from your local
server. IMAP is a client/server protocol in which e-mail is
received and held for you by your Internet server.

 As this requires only a small data transfer this works well

even over a slow connection such as a modem. Only if you
request to read a specific email message will it be
downloaded from the server. You can also create and
manipulate folders or mailboxes on the server, delete
messages etc.
 HTTP Protocol Summary
 The HTTP protocol is NOT a protocol
dedicated for email communications, but it
can be used for accessing your mailbox.

 Also called web based email, this protocol

can be used to compose or retrieve emails
from an your account.
– Hotmail is a good example of using HTTP as an
email protocol.
Recalling the OSI model
DHCP Basics
 DHCP functional goals
 A host without a valid IP address locates and
communicates with a DHCP server

 A DHCP server passes configuration

parameters, including an IP address, to the
host

 The DHCP server may dynamically allocate

addresses to hosts and reuse addresses
 What does DHCP do?
 Providesprotocol stack, application
and other configuration parameters
to hosts

 Eliminates
need for individual,
manual configuration for hosts

 Includes
administrative controls for
network administrators
 What does DHCP do?
 Backwardcompatible packet format
for BOOTP interoperation (RFC 1542)

 Can coexist with hosts that have pre-

assigned IP addresses and hosts that
do not participate in DHCP
 Design Goals
 Eliminate manual configuration of hosts

 Prevent use of any IP address by more

than one host

 Should not require a server on every

subnet

 Allow for multiple servers

 What DHCP doesn’t do
 Support multiple addresses per interface

 Inform running host that parameters have

changed

 Propagate new addresses to DNS

 Support inter-server communication

 Provide authenticated message delivery

 What DHCP doesn’t do
 Configure
routers and other network
equipment

 Design network addressing plan

 Determineother configuration
parameters

 Locate other servers

DHCP Assigning Addresses
Newly installed computer

Router 201.157.7.198

DHCP
server
201.157.7.96

New computer
 Relocated computer
 Computer retains address

 When restarted, computer checks with

server to confirm address

 If address OK, computer retains old address

 If computer attached to different subnet,

obtains new address
Relocated computer

201.157.7.96
201.157.7.64

Router 201.157.7.198

DHCP
server
201.157.7.96

Moved!
Problems with DHCP
DHCP ON WINDOWS
 Summary
 DHCP works today as a tool for automatic
configuration of TCP/IP hosts

 It is an open Internet standard and interoperable

client implementations are widely available

 Provides automation for routine configuration

tasks, once network architect has configured
network and addressing plan

 Ongoing work will extend DHCP with

authentication, DHCP-DNS interaction and inter-
server communication
 FTP:ACTIVE MODE
 Starts with the FTP CLIENT initiating a
connection through a random port >1023
(i.e. 1056) with the FTP server on its port
21. Port 21 is where the server is listening
for commands issued to it, and in turn,
which it will respond to

 The SERVER completes the handshake

between SERVER port 21 and CLIENT port
(i.e. 1056)

 The CLIENT assigns another port >1023 (i.e.

Port 1059) to receive data


 FTP:ACTIVE MODE
 At this point the client begins to send commands
to the FTP port 21 including the port at which the
CLIENT wants the data to be send. (Port 1059)

 Once this is done the SERVER REQUEST A

connection with the CLIENT into PORT 1059 in
order to transfer data from SERVER port 20 to
the client’s port 1059

 Though if the client has a firewall in place, this

whole communication process will come to a
grinding halt. The clients firewall would drop what
it considers to be an unsolicited communication
attempt on port 1059
 FTP:PASIVE MODE
 The FTP client, will start up two connections
to the FTP server

 We need to keep in mind as well that both

connections that are initiated by the client
are using ports > 1023 themselves, as it
should be

 By opening two connections, or sockets with

the FTP server, the client is able to resolve
the issue of its firewall denying access to the
FTP server initiating contact on one of the
client’s ports (>1023)
 Note About FTP
 FTP has become an anachronism for downloading
and uploading files , it is explained here for the
purpose of understanding the danger of opening
un controlled ports.(It has been substituted by
http)
– Please read
http://alblue.bandlem.com/2009/02/wh
y-do-people-still-use-ftp.html
– http://www.policypatrol.com/five-
reasons-why-you-need-to-replace-your-
ftp-server/
 FTP:PASIVE MODE
 One of the connections opened by the client will
contact the FTP server on port 21, and issue it the
PASV (passive) command, via the normal PORT
command when using active FTP

 Now what happens is that the FTP server opens a

port >1023 and issues the PORT command to the
FTP client

 With this in hand the client then starts a connection

back to the server port for the data transfer.
 It is a rather nifty way to deal with the
aforementioned issue of Active FTP and client
firewalls
Passive mode Vs. Active mode
 Active
mode data connections are
very unsafe when using firewalls that
are based ONLY on Ports

 PassiveMode still can be unsafe by

allowing ANY client program to
connect to any server in the internet
by using a port > 1023.
 Client-Server operation
 AnFTP server can attend many FTP
request because
– It is possible for the server to create
“slave” replicas of the same program to
attend the request

– Can assign arbitrary ports to that

“slave” to serve the different request
 FTP Problems
 Passwords and file contents are sent in clear text,
which can be intercepted by eavesdroppers. There
are protocol enhancements that circumvent this

 Multiple TCP/IP connections are used, one for the

control connection, and one for each download,
upload, or directory listing. Firewall software needs
additional logic to account for these connections

 It is hard to filter active mode FTP traffic on the

client side by using a firewall, since the client must
open an arbitrary port in order to receive the
connection. This problem is largely resolved by using
passive mode FTP.
 FTP problems
 FTP is a high latency protocol due to the
number of commands needed to initiate a
transfer

 No integrity check on the receiver side

– If transfer is interrupted the receiver has no
way to know if the received file is complete or
not. It is necessary to manage this externally
for example with cyclic redundancy checking
(CRCs)
 Security problems
 The original FTP specification is an
inherently insecure method of
transferring files because there is no
method specified for transferring data
in an encrypted fashion

 Thismeans that under most network

configurations, user names, passwords,
FTP commands and transferred files can
be "sniffed" or viewed by anyone on the
same network using a packet sniffer
 Security problems
 This is a problem common to many
Internet protocol specifications written
prior to the creation of SSL (Secure Sockets Layer)
such as HTTP, SMTP and Telnet

 The common solution to this problem is to

use either SFTP (SSH File Transfer
Protocol), or FTPS (FTP over SSL), which
adds SSL or TLS encryption to FTP as
specified in RFC 4217
 More Problems with FTP and
Firewalls
 Please expand your knowledge and
check
http://www.ncftp.com/ncftpd/doc/misc/ft
p_and_firewalls.html
 SNMP
 The Simple Network Management Protocol
(SNMP) is an application layer protocol that
facilitates the exchange of management
information between network devices. It is part
of the Transmission Control Protocol/Internet
Protocol (TCP/IP) protocol suite

 SNMP enables network administrators to manage

network performance, find and solve network
problems, and plan for network growth

 Two versions of SNMP exist: SNMP version 1

(SNMPv1) and SNMP version 2 (SNMPv2)

 Both versions have a number of features in

common, but SNMPv2 offers enhancements, such
as additional protocol operations. Standardization
of yet another version of SNMP—SNMP Version 3
(SNMPv3)
 What is SNMP?

 SNMP is a tool (protocol) that allows for remote

and local management of items on the network
including servers, workstations, routers, switches
and other managed devices.
 Comprised of agents and managers
•Agent - process running on each managed node collecting
information about the device it is running on.

•Manager - process running on a management workstation

that requests information about devices on the network.
•Info/slide from Dr. Chris Francois
 Advantages of using SNMP
 Standardized

 universally supported
 extendible

 portable

 allows distributed management access

 lightweight protocol
•Info/slide from Dr. Chris Francois
 Client Pull & Server Push

 SNMP is a “client pull” model

The management system (client) “pulls” data from the agent
(server).

• SNMP is a “server push” model

The agent (server) “pushes” out a trap message to a (client)
management system
 Ports & UDP

•SNMP uses User Datagram Protocol (UDP) as the transport

mechanism for SNMP messages

Ethern
et
Frame
IP
Packet
SNMP Message CRC
UDP
Datagra
m

•Like FTP, SNMP uses two well-known ports to operate:

•UDP Port 161 - SNMP Messages

•UDP Port 162 - SNMP Trap Messages
•Info/slide from Dr. Chris Francois
 The Three Parts of SNMP
SNMP network management is based on three parts:

•SNMP Protocol

•Defines format of messages exchanged by

management systems and agents.
•Specifies the Get, GetNext, Set, and Trap operations
•Structure of Management Information (SMI)

•Rules specifying the format used to define objects

managed on the network that the SNMP protocol
accesses
•Management Information Base (MIB)

•A map of the hierarchical order of all managed

objects and how they are accessed
•Info/slide from Dr. Chris Francois
 SNMP Basic Components

A managed device is a network node that

contains an SNMP agent and that resides
on a managed network
– Managed devices collect and store
management information and make this
information available to a network-
management systems NMSs using SNMP

– Managed devices, sometimes called network

elements, can be routers and access servers,
switches and bridges, hubs, computer hosts,
or printers
 The Three Parts of SNMP
SNMP network management is based on three parts:

•SNMP Protocol

•Defines format of messages exchanged by

management systems and agents.
•Specifies the Get, GetNext, Set, and Trap operations
•Structure of Management Information (SMI)

•Rules specifying the format used to define objects

managed on the network that the SNMP protocol
accesses
•Management Information Base (MIB)

•A map of the hierarchical order of all managed

objects and how they are accessed
 Nodes
Items in an SNMP Network are called nodes. There are different
types of nodes.

•Managed nodes

Typically runs an agent process that services requests from a management

node

•Management nodes

Typically a workstation running some network management & monitoring

software
•Nodes that are not manageable by SNMP

A node may not support SNMP, but may be manageable by SNMP through a
proxy agent running on another machine

Nodes can be both managed nodes and a management node at the

same time (typically this is the case, since you want to be able to manage the workstation that your
management application is running on.)
•Info/slide from Dr. Chris Francois
 Community Names

Community names are used to define where an SNMP message is

destined for.
•Set up your agents to belong to certain communities.
•Set up your management applications to monitor and receive
traps from certain community names.
 NMS
 An agent is a network-management software
module that resides in a managed device. An
agent has local knowledge of management
information and translates that information into a
form compatible with SNMP

 An NMS executes applications that monitor and

control managed devices. NMSs provide the bulk
of the processing and memory resources required
for network management. One or more NMSs
must exist on any managed network.
 MIBS
A Management Information Base
(MIB) is a collection of information
that is organized hierarchically

 MIBs are accessed using a network-

management protocol such as SNMP.
They are comprised of managed
objects and are identified by object
identifiers
SNMP Basics
 SNMP Basic Commands
 Managed devices are monitored and
controlled using four basic SNMP
commands: read, write, trap, and
traversal operations

 The read command is used by an NMS to

monitor managed devices. The NMS
examines different variables that are
maintained by managed devices.

 The write command is used by an NMS to

control managed devices. The NMS
changes the values of variables stored
within managed devices.
 SNMP Basic Commands
 The trap command is used by managed
devices to asynchronously report events
to the NMS. When certain types of events
occur, a managed device sends a trap to
the NMS

 Traversal operations are used by the NMS

to determine which variables a managed
device supports and to sequentially gather
information in variable tables, such as a
routing table
 Traps
•Traps are unrequested event reports that are sent to a management
system by an SNMP agent process

•When a trappable event occurs, a trap message is generated by the

agent and is sent to a trap destination (a specific, configured network address)

•Many events can be configured to signal a trap, like a network cable

fault, failing NIC or Hard Drive, a “General Protection Fault”, or a
power supply failure.

•Traps can also be throttled -- You can limit the number of traps sent
per second from the agent.

•Traps have a priority associated with them -- Critical, Major, Minor,

Warning, Marginal, Informational, Normal, Unknown

•Info/slide from Dr. Chris Francois

 Trap Receivers
•Traps are received by a management application.
•Management applications can handle the trap in a few ways:

•Poll the agent that sent the trap for more information about the
event, and the status of the rest of the machine.
•Log the reception of the trap.
•Completely ignore the trap.
•Management applications can be set up to send off an e-mail, call a
voice mail and leave a message, or send an alpha-numeric page to the
network administrator’s pager that says:

Your PDC just Blue-Screened at 03:46AM. Have a nice day. :)

•Info/slide from Dr. Chris Francois

 SNMP Security
 SNMP Version 1, lacks any authentication
capabilities, which results in vulnerability to a
variety of security threats.
– These include masquerading occurrences,
modification of information, message sequence and
timing modifications, and disclosure

 Masquerading consists of an unauthorized

entity attempting to perform management
operations by assuming the identity of an
authorized management entity
 SNMP Security
 Modification of information involves an
unauthorized entity attempting to alter a
message generated by an authorized
entity so that the message results in
unauthorized accounting management or
configuration management operations

 Message sequence and timing

modifications occur when an unauthorized
entity reorders, delays, or copies and later
replays a message generated by an
authorized entity
 SNMP security

 Disclosure…. results when an

unauthorized entity extracts values stored
in managed objects, or learns of notifiable
events by monitoring exchanges between
managers and agents

 Because SNMP does not implement

authentication, many vendors do not
implement Set operations, thereby
reducing SNMP to a monitoring facility.
 SNMP Version 2/3
 The new security features of SNMPv2 are
designed to provide three security-related
services: privacy, message authentication, and
access control.
– Privacy is the protection of transmitted data from
eavesdropping or wiretapping. Privacy requires that the
contents of any message be disguised so that only the
intended recipient can recover it

– Message authentication enables communicating parties

to verify that no one has altered received messages and
that their sources are authentic. This includes
verification of a message's timeliness to ensure that it
has not been artificially delayed and replayed

– Access control ensures that only authorized users have

access to a particular management information base.
SNMP Message Formats Message Length
SNMP Message Version
Message Length
Message Community String
Message Version Preamble
PDU Type
Community String
PDU Length
PDU Type
Enterprises MIB OID
PDU Length
Agent IP Address
Request ID PDU
Standard Trap Type
Error Status Header
Specific Trap Type
Error Index Time Stamp
Length of Variable Bindings Length of Variable Bindings

Length of First Binding Length of First Binding

OID of First Binding OID of First Binding
Type of First Binding Type of First Binding
Value of First Binding PDU Value of First Binding
Length of Second Binding Body Length of Second Binding
OID of Second Binding OID of Second Binding
Type of Second Binding Type of Second Binding
Value of Second Binding •Info/slide from Dr. Value of Second Binding
Chris Francois

Additional Variable Bindings Additional Variable Bindings

 Commercial SNMP Applications
Here are some of the various SNMP Management products available today:
•http://www.hp.com/go/openview/ HP OpenView
•http://www.tivoli.com/ IBM NetView
•http://www.novell.com/products/managewise/ Novell ManageWise
•http://www.sun.com/solstice/ Sun MicroSystems Solstice
•http://www.microsoft.com/smsmgmt/ Microsoft SMS Server
•http://www.compaq.com/products/servers/management/ Compaq Insight Manger
•http://www.redpt.com/ SnmpQL - ODBC Compliant
•http://www.empiretech.com/ Empire Technologies
•ftp://ftp.cinco.com/users/cinco/demo/ Cinco Networks NetXray
•http://www.netinst.com/html/snmp.html SNMP Collector (Win9X/NT)
•http://www.netinst.com/html/Observer.html Observer
•http://www.gordian.com/products_technologies/snmp.html Gordian’s SNMP Agent
•http://www.castlerock.com/ Castle Rock Computing
•http://www.adventnet.com/ Advent Network Management
•http://www.smplsft.com/ SimpleAgent, SimpleTester
•Info/slide from Dr. Chris Francois
IPV4 vs IPV6
 IPV6
 In IPV6, most of the informational options have been
moved to the optional area AFTER the Addresses.

 This series of optional extensions headers allow the

efficient use of the header in processing the routing
information during packet routing operations.
– One of the MOST common options is the “IPSEC” extension,
which is used to establish IPsec connections. IPsec uses
encryption to provide a variety of protections to packets.
 The expansion of the address space from 32 to 128 bits
is the significant change.
– IPv6 has about 1500 addresses per square meter of the entire
hearth’s surface!
– The IPV4 space is EMBEDDED in the IPv6 Schemma
 Benefits of IPV6
 Vendors have been making every IP based telecom
equipment with IPv6 and IPv4 capabilities.

 Simplified packet header

– More efficient routing
– Smaller routing tables
– Faster packet processing

 Designed to incorporate multicasting flows natively,

which allows BW-intensive multimedia stream to be set
simultaneously to multiple destinations.

 The SECURITY model is incorporated: IPsec available