DHCPv6 leases not showing



  • I use a HE tunnel for IPv6 and have activated the DHCP V6 server/RA.  My DHCP V6 settings are enabled, with a start and end address and a router advertisement of assisted per the doc page on IPV6.  Yet I do not see any leased addresses.  My PC is not showing that it has received a valid IPV6 address from PF sense since it still only shows the windows default value. What am I missing?

    Thanks

    cjb



  • Do have Interfaces-LAN(Block bogon networks) UN-checked, cause else will block broadcast.
    Have you tried with RA-managed too ?



  • Yes both private and bogon on the HeIPV6 Lan interface do not have a check mark.  I also tried Managed as an option with the same result.  The DHCP V6 does not seem to be sending any IPV6 addresses to the PC's.

    Pfsense is on the latest version and PC's are Windows 10 and 8.1 with 2012R2 servers in a workgroup configuration.

    cjb



  • With Diagnostics-Packet Capture (evaluate wireshark) on that LAN, you can check if the Win-client sends a (dhcp6c)request (broadcast) to pfSense.



  • Post screenshots of your config…that'll help track down the issue.



  • My server:

    2.3-RELEASE (amd64)
    built on Mon Apr 11 18:10:34 CDT 2016
    FreeBSD 10.3-RELEASE

    here is what I see in the log

    Apr 21 16:59:24 radvd 70137 Exiting, failed to read config file.
    Apr 21 16:59:24 radvd 70137 error parsing or activating the config file: /var/etc/radvd.conf
    Apr 21 16:59:24 radvd 70137 syntax error in /var/etc/radvd.conf, line 11: /
    Apr 21 16:59:24 radvd 70137 version 1.9.1 started

    The config file is:

    Automatically Generated, do not edit

    Generated for DHCPv6 Server lan

    interface alc0 {
    AdvSendAdvert on;
    MinRtrAdvInterval 5;
    MaxRtrAdvInterval 20;
    AdvLinkMTU 1500;
    AdvDefaultPreference high;
    AdvManagedFlag on;
    AdvOtherConfigFlag on;
    prefix / {
    DeprecatePrefix on;
    AdvOnLink on;
    AdvAutonomous on;
    AdvRouterAddr on;
    AdvValidLifetime 86400;
    AdvPreferredLifetime 14400;
    };
    route ::/0 {
    RemoveRoute on;
    };
    DNSSL accra.ca { };
    };



  • Assuming you have an IPv6 address on the LAN interface, and you have the RA on the LAN interface turned on, it should collect the prefix from the interface config.

    A working config looks like this:

    # Automatically Generated, do not edit
    # Generated for DHCPv6 Server lan
    interface em1 {
    	AdvSendAdvert on;
    	MinRtrAdvInterval 5;
    	MaxRtrAdvInterval 20;
    	AdvLinkMTU 1500;
    	AdvDefaultPreference low;
    	AdvManagedFlag on;
    	AdvOtherConfigFlag on;
    	prefix 2001:470:xxxx::/64 {
    		DeprecatePrefix on;
    		AdvOnLink on;
    		AdvAutonomous on;
    		AdvRouterAddr on;
    		AdvValidLifetime 7200;
    		AdvPreferredLifetime 3600;
    	};
    	route ::/0 {
    		RemoveRoute on;
    	};
    	RDNSS 2001:470:xxxx::1 { };
    	DNSSL example.local { };
    };
    

Log in to reply