DOCSLIB.ORG

Solaris Networking

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Solaris Networking Solaris Networking Solaris Basic Network Configuration Solaris comes with a bounteous supply of startup scripts. Solaris stashes some network configuration files in /etc and some in /etc/inet. Many are duplicated through the magic of symbolic links, with the actual files living in /etc/inet and the links in /etc. To set the hostname, enter it into the file /etc/nodename. The change will take effect when the machine is rebooted. Some sites use just the short hostname. Others use the fully qualified domain name. The /etc/defaultdomain file’s name suggests that it might be used to specify the DNS domain, but it actually specifies the NIS and NIS+ domain name. The DNS domain is specified in /etc/resolv.conf as usual. Solaris uses /etc/nsswitch.conf to set the order in which /etc/hosts, NIS, NIS+, and DNS are consulted for hostname resolution. We recommend looking at the hosts file, then DNS for easy booting. A line from nsswitch.conf would be hosts: files dns This is the default configuration if the host receives the addresses of its DNS server through DHCP. Solaris networking can run in traditional mode or in “Network Auto-Magic” (NWAM) mode, where networking is managed autonomously by the nwamd daemon. NWAM mode is fine for workstations, but it has limited configurability and allows only one network interface to be active at a time. What follows assumes traditional mode. To see which networking mode is active, run svcs svc:/network/physical. There should be two configuration lines, one for NWAM and one for the traditional mode, i.e. default. Run svcadm to switch the configuration. For example, the following exchange shows the system being taken from NWAM to traditional mode. $ svcs svc:/network/physical STATE STIME FMRI Disabled Mar_31 svc:/network/physical:default Online Mar_31 svc:/network/physical:nwam $ sudo svcadm disable svc:/network/physical:nwam $ sudo svbcadm enable svc:/network/physical:default Solaris configures the IP address of each network interface through a file called /etc/hostname.interface, where interface is the usual name of the interface. These files can contain either a hostname that appears in the hosts file or an IP address. The value in a hostname.interface file is used as the address parameter to ifconfig, so it is safest to use an address, even though the configuration filename implies that a hostname is expected. Any special ifconfig options can also be put in the hostname.interface file on the same line as the hostname or IP address. It is all one big ifconfig command line. The startup scripts try to discover the IP addresses of any interfaces without corresponding hostname files by using DHCP. As shipped, the Solaris startup files rely on using the ifconfig options netmask + and broadcast +. The pluses mean to look in /etc/netmasks for the netmask value and to figure out the broadcast address value from it. The /etc/netmasks file lists network numbers and their corresponding netmask values. Any network that is subnetted differently from its inherent network class, e.g. A, B, or C, must be represented in the file. Here is an example of a netmasks file from SPARC2: # # The netmasks file associates Internet Protocol (IP) address # masks with IP network numbers. # # network-number netmask # # The term network-number refers to a number obtained from the Internet Network # Information Center. # # Both the network-number and the netmasks are specified in # "decimal dot" notation, e.g: # # 128.32.0.0 255.255.255.0 # 192.168.48.0 255.255.255.128 From the textbook we have: # CS Department network masks database # Network netmask # ======= ####### # 128.138.0.0 255.255.255.192 # default for dept # 128.138.192.64 255.255.255.192 # drag 128.138.192.192 255.255.255.192 # csops 128.138.193.0 255.255.255.224 # bcrg 128.138.193.32 255.255.255.224 # database 128.138.198.0 255.255.255.0 # slip ………… The first line sets a default of /26 for the class B address 128.138.0.0, which is then overridden with specific masks that vary from the default. All networks are listed, even though many use the default value and could in fact be left out. On the systems from which this example is taken the netmasks file is centrally maintained and distributed to all hosts. No single host has interfaces on all of these networks. The startup scripts live in /lib/sbc/method on Solaris 10 operating systems. If /etc/defaultrouter exists, it is assumed to contain the identity which again can be either a hostname or a numeric address of the default gateway, and no further routing configuration is performed. As usual, a numeric address is preferable. Using a name requires an /etc/hosts entry or a DNS server on the local network. Solaris Configuration Examples Here are some examples of the commands needed to bring up a Solaris interface and add a route to a default gateway: $ sudo ifconfig e1000g0 plumb $ sudo ifconfig e1000g0 192.108.21.48 netmask 255.255.255.0 up $ sudo route add default 192.108.21.254 The following examples show how to see the status of network interfaces and routing tables. Commands prefaced with sudo must be run as root. The final example shows a feature of the Solaris route command that is not present on other architectures: the get argument shows the next hop to a particular destination. We have taken some liberties to make the examples fit the screen. From Orange we have $ /sbin/ifconfig -a lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1 inet 127.0.0.1 netmask ff000000 e1000g0: flags=1004843<UP,BROADCAST,RUNNING,MULTICAST,DHCP,IPv4> mtu 1500 index 2 inet 172.19.48.214 netmask ffffff00 broadcast 172.19.48.255 $ sudo ifconfig e1000g0 e1000g0: flags=1004843<UP,BROADCAST,RUNNING,MULTICAST,DHCP,IPv4> mtu 1500 index 2 inet 172.19.48.214 netmask ffffff00 broadcast 172.19.48.255 ether 8:0:27:13:c9:20 Notice that when run as root, ifconfig shows the hardware address, but when run as a user, it does not. $ netstat -r Routing Table: IPv4 Destination Gateway Flags Ref Use Interface -------------------- -------------------- ----- ----- ---------- --------- default 172.19.48.1 UG 1 1662696 e1000g0 172.19.48.0 CPSC424-Orange U 1 809 e1000g0 BASE-ADDRESS.MCAST.NET CPSC424-Orange U 1 0 e1000g0 localhost localhost UH 1 92 lo0 solaris$ route get google.com route to: yw-in-f99.1e100.net destination: default mask: default gateway: 172.19.48.1 interface: e1000g0 flags: <UP,GATEWAY,DONE,STATIC> recvpipe sendpipe ssthresh rtt,ms rttvar,ms hopcount mtu expire 0 0 0 0 0 0 1500 0 Solaris DHCP Configuration Solaris includes a DHCP client and wins the prize for the easiest and most sensible DHCP client configuration: $ sudo ifconfig interface dhcp It just works! ifconfig calls the dhcpagent program to get the parameters for the interface from DHCP and to configure the interface with them. You can include several options on the ifconfig command line to specify the interface as the primary one, set timeouts, increase lease times, or display the status of the interface. To manually unconfigure DHCP, just run $ sudo ifconfig interface drop This is all very nice, but you probably want DHCP to be automatically consulted at boot time. You can set this up either by providing no configuration files for an interface at all, thus relying on autoconfiguration, or by creating an /etc/dhcp.interface file to go with the corresponding /etc/hostname.interface file. If you like, the dhcp.interface file can contain additional command-line parameters to be passed to the ifconfig command. The hostname.interface file must still exist to get the interface to be plumbed. However, it can be left empty. If the hostname.interface file is not empty, the startup scripts will first statically configure the interface by using its content and then later reconfigure the interface by using DHCP. dhcpagent manages the interface from DHCP’s point of view. Among other tasks, it negotiates extensions to leases and cancels leases when they are no longer needed. If an interface that has been configured with DHCP is later reconfigured by hand, dhcpagent will discontinue management of that interface. dhcpagent collects the leased values from the DHCP server, default route, domain name servers, etc, but it does not act on most of them directly. Instead, it makes the parameters available through the dhcpinfo command. The service management scripts consult dhcpinfo for various pieces of information, which are then used as arguments to route, put into the resolv.conf file, etc. dhcpagent transmits errors to syslog with facility daemon and priorities info through critical. Debug-level syslog output is available with the -d flag. You can check the files in /etc/dhcp to view the configuration of a particular interface. However, the existence of an interface.dhc file for an interface does not necessarily mean that dhcpagent is currently controlling the interface – the lease may have expired. ndd: TCP/IP and Interface Tuning For Solaris Solaris’s ndd command reconfigures the TCP/IP protocol stack on a running system. Perhaps “reconfigure” is too strong a word. Each module exposes parameters that can be examined and in some cases adjusted on the fly. The basic syntax is nnd [ -set ] device ? | variable [ value ] If you give the argument ?, which must be protected from the shell as \?, ndd returns a list of variables understood by the driver for the specific device. If you supply the name of a variable, nnd returns the value of that variable.
Load more

Recommended publications
  • Rudiments of Routing
    Rudiments of Routing Moving bits from the source to the destination is a major function of computer networking. On the current Internet, the Network layer is responsible for achieving this. AS 2 AS 1 Inter-domain routing OSPF and RIP Inter-domain routing OSPF and RIP Intra-domain routing BGP In general, most routing within Autonomous Systems use Routing Information Protocol (RIP), or its enhanced version Open Shortest Path First (OSPF). The current de facto Intra-domain routing standard is Border Gateway Protocol(BGP), Version 4. You need to concern yourself with these protocols if you are dealing with routers inside or between Autonomous Systems. At the host level, however, most likely you need only a static routing table. This is a table of routes that the OS kernel keeps. It is possible to add to and delete from routes in the kernel routing table relatively easily. We discuss routing tables based on RIP (RFC2453). When looking at routing tables, remember that most Unix-like operating systems use mnemonic names for their interfaces. For example, in Linux, the Ethernet interfaces on a machine are called eth0, eth1, eth2, etc. On the newer SUN/Solaris machines the interfaces are named eri0, eri1, etc. PPP interfaces are usually names ppp0, ppp1 etc. You can see all the configured interfaces on a host using the ifconfig command which is usually found in /sbin/ directory (but not always). You can see the routing table with ªnetstat -rº command. Here©s a screen shot of these commands run on matrix.newpaltz.edu which is a SUN/Solaris machine: The output from /sbin/ifconfig command shows that there are two configured interfaces, one an Ethernet and the other the loopback interface.
    [Show full text]
  • Powerview Command Reference
    PowerView Command Reference TRACE32 Online Help TRACE32 Directory TRACE32 Index TRACE32 Documents ...................................................................................................................... PowerView User Interface ............................................................................................................ PowerView Command Reference .............................................................................................1 History ...................................................................................................................................... 12 ABORT ...................................................................................................................................... 13 ABORT Abort driver program 13 AREA ........................................................................................................................................ 14 AREA Message windows 14 AREA.CLEAR Clear area 15 AREA.CLOSE Close output file 15 AREA.Create Create or modify message area 16 AREA.Delete Delete message area 17 AREA.List Display a detailed list off all message areas 18 AREA.OPEN Open output file 20 AREA.PIPE Redirect area to stdout 21 AREA.RESet Reset areas 21 AREA.SAVE Save AREA window contents to file 21 AREA.Select Select area 22 AREA.STDERR Redirect area to stderr 23 AREA.STDOUT Redirect area to stdout 23 AREA.view Display message area in AREA window 24 AutoSTOre ..............................................................................................................................
    [Show full text]
  • Lab Intro to Console Commands
    New Lab Intro to KDE Terminal Konsole After completing this lab activity the student will be able to; Access the KDE Terminal Konsole and enter basic commands. Enter commands using a typical command line interface (CLI). Explain the use of the following commands, ls, ls –al, dir, mkdir, whoami, Explain the directory structure of a typical user. This lab activity will introduce you to one of the many command line interfaces available in Linux/UNIX operating systems and a few of the most basic commands. The command line interface you will be using for this lab activity is the console called the Konsole and is also referred to as Terminal. Note: As you notice, in the KDE system many features are written with the capital letter “K” in place of the first letter or the utility to reflect the fact it was modified for the KDE system. The original UNIX system did not use a graphical user interface GUI but rather was a command line interface (CLI) similar to the command prompt in Windows operating systems. The command line interface is referred to as a shell. Even today the command line interface (the shell) is used to issue commands on a Linux server to minimize system resources. For example, there is no need to start the GUI on the server to add a new user to an existing system. Starting the GUI will reduce the system performance because it requires RAM to run the GUI. A GUI will affect the overall performance of the server when it is supporting many users (clients).
    [Show full text]
  • Command-Line IP Utilities This Document Lists Windows Command-Line Utilities That You Can Use to Obtain TCP/IP Configuration Information and Test IP Connectivity
    Guide to TCP/IP: IPv6 and IPv4, 5th Edition, ISBN 978-13059-4695-8 Command-Line IP Utilities This document lists Windows command-line utilities that you can use to obtain TCP/IP configuration information and test IP connectivity. Command parameters and uses are listed for the following utilities in Tables 1 through 9: ■ Arp ■ Ipconfig ■ Netsh ■ Netstat ■ Pathping ■ Ping ■ Route ■ Tracert ARP The Arp utility reads and manipulates local ARP tables (data link address-to-IP address tables). Syntax arp -s inet_addr eth_addr [if_addr] arp -d inet_addr [if_addr] arp -a [inet_address] [-N if_addr] [-v] Table 1 ARP command parameters and uses Parameter Description -a or -g Displays current entries in the ARP cache. If inet_addr is specified, the IP and data link address of the specified computer appear. If more than one network interface uses ARP, entries for each ARP table appear. inet_addr Specifies an Internet address. -N if_addr Displays the ARP entries for the network interface specified by if_addr. -v Displays the ARP entries in verbose mode. -d Deletes the host specified by inet_addr. -s Adds the host and associates the Internet address inet_addr with the data link address eth_addr. The physical address is given as six hexadecimal bytes separated by hyphens. The entry is permanent. eth_addr Specifies physical address. if_addr If present, this specifies the Internet address of the interface whose address translation table should be modified. If not present, the first applicable interface will be used. Pyles, Carrell, and Tittel 1 Guide to TCP/IP: IPv6 and IPv4, 5th Edition, ISBN 978-13059-4695-8 IPCONFIG The Ipconfig utility displays and modifies IP address configuration information.
    [Show full text]
  • Lab 5.5.2: Examining a Route
    Lab 5.5.2: Examining a Route Topology Diagram Addressing Table Device Interface IP Address Subnet Mask Default Gateway S0/0/0 10.10.10.6 255.255.255.252 N/A R1-ISP Fa0/0 192.168.254.253 255.255.255.0 N/A S0/0/0 10.10.10.5 255.255.255.252 10.10.10.6 R2-Central Fa0/0 172.16.255.254 255.255.0.0 N/A N/A 192.168.254.254 255.255.255.0 192.168.254.253 Eagle Server N/A 172.31.24.254 255.255.255.0 N/A host Pod# A N/A 172.16. Pod#.1 255.255.0.0 172.16.255.254 host Pod# B N/A 172.16. Pod#. 2 255.255.0.0 172.16.255.254 S1-Central N/A 172.16.254.1 255.255.0.0 172.16.255.254 All contents are Copyright © 1992–2007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 1 of 7 CCNA Exploration Network Fundamentals: OSI Network Layer Lab 5.5.1: Examining a Route Learning Objectives Upon completion of this lab, you will be able to: • Use the route command to modify a Windows computer routing table. • Use a Windows Telnet client command telnet to connect to a Cisco router. • Examine router routes using basic Cisco IOS commands. Background For packets to travel across a network, a device must know the route to the destination network. This lab will compare how routes are used in Windows computers and the Cisco router.
    [Show full text]
  • DVR Network Setup Connect the DVR to a Router Using a Networking
    DVR Network Setup Connect the DVR to a router using a networking cable. The cable should snap in on both ends. Connect a monitor and mouse to the DVR. Power on the DVR. On a computer connected to the same router as the DVR: Go to the Start Menu and Search or Run "cmd". If using Windows 8 or 10, press Windows + X and select "Command Prompt" Type in "ipconfig" and press enter. Write down the IP address, subnet mask, and default gateway. If using Mac OS X, go to System Preferences->Network->Advanced and note the IPv4 address, subnet mask, and router (gateway) address. You can skip the wizard on the DVR if it comes up. On the DVR , go to Menu->Configuration->Network->General. The default login is user “admin” and password “aaaa1111” (or “12345” on revision 1 units). Uncheck “Enable DHCP” Set the IPv4 address to the same as the PC's except the last 3 digits . The last 3 digits must be unique on the network (not used by any other device including the default gateway). If you don't know which addresses are already in use, check your router's list of connected devices. The last 3 digits should be less than 254 and greater than 1. Some routers may have additional restrictions on the range of allowed addresses. Here we have selected "112" for the last 3 digits. Write down the new IP address. Set the IPv4 Subnet and Default Gateway numbers to be same as the PC's. The Prefered DNS Server can be either your Gateway number (192.168.1.1 in this example) or the DNS address provided by your ISP.
    [Show full text]
  • Hikvision IP Camera Setup
    Hikvision IP camera setup Introduction: In this guide we will go through the necessary steps to enable a Hikvision IP camera to be accessible on a network and viewable through a web browser. Step 1: First plug your camera into your network switch or router and make sure it has power either through POE or using a power supply. Next, locate the CD that came with your Hikvision IP camera and insert it into a PC. There should be a folder named SADP. Inside you will see a file labeled SADP Setup, double click this file to begin the installation. Once the installation is done the program should automatically open and list any Hikvision devices connected to your network. (The Default IP address is 192.0.0.64) Step 2: Next you will need to find the Default Gateway for your network. To do this click on the start menu, in the search bar at the bottom type in "cmd" then press enter. This will bring up the command prompt window. In the command prompt window type "ipconfig" then press enter. This will bring up information such as your IP address, Subnet Mask, and Default Gateway. Now, find where it says Default Gateway and you should have a set of numbers listed to the right. Write this down or take note of it because we will use it here soon. (You can see in the example below our Default Gateway is: 192.168.1.1, keep in mind that yours may be different, that is okay.) Step 3: Now that we have the Default Gateway go back to the SADP program and select your IP camera by clicking on it.
    [Show full text]
  • Changing the IP Address Scope of the Media Gateway to Allow Use of Customer-Owned Routers
    Changing the IP Address scope of the media gateway to allow use of customer-owned routers This method does not require making any changes to the customer-owned router and can be completed by accessing the Media Gateway’s router and the powercycling of devices. The HomeConnect functionality may not be available on some devices when using this method. HomeConnect functionality may not work correctly using this method and devices connected to the Gateway’s Ethernet ports or wireless may not be able to communicate with devices connected to the customer’s router. Description The wireless can be enabled on both the Ultra TV Media Gateway and the customer- owned router at the same time. The DHCP is enabled on the customer-owned router and the Media Gateway, and both have a separate IP address scope to assign to connected devices. The customer- owned router is connected to the “1” Ethernet port of the Gateway using the Internet/WAN port on the router. Example This image shows how devices are connected to the Media Gateway and the customer-owned router. Configuring the Gateway 1. Access the Media Gateway: a. Enter “192.168.0.1” into the address bar of any web browser. b. Press the “Enter” key. c. Enter “technician” in the User Name field. d. Enter “WOWpass” in the Password field. If the user name and password combination do not work, the customer must call WOW! to have the password reset. e. Click the “Apply” button. 2. Click the “LAN Setup” tab. 3. Enter “192.168.2.1” in the IP Address field.
    [Show full text]
  • UEFI Shell Specification
    UEFI Shell Specification January 26, 2016 Revision 2.2 The material contained herein is not a license, either expressly or impliedly, to any intellectual property owned or controlled by any of the authors or developers of this material or to any contribution thereto. The material contained herein is provided on an "AS IS" basis and, to the maximum extent permitted by applicable law, this information is provided AS IS AND WITH ALL FAULTS, and the authors and developers of this material hereby disclaim all other warranties and conditions, either express, implied or statutory, including, but not limited to, any (if any) implied warranties, duties or conditions of merchantability, of fitness for a particular purpose, of accuracy or completeness of responses, of results, of workmanlike effort, of lack of viruses and of lack of negligence, all with regard to this material and any contribution thereto. Designers must not rely on the absence or characteristics of any features or instructions marked "reserved" or "undefined." The Unified EFI Forum, Inc. reserves any features or instructions so marked for future definition and shall have no responsibility whatsoever for conflicts or incompatibilities arising from future changes to them. ALSO, THERE IS NO WARRANTY OR CONDITION OF TITLE, QUIET ENJOYMENT, QUIET POSSESSION, CORRESPONDENCE TO DESCRIPTION OR NON-INFRINGEMENT WITH REGARD TO THE SPECIFICATION AND ANY CONTRIBUTION THERETO. IN NO EVENT WILL ANY AUTHOR OR DEVELOPER OF THIS MATERIAL OR ANY CONTRIBUTION THERETO BE LIABLE TO ANY OTHER PARTY FOR THE COST OF PROCURING SUBSTITUTE GOODS OR SERVICES, LOST PROFITS, LOSS OF USE, LOSS OF DATA, OR ANY INCIDENTAL, CONSEQUENTIAL, DIRECT, INDIRECT, OR SPECIAL DAMAGES WHETHER UNDER CONTRACT, TORT, WARRANTY, OR OTHERWISE, ARISING IN ANY WAY OUT OF THIS OR ANY OTHER AGREEMENT RELATING TO THIS DOCUMENT, WHETHER OR NOT SUCH PARTY HAD ADVANCE NOTICE OF THE POSSIBILITY OF SUCH DAMAGES.
    [Show full text]
  • Networking Basics
    Networking Basics Pre-class work…read/watch all the material at least once before class…I will clarify in class. Binary Training(Google search for “binary tutorial”): http://www.math.grin.edu/~rebelsky/Courses/152/97F/Readings/student-binary http://www.codeconquest.com/tutorials/binary/ https://www.youtube.com/watch?v=0qjEkh3P9RE https://www.youtube.com/watch?v=VBDoT8o4q00 Subnet Addressing and Masks(Google search for “subnet mask tutorial”: http://www.techopedia.com/6/28587/internet/8-steps-to-understanding-ip-subnetting http://www.subnetting.net/Tutorial.aspx https://www.youtube.com/watch?v=aA-8owNNy_c 2/10/2017 1 Table of Contents (3)What is the OSI Model? (6)What is a Hub, Switch, & Router/Access Server? (10)Mac Addresses and IP Addresses (15)The “3 GOLDEN PARAMETERS” (16)Day in the Life of a Packet (17)Duplex Issues (18)PC Configuration Guidance (21)Basic Discovery & Connectivity Tools (23)IPv4 Layers and Port Numbers 2/10/2017 2 What is the OSI Model? OSI – open systems interconnection Main functions Network dependent functions Application-oriented functions Seven layer model Each layer performs a well- defined set of functions 2/10/2017 3 Data Encapsulation Application User data Presentation converted for Data (PDU) transmission Session Add transport Segments Transport type header Add network Packets Network header (datagram) Add datalink Frames Datalink header Convert 11001010…100 Bits Physical to bits 2/10/2017 4 ISO’s OSI Reference Model Application Application Presentation Presentation Session Session Transport Transport
    [Show full text]
  • Linux Networking 101
    The Gorilla ® Guide to… Linux Networking 101 Inside this Guide: • Discover how Linux continues its march toward world domination • Learn basic Linux administration tips • See how easy it can be to build your entire network on a Linux foundation • Find out how Cumulus Linux is your ticket to networking freedom David M. Davis ActualTech Media Helping You Navigate The Technology Jungle! In Partnership With www.actualtechmedia.com The Gorilla Guide To… Linux Networking 101 Author David M. Davis, ActualTech Media Editors Hilary Kirchner, Dream Write Creative, LLC Christina Guthrie, Guthrie Writing & Editorial, LLC Madison Emery, Cumulus Networks Layout and Design Scott D. Lowe, ActualTech Media Copyright © 2017 by ActualTech Media. All rights reserved. No portion of this book may be reproduced or used in any manner without the express written permission of the publisher except for the use of brief quotations. The information provided within this eBook is for general informational purposes only. While we try to keep the information up- to-date and correct, there are no representations or warranties, express or implied, about the completeness, accuracy, reliability, suitability or availability with respect to the information, products, services, or related graphics contained in this book for any purpose. Any use of this information is at your own risk. ActualTech Media Okatie Village Ste 103-157 Bluffton, SC 29909 www.actualtechmedia.com Entering the Jungle Introduction: Six Reasons You Need to Learn Linux ....................................................... 7 1. Linux is the future ........................................................................ 9 2. Linux is on everything .................................................................. 9 3. Linux is adaptable ....................................................................... 10 4. Linux has a strong community and ecosystem ........................... 10 5.
    [Show full text]
  • Lab 9.3.7 Workstation ARP – Instructor Version
    Lab 9.3.7 Workstation ARP – Instructor Version Objective • Introduce Address Resolution Protocol (ARP) and the arp –a workstation command. • Explore the arp command help feature using the -? option. Background / Preparation ARP is used as a tool for confirming that a computer is successfully resolving network Layer 3 addresses to Media Access Control (MAC) Layer 2 addresses. The TCP/IP network protocol relies on IP addresses like 192.168.14.211 to identify individual devices and to assist in navigating data packets between networks. While the IP address is essential to move data from one LAN to another, it cannot deliver the data in the destination LAN by itself. Local network protocols, like Ethernet or Token Ring, use the MAC, or Layer 2, address to identify local devices and deliver all data. A computer MAC address has been seen in prior labs. This is an example of a MAC address: • 00-02-A5-9A-63-5C A MAC address is a 48-bit address displayed in Hexadecimal (HEX) format as six sets of two HEX characters separated by dashes. In this format each hex symbol represents 4 bits. With some devices, the 12 hex characters may be displayed as three sets of four characters separated by periods or colons (0002.A59A.635C). ARP maintains a table in the computer of IP and MAC address combinations. In other words, it keeps track of which MAC address is associated with an IP address. If ARP does not know the MAC address of a local device, it issues a broadcast using the IP address.
    [Show full text]