riplib.html

vxworks相关论文

    char*                                  pIpAddr, /* IP address in dotted */
                                                    /* notation */
    BOOL (* ripSendHook) (struct rt_entry* pRt)     /* Routine to use. */
    )</pre>

</blockquote><h4>DESCRIPTION</h4><blockquote><p>
This routine installs a hook routine to screen individual route entries
for inclusion in a periodic update. The routine is installed for the
registered interface given by <i>pIpAddr</i>. (Interfaces created or
changed after a RIP session has started may be installed/updated with 
the <b><i><a href="./ripLib.html#ripIfSearch">ripIfSearch</a></i>(&nbsp;)</b> and <b><i><a href="./ripLib.html#ripIfReset">ripIfReset</a></i>(&nbsp;)</b> routines).
<p>
The hook uses the following prototype:
<pre>    BOOL ripSendHookRtn (struct rt_entry* pRt);
</pre>

If the hook returns FALSE, the route is not included in the update.
Otherwise, it is included if it meets the other restrictions, such
as simple split horizon and border gateway filtering. The 
<b><i><a href="./ripLib.html#ripSendHookDelete">ripSendHookDelete</a></i>(&nbsp;)</b> routine removes this additional filter from the
output processing.
<p>
</blockquote><h4>RETURNS</h4><blockquote><p>
OK, or ERROR if the interface could not be found.
<p>
</blockquote><h4>ERRNO</h4><blockquote><p>
<p>
&nbsp;S_m2Lib_INVALID_PARAMETER<br>
&nbsp;S_m2Lib_ENTRY_NOT_FOUND
</blockquote><h4>SEE ALSO</h4><blockquote><p>
<b><a href="./ripLib.html#top">ripLib</a></b>

<hr>
<a name="ripSendHookDelete"></a>
<p align=right>
<a href="rtnIndex.html"><i>Libraries :  Routines</i></a></p>

</blockquote><h1><i>ripSendHookDelete</i>(&nbsp;)</h1> <blockquote></a></blockquote><h4>NAME</h4><blockquote>  
<p><strong><i>ripSendHookDelete</i>(&nbsp;)</strong> - remove an update filter from a RIP interface</p>

</blockquote><h4>SYNOPSIS</h4><blockquote><p>
<pre>STATUS ripSendHookDelete
    (
    char* pIpAddr /* IP address in dotted decimal notation */
    )</pre>

</blockquote><h4>DESCRIPTION</h4><blockquote><p>
This routine removes the hook routine that allowed additional screening
of route entries in periodic updates from the registered interface
indicated by <i>pIpAddr</i>. (Interfaces created or changed after a RIP 
session has started may be installed/updated with the <b><i><a href="./ripLib.html#ripIfSearch">ripIfSearch</a></i>(&nbsp;)</b> 
and <b><i><a href="./ripLib.html#ripIfReset">ripIfReset</a></i>(&nbsp;)</b> routines). The RIP session will return to the default 
behavior and include any entries which meet the other restrictions (such 
as simple split horizon).
<p>
</blockquote><h4>RETURNS</h4><blockquote><p>
OK, or ERROR if the interface could not be found.
<p>
</blockquote><h4>ERRNO</h4><blockquote><p>
<p>
&nbsp;S_m2Lib_INVALID_PARAMETER<br>
&nbsp;S_m2Lib_ENTRY_NOT_FOUND
</blockquote><h4>SEE ALSO</h4><blockquote><p>
<b><a href="./ripLib.html#top">ripLib</a></b>

<hr>
<a name="ripIfSearch"></a>
<p align=right>
<a href="rtnIndex.html"><i>Libraries :  Routines</i></a></p>

</blockquote><h1><i>ripIfSearch</i>(&nbsp;)</h1> <blockquote></a></blockquote><h4>NAME</h4><blockquote>  
<p><strong><i>ripIfSearch</i>(&nbsp;)</strong> - add new interfaces to the internal list</p>

</blockquote><h4>SYNOPSIS</h4><blockquote><p>
<pre>

void ripIfSearch (void)</pre>

</blockquote><h4>DESCRIPTION</h4><blockquote><p>
By default, a RIP session will not recognize any interfaces initialized
after it has started. This routine schedules a search for additional
interfaces which will occur during the next update of the internal routing
table. Once completed, the session will accept and send RIP messages over
the new interfaces.
<p>
</blockquote><h4>RETURNS</h4><blockquote><p>
N/A
<p>
</blockquote><h4>ERRNO</h4><blockquote><p>
N/A
<p>
</blockquote><h4>SEE ALSO</h4><blockquote><p>
<b><a href="./ripLib.html#top">ripLib</a></b>

<hr>
<a name="ripIfReset"></a>
<p align=right>
<a href="rtnIndex.html"><i>Libraries :  Routines</i></a></p>

</blockquote><h1><i>ripIfReset</i>(&nbsp;)</h1> <blockquote></a></blockquote><h4>NAME</h4><blockquote>  
<p><strong><i>ripIfReset</i>(&nbsp;)</strong> - alter the RIP configuration after an interface changes</p>

</blockquote><h4>SYNOPSIS</h4><blockquote><p>
<pre>STATUS ripIfReset
    (
    char * pIfName /* name of changed interface */
    )</pre>

</blockquote><h4>DESCRIPTION</h4><blockquote><p>
This routine updates the interface list and routing tables to reflect
address and/or netmask changes for the device indicated by <i>pIfName</i>. 
To accommodate possible changes in the network number, all routes using 
the named interface are removed from the routing tables, but will be
added in the next route update if appropriate. None of the removed
routes are poisoned, so it may take some time for the routing tables of
all the RIP participants to stabilize if the network number has changed.
<p>
</blockquote><h4>RETURNS</h4><blockquote><p>
OK, or ERROR if named interface not found or not added to list.
<p>
</blockquote><h4>ERRNO</h4><blockquote><p>
N/A
<p>
</blockquote><h4>SEE ALSO</h4><blockquote><p>
<b><a href="./ripLib.html#top">ripLib</a></b>

<hr>
<a name="ripFilterEnable"></a>
<p align=right>
<a href="rtnIndex.html"><i>Libraries :  Routines</i></a></p>

</blockquote><h1><i>ripFilterEnable</i>(&nbsp;)</h1> <blockquote></a></blockquote><h4>NAME</h4><blockquote>  
<p><strong><i>ripFilterEnable</i>(&nbsp;)</strong> - activate strict border gateway filtering</p>

</blockquote><h4>SYNOPSIS</h4><blockquote><p>
<pre>

void ripFilterEnable (void)</pre>

</blockquote><h4>DESCRIPTION</h4><blockquote><p>
This routine configures an active RIP session to enforce the restrictions 
necessary for RIP-1 and RIP-2 routers to operate correctly in the same 
network as described in section 3.2 of RFC 1058 and section 3.3 of RFC 1723. 
When enabled, routes to portions of a logical network (including host 
routes) will be limited to routers within that network. Updates sent 
outside that network will only include a single entry representing the 
entire network. That entry will subsume all subnets and host-specific
routes. If supernets are used, the entry will advertise the largest
class-based portion of the supernet reachable through the connected
interface.
<p>
</blockquote><h4>RETURNS</h4><blockquote><p>
N/A
<p>
</blockquote><h4>ERRNO</h4><blockquote><p>
N/A
<p>
</blockquote><h4>SEE ALSO</h4><blockquote><p>
<b><a href="./ripLib.html#top">ripLib</a></b>

<hr>
<a name="ripFilterDisable"></a>
<p align=right>
<a href="rtnIndex.html"><i>Libraries :  Routines</i></a></p>

</blockquote><h1><i>ripFilterDisable</i>(&nbsp;)</h1> <blockquote></a></blockquote><h4>NAME</h4><blockquote>  
<p><strong><i>ripFilterDisable</i>(&nbsp;)</strong> - prevent strict border gateway filtering</p>

</blockquote><h4>SYNOPSIS</h4><blockquote><p>
<pre>

void ripFilterDisable (void)</pre>

</blockquote><h4>DESCRIPTION</h4><blockquote><p>
This routine configures an active RIP session to ignore the restrictions 
necessary for RIP-1 and RIP-2 routers to operate correctly in the same 
network. All border gateway filtering is ignored and all routes to
subnets, supernets, and specific hosts will be sent over any available 
interface. This operation is only correct if no RIP-1 routers are present 
anywhere on the network. Results are unpredictable if that condition is 
not met, but high rates of packet loss and widespread routing failures are 
likely.
<p>
The border gateway filtering rules are in force by default.
<p>
</blockquote><h4>RETURNS</h4><blockquote><p>
N/A
<p>
</blockquote><h4>ERRNO</h4><blockquote><p>
N/A
<p>
</blockquote><h4>SEE ALSO</h4><blockquote><p>
<b><a href="./ripLib.html#top">ripLib</a></b>

<hr>
<a name="ripShutdown"></a>
<p align=right>
<a href="rtnIndex.html"><i>Libraries :  Routines</i></a></p>

</blockquote><h1><i>ripShutdown</i>(&nbsp;)</h1> <blockquote></a></blockquote><h4>NAME</h4><blockquote>  
<p><strong><i>ripShutdown</i>(&nbsp;)</strong> - terminate all RIP processing</p>

</blockquote><h4>SYNOPSIS</h4><blockquote><p>
<pre>

STATUS ripShutdown (void)</pre>

</blockquote><h4>DESCRIPTION</h4><blockquote><p>
This routine "poisons" all routes in the current table by transmitting
updates with an infinite metric for each entry over all available
interfaces. It then halts all RIP processing and removes the associated
tasks and data structures. When completed successfully, the RIP
services are unavailable until restarted with the <b><i><a href="./ripLib.html#ripLibInit">ripLibInit</a></i>(&nbsp;)</b> routine.
<p>
</blockquote><h4>RETURNS</h4><blockquote><p>
OK if shutdown completed, or ERROR otherwise.
<p>
</blockquote><h4>ERRNO</h4><blockquote><p>
N/A
<p>
</blockquote><h4>SEE ALSO</h4><blockquote><p>
<b><a href="./ripLib.html#top">ripLib</a></b>

<hr>
<a name="ripDebugLevelSet"></a>
<p align=right>
<a href="rtnIndex.html"><i>Libraries :  Routines</i></a></p>

</blockquote><h1><i>ripDebugLevelSet</i>(&nbsp;)</h1> <blockquote></a></blockquote><h4>NAME</h4><blockquote>  
<p><strong><i>ripDebugLevelSet</i>(&nbsp;)</strong> - specify amount of debugging output</p>

</blockquote><h4>SYNOPSIS</h4><blockquote><p>
<pre>void ripDebugLevelSet
    (
    int level /* verbosity level (0 - 3) */
    )</pre>

</blockquote><h4>DESCRIPTION</h4><blockquote><p>
This routine influences the amount of debugging information sent to
standard output during the RIP session. Higher values of the <i>level</i>
parameter result in increasingly verbose output. A <i>level</i> of zero
restores the default behavior by disabling all debugging output.
<p>
</blockquote><h4>RETURNS</h4><blockquote><p>
N/A
<p>
</blockquote><h4>ERRNO</h4><blockquote><p>
N/A
</blockquote><h4>SEE ALSO</h4><blockquote><p>
<b><a href="./ripLib.html#top">ripLib</a></b>

</body>
</html>