Demand-Dial Routing
Demand-Dial Routing |
|
For persistent demand-dial connections, routing protocols can be enabled to operate in the same fashion as LAN interfaces to provide dynamic updates of routing tables. Special configuration of the routing protocol for a persistent demand-dial interface is outlined in Table 6.3.
Table 6.3 Changes to Default Routing Protocol Configuration for Demand-Dial Interfaces
| Routing Protocol | Configuration Change |
|---|---|
| RIP for IP | Change the default operation mode to Periodic update mode and enable triggered updates. |
| OSPF | Select the Point-to-point network type on the General tab on the properties of an OSPF interface. This is the default network type for demand-dial interfaces. For a persistent router-to-router VPN connection, you might want to increase the values of the transit delay, the re-transmit interval, the hello interval, and the dead interval on the Advanced tab on the properties of an OSPF interface to account for the delay of forwarding OSPF packets across the Internet. |
| RIP for IPX | Change the update mode to Standard. |
| SAP for IPX | Change the update mode to Standard. |
In all cases, including autostatic updates, routing protocols provided by the Windows 2000 Routing and Remote Access service must run over a numbered connection. A numbered connection is assigned an IP or IPX address during the PPP connection process. Unnumbered connections are supported by the Routing and Remote Access service, but routing protocols do not work over them. An unnumbered connection is typically used when dialing an Internet service provider who does not want to waste IP addresses for the point-to-point connection. The Internet connection can be unnumbered because you would typically configure a default static IP route, rather than run a routing protocol.