ml@gandalf.UUCP (Marcus Leech) (07/29/89)
We're having a problem with TCP/IP under CTIX6.1. Here's our configuration:
Machine B <---SLIP----> Machine A
| | |
| | |
[ETHERNET] [ETHERNET][ETHERNET]
Both machines run ROUTED. The two ends of the SLIP link have addresses
134.22.128.1 and 134.22.128.3. The ETHERNET interfaces on Machine A
have addresses of 134.22.80.9 and 134.22.32.6. Machine B's ETHERNET
interface has an address of 134.22.48.1. All the ETHERNET interfaces
run with a netmasks of 255.255.240.0 (yielding 16 possible subnets).
The SLIP links have netmasks of 255.255.0.0. Both systems add routes
statically at system boot time, so that hosts on any of the ethernets
can see each other. This all works swimmingly well for the first
hour or so after Machine A gets booted. After about an hour of
operation, the SLIP link seems to die. Neither Machine B, nor Machine A
can see any packets, nor even any packet-errors. Rebooting machine A
clears things up--it is never necessary to reboot machine B. I
thought of hardware, so I switched SLIP ports (to a different controller)
and the same thing happens. The routing information seems to still be
valid, because when machine A pings machine B, the Opkt count on the
SLIP interface goes up by an appropriate number. I'm kinda stumped.
Anybody got any brilliant ideas?
-Marcus Leech
Gandalf Data Ltd
--
"If at first you dont succeed, STOP!" PaperMail: 130 Colonnade Rd, Nepean,ON
Marcus Leech E-mail: ml@gandalf.UUCP
Gandalf Data Ltd PacketRadio: VE3MDL@VE3JF
"The opinions expressed herein are solely my own" So there