From owner-freebsd-hackers Mon Apr 22 05:41:44 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id FAA02155 for hackers-outgoing; Mon, 22 Apr 1996 05:41:44 -0700 (PDT) Received: from gw.itfs.nsk.su (gw.itfs.nsk.su [193.124.36.33]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id FAA02144 for ; Mon, 22 Apr 1996 05:40:51 -0700 (PDT) Received: from itfs.UUCP (uucp@localhost) by gw.itfs.nsk.su (8.6.12/8.6.12) with UUCP id TAA03782 for hackers@freebsd.org; Mon, 22 Apr 1996 19:40:13 +0700 Received: by itfs.nsk.su; Mon, 22 Apr 96 19:29:45 +0700 (NST) Received: (from daemon@localhost) by news.itfs.nsk.su (8.6.12/8.6.12) id TAA27986; Mon, 22 Apr 1996 19:23:50 +0700 From: nnd@itfs.nsk.su (Nickolay N. Dudorov) To: hackers@freebsd.org Subject: Re: ip-in-ip tunnel Message-ID: References: Date: Mon, 22 Apr 1996 12:23:46 GMT Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Dirk Froemberg (dirk@methan.chemie.fu-berlin.de) wrote: > 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? > I've send 'a problem report' with send-pr with example of program which configure tunN device as a point-to-point interface between this host and target one. It uses ip-over-ip encapsulation (protocol 94) - the same which is used by CISCO-routers (among others, they named it NOS-encapsulation) and (may be) Linux. N. Dudorov