From owner-freebsd-isp Tue Jan 7 21:24:46 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id VAA13431 for isp-outgoing; Tue, 7 Jan 1997 21:24:46 -0800 (PST) Received: from gamespot.com (ns1.gamespot.com [206.169.18.2]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id VAA13426 for ; Tue, 7 Jan 1997 21:24:43 -0800 (PST) Received: from tech-a.gamespot.com (tech-a.gamespot.com [206.169.18.66]) by gamespot.com (8.7.5/8.7.3) with SMTP id FAA13424 for ; Wed, 8 Jan 1997 05:24:38 GMT Message-Id: <199701080524.FAA13424@gamespot.com> Comments: Authenticated sender is From: "Ian Kallen" To: freebsd-isp@freebsd.org Date: Tue, 7 Jan 1997 21:26:35 +0000 Subject: was IP forwarding broken in 2.1.5? Reply-to: ian@gamespot.com Priority: normal X-mailer: Pegasus Mail for Windows (v2.23) Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I've two freeBSD boxes I want to have provide routing between two LANs. Each has a working ethernet interface and we're using ppp with ijppp and tun0. OK. Machine A (and its ethernet peers) can ping machine B's "modem" interface and B's ethernet card i.e. machine B is forwarding packets as we desire between the two devices. However, pings to machine A (and from B and its ethernet peers) only get as far as A's modem -- nor are Machine A's ethernet peers reachable from the machine B network. Machine A is 2.1.5 off the CD. (not providing ip forwarding) Machine B is 2.1.6.1 from freebsd.org as of three weeks ago or so. (forwarding fine) is this a known bug we'll get past by upgrading?? -- Ian Kallen ian@gamespot.com Director of Technology & Web Administration http://www.gamespot.com