From owner-freebsd-hackers Wed Apr 17 04:13:33 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id EAA02116 for hackers-outgoing; Wed, 17 Apr 1996 04:13:33 -0700 (PDT) Received: from methan.chemie.fu-berlin.de (methan.chemie.fu-berlin.de [130.133.2.81]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id EAA02110 for ; Wed, 17 Apr 1996 04:13:27 -0700 (PDT) Received: by methan.chemie.fu-berlin.de (Smail3.1.29.1) id ; Wed, 17 Apr 96 13:12 MET DST Message-Id: From: dirk@methan.chemie.fu-berlin.de (Dirk Froemberg) Subject: ip-in-ip tunnel To: hackers@freebsd.org Date: Wed, 17 Apr 1996 13:12:46 +0200 (MET DST) Cc: xadmin@methan.chemie.fu-berlin.de, alf@bolzen.in-berlin.de X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hello! We need to set up a ip-in-ip (protocol number 4) tunnel with FreeBSD (i. e. tunnel entry should be on a FreeBSD machine). Unfortunaly there seems to be no easy way of doing so. mrouting has the functionality of tunneling being limited on multicast addresses. Although this limitation may easily be removed there is no way of adding routes manually (e. g. route add). Another approach might be to create a interface doing the encapsulation. The implementation of the ip-in-ip-encapsulation itself is not very difficult. At the moment we are a stucked "a little bit" in the BSD-networking-code. Btw. Linux has such interface called "tunl". Is anyone working on this? Best regards Dirk -- Dirk Froemberg (Admin-Team Methan) e-mail: dirk@methan.chemie.fu-berlin.de