I don’t know if this is the right place to post this, but I see that the project is now under the VyOS group.
I’m using accel-ppp on Debian together with FRR for a very small ISP, and I really appreciate your work – it allowed me to replace an old hardware router.
I’m using Debian because in VyOS I’m not able to get PPPoE and IPoE working on the same parent interface.
I started running some tests with the vlan_mon kernel module to handle QinQ and to automatically detect new ENNI interfaces.
Right now it can detect ETH_P_8021AD on the skb, and I extended the VLAN_MON_ATTR enum to pass the detected data to the userspace accel-ppp vlan_mon.
Do you think this is the right way to proceed? I would be glad to contribute to the project.
Another question: I saw your work to integrate VPP with accel-ppp. I see support for PPPoE, but what about IPoE? I prefer PPPoE over IPoE; at the moment I use IPoE only on one test line that I have at home, because PPPoE is easier to debug.
There are actually multiple topics here that probably deserve separate discussions in different places.
First, regarding accel-ppp under the VyOS umbrella - that’s not accurate. Right now, there are technically two actively maintained forks. The first one is the standard accel-ppp that you’re currently using. For questions about this fork, there is both commercial and community support available.
Next, there’s the issue of sharing PPPoE and IPoE on the same parent interface in VyOS. This seems like a purely VyOS-specific limitation. If you can get this working with the standalone accel-ppp (not integrated into VyOS), I’d highly recommend creating a feature request with an example of how you achieved it. We’d be happy to check if this can be integrated into VyOS to remove that limitation.
Finally, there’s VPP integration. This is one of the features we’re actively working on in the accel-ppp-ng repository. We expect the PPPoE functionality to be ready for use soon. There are still a few key points missing before we can call it production-ready, but not many. So, hopefully, you’ll be able to use VyOS as an accelerated PPPoE concentrator in the near future.
For Vyos, i checked the j2 scripts and it will be very complicated every conf change call a restart of the deamon, for pppoe client they will see reconnect for ipoe it’s depents on lease time.
About QinQ first problem is kernel IFNAMSIZ, my workaround was to call e0 ENNI interface…
All my test was done on GNS3, without live traffic…
As I mentioned, there are technically two different versions of accel-ppp. The version in VyOS has planned improvements that should eliminate the need for a full daemon restart to apply changes.
In other words, without a feature request, the functionality you need will definitely never make it into VyOS. With a feature request, however, it might become available - if it’s considered interesting and feasible.
