From owner-freebsd-current@FreeBSD.ORG Sun Aug 10 09:41:43 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 90E5137B401 for ; Sun, 10 Aug 2003 09:41:43 -0700 (PDT) Received: from tao.xtaz.co.uk (pc-62-30-69-139-az.blueyonder.co.uk [62.30.69.139]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4C15043F3F for ; Sun, 10 Aug 2003 09:41:42 -0700 (PDT) (envelope-from matt@xtaz.co.uk) Received: from webmail.xtaz.co.uk (localhost [127.0.0.1]) by tao.xtaz.co.uk (Postfix) with SMTP id 76A628FD68 for ; Sun, 10 Aug 2003 17:41:40 +0100 (BST) MIME-Version: 1.0 X-Mailer: V-webmail 1.5.0 ( http://www.v-webmail.co.uk/ ) Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-ID: Date: Sun, 10 Aug 2003 17:41:40 +0100 From: "Matt" To: current@freebsd.org Subject: problem with IPv6 gif tunnel activation in rc.conf (latest current) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Aug 2003 16:41:43 -0000 Hi, I may have done something really stupid here but if I have I can not see what it is. Basically I have some configuration in rc.conf to set up a gif tunnel for ipv6. I have used the same config I used to use on 5.0-RELEASE a few months ago but I removed that config when the tunnel broker I was using went out of business. I have been tracking -CURRENT since but only this morning decided to set up a new tunnel broker service. I placed the same config back in rc.conf to set this up, changed the relevant ip address's for the new broker and rebooted after my latest cvsup/buildworld. What happened was that the lan interface (xl1) got configured with link-local and site-local and rtadvd was started. This all worked perfectly. However the gif tunnel only managed to configure the inet4 tunnel part of the configuration and was missing the inet6. This caused further errors during boot as the default route was attempted to be set. The relevant parts of rc.conf look like this: ipv6_enable="YES" ipv6_network_interfaces="xl1 lo0" ipv6_ifconfig_xl1="fec0:0:0:1::1 prefixlen 64" gif_interfaces="gif0" gifconfig_gif0="62.30.69.139 64.71.128.82" ipv6_ifconfig_gif0="2001:470:1F00:FFFF::32F 2001:470:1F00:FFFF::32E prefixlen 128" ipv6_defaultrouter="2001:470:1F00:FFFF::32E" ipv6_ifconfig_xl1_alias0="2001:470:1F00:507::1 prefixlen 64" ipv6_gateway_enable="YES" rtadvd_enable="YES" rtadvd_interfaces="xl1" xl0 is my internet connection, xl1 is my lan connection, and gif0 is the tunnel. After booting the system ifconfig gif0 looks like this: gif0: flags=8050 mtu 1280 tunnel inet 62.30.69.139 --> 64.71.128.82 There is no inet6 part and the default route for inet6 has not been set. If I manually then add the configuration I specified in rc.conf it works fine: [root@tao root]# ifconfig gif0 inet6 2001:470:1F00:FFFF::32F 2001:470:1F00:FFFF::32E prefixlen 128 [root@tao root]# route add -inet6 default 2001:470:1F00:FFFF::32E add net default: gateway 2001:470:1F00:FFFF::32E [root@tao root]# ifconfig gif0 gif0: flags=8051 mtu 1280 tunnel inet 62.30.69.139 --> 64.71.128.82 inet6 2001:470:1f00:ffff::32f --> 2001:470:1f00:ffff::32e prefixlen 128 inet6 fe80::2a0:24ff:feac:e1b4%gif0 prefixlen 64 scopeid 0x4 So my question is have I done the rc.conf configuration incorrectly or is there something wrong with the rc scripts that start inet6? My uname -a is as follows: FreeBSD tao.xtaz.co.uk 5.1-CURRENT FreeBSD 5.1-CURRENT #0: Sun Aug 10 13:03:29 BST 2003 root@shakira.xtaz.co.uk:/usr/obj/usr/src/sys/TAO i386 Regards, Matt. -- email: matt@xtaz.co.uk - web: http://xtaz.co.uk/ Hardware, n.: The parts of a computer system that can be kicked.