[SOLVED] DHCP6 radvd error



  • Latest snap (pfSense-Full-Update-2.1-DEVELOPMENT-i386-20120606-0914) broke ipv6 gateway & radvd on upgrade from [4/12 image].

    uname -a
    FreeBSD [hostname.domain] 8.3-RELEASE-p2 FreeBSD 8.3-RELEASE-p2 #1: Wed Jun  6 10:30:38 EDT 2012     root@FreeBSD_8.3_pfSense_2.1.snaps.pfsense.org:/usr/obj./usr/pfSensesrc/src/sys/pfSense_SMP.8  i386
    
    Jun 6 16:09:35	php: : Could not find IPv6 gateway for interface(wan).
    Jun 6 16:09:35	php: : Could not find IPv6 gateway for interface(wan).
    Jun 6 16:09:35	php: : Could not find IPv6 gateway for interface(wan). 
    

    [v6 is (was) through HE tunnel on gif interface]

    Jun 6 16:05:55 	radvd[47645]: Exiting, failed to read config file.
    Jun 6 16:05:55 	radvd[47645]: error parsing or activating the config file: /var/etc/radvd.conf
    Jun 6 16:05:55 	radvd[47645]: syntax error in /var/etc/radvd.conf, line 3: {
    
    
    # Automatically Generated, do not edit
    # Generated for DHCPv6 Server lan
    interface  {
    	AdvSendAdvert on;
    	MinRtrAdvInterval 3;
    	MaxRtrAdvInterval 10;
    	AdvLinkMTU 1280;
    	prefix xx:xx:xx:0:0:0:0/64 {
    	};
    	RDNSS 2001:470:20::2 2620:0:ccc::2 { };
    	DNSSL xxxxx { };
    };
    
    

    I'm not familiar with radvd.conf, but the examples I've seen today usually show an interface on Line3 before the "{". Shouldn't line 3 show my LAN interface [lagg0]?

    Had dual stack with Assisted DHCPv6 before the upgrade from web configurator. Manual backup before. Applied gitsync then manual backup after v6 was not functional post upgrade. No dice.
    Repeated the upgrade from console/URL via ssh. PfSense can resolve and ping ipv6 hosts on WAN, but DHCPv6 on LAN only hands out link local & nonrouted [nonworking] static addresses.

    Any help or suggestions to get v6 back?  Thanks.



  • adding my interface to the conf fixed it for now… but a reboot will wipe it out...

    example:

    
    # Automatically Generated, do not edit
    # Generated for DHCPv6 Server lan
    interface em2 {
    	AdvSendAdvert on;
    	MinRtrAdvInterval 3;
    	MaxRtrAdvInterval 10;
    	AdvLinkMTU 1280;
    	prefix 2001:470:1d:6aa:0:0:0:0/64 {
    	};
    	RDNSS 2001:470:20::2 2620:0:ccc::2 { };
    	DNSSL realm { };
    };
    
    


  • @Cino:

    adding my interface to the conf fixed it for now… but a reboot will wipe it out...

    example:

    
    # Automatically Generated, do not edit
    # Generated for DHCPv6 Server lan
    interface em2 {
    	AdvSendAdvert on;
    	MinRtrAdvInterval 3;
    	MaxRtrAdvInterval 10;
    	AdvLinkMTU 1280;
    	prefix 2001:470:1d:6aa:0:0:0:0/64 {
    	};
    	RDNSS 2001:470:20::2 2620:0:ccc::2 { };
    	DNSSL realm { };
    };
    
    

    Doesn't last or do anything for me…

    Tried changing dc0 to lagg0 in rtdvd.conf as well. No joy.

    #
    # common definitions.
    #
    default:\
            :raflags#0:rltime#3600:\
            :vltime#360000:pltime#360000:mtu#1500:
    ether:\
            :mtu#1280:tc=default:
    # Generated for DHCPv6 Server lan
    lagg0:\
    	:addr="2001:470:1d:6aa:0:0:0:0":\
    	:prefixlen#64:\
    	:raflags="mo":\
    	:tc=ether:\
    	:rdnss="2001:470:1d:6aa::1":\
    	:dnssl="realm":
    
    

    on edit: reinstalled pfSense 2.1 from latest .iso, restored, gitsynced. No change (still no ipv6 gateway or radvd, adding LAN interface to radvd.conf does not help)…except now Unbound will not start.

    php: : The command '/usr/local/sbin/unbound-control start' returned exit code '1', the output was ''
    


  • I can confirm the same problem here. Fixing the configuration file and manually starting radvd (the command will be listed in system.log with the failure message) gets it up, until reboot anyway.

    I also notice that in 'unmanaged' mode, a valid rtadvd configuration is generated, but the daemon doesn't start. It seems to want to load the /etc/rtadvd.conf file rather than the generated one (/cf/conf/rtadvd.conf IIRC). Didn't look into that too far as I need DHCP myself.



  • same issue here



  • same here



  • 6/07 2.1 32bit Full snapshot (bare metal) is also badly broken. Update tarball and full.iso.

    Gateways down
    DHCP Server (v4 & v6) = non functional
    Unbound = Can not start

    The above with either previous working config backup applied, or fresh install.



  • Saw the bug HERE

    Updated to http://snapshots.pfsense.org/FreeBSD_RELENG_8_3/i386/pfSense_HEAD/updates/pfSense-Full-Update-2.1-DEVELOPMENT-i386-20120608-0546.tgz

    radvd fails with same errors
    Unbound DNS will not start and I can't reinstall as package is no longer available in GUI Packages or at
    http://files.pfsense.com/packages/8/All/

    Devs: Thanks for putting this on your radar screen, as currently pfSense can't do IPv6 at all.
    Let me know if I can provide any info that may be of help.



  • please try again



  • @databeestje:

    please try again

    Success! Naow haz DHCPv6!
    LAN hosts can ping ipv6.google.com, and I noticed the new GUI page for DHCPv6 RA.

    Thank you! (I thought I may have "jumped the gun" with the 05:55 AM build.  ::) )

    I lost Unbound somewhere along the way though, and can't get it back as Unbound is not listed in Installed or Available packages in GUI, and a manual install from pfsense repo shows a dependency as too recent.

    ^^Personal Problem - Related to a previous CLI install/uninstall that wiped Unbound's /pkg/ .xmls

    Again, thanks!

    TL;DR: Snap issue solved by newer snap.  ;)



  • @databeestje:

    please try again

    thanks man! its working again



  • thanks, all seems ok


Locked