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

    Issues with IPv6 PD over PPPoE IPv4

    Scheduled Pinned Locked Moved IPv6
    9 Posts 3 Posters 1.2k 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.
    • S
      S_m
      last edited by

      I'm trying to get my /48 from WAN (PPPoE) with DHCPv6 client with prefix delegation, I got the prefix delegation working within rOS
      PPPoE and then DHCP6 client without issues.

      But in pfsense don't. Tested 2.4.4-p3 and 2.5 Feb10 2020 build. Two different installs.

      Screenshot 2020-02-10 23.55.54.png

      Screenshot 2020-02-11 00.06.48.png

      There's no entries on DHCP logs about DHCPv6, I mde captures over PPPoE and WAN, not a single dhcp query.

      pppoe0: flags=88d1<UP,POINTOPOINT,RUNNING,NOARP,SIMPLEX,MULTICAST> metric 0 mtu 1492
              inet6 fe80::d6ae:52ff:fec1:7d5e%pppoe0 prefixlen 64 scopeid 0x16 
              inet xx.xxx.xxx.32 --> xxx.xxx.xx.32 netmask 0xffffffff 
              nd6 options=23<PERFORMNUD,ACCEPT_RTADV,AUTO_LINKLOCAL>
      

      Set Track interface on LAN and DHCP server, no luck.

      JKnottJ 1 Reply Last reply Reply Quote 0
      • JKnottJ
        JKnott @S_m
        last edited by

        @S_m

        Why do you have Request only an IPv6 prefix selected?

        PfSense running on Qotom mini PC
        i5 CPU, 4 GB memory, 32 GB SSD & 4 Intel Gb Ethernet ports.
        UniFi AC-Lite access point

        I haven't lost my mind. It's around here...somewhere...

        1 Reply Last reply Reply Quote 0
        • S
          S_m
          last edited by

          In mikrotik only got the PD working without getting an address. I also tested all combinations. But no luck.

          1 Reply Last reply Reply Quote 0
          • G
            Gilera
            last edited by Gilera

            Doubt i have exactly same setup as you, similar though.

            272d6a35-273f-43a6-82b3-f90a961ce2b1-image.png

            Have you tried changing the Advertisement options?

            154511ad-70bc-4941-ada9-c40b91b80035-image.png

            1 Reply Last reply Reply Quote 0
            • S
              S_m
              last edited by

              I got it running sorta.

              Screenshot 2020-04-13 22.14.15.png

              I had to enable Do not wait for RA to get it working.

              Then I used static IPv6 on the LAN and assigned my /64 static.

              Then enabled the DHCv6 server on the LAN with the range I wanted. But with this you need to in account, Android devices don't like DHCPv6 so you have to fix the Router Adverisment with te Router mode put in assited for android or managed. With assited they won't get IPs.

              Note, on the WAN interface you won't get a public IP, I got a local IPv6 only.

              Another issue I got with pfsesne and ipv6 it's that with IPv6 enabled the update process can't be used properly taking more than 3 minutes to check updates and almost 2 hours to donwload 40 packages. Disabling IPv6 before upgrading fixes that.

              JKnottJ 1 Reply Last reply Reply Quote 0
              • JKnottJ
                JKnott @S_m
                last edited by

                @S_m said in Issues with IPv6 PD over PPPoE IPv4:

                Note, on the WAN interface you won't get a public IP, I got a local IPv6 only.

                That's because you have Request only an IPv6 prefix selected.

                PfSense running on Qotom mini PC
                i5 CPU, 4 GB memory, 32 GB SSD & 4 Intel Gb Ethernet ports.
                UniFi AC-Lite access point

                I haven't lost my mind. It's around here...somewhere...

                S 1 Reply Last reply Reply Quote 0
                • G
                  Gilera
                  last edited by

                  Learning everyday about ipv6........@JKnott, why do i only get a link local ipv6 address on the WAN? I do not have that option selected.

                  I don't have a requirement for it but just wondering why a lot of people seem use that as a metric as to whether ipv6 is working or for some other reasons i'm not aware of.

                  JKnottJ 1 Reply Last reply Reply Quote 0
                  • S
                    S_m @JKnott
                    last edited by S_m

                    @JKnott said in Issues with IPv6 PD over PPPoE IPv4:

                    @S_m said in Issues with IPv6 PD over PPPoE IPv4:

                    Note, on the WAN interface you won't get a public IP, I got a local IPv6 only.

                    That's because you have Request only an IPv6 prefix selected.

                    Yes, it was my mistake I wanted to say this:
                    You don't have info about the prefix you were delegated on the wan.
                    In mikrotik routerOS you have the /48 right there

                    Like this:
                    prefix.png

                    1 Reply Last reply Reply Quote 0
                    • JKnottJ
                      JKnott @Gilera
                      last edited by

                      @Gilera said in Issues with IPv6 PD over PPPoE IPv4:

                      Learning everyday about ipv6........@JKnott, why do i only get a link local ipv6 address on the WAN? I do not have that option selected.

                      You do in that screen capture you posted. That's why I mentioned it.

                      PfSense running on Qotom mini PC
                      i5 CPU, 4 GB memory, 32 GB SSD & 4 Intel Gb Ethernet ports.
                      UniFi AC-Lite access point

                      I haven't lost my mind. It's around here...somewhere...

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