Summary routing

The route command

With the route command you can add routes to the Windows 2000 machine's routing table.  By default this table contains the following routes :

Network destination Netmask Gateway Interface Metric
Own network Own subnetmask Own ip address Own ip address 1
Own ip address 255.255.255.255 127.0.0.1 127.0.0.1 1
x.255.255.255 255.255.255.255 Own ip address Own ip address 1
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
224.0.0.0 255.0.0.0 Own ip address Own ip address 1
255.255.255.255 255.255.255.255 Own ip address Own ip address 1

The 127.0.0.0 row contains the loopback information. The 224.0.0.0 row is used for internet broadcasting. The 255.255.255.255 is called the limited broadcast address.

The metric column contains the number of routers that must be passed + 1 to reach the destination. If there are two routes the to the same destination, the route with the lowest metric is chosen. If the metric is the same, the route with the most restrictive subnetmask is chosen.

You can use the route command to add a static route :

Route add network destination  mask  netmask gateway metric metric if interface. Use the -p option if the route should be persistant.

You can use Route print to view the current routes.

If you want to add a internet router in the routing table, use the following command structure :

Route add 0.0.0.0 mask 0.0.0.0 ip address internet gateway

The 0.0.0.0 entry will handle all addresses that cannot be handled by the other entries in the routing table. This entry is called the default route.

Protocols

RIP

Routing Information Protocol. This protocol broadcasts routing information to neighboring routers when a change in the network layout is made. At a specific periods (by default every 30 seconds) RIP sends all routing information to neighboring routers. RIP is a distance vector routing protocol which means that the route used is based on the number of hops that must be passed. It is designed for small- and medium sized networks.
Windows 2000 support RIP version 1 and version 2. The main differences between RIP version 1 and RIP version 2 are :

bulletRIP version 2 supports CIDR (Classless inter domain routing). CIDR shows ip addresses in the format x.x.x.x /y where y indicates the number of bits used by the subnetmask.
bulletRIP version 2 supports Variable length subnet masks.
bulletRip version 2 uses multicast to update other routers (224.0.0.9), RIP version 1 uses broadcasts.
bulletRIP version 2 also offers authentication which RIP version 1 does not.

The main disadvantage of RIP is that it supports up to 15 hops, if more hops need to be taken the destination is reported unreachable. RIP also gives a higher chance of routing loops. When RIP advertises non-RIP-learned routers at a distance of 2 hops, even if the network is directly connected. RIP uses UPD port 520, the TTL for a RIP route is 3 minutes. If no update is receive after 3 minutes, the metric is increased to 16.

When customizing RIP you can e.g. modify the following entries :

bulletOperation mode. You can choose to use Auto-static mode or periodic mode. The periodic mode will send RIP information every 30 seconds by default (this value can be changed at the Advanced tab). Auto-static mode will only send updates when asked for by another router. This router will than clear existing auto-static entries and enter the new ones at static entries.
bulletOutgoing packet protocol. Set how RIP information is send. RIP v1 broadcast should be used if you only have RIP v1 routers. RIP v2 broadcasts will send broadcasts to RIP v1 and RIP v2 routers. RIP v2 multicast will only send RIP information to RIP v2 routers via a multicast. Silent RIP will disable outgoing RIP packets.
bulletIncoming packet protocol. RIP v1 and 2 will accept both kind of RIP information.
bulletAdded cost for routes. Set the cost for this interface between 1 and 15. The interface with the lowest cost will be shown if there is more than one interface to the same network.
bulletActive authentication. Enter the password that should be used to update the RIP tables. This password is send without encryption !
bulletRoute filter. Set which routes you allow to be stored in the routing table. You can choose Accept all routes, Accept all routes in the ranges listed or Ignore all routes in the ranges listed.
bulletNeighbors. Set which routers you want to send information Choose from Broadcast only, Multicast only, Neighbors in addition to broadcast or multicast or Neighbors instead of broadcasts or multicasts.
RIP version 1 is described in RFC 1058, RIP version 2 in RFC 2453.

OSPF

Open Shortest Path is a link-state routing protocol. In a link-state routing protocol, each router maintains a database of router advertisements called Link State Advertisements (LSAs). The LSA's within an autonomous system consist of a router, its attached networks, and their metrics.
The routers within an autonomous system distribute their LSA' s to their neighboring routers which store all information in a link state database (LSDB). These databases are synchronized between all neighboring routers so that each router has the same LSDB.
You can create various areas within a network. These areas will each have their own LSDB and there own area ID. If a router is within two or more areas, it keep LSDB's for each of these areas. Routers on the border of an area, connected to two or more areas, are called Area Border Routers (OBR). They advertise networks within the area to neighboring areas.
Each OSPF network has a backbone area with the area ID of 0.0.0.0. This backbone area acts as a hub for inter-area transit traffic and the distribution of routing information between areas. Inter-area traffic is routed to the backbone, then routed to the destination area, and finally routed to the destination host within the destination area. Routers on the backbone also advertise the summarized routes within their areas to the other routers on the backbone. Therefore, each router in an area has a routing table that reflects the routes available within its area and the routes corresponding to the summary advertisements of the ABR's of the other areas in the autonomous system.

OSPF uses the addresses 224.0.0.5 and 224.0.0.6 to send link update information.

The main advantages of OSPF are :

bulletRoutes outside an autonomous system can be advertised within a LSDB.
bulletOSPF detects changes faster than RIP.
bulletCount-to-infinity and loops will not occur.
bulletVery scalable to very large networks by subdividing autonomous system into seperate areas.
bulletOSPF supports supernetting, variable-length subnet masks and disjoint subnets.
bulletOSPF support clear password authentication.

Router discovery

Windows 2000 has a new feature to automatically detect default gateways. The mechanism is called router discovery and provides more flexibility than fixed default gateways offered via DHCP or fixed addresses. Windows 2000 support router discovery as a host and as a router. Router discovery uses two types of packets :

bulletRouter solicitations. When a RFC 1256 clients needs a default gateway it sends a ICMP multicast to address 224.0.0.2 (default) or a limited broadcast on address 255.255.255.255. Routers compliant with RFC 1256 will send responds from which the client chooses the default gateway with the highest preference level.
bulletRouter advertisements. A router advertisement is a periodic notice from the router to the host that the router is still available.

Windows 2000 and NT 4.0 SP5 and later include host support router discovery. To activate the host function, you need to add two subkeys to the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Adaptername\Parameters\Tcpip Registry key. Add the PerformRouterDiscovery subkey with a REG_DWORD value of 1, and add the SolicitationAddressBcast subkey with a REG_DWORD value of 0 (for multicast router solicitation) or 1 (for broadcast).

If you have an RRAS server participating in the discovery process as an "advertiser," you must set up RRAS by selecting IP ROUTING, then GENERAL, then choose the interface you would like to enable. From the GENERAL tab, select ENABLE ROUTER DISCOVERY ADVERTISEMENTS.

Router discovery is described in RFC 1256.

Multicast Routing

Windows 2000 Server supports a limited form of multicast routing by using a multicast proxy. This proxy can be used to provide multicast functionality for remote access users or a single LAN network connected to the Internet. One or more interfaces acts like a multicast router, while the other interface that has direct access to a true multicast router, forwards multicast traffic on behalf of the local clients.

Tools

Netsh

Netsh is a command-line and scripting tool.  You can use the RAS, Routing and Interface parts to configure and monitor RRAS.

Network monitor

Network monitor can be used to monitor network traffic at a computer's interface.

Rassrvmon

A resource kit utility to monitor details of the RRAS server.

Traceenable

A resource kit utility to trace RRAS internal components.

Windows XP/.Net improvements

bullet

Route management. Provides the ability to redirect internet traffic for a VPN. (WH0537N020701)

bullet

DHCP classless source routing (WH1252N101800)

bullet

Static IP route information via WMI (WH0053M101800)

bullet

IGMPv3 support (WH1022-0539N020601)

More information

Microsoft support articles

bulletHow to implement routing in Windows 2000 (Q274141)
bulletWindows NT/Windows 2000 is a single-route router (Q230623)
bulletHow to enable TCP/IP forwarding in Windows 2000 (Q230082)
bulletHow to use the Netsh.exe tool and command-line switches (Q242468)
bulletUsing the command Netsh to locally configure Windows 2000-based remote access servers and routers (Q254184)
bulletHow to use static routes with Routing and Remote Access Service (Q178993)
bulletInformation on static routes in Routing and Remote Access (Q169203)
bullet'p' switch for route command added in Windows NT (Q141383)
bulletDescription of the PING and Tracert rools (Q217014)
bulletUse tracert to troubleshoot TCP/IP problems in Windows NT (Q162326)
bulletSyntax help for PathPing utility shows incorrect options (Q244602)
bulletInterface number is changed after reboot using the Route command with IF parameter (Q263093)
bulletBoth adapters can be reached in multihomed Windows NT or Windows 2000 computer (Q139334)
bulletChange in remote access behavior with Windows 2000 (Q254231)
bulletMultiple default gateways can cause connection problems (Q159168)
bulletExpected behavior of multiple adapters on same network (Q175767)
bulletIPSec and IP-to-IP tunnels do not work with routing protocols such as RIP and OSPF (Q227523)
bulletHow to implement RIP over RRAS in Windows 2000 (Q241545)
bulletHow to implement RIP of RRAS in Windows 2000 (Q241545)
bulletSilent RIP and Windows 2000 server (Q246540)
bulletWindows NT 4.0 IP routing information protocol service does not upgrade to Windows 2000 routing and remote access (Q254269)
bulletOSPF over RRAS Dial-on-demand and VPN connections in Windows 2000 (Q241540)
bulletOSPF cost value limited to 32767 (Q234140)
bulletICMP redirect routes override OSPF routes (Q243427)
bulletOSPF non-broadcast multiple access neighbors are not display when you add them remotely to a Windows NT 4.0-based router (Q254237)
bulletIncorrect interface status when adding IP addresses to active OSPF interface (Q254238)
bulletPPP or PPTP multicast may require a manual route statements (Q226124)
bulletVPN tunnels - GRE protocol 47 packet description and use (Q241251)
bulletClient VPN IP address must be used when you add static routes for Windows 2000 VPN in (Q259171)
bulletRRAS VPN dial-on-demand failover mechanism (Q262990)
bulletDiagnoses and treatment of black hole routers (Q159211)
bulletEnabling IGMP routing causes event ID 202157 (Q221570)
bulletSome LAN switches with IGMP snooping enabled stop forwarding multicast packets on RRAS startup (Q223136)
bulletDescription of the mrinfo.exe tool for command-line access to multicast routing (Q225158)
bulletRouting does not work when multiple adapters use automatic private ip addressing simultaneously (Q244268)
bulletSupport demand-dial connections with LAN-only routing (Q254234)
bulletErr msg: The route addition failed: 87 (Q151795)
bulletWindows 2000 server with incoming connections configured loses TCP/IP redundancy features (Q254236)
bulletWindow appears briefly in routing and remote access MMC (Q233334)
bullet'Use default gateway on remote network' check boy is unavailable (Q254762)
bulletClient retains lower MTU on subsequent transmissions to multicast route (Q289165)
bulletNewly added static route is gone after reception of ICMP redirect message (Q289211)
bulletNETSH command does not show correct state for the internal interface (Q242065)
bulletRAS server silently enables IP forwarding on all interfaces (Q262083)

 

Links

bulletRouting and remote access links (Microsoft)
bulletConnecting remote sites (Resource kit chapter 7)
bulletRouting and remote access (Swynk)
bulletRAS links on Labmice
bulletBuilding redundant ip routing (Windows 2000 magazine jul 2000)
bulletRouting, NT and RIP (Windows 2000 magazine sept 1999)
bulletEase networking by using dynamic routing with RIP (TechRepublic)
bullet What's new in Routing and Remote access ? (Windows 2000 mag jun 2001)
bulletUnattended RRAS installations part 1 (Windows 2000 magazine)
bulletUnattended RRAS installations part 2 (Windows 2000 magazine)
bulletWin2K's premier IP multicast functionality (Windows 2000 magazine nov 2000)
bulletSteelhead's OSPF routing (Windows 2000 magazine august 1997)
bulletUsing OSPF routing for multiplatform networks (TechRepublic)
bullet The W2K routing table (BrainBuzz)
bullet Master the steps that ip routing uses to move data (TechRepublic)
bullet W2K demand-dial routing Pt. 1 (BrainBuzz)
bullet W2K demand-dial routing Pt. 2 (BrainBuzz)
bulletIP multicast and your network (Windows 2000 magazine april 1999)
bulletIP multicast resources (Windows 2000 magazine april 1999)

Last update : 5 December 2001