Hey,

I am using a Mikrotik Board 1100AHx2 as PPPoE Server for our Network.
Dual Stack IPv4 & IPv6 has now been implemented. It is working nice if a client router (Fritzbox 7330) connects for the first time. But when you reboot the client router or just make a reconect, IPv6 will not work anymore.

And this is what I might found as an explaination:

for the server on the mirkotik I configured as
http://wiki.mikrotik.com/wiki/Manual:IPv6_PD_over_PPP

So when a new client router connects as pppoe client, the following is added in the Mikrotik:
- IPv6 dynamic route
- IPv6 DHCP Client
- IPv6 DHCP Binding

IPv6 on Client is working then.

BUT: when I unplug/restart the client router the following happens:

In the Mikrotik first the three points above become "inactive", after restart the client router receives the same IPv6 Prefix again because of existing DHCP Binding. However the dynamic route for this Prefix will remain inactive. As a result the client has no IPv6 because of missing route in the Mikrotik.

When removing the three points above manually from the mikrotik and reconnecting´the client router, everything is set again correctly.

Sounds like a little bug to me.
Contact me for further information on this if necessary.

I can confirm a similar issue (bug?) but RB450 is the DHCP client - maybe it points to the same problem.

On setting up the connection to my ISP, i get an IPv6 block via DHCP client, and a dynamic address pool is created as defined and on one of my ethernet interfaces, an IP address is correctly assigned, working as expected.
On router restart, the DHCP address is again assigned (have to check if it si the same...), but the pool is not there and no IP is assigned to the internal interface.
If I request a release on the DHCP client, the DHCP client gets the same IP again. The address pool is created briefly, the interface gets a correct IP but after a few seconds the dynamic pool disappears and the address is lost. The DHCP client remains in the bound state with that IP prefix assigned. On requesting a release this sequence will repeat: pool is created, addresses delegated and after 2-3 seconds the pool vanishes (the assigned prefix remains the same).
If i disconnect and reconnect the PPPoE connection, then a new IP prefix is assigned via DHCP, and everything works as expected, with a stable pool and correct PD.
The same offer from my side, as from captainproton: For more testing, checking and debugging I am of course available
I want to mention that i observed this behavior in all 5.x releases (and still here in 5.17).

I have just experiences the same bug as you.

I set it all up.. connected Cisco 887 Router and Assigned PD Network Correctly via PPPoE and I could surf the internet on IPv6 100% . Disconnected Cisco and reconnected and no PD now

Running 5.17 on same Hardware.

Makes IPv6 via PPPoE useless as it doesn't work properly

support told me that they can reproduce the problem and will fix it in next release!

I have 5.18 on 1100AHx2 and it is all effed up. Unable to create a simple dhcp server with wizard or manually. I reset to factory and port 12 on the case is now "ethernet1" interface with the 192.168.88.1 IP??? I was using NeighborViewer to see which port to connect to and they all said 0.0.0.0 until I got to port 12 which said the above address 192.168.88.1. I plugged into 12 and looked at interfaces and it says ethernet 1 is running with nothing plugged in. Clearly something is wrong. All I want to do is group ports for PPPOE, dhcp server and static connections for testing lab equipment. I created a vlan2 and applied 192.168.200.1/24 IP to it. Then I run dhcp wizard and it says successful but fails to serve addresses from the pool. I then delete it all and create all manually, same thing. Only pppoe and static work. I was supposed to go production tomorrow. You know why Mikrotik will never be a contender? Because they don't offer support. There is no number I can call in the U.S. to get my 90 days of support for the $500 product I purchased. I would gladly pay more money for the box to get support from Mikrotik.

Same issue right here, I'm using RB750 and RB411U... and already tested in firmware (5.21).
Hoping next new release firmware able to fix this...

the issue was fixed in my case after upgrading to 5.18

i am still on 5.18