Ens - Routing tab (overview)
Posted by Adrien de Croy (Import) on 30 January 2004 04:59 PM
The purpose of this tab is to show all of the routes currently listed in the routing table that WinGate uses. This tab will only appear if Support for multiple Subnet works
has been enabled on the General
tab of ENS, as WinGate's routing table will be able to determine where traffic from one subnet is to be sent in order to reach the other subnet. There are several options that can be configured to allow WinGate to handle this routing.
- Relay UDP broadcast packets
Most Windows based network PC’s use Netbios broadcast to advertise themselves and discover machine identities on the LAN. Usually they will send UDP packets on ports 137,138, to discover this information. This option allows these Netbios broadcasts to travel across the dissimilar subnets that are being bridged by WinGate and inturn allow the sharing of Network information shared resources, machine identities etc.
In the advanced section (accessed by clicking the Advanced button on the Routing tab) you can set specific ports which UDP broadcasts are allowed to be sent on if required. Obviously Ports 137 and 138 are listed by default, but this is useful for other LAN applications that require the use of UDP broadcast packets such as DHCP and certain LAN games.
- Indicate UDP broadcasts (Ports < 1024)
Excessive UDP broadcasts on ports under 1024 can lead higher then normal memory consumption. By enabling this option (ticked by default) ONLY excessive UDP broadcasts (lasting longer then 20 seconds and at least 10 seconds since the last activity) will be displayed in the Activity screen in GateKeeper. (This is switched on by default).
- Enable Support for Multiple Default routes
One of the problems that arises in routing is where more then one default route is given. For example: A default gateway is listed for the internal network interface on a machine, but whenever the machines Dialup connection connects to it's ISP, it is given another default gateway. This new gateway is sometimes given a higher priority for traffic then the internal interface's existing gateway, which will break the internal routing of traffic between differing subnets. Enabling this option will rectify this by allowing all privately addressed packets to use the proper internal gateway.