-
Notifications
You must be signed in to change notification settings - Fork 231
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add VRF binding support #311
Comments
@paulusmack, @enaess: What do you think? |
Sounds reasonable. Do you have a patch? |
I do not have a patch but I would provide one. As I am not familiar with the codebase maybe you can point me to the file which needs to be extended.
From https://www.kernel.org/doc/Documentation/networking/vrf.txt
|
@c-po: Have you looked? |
Hi @Neustradamus, I have workarounded the issue by calling a custom script which does all the VRF handling once the interface was dialed. IMHO not that nice but it works |
@EasyNetDev: Can you look it? |
Hi all, I can take a look in the near future for a patch. Now I'm busy with creating a script to build custom Debian OS for Banana Pi R4 and not only. |
Hi Paul,
I am one of the mainters of VyOS an open source, Linux (Debian) based network operating system. We utilize pppd to provide dial-up (pppoe) connections for the users. We have added VRF support in our upcoming 1.3 release by using ip-up/ip-down scripts to move an interface into the appropriate VRF - that somehow works but could be nicer.
Why?
The flakyness now comes into play when routes should be installed by pppd, pppd will always install the route into the main routing table - no problem - we can workaround this in an ip-up/down helper, too.
Feature Request
Could a new configuration item named
vrf
be added into the peer configuration file? If that vrf is defined, and the vrf exists, pppd can then automatically assign the interface into the appropriate VRF without the need for additional external helpers.The text was updated successfully, but these errors were encountered: