ESIS(4) BSD Programmer's Manual ESIS(4)
e
\bes
\bs-
\b-i
\bis
\bs - End System to Intermediate System Routing Protocol
S
\bSY
\bYN
\bNO
\bOP
\bPS
\bSI
\bIS
\bS
p
\bps
\bse
\beu
\bud
\bdo
\bo-
\b-d
\bde
\bev
\bvi
\bic
\bce
\be
D
\bDE
\bES
\bSC
\bCR
\bRI
\bIP
\bPT
\bTI
\bIO
\bON
\bN
The E
\bES
\bS-
\b-I
\bIS
\bS routing protocol is used to dynamically map between ISO NSAP
addresses and ISO SNPA addresses; to permit End and Intermediate Systems
to learn of each other's existence; and to allow Intermediate Systems to
inform End Systems of (potentially) better routes to use when forwarding
NPDUs to a particular destination.
The mapping between NSAP addresses and SNPA addresses is accomplished by
transmitting hello PDUs between the cooperating Systems. These PDUs are
transmitted whenever the _
\bc_
\bo_
\bn_
\bf_
\bi_
\bg_
\bu_
\br_
\ba_
\bt_
\bi_
\bo_
\bn timer expires. When a hello PDU
is received, the SNPA address that it conveys is stored in the routing
table for as long as the _
\bh_
\bo_
\bl_
\bd_
\bi_
\bn_
\bg _
\bt_
\bi_
\bm_
\be in the PDU suggests. The default
_
\bh_
\bo_
\bl_
\bd_
\bi_
\bn_
\bg _
\bt_
\bi_
\bm_
\be (120 seconds) placed in the hello PDU, the configuration
timer value, and the system type (End System or Intermediate System) may
be changed by issuing an SIOCSSTYPE ioctl(2), which is defined in
_
\b/_
\bs_
\by_
\bs_
\b/_
\bn_
\be_
\bt_
\bi_
\bs_
\bo_
\b/_
\bi_
\bs_
\bo_
\b__
\bs_
\bn_
\bp_
\ba_
\bc_
\b._
\bh_
\b.
The protocol behaves differently depending on whether the System is con-
figured as an End System or an Intermediate System.
E
\bEN
\bND
\bD S
\bSY
\bYS
\bST
\bTE
\bEM
\bM O
\bOP
\bPE
\bER
\bRA
\bAT
\bTI
\bIO
\bON
\bN
When an interface requests a mapping for an address not in the cache, the
SNPA of any known Intermediate System is returned. If an Intermediate
System is not known, then the _
\ba_
\bl_
\bl _
\be_
\bn_
\bd _
\bs_
\by_
\bs_
\bt_
\be_
\bm_
\bs multicast address is re-
turned. It is assumed that the intended recipient of the NPDU will imme-
diately transmit a hello PDU back to the originator of the NPDU.
If an NPDU is forwarded by the End System, a redirect PDU will not be
generated. However, redirect PDUs received will be processed. This pro-
cessing consists of adding an entry in the routing table. If the redirect
is towards an Intermediate System, then an entry is made in the routing
table as well. The entry in the routing table will may mark the NSAP ad-
dress contained in the redirect PDU as the gateway for the destination
system (if an NET is supplied), or will create a route with the NSAP ad-
dress as the destination and the SNPA address (embodied as a link-level
sockaddr) as the gateway.
If the System is configured as an End System, it will report all the
NSAPs that have been configured using the ifconfig command, and no oth-
ers. It is possible to have more than one NSAP assigned to a given in-
terface, and it is also possible to have the same NSAP assigned to multi-
ple interfaces. However, any NSAP containing an NSEL that is consistent
with the nsellength option (default one) of any interface will be accept-
ed as an NSAP for this System.
I
\bIN
\bNT
\bTE
\bER
\bRM
\bME
\bED
\bDI
\bIA
\bAT
\bTE
\bE S
\bSY
\bYS
\bST
\bTE
\bEM
\bM O
\bOP
\bPE
\bER
\bRA
\bAT
\bTI
\bIO
\bON
\bN
When an interface requests a mapping for an address not in the routing
table, an error is returned.
When an NPDU is forwarded out on the same interface that the NPDU arrived
upon, a redirect PDU is generated.
M
\bMA
\bAN
\bNU
\bUA
\bAL
\bL R
\bRO
\bOU
\bUT
\bTI
\bIN
\bNG
\bG T
\bTA
\bAB
\bBL
\bLE
\bE M
\bMO
\bOD
\bDI
\bIF
\bFI
\bIC
\bCA
\bAT
\bTI
\bIO
\bON
\bN
To facilitate communications with systems which do not use E
\bES
\bS-
\b-I
\bIS
\bS,
\b, one may
add a route whose destination is a sockaddr_iso containing the NSAP in
question, and the gateway being a link-level sockaddr, either by writing
a special purpose program, or using the route(8) command e.g.:
route add -iface -osi 49.0.4.8.0.2b.b.83.bf -link qe0:8.0.2b.b.83.bf
If the System is configured as an End System and has a single network in-
terface which does not support multicast reception, it is necessary to
manually configure the location of an IS, using the route command in a
similar way. There, the destination address should be ``default''
(spelled out literally as 7 ASCII characters), and the gateway should be
once again be a link-level sockaddr specifying the SNPA of the IS.
S
\bSE
\bEE
\bE A
\bAL
\bLS
\bSO
\bO
un(4), iso(4), route(8), ifconfig(8)
_
\bE_
\bn_
\bd _
\bs_
\by_
\bs_
\bt_
\be_
\bm _
\bt_
\bo _
\bI_
\bn_
\bt_
\be_
\br_
\bm_
\be_
\bd_
\bi_
\ba_
\bt_
\be _
\bs_
\by_
\bs_
\bt_
\be_
\bm _
\br_
\bo_
\bu_
\bt_
\bi_
\bn_
\bg _
\be_
\bx_
\bc_
\bh_
\ba_
\bn_
\bg_
\be _
\bp_
\br_
\bo_
\bt_
\bo_
\bc_
\bo_
\bl _
\bf_
\bo_
\br _
\bu_
\bs_
\be _
\bi_
\bn
_
\bc_
\bo_
\bn_
\bj_
\bu_
\bn_
\bc_
\bt_
\bi_
\bo_
\bn _
\bw_
\bi_
\bt_
\bh _
\bt_
\bh_
\be _
\bP_
\br_
\bo_
\bt_
\bo_
\bc_
\bo_
\bl _
\bf_
\bo_
\br _
\bp_
\br_
\bo_
\bv_
\bi_
\bd_
\bi_
\bn_
\bg _
\bt_
\bh_
\be _
\bc_
\bo_
\bn_
\bn_
\be_
\bc_
\bt_
\bi_
\bo_
\bn_
\bl_
\be_
\bs_
\bs_
\b-_
\bm_
\bo_
\bd_
\be
_
\bn_
\be_
\bt_
\bw_
\bo_
\br_
\bk _
\bs_
\be_
\br_
\bv_
\bi_
\bc_
\be, ISO, 9542.
Redirect PDUs do not contain options from the forwarded NPDU which gener-
ated the redirect. The multicast address used on the 802.3 network is
taken from the NBS December 1987 agreements. This multicast address is
not compatible with the 802.5 (Token Ring) multicast addresses format.
Therefore, broadcast addresses are used on the 802.5 subnetwork. Re-
searchers at the University of Wisconsin are constructing an implementa-
tion of the IS-IS routing protocol.
projects / unix-history / blob