How to use accel-ppp to build a PPPoEV6 server

[kite896]

Before using accel, I used rp-pppoe to build a PPPoeV6 environment:

1. First, the router dials normally
2. Radvd needs to be enabled in the server to send router Adevertise to the listening port ppp0
3. The router sends a DHCPV6 solicit request to obtain an IPV6 address. I use dibbler or kea-dhcp6 as the DHCPV6 server

Now here is my question: I asked the AI ​​to answer me, accel-ppp does not support enabling DHCPV6 on the ppp virtual interface, but supports enabling it on the physical port, or negotiating the IPV6 address and prefix during the PPPOE negotiation phase.

So I would like to ask whether [ipv6-dhcp] supports enabling dhcpv6 on the ppp0 interface?

However, my router does not support direct negotiation at the PPPOE stage, so an additional DHCPV6 server is required.

Of course, I have also tried using ACCEL as the PPPoE server and kea as the DHCPV6 server, but the address is obtained normally when the first dial-up connection is connected, but once the connection is disconnected and reconnected, the address cannot be obtained

[kite896]

At this time, kea starts normally but does not respond to solicit, and there is no additional log output. It seems to be a kea problem.
But in the old environment, rp-pppoe is normal, so can it be said to be a compatibility problem?

[kite896]

One more thing to add, radvd works fine in the same ip-up configuration, even if I roughly killall radvd and then restart it, it still works. Well, kea seems to have a problem, maybe I implemented dibbler in the same environment?

The environment I have built can be used barely, but if the client cannot get the address, I need to ： systemctl restart accel-ppp

[svlobanov]

Hi @kite896. Do not trust AI, use man accel-ppp.conf. It supports DHCPv6

[kite896]

man accel-ppp.conf

Ok I'll try that, thanks.

[kite896]

Hi @kite896. Do not trust AI, use man accel-ppp.conf. It supports DHCPv6

I would like to ask if you have a complete accel-ppp.conf file that supports dhcpv6. I don't quite understand the difference between the ipoe, ipv6-pool, and ipv6-dhcp modules. From my network topology, I think I need to use the ipv6-dhcp module.

But when I checked use man accel-ppp.conf, there is only a description of ipv6-pool.

Sorry to bother you, don't worry if it's necessary.I will try to read the document, configure and test it later.

[kite896]

use man accel-ppp.conf

Good news, using man accel-ppp.conf it works.
You need to load ipv6 related modules in module:
[modules]
ipv6_nd
ipv6_dhcp
ipv6pool

Then write the detailed configuration in the configuration file:
[ipv6-pool]
#gw-ip6-address=fc00:0:1::1
#vendor=
#attr-prefix=Delegated-IPv6-Prefix-Pool
#attr-address=Stateful-IPv6-Address-Pool
fc00:0:1::/48,64
......
[ipv6-nd]
verbose=1
MaxRtrAdvInterval=600
MinRtrAdvInterval=33
......

AI told me that accel-ppp does not support ra and must use radvd. It turns out that AI is wrong. The [ipv6-nd] module can be used to configure the neighbor discovery protocol.

This is an apology from AI:
Thank you for your correction. You are absolutely right: accel-ppp’s [ipv6-nd] module does provide built-in Router Advertisement (RA) functionality, and it can be used to send RA messages directly from accel-ppp, making external tools like radvd unnecessary in many scenarios.

[svlobanov]

@kite896 AI has almost zero knowledge regarding accel-ppp because there is too little public information. There are no discussion on stackoverflow and so on. You can use the following resources if you need more info

1. man accel-ppp.conf
2. https://docs.accel-ppp.org/
3. telegram chats: en: @accel_ppp_en, pt_BR : @accel_ppp_br, ru: @accel_ppp

[kite896]

@kite896 AI has almost zero knowledge regarding accel-ppp because there is too little public information. There are no discussion on stackoverflow and so on. You can use the following resources if you need more info

1. man accel-ppp.conf
2. https://docs.accel-ppp.org/
3. telegram chats: en: @accel_ppp_en, pt_BR : @accel_ppp_br, ru: @accel_ppp

OK got it, thank you for your reply！