From owner-freebsd-bugs Sun Apr 9 3:40: 7 2000 Delivered-To: freebsd-bugs@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 7B33237B596 for ; Sun, 9 Apr 2000 03:40:03 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id DAA36951; Sun, 9 Apr 2000 03:40:03 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Date: Sun, 9 Apr 2000 03:40:03 -0700 (PDT) Message-Id: <200004091040.DAA36951@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Brian Somers Subject: Re: kern/17873: Can not routing IPV6 packet with tun-device Reply-To: Brian Somers Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR kern/17873; it has been noted by GNATS. From: Brian Somers To: greg@greg.rim.or.jp Cc: freebsd-gnats-submit@FreeBSD.ORG, brian@hak.lan.Awfulhak.org Subject: Re: kern/17873: Can not routing IPV6 packet with tun-device Date: Sun, 09 Apr 2000 11:30:38 +0100 > > >Number: 17873 > >Category: kern > >Synopsis: Can not routing IPV6 packet with tun-device [.....] > This is a diffs for net/if_tun.c This breaks the if_tun module. If the module is built with INET6 defined, it'll fail to load on a non-INET6 kernel. If it's not, it can't call in6_ifattach. if_tun.c is already broken by calling if_attach() here. We need to abstract the interface creation in a way similar to the way data's dispatched via sys/net/intrq.c. Maybe there should be a all_ifattach() that's unconditionally built into the kernel and does something like #ifdef INET if_attach(ifp); #endif #ifdef INET6 in6_ifattach(ifp, IN6_IFT_P2P, 0, 0); #endif and so on ? There'd need to be a more generic way of telling it to use IN6_IFT_P2P, and I'm not sure why the if_type = IFT_RS232 bit is necessary.... -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message