creating new radius and tacacs data classes.
We would need couple of new options based on whether user wants to select vpn directly or if they want to select source VPN along with VXLAN tunnel.
Description of changes:
When we use direct VPN0/VPN512, and use vpn,vpn subnet ip, it will fail. it only needs source vpn, which is not there.
On the other hand, when we use VPN 512 via VXLAN, then sourcevpn, vpn, vpn subnet ip are requited. Which is also not there.
Hence we need new data classes
Checklist:
[X] Make sure to run pre-commit before committing changes
[X] Make sure all checks have passed
[X] PR description is clear and comprehensive
[X] Mentioned the issue that this PR solves (if applicable)
Pull Request summary:
creating new radius and tacacs data classes. We would need couple of new options based on whether user wants to select vpn directly or if they want to select source VPN along with VXLAN tunnel.
Description of changes:
When we use direct VPN0/VPN512, and use vpn,vpn subnet ip, it will fail. it only needs source vpn, which is not there.
On the other hand, when we use VPN 512 via VXLAN, then sourcevpn, vpn, vpn subnet ip are requited. Which is also not there.
Hence we need new data classes
Checklist: