From owner-freebsd-net Fri Mar 14 6:51:53 2003 Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3068337B401 for ; Fri, 14 Mar 2003 06:51:51 -0800 (PST) Received: from almso2.proxy.att.com (almso2.att.com [192.128.166.71]) by mx1.FreeBSD.org (Postfix) with ESMTP id C688D43FAF for ; Fri, 14 Mar 2003 06:51:49 -0800 (PST) (envelope-from jwb@homer.att.com) Received: from ulysses.homer.att.com ([135.205.193.8]) by almso2.proxy.att.com (AT&T IPNS/MSO-4.0) with ESMTP id h2EEpmWx001921; Fri, 14 Mar 2003 09:51:48 -0500 (EST) Received: from akiva.homer.att.com (akiva.homer.att.com [135.205.212.39]) by ulysses.homer.att.com (8.9.3/8.9.3) with ESMTP id JAA21284; Fri, 14 Mar 2003 09:51:47 -0500 (EST) Received: from akiva.homer.att.com (localhost [127.0.0.1]) by akiva.homer.att.com (8.11.6+Sun/8.9.3) with ESMTP id h2EEpkQ19585; Fri, 14 Mar 2003 09:51:46 -0500 (EST) Message-Id: <200303141451.h2EEpkQ19585@akiva.homer.att.com> To: Guido van Rooij Cc: freebsd-net@FreeBSD.ORG Subject: Re: route pointing to a gateway that's not on net In-reply-to: Your message of "Fri, 14 Mar 2003 11:24:31 +0100." <20030314102431.GA97899@gvr.gvr.org> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <19582.1047653505.1@akiva.homer.att.com> Date: Fri, 14 Mar 2003 09:51:46 -0500 From: "J. W. Ballantine" 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 So what you are saying is that with the: route add -net default -iface -interface xl0 command the system thinks there is a direct connect. Doesn't this then send all packets out, since there is no address supplied with the route command, or is this a function the the 10.*.*.* addresses are private network addresses. If it sends all packets out, I would expect the 10.17.47.37 to receive it and forward it, since it is the gateway/modem. Having taken a quick look at the arp man page, it seems that one needs to arp each address/host rather than globally. Again, what I'm trying to do is get the system to pass all packets to the gateway/modem for forwarding over the net. Thanks Jim ---------- In Response to your message ------------- > Date: Fri, 14 Mar 2003 11:24:31 +0100 > To: "J. W. Ballantine" > From: Guido van Rooij > Subject: Re: route pointing to a gateway that's not on net > Sender: owner-freebsd-net@FreeBSD.ORG > > On Thu, Mar 13, 2003 at 03:34:18PM -0500, J. W. Ballantine wrote: > > round-trip min/avg/max/stddev = 3.022/3.428/5.029/0.801 ms > > # ping 207.172.3.8 <<< one of isp's name ser ver > > PING 207.172.3.8 (207.172.3.8): 56 data bytes > > ping: sendto: Host is down > > ping: sendto: Host is down > > ping: sendto: Host is down > > ping: sendto: Host is down > > > > So this method allows my system to get to the > > modem/dhcp server/gateway, but no further. (when I ping > > from windows I get a response, so the system isn't down.) > > That is because 207.172.3.8 is not directly connected. By speficying a > route entry with -iface you specify it is directly connected. That > is the reason you can now reach the 10.*hosts. > > The problem with the 207.172.3.* hosts exists because your routing > table expects the 207.172.3.* range to be directly connected. > > So either you have to make them apear directly connected, or you must say th at > they are not directly connected. The first can be doe by having your gateway > do proxy arp, or by manually setting arp entries on your host > (for all 207.172.3.* hosts, do arp -s host MAC, where MAC is the mac address > of your gateway). > I don't know how to do the second one, except for adding single host routes > for each host, i.e.: route add host-ip-address gateway-ip-address. > > -Guido > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-net" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message