Technical data

Configuring Routing
4.4 Configuring GATED
Or use the sysconfig utility to enable forwarding. First, define foreign
commands:
$ @SYS$MANAGER:TCPIP$DEFINE_COMMANDS.COM
Enter the following sysconfig command:
$ sysconfig -r inet ipforwarding=1 ipgateway=1
To make sure forwarding is enabled after restarting TCP/IP Services, add the
command to TCPIP$SYSTARTUP.COM.
To view the setting, use the following command:
$ sysconfig -q inet ipforwarding ipgateway
When multiple networks share the same physical media and the host has just
one interface, it is still possible to forward packets between these networks by
creating a network alias, as described in Section 2.3.3.
For example, consider a network in which two networks have network addresses
of 16.20.1/24 and 16.20.2/24, and the host address is 180. If the host has a single
ethernet interface, WE0, create the interface and pseudointerfaces as follows:
TCPIP> SET CONFIGURATION INTERFACE WE0 /HOST=16.20.1.180 -
_TCPIP> /NETWORK_MASK=255.255.255.0 /BROADCAST_MASK=16.20.1.255
TCPIP> SET CONFIGURATION INTERFACE WEA0 /HOST=16.20.2.180 -
_TCPIP> /NETWORK_MASK=255.255.255.0 /BROADCAST_MASK=16.20.2.255
TCPIP> SET CONFIGURATION PROTOCOL IP /FORWARD
When TCP/IP Services is restarted, the host will forward packets between these
networks.
Alternatively, you can add the following commands to TCPIP$SYSTARTUP.COM
and then restart TCP/IP Services:
$ ifconfig we0 aliaslist 16.20.1-2.180/24
$ sysconfig -r inet ipforwarding=1 ipgateway=1
4.4.3 Extending Routing
To use extended routing, define pseudointerfaces. A pseudointerface is a
data structure that extends routing. Like an interface, the name of an internet
pseudointerface is three alphabetic characters, followed by the pseudointerface
unit number in the range of 0 through 255.
The first two characters are the same as the two characters in the internet
interface name (interface type and interface class). See Section 2.3.1 for more
information about interface names.
The third character identifies the controller letter that corresponds to the
OpenVMS hardware controller.
For example, for an OpenVMS Alpha system with two Ethernet controllers, EZA0
and EZB0, you can define the following internet interfaces and pseudointerfaces:
• Internet interfaces:
ZE0
ZE1
4–8 Configuring Routing