Routers

• I want to connect branch office printers and terminals to the head office system. How can Perle help?
  One of the best ways to connect your serial equipment in the branch office to the head office systems is using a LinkStream2000. The 2 sites can be linked using an LinkStream2000/833IS-833AS combination (or router) to giving TCP/IP and IPX access from one network to the other. Terminals and printers can then be connected using Telnet, Rlogin & LPD.
• When I enabled IP Routing, I receive an error message stating, "IP network or sub-net addresses not unique", what is wrong?
  This is saying that you have configured the IP Addresses of the individual routers connected via the WAN incorrectly. Verify that the IP Addresses and sub-net masking results in unique sub-nets of the same network space, or that you have not selected IP Addresses on the same IP network/sub-net as another Perle Router.
• When the link connects to a remote Perle Router, I receive an error message stating, "Mixture of IP network and sub-net addresses on WAN." Why?
  You are unable to mix IP network addresses and sub-net networks on Perle Routers which are connected via the WAN. Make sure that all Perle Router's connected via the WAN are on different sub-nets of the same network, or that they have distinctly different network addresses.
• When should I route, when should I bridge?
  Generally, you should bridge IP when you are connecting existing LAN segments or are partitioning an existing LAN in half and where you do not want to modify IP configurations of the stations on the LAN.
  You will need to route if you are trying to connect two or more LANs that exist in different IP address spaces. Routers are required to connect two IP networks together.
  If you are adding another segment to an already sub-netted network, it may be more efficient to route.
  Rule of thumb: The same IP network, bridge; Different IP networks; route.
• I am connecting a single remote site to my central LAN. We've standardise on OSPF, so how can I make the Perle Router work?
  In order to accomplish this, you will have to use Static Routes and disable RIP as the routing protocol. This is simple to accomplish.
  In the remote location Perle Router, all you will need to do is configure the Default Gateway of that Router to point to the central site Perle Router. This is all that is required to support a route back to the central site.
  On the central site router, explicit static routes will have to be added for all other routers located on the central site LAN, identifying which networks they service. You may also simplify this by defining a Default Gateway in the central site Router and point it at another router on the central site LAN.
  The last step is to define the existence of the remote LAN on all routers in the central LAN. This will require placing a static route in the other routers so they know that the Perle Router on the central LAN supports the route to the remote LAN.
• How can I support Variable Length Sub-net Masks (VLSM)?
  To support VLSM on the Perle Router, you must change the IP Routing Protocol from RIP to NONE, and define explicit static routes for each remote network. This is because RIP does not support VLSM, since it does not propagate the MASK with each route, which is fundamental to VLSM. You will be allowed to configure network address/mask combinations in the routing table to support all manner of network configurations.
• I have configured two Perle Router's to route but none of my remote clients can communicate with my central host. Why?
  There is a good chance that you have not configured your clients and hosts to use the newly installed router. You must configure the clients and the hosts to use the router to transfer any off network traffic. Usually this is a simple as configuring the Default Gateway of the clients and hosts and pointing them to the router located on their LAN.
• Default gateway - What should this be configured to?
  A Default Gateway is the router which handles all traffic for which there is no predefined route. It is the "catch-all" router.
  If there are only two networks being connected via the Perle Router's, you need not configure this parameter.
  If the Router is at the tail-end (or stub) of a network, you need not configure this parameter.
  If the Perle Router is on a LAN where there may be other routers, you may want to configure this parameter to point to one of the routers, if, and only if, other non-advertised routes are available through this router.routes are available through this router.