-
Notifications
You must be signed in to change notification settings - Fork 45
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
New module - meraki_mx_site_to_site_vpn #59
Comments
@pokepoke81 - This module will be almost identical to |
@pokepoke81 I don't know if you'll be notified on the new PR, but please check out #68. Test and let me know if it works. |
Also, there isn’t an endpoint to configure site to site VPNs as far as I can tell. The best I can do is firewall rules for them. |
I'm trying to piece some things together. It seems that Site to Site VPN settings are defined in the Network: https://developer.cisco.com/meraki/api/#/python/api-endpoints/networks/update-network-site-to-site-vpn So, do you have a separate module to add VLANs to the Site-to-Site VPN like the API? Or do you allow adding/editing them with the This will also apply to static routes defined on the MX. https://community.meraki.com/t5/Developers-APIs/VPN-Static-Routes-through-API/m-p/50002 |
Also, I don't have a way to test your PR. I only have one organization and it's production. I'm testing the MS and MX stuff against spare hardware in the organization. I don't think that will work for me since VPN settings are across the organization, not the network. |
You may be able to create a new organization without licensing to test the module. |
@kbreit I'm on a deadline this week, so haven't had a chance to get to this. Hopefully I can find a way to test it next week. |
No problem. Let me know when you're able to test it. |
Meraki had support for configuring and querying site-to-site VPN information. A new module should be created to support this.
https://developer.cisco.com/meraki/api/#/rest/api-endpoints/networks/get-network-site-to-site-vpn
This issue is merged from ansible/ansible from issue request ansible/ansible#55997.
The text was updated successfully, but these errors were encountered: