From owner-freebsd-isp Mon Aug 3 12:35:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA23943 for freebsd-isp-outgoing; Mon, 3 Aug 1998 12:35:25 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from darla.swimsuit.internet.dk (mail.swimsuit.internet.dk [194.255.12.232]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA23924 for ; Mon, 3 Aug 1998 12:35:16 -0700 (PDT) (envelope-from leifn@internet.dk) Received: from darla.swimsuit.internet.dk (darla.swimsuit.internet.dk [192.168.0.10]) by darla.swimsuit.internet.dk (8.9.1/8.9.1) with SMTP id VAA03346 for ; Mon, 3 Aug 1998 21:34:59 +0200 (CEST) Date: Mon, 3 Aug 1998 21:34:52 +0200 (CEST) From: Leif Neland Reply-To: leifn@internet.dk To: freebsd-isp@FreeBSD.ORG Subject: route problems Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org We have two livingston's which gives the dialins ip's in one net (194.255.12.x) while the rest of the net and servers are in another net (194.19.140.x). The we have a cisco for our uplink, which we can't control. How can the cisco know which livingston to route to to get to a dialin? What if we get more livingston's, and somebody with a fixed ip could get either one or the other livingston? Also, perhaps related, sometimes when I dial in, I can ping our servers, but a traceroute stops at the cisco to the uplink. But if I log in to a server, I can reach the rest of the world. Is it because the cisco sometimes doesn't know the route to the dialin? Leif Neland leifn@internet.dk To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message