Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Internode Native IPv6, No Address?

    Scheduled Pinned Locked Moved IPv6
    34 Posts 6 Posters 10.9k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • T
      Toje
      last edited by

      Looking over my logs, I have a feeling something's gone wrong on the nodes end.

      It was not link local in the past.

      1 Reply Last reply Reply Quote 0
      • R
        Rezin
        last edited by

        I haven't called support yet, but in the meantime I thought I'd try disabling IPv6 in the Node CP, and will enable it again later tonight… might kick something on their end into working differently.

        1 Reply Last reply Reply Quote 0
        • T
          Toje
          last edited by

          As silly as it sounds, try changing your MAC,

          1 Reply Last reply Reply Quote 0
          • R
            Rezin
            last edited by

            Tried setting it all up again today… still doesn't work 100%. I can use Diagnostics > Ping to google.com using IPv6, and get replies... but nothing on the LAN side can access remote IPv6 addresses.

            Toje, are you seeing entries like these in your System Log?

            php: rc.filter_configure_sync: The command '/sbin/route change -inet6 default fe80::224:14ff:fe9a:9810' returned exit code '1', the output was 'route: writing to routing socket: Network is unreachable route: writing to routing socket: Network is unreachable change net default: gateway fe80::224:14ff:fe9a:9810: Network is unreachable'
            
            php: rc.newwanip: The command '/sbin/route change -inet6 default fe80::224:14ff:fe9a:9810' returned exit code '1', the output was 'route: writing to routing socket: Network is unreachable route: writing to routing socket: Network is unreachable change net default: gateway fe80::224:14ff:fe9a:9810: Network is unreachable'
            
            IPv6
            Destination	Gateway					Flags	Refs	Use	Mtu	Netif	Expire
            default		fe80::224:14ff:fe9a:9810%pppoe0		UGS	0	2146	1492	pppoe0	 
            

            Similar to another thread here.

            Edit: Seems to be working now, for some reason.  ???  ;D

            The settings I'm using:

            WAN:

            • IPv6 Configuration Type: DHCP6

            • Use IPv4 connectivity as parent interface: Ticked

            • Request only a IPv6 prefix: Ticked

            • DHCPv6 Prefix Delegation size: 64

            • Send IPv6 prefix hint: Ticked

            LAN:

            • IPv6 Configuration Type: Static IPv6

            • IPv6 address: 2001:44b8:xxx:yyyy:: (/64)

            DHCP:

            • Enable DHCPv6 server on LAN interface: Un-ticked

            • Router Advertisements: Assisted (though I think it should be Unmanaged.. but I'll just leave it as is for the minute  ;))

            … and a few WAN and LAN firewall rules.

            Edit 2: ugh, borked again, without any changes made.

            1 Reply Last reply Reply Quote 0
            • R
              razzfazz
              last edited by

              @ingenieurmt:

              Request only a IPv6 prefix: Yes
              DHCPv6 Prefix Delegation size: None

              That seems a bit odd; the first option says you only want a delegated prefix, but the second option says you don't want a prefix. Why do you think you want the first one, anyway?

              1 Reply Last reply Reply Quote 0
              • R
                razzfazz
                last edited by

                @Rezin:

                The settings I'm using:

                WAN:

                • IPv6 Configuration Type: DHCP6

                • Request only a IPv6 prefix: Ticked

                • DHCPv6 Prefix Delegation size: 64

                • Send IPv6 prefix hint: Ticked

                LAN:

                • IPv6 Configuration Type: Static IPv6

                That, too, seems odd: You're requesting prefix delegation, but then you're not actually using the prefix information obtained via DHCP-PD but instead configure your prefix statically. Also, I thought the delegated prefix was supposed to be a /56, not a /64?!

                1 Reply Last reply Reply Quote 0
                • R
                  Rezin
                  last edited by

                  @razzfazz:

                  That, too, seems odd: You're requesting prefix delegation, but then you're not actually using the prefix information obtained via DHCP-PD but instead configure your prefix statically.

                  Not too sure what you're saying… any chance you could elaborate?

                  @razzfazz:

                  Also, I thought the delegated prefix was supposed to be a /56, not a /64?!

                  Your delegated static /56 IPv6 prefix for your LAN is: 2001:44b8:xxx:yyyy

                  • Your existing IPv4 address (if static) and any existing framed route(s)
                  • A dynamic /64 IPv6 prefix for your PPP session
                  • A static /56 IPv6 prefix for your LAN (if you are using a router with Prefix Delegation)

                  That's what's shown in the Node control panel. My interpretation of that is 64 is used on the WAN's "DHCPv6 Prefix Delegation size" drop-down, and 56 is used for the LAN's "IPv6 address" (although Logs > System > Routing then has entries saying "radvd[79545]: prefix length should be 64 for em0", so I just set it to 64 there as well).

                  Edit: em0 is the LAN interface.

                  1 Reply Last reply Reply Quote 0
                  • T
                    Toje
                    last edited by

                    I have the same Setup Rezin,

                    Razzfazz I set it up with the idea my WAN is the Internode side of the network and my LAN is my side, so like on a normal lan-lan router there are two different IP's

                    1 Reply Last reply Reply Quote 0
                    • R
                      razzfazz
                      last edited by

                      @Rezin:

                      Your delegated static /56 IPv6 prefix for your LAN is: 2001:44b8:xxx:yyyy

                      • Your existing IPv4 address (if static) and any existing framed route(s)
                      • A dynamic /64 IPv6 prefix for your PPP session
                      • A static /56 IPv6 prefix for your LAN (if you are using a router with Prefix Delegation)

                      That's what's shown in the Node control panel. My interpretation of that is 64 is used on the WAN's "DHCPv6 Prefix Delegation size" drop-down, and 56 is used for the LAN's "IPv6 address" (although Logs > System > Routing then has entries saying "radvd[79545]: prefix length should be 64 for em0", so I just set it to 64 there as well).

                      Edit: em0 is the LAN interface.

                      The "dynamic /64 IPv6 prefix for your PPP session" is what you get on your WAN side; this has nothing to do with prefix delegation. The "delegated prefix size" field determines (as the name implies) the size of the prefix that your provider is delegating to you (in this case, /56); parts of that delegated prefix (e.g., one of the 256 /64 prefixes that your delegated /56 prefix spans) is what you'd use on your LAN-side interfaces.

                      From the quoted blurb, it is not clear to me that your provider actually requires the use of DHCP6-PD (–> prefix delegation via DHCP6) at all; given that your prefix is in fact statically assigned, you may be able to get away with just configuring your LAN side as "static IPv6" with an address from the prefix and without requesting delegation through the WAN interface.

                      1 Reply Last reply Reply Quote 0
                      • R
                        razzfazz
                        last edited by

                        @Toje:

                        Razzfazz I set it up with the idea my WAN is the Internode side of the network and my LAN is my side, so like on a normal lan-lan router there are two different IP's

                        Right; on the WAN side, you have an address from a dynamically assigned /64 prefix, whereas any LAN-side interfaces would get addresses from (different sub-prefixes of) the delegated /56; pfSense will then route between them, with a default route out the WAN interface, while your provider will just route your delegated prefix to your WAN address.

                        1 Reply Last reply Reply Quote 0
                        • T
                          Toje
                          last edited by

                          That's exactly how I have it and see it.

                          1 Reply Last reply Reply Quote 0
                          • R
                            Rezin
                            last edited by

                            Hey Toje, try this if you haven't already got it going:

                            WAN:

                            • IPv6 Configuration Type: DHCP6

                            • Use IPv4 connectivity as parent interface: Ticked

                            • Request only a IPv6 prefix: Ticked

                            • DHCPv6 Prefix Delegation size: 64

                            • Send IPv6 prefix hint: Un-ticked

                            LAN:

                            • IPv6 Configuration Type: Static IPv6

                            • IPv6 address: 2001:44b8:xxx:yyyy::  /64

                            • Gateway IPv6: None

                            DHCP:

                            • Enable DHCPv6 server on LAN interface: Un-ticked

                            • Router Advertisements: Unmanaged

                            .. and some WAN/LAN firewall rules to allow outgoing, and incoming IPv6 ICMP.

                            You may also need to edit /etc/inc/interfaces.inc, and comment out:

                            if(!isset($wancfg['dhcp6prefixonly']))
                                  $dhcp6cconf .= "        send ia-na 0;   # request stateful address\n";
                            

                            http://forums.whirlpool.net.au/archive/2126663

                            Edit: Actually just check "Request only a IPv6 prefix".

                            1 Reply Last reply Reply Quote 0
                            • T
                              Toje
                              last edited by

                              Yeah no change for me,

                              still getting fe80::20c:29ff:fe65:5f35%em1 on WAN

                              1 Reply Last reply Reply Quote 0
                              • R
                                Rezin
                                last edited by

                                @Toje:

                                still getting fe80::20c:29ff:fe65:5f35%em1 on WAN

                                Run "ifconfig pppoe0" (or your WAN interface). Looking at Status > Interfaces for my "WAN1 interface (pppoe0)", it doesn't show one of the IPv6 addresses that ifconfig does:

                                inet6 2001:44b8:etc prefixlen 64 autoconf

                                1 Reply Last reply Reply Quote 0
                                • T
                                  Toje
                                  last edited by

                                  I see, seems like that sothing that needs to be fixed

                                  I am getting
                                  inet6 2001:44b8:1050:8934:7c67:270:8842:cc3c prefixlen 64 autoconf
                                  nd6 options=3<performnud,accept_rtadv></performnud,accept_rtadv>

                                  1 Reply Last reply Reply Quote 0
                                  • D
                                    doktornotor Banned
                                    last edited by

                                    Sounds like it works… :)

                                    1 Reply Last reply Reply Quote 0
                                    • T
                                      Toje
                                      last edited by

                                      Anyone got it working?

                                      1 Reply Last reply Reply Quote 0
                                      • B
                                        bierhedd
                                        last edited by

                                        I've had this problem for a while, since upgrading beyond 2.1-RC0. I have IPv6 working fine with Internode on an install from pfSense-LiveCD-2.1-RC0-i386-20130528-0427.iso but I can't get it working in 2.1-RELEASE-i386.

                                        I've even tried backing up and restoring the pfSense config from the old install to the new one (I run pfSense VMs). Everything works after restoring, except IPv6!

                                        The 2.1-RELEASE has more WAN IPV6 options than the 2.1-RC0. In RC0 I select "DHCP6", which then shows the "DHCP6 client configuration" options below it. The only option is the prefix delegation size which I set to /56 and when I apply the settings my WAN interface gets assigned my static IPv4 address from Internode and a global /64 Internode IPv6 address.

                                        In the final release 2.1-RELEASE there are three tickboxes in addition to the prefix delegation size drop down box. I'm sure I've tried every combination of these tickboxes to no avail.

                                        I'm confident the problem is something that has broken in pfSense since 2.1-RC0 due to the new options for DHCP6.

                                        I'm happy to post system logs from both the 2.1-RC0 and the 2.1-RELEASE installs if somebody is a good pfSense troubleshooter, although the only DHCP6 entries I can see in the logs are under the PPP tab. If there's a better log file to be looking at via command line please let me know.

                                        Cheers, BieRHeDD.

                                        1 Reply Last reply Reply Quote 0
                                        • First post
                                          Last post
                                        Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.