From owner-freebsd-hackers Wed Apr 17 16:28:15 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id QAA24026 for hackers-outgoing; Wed, 17 Apr 1996 16:28:15 -0700 (PDT) Received: from cs.pdx.edu (root@cs.pdx.edu [204.203.64.22]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id QAA24020 Wed, 17 Apr 1996 16:28:13 -0700 (PDT) Received: from sirius.cs.pdx.edu (root@sirius.cs.pdx.edu [204.203.64.13]) by cs.pdx.edu (8.7.3/CATastrophe-2/10/96-P) with ESMTP id QAA22173; Wed, 17 Apr 1996 16:27:49 -0700 (PDT) for Received: from localhost (jrb@localhost [127.0.0.1]) by sirius.cs.pdx.edu (8.7.3/CATastrophe-9/18/94-C) with ESMTP id QAA03920; Wed, 17 Apr 1996 16:27:43 -0700 (PDT) Message-Id: <199604172327.QAA03920@sirius.cs.pdx.edu> To: "Gary Palmer" cc: dirk@methan.chemie.fu-berlin.de (Dirk Froemberg), hackers@FreeBSD.org, xadmin@methan.chemie.fu-berlin.de, alf@bolzen.in-berlin.de Subject: Re: ip-in-ip tunnel In-reply-to: Your message of "Wed, 17 Apr 1996 20:03:49 BST." <2478.829767829@palmer.demon.co.uk> Date: Wed, 17 Apr 1996 16:27:41 -0700 From: Jim Binkley Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk As another possibility, I can give you some experimental kernel code that basically is integrated with the multicast tunnel code in the kernel and gives you a device called "mvif0" that allows you to put a route between two boxes and route all packets to a destination X between a tunnel system Y. Logically: send all unicast packets to X via ip dst Y (ip dst in outer ipip protocol packet) This is for support of mobile ip, what at this point I can at least do by statically inserting routes in the kernel. I sent about 20000 packets through it yesterday so it isn't that bad, but it's still experimental. Depends on what you want to do. regards, Jim Binkley jrb@cs.pdx.edu