From owner-freebsd-net Thu May 31 0:54:22 2001 Delivered-To: freebsd-net@freebsd.org Received: from shadow.otel.net (JuDiCaToR.OTEL.net [212.36.9.113]) by hub.freebsd.org (Postfix) with ESMTP id DB6E437B424 for ; Thu, 31 May 2001 00:54:17 -0700 (PDT) (envelope-from tbyte@tbyte.org) Received: from localhost (localhost [127.0.0.1]) by shadow.otel.net (8.11.3/8.11.1) with ESMTP id f4V7sF036877; Thu, 31 May 2001 10:54:15 +0300 (EEST) (envelope-from tbyte@tbyte.org) Date: Thu, 31 May 2001 10:54:15 +0300 (EEST) From: Iasen Kostoff X-Sender: tbyte@shadow.otel.net To: Hroi Sigurdsson Cc: freebsd-net@FreeBSD.ORG Subject: Re: routing socket and routes assignment In-Reply-To: <3B157021.8DF52B75@asdf.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Thu, 31 May 2001, Hroi Sigurdsson wrote: > Iasen Kostoff wrote: > > > The gateway is directly connected and I think this is obvious and should > > not even be discused. The IP address of the gateway is not from > > network that the computer is. But there is a route throu interface to it > > and the kernel still refuses to use that gateway with error ENETUNREACH. > > And I wrote a patch which allows kernel to set that route. It's kinda > > unfinished still but it works. Even now (without the patch) you can set > > this route but it's not straight forward and I don't think that's the > > right way to be done. > > That is just broken IMHO. You will also need to disable any > e/ingress-filtering that may be on the gateway. > The right thing to do would be to assign an address on that net to your > interface which will allow you to point your default gateway at an > address on that net. > > -- > Hroi Sigurdsson > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-net" in the body of the message > I don't think that assigning an address from net of the gateway is the right way and none of the cisco's routers need that, why should FreeBSD need it ? And no there is not any e/ingress-filtering for the FreeBSD computer. Regards. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message