problem with IPv6 gif tunnel activation in rc.conf (latest current)

From: Matt (matt_at_xtaz.co.uk)
Date: 08/10/03

  • Next message: Hajimu UMEMOTO: "Re: problem with IPv6 gif tunnel activation in rc.conf (latest current)"
    Date: Sun, 10 Aug 2003 17:41:40 +0100
    To: current@freebsd.org
    
    

    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<POINTOPOINT,RUNNING,MULTICAST> 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<UP,POINTOPOINT,RUNNING,MULTICAST> 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.
    _______________________________________________
    freebsd-current@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-current
    To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
    

  • Next message: Hajimu UMEMOTO: "Re: problem with IPv6 gif tunnel activation in rc.conf (latest current)"

    Relevant Pages

    • FreeS/WAN - Routing all traffic (0.0.0.0) through a client tunnel
      ... the client to forward ALL traffic through the tunnel? ... I have experience with this type of configuration using a Nortel ... but have never tried it with freeswan. ... anything that comes in through the tunnel is dumped out ...
      (comp.os.linux.security)
    • Re: Cannot add subnets to Cisco ASA VPN tunnel
      ... I have a working VPN configured on my ASA 5510. ... But I cannot tunnel another subnet through this ... Here is the part of my ASA configuration where i define the VPN ... access-list VPN_access extended permit ip 10.2.5.0 255.255.255.0 ...
      (comp.dcom.sys.cisco)
    • IPSec IKE Phase II Malfunction
      ... I think I may have found a bug in the ISA 2004 site to site IPSec ... configuration interface. ... If you build an IPSec tunnel, ...
      (microsoft.public.isa.vpn)
    • Re: (OT?) Nylon Proxy Server Help
      ... > is pretty thin and I am having problems configuration nylon to run as I ... the tunnel part is down to your SSH configuration. ...
      (comp.unix.bsd.freebsd.misc)