|
ru.unix.bsd
- RU.UNIX.BSD ------------------------------------------------------------------
From : Alexandr Oskolkov 2:5080/68.38 15 May 2004 21:11:56
To : eugen@grosbein.pp.ru
Subject : RIPv2 на P2P
--------------------------------------------------------------------------------
14 May 04 21:44, Eugene Grosbein wrote to Slawa Olhovchenkov:
EG>>>>> Hачнем с того, что переписывание ripd я не потяну.
EG>>> routed/ripd хотят работать мультикастоми. Первая строка квоты.
SO>> Hу и что? А по стандарту им это разрешено?
EG> Hе знаю. Думаю, что да.
RFC 2453 RIP Version 2 November 1998
3.9.1 Request Messages
A Request is used to ask for a response containing all or part of a
router's routing table. Normally, Requests are sent as broadcasts
(multicasts for RIP-2), from the RIP port, by routers which have just
come up and are seeking to fill in their routing tables as quickly as
possible. However, there may be situations (e.g., router monitoring)
where the routing table of only a single router is needed. In this
case, the Request should be sent directly to that router from a UDP
port other than the RIP port. If such a Request is received, the
router responds directly to the requestor's address and port.
3.10 Output Processing
This section describes the processing used to create response
messages that contain all or part of the routing table. This
processing may be triggered in any of the following ways:
- By input processing, when a Request is received (this Response is
unicast to the requestor; see section 3.7.1)
- By the regular routing update (broadcast/multicast every 30
seconds) router.
- By triggered updates (broadcast/multicast when a route changes)
When a Response is to be sent to all neighbors (i.e., a regular or
triggered update), a Response message is directed to the router at
the far end of each connected point-to-point link, and is broadcast
(multicast for RIP-2) on all connected networks which support
broadcasting. Thus, one Response is prepared for each directly-
connected network, and sent to the appropriate address (direct or
broadcast/multicast). In most cases, this reaches all neighboring
routers. However, there are some cases where this may not be good
enough. This may involve a network that is not a broadcast network
(e.g., the ARPANET), or a situation involving dumb routers. In such
cases, it may be necessary to specify an actual list of neighboring
routers and send a datagram to each one explicitly. It is left to
4.5 Multicasting
In order to reduce unnecessary load on those hosts which are not
listening to RIP-2 messages, an IP multicast address will be used for
periodic broadcasts. The IP multicast address is 224.0.0.9. Note
that IGMP is not needed since these are inter-router messages which
are not forwarded.
On NBMA networks, unicast addressing may be used. However, if a
response addressed to the RIP-2 multicast address is received, it
should be accepted.
In order to maintain backwards compatibility, the use of the
multicast address will be configurable, as described in section 5.1.
If multicasting is used, it should be used on all interfaces which
support it.
With best wishes,
Alexandr.
--- GoldED+/W32 1.1.5-20020105
* Origin: 2B||!2B=? (2:5080/68.38)
Вернуться к списку тем, сортированных по: возрастание даты уменьшение даты тема автор
|
