readme.gateway

无线网络路有协议aodv的 linux的实现

Kernel AODV Gatewaying
Luke Klein-Berndt
National Institute of Standards and Technology
http://w3.antd.nist.gov/wctg/aodv_kernel/
----------------------------------------------------

Managed Internet Gatewaying:
In this mode there are two different types of nodes, Gateway Nodes and Client
Nodes. A Gateway node requires two interfaces, one which hooked up to the normal
network and another which will connect to the AODV network. The Client is
simply a regular AODV node which has been configured with the correct setting to
communicate on the network which the Gateway node is attached to. This means
that a client node should have the same DNS settings as a Gateway node. These
setting can usaully be accessed through the netconf program.

A Gateway node should be configured should that it can communication with the
external network. This means it non-AODV interface should have a correctly
configured IP address. The correctly route towards the subnet gateway of the
external network should also be configured. It is also important to make sure
that the subnets of the two interfaces do not overlap.

The Gateway node will generate a Route Reply to all Route Request which are not
in the AODV subnet. The Gateway node considers the AODV subnet to be equivlant
to the subnet settings for the interface being used by AODV. So if the interface
is configured for 192.168.1.34/255.255.255.0, AODV would consider everything
from 192.168.1.0 - 192.168.1.255 to be part of the AODV subnet. Of course all
of the Client nodes have to be configured so that their IP address is
in this subet. The Gateway node assumes every address in the AODV subnet can be
routed by AODV and all other addresses can be routed locally through the routing
table.

IPTABLES is used to do NAT, allowing AODV nodes to access the external
network, even if their IP address is not externally routable. IPTABLES should
be installed on the Gateway node.

After a Client node's network settings have been correctly configured it is
started using './start.sh'. Before a Gateway node can be started, its startup
script must first be edited. Edit start_gateway.sh to reflect your current
network configuration. Once that is done you should be ready to go!

For example:
   Node A - the gatewaying nodes
            eth0- connected to internet
	          IP= 129.6.53.50
	    eth1- WLAN connected to other AODV nodes
		  IP= 129.6.230.5


   Node B - AODV node
	  eth0- connected to other AODV nodes
		IP=129.6.230.4

   The AODV subnet in this example would be 129.6.230

	Also make sure /proc/sys/net/route/min_delay is set to zero. This is the time
that changes to the routing table are cached before being written. If it is not
zero, crazy things happen... crazy things...

Created: 11/05/01 Updated: 03/01/04
NIST is an agency of the U.S. Commerce Department's Technology Administration