#Cox 255 255 255 40 default gateway how to#

The principle is the same as with the servers: you basically tell the machine to send al packets with destination net A to this interface, all packets with destination B to that interface and usually add a 'default' route as a last resort - it means 'if there's no explicit rule where to send the packet then send it there and hope for the best'.

#Cox 255 255 255 40 default gateway how to#

Consult your routers manual on how to do this. The routing between the networks should be handled by the router (after all, that's his genuine job). This procedure will be the same for any machine on your network, regardless of being server or client, Windoze or *NIX machine. In the upcoming screen there will be the option 'default route'. Use SMIT to add the default route by issuing 'smitty tcpip' at the commandline, then select 'minimum configuration' and your interface, presumably 'en0'. This would be 128.2.1.2 for all machines in your location and 128.2.2.2 for all machines in the remote location. a default route, pointing to their nearest router. A user cannot reach the corporate server form their remote office. Transmission to this address is limited by definition, in that it is never forwarded by the routers connecting the local network to. It is the broadcast address of the zero network or 0.0.0.0, which in Internet Protocol standards stands for this network, i.e. You can find the panel by typing 'smitty tcpip' on the commandline, then select further 'configuration/static routes'.ДЈ. A special definition exists for the IP address 255.255.255.255. As this route would be lost upon reboot use SMIT to insert it in a lasting way.

a net route for their own net pointing to their own interface.

Usually it is the job of the routers (not the servers) to know how to relay packets from one network to another, therefore the machines (regardless of being servers or clients) should have only three entries in their routing table:Дў.