From owner-freebsd-hackers Wed Oct 25 7:54: 8 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from topperwein.dyndns.org (acs-24-154-28-99.zoominternet.net [24.154.28.99]) by hub.freebsd.org (Postfix) with ESMTP id 262A637B479; Wed, 25 Oct 2000 07:54:01 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by topperwein.dyndns.org (8.11.0/8.11.1) with ESMTP id e9PEsY420595; Wed, 25 Oct 2000 10:54:34 -0400 (EDT) (envelope-from behanna@zbzoom.net) Date: Wed, 25 Oct 2000 10:54:34 -0400 (EDT) From: Chris BeHanna Reply-To: behanna@zbzoom.net To: Marko Ruban Cc: freebsd-questions@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: gateway on different subnet In-Reply-To: <39F49ECC.AF8CDFD2@dppl.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 23 Oct 2000, Marko Ruban wrote: > Summary of the problem: > > Can't assign cable modem gateway (10.17.56.12) to interface > ed0 with assigned IP (208.59.162.242) - "network unreachable". > > I called RCN (my cable provider) and asked them to give me > a gateway on the same subnet; they said they "don't do that". man dhcp.conf(5). From what I saw there, "option routers" and "option routes" are what you need to stick into your dhclient.conf. Can you add routes by hand and make it work? If not, then even the above won't help you. > Part of solution: > > I set an alias for ed0 to 10.17.0.1 and it accepted the cable > modem gateway as is. BUT, the packets are sent out with source > address (10.17.0.1) responses to which, I suspect, gateway doesn't > know how to route. I would imagine you're right. > Question: how can I have an alias of 10.17.0.1 and send out all > packets with source address set to 208.59.162.242 (the IP > that is actually assigned to the interface - not alias). natd? > P.S. Alternately, how can I force the system to allow a gateway > that is on a different subnet (like windows allows that). Who > can I turn to for help ? I'm not a routing guru, but the guy in the next office is. I'll ask him. (tromp, tromp, tromp) The answer is this: run routed in verbose or debug mode, or listen with rip, or some other network sniffer (you could even ping the network and see who answers). You should have a local router within 30 seconds. Failing that, there have been a lot of other good suggestions, among which probably the best is to switch to DSL. :-/ -- Chris BeHanna Software Engineer (at yourfit.com) behanna@zbzoom.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message