STREIF@uwec.bitnet (05/22/91)
Hi, I need to build a TCP/IP link between one building on our campus and another building which has it's own ethernet and a link to the outside world via a Cisco router. Unfortunately, I don't have the budget to buy a commercial solution; so I'm hoping to use PCROUTE version 2.2 to provide the necessary connection. My layout would (ideally) look something like the following: 137.28.84.x through 137.28.3.x 137.28.87.x (no machines present) mask = 255.255.252.0 mask = 255.255.255.224 /--------------------/ /--------------------------/ Thin A | | Thick B | | +-----------+ | | | | | | | +--+ PCRoute |--+ | 137.28.84.1 | 1 | 137.28.3.2 | +-----------+ | | +-------+ +-----------+ | | | 137.28.2.1 137.28.2.3 | | | | GW +--+ +--+ PCRoute |--+ | Cisco | | | | 2 | 137.28.3.1 +-------+ | | +-----------+ | Thick C | /------------------------------/ 137.28.x.x mask = 255.255.0.0 We are using a class B number (137.28) but we are subneting it so that the first 22 bits are the network part. The first router will have the address 137.28.84.1 on network A and 137.28.3.2 on network B. The second router will have the address 137.28.3.1 on network B and 137.28.2.3 on network C. Network A is thin ethernet (uses the BNC connector) and networks B and C are thick ethernet. There is a gateway on network C (it's a Cisco router) that should be the default for any address not in 137.28.x.x. The reason for two PCRoute boxes is that network B is _very_ close to the maximum length for a thick ethernet. There is _no_ Unix host available to provide syslog services. My problem (obviously) is that I'm having troubles configuring the beast. My best results (so far) have involved turning on proxy ARP, but the Cisco box then has a fit (I get ICMP redirects on local hosts and it sends IP packets from remote host to both the IP and ethernet address of a machine on network A -- which the routers ignore :-(). I'd appreciate any ideas... Thanks, Vince Streif streif@uwec.edu Systems Programmer Univ of Wisc - Eau Claire