From owner-freebsd-isp Fri Jul 10 14:59:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA25074 for freebsd-isp-outgoing; Fri, 10 Jul 1998 14:59:43 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from bastuba.partitur.se (bastuba.partitur.se [193.219.246.194]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA24969 for ; Fri, 10 Jul 1998 14:59:06 -0700 (PDT) (envelope-from girgen@partitur.se) Received: from solist. (solist.partitur.se [193.219.246.204]) by bastuba.partitur.se (8.8.8/8.8.8) with SMTP id XAA10909; Fri, 10 Jul 1998 23:59:01 +0200 (CEST) (envelope-from girgen@partitur.se) Received: from partitur.se by solist. (SMI-8.6/SMI-SVR4) id XAA04667; Fri, 10 Jul 1998 23:57:28 +0200 Message-ID: <35A68E48.BD4B924A@partitur.se> Date: Fri, 10 Jul 1998 23:57:28 +0200 From: Palle Girgensohn Organization: Partitur X-Mailer: Mozilla 4.05 [en] (X11; I; SunOS 5.6 sun4u) MIME-Version: 1.0 To: Glen Foster CC: freebsd-isp@FreeBSD.ORG Subject: Re: Help: bridge router trouble References: <199807102131.RAA11918@gfoster.intr.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Glen, Thanks for your reply. I'll get back to my ISP on monday. BTW, did I mentione that my ISP could ping me if I set up a client machine (a mac, in fact) directly on the cisco with IP x.y.q.46. But he couldn't ping me when the freebsd machine was there instead, even if I shut off ip forwarding in the kernel (w/ sysctl) and shut off the internal interface (sort of simulating a client)? Odd... I'm _not_ using a private address space, btw. (I have set up the machine to route a private net with natd now, just to test that it works. seems to be just fine; it routes my 192.168.0.2 powerbook and an old fbsd workstation out to the internet and back, which also leads me to believe that my isp made a mistake... a static route seems like the way to go). Thanks! /Palle Glen Foster wrote: > > It sounds like A is missing a route to C (through B). Either have > your ISP configure a static route on A or run a routing protocol > between A & B (RIP/routed is fine). Just running routed on B isn't > enough unless A knows to listen to it. > > If A is a Cisco > > Cisco> show ip route x.y.z.193 > > should return > > x.y.q.46 > > If you cannot get your ISP to configure a static route on the Cisco > (e.g. if you are using private address space for C), you will have to > do NAT to make your C addresses appear to be x.y.q.46 to the outside > world. > > Good luck, > Glen Foster > > >Date: Fri, 10 Jul 1998 20:07:55 +0200 > >From: Palle Girgensohn > >Organization: Partitur > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message