- CheckMates
- :
- Products
- :
- CloudMates Products
- :
- Cloud Network Security
- :
- Discussion
- :
- Alias IP addresses on 1 NIC in Azure CloudGuard
Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Are you a member of CheckMates?
×
Sign in with your Check Point UserCenter/PartnerMap account to access more great content and get a chance to win some Apple AirPods! If you don't have an account, create one now for free!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Alias IP addresses on 1 NIC in Azure CloudGuard
Hi All,
We have a customer trying to go off script and not follow the CP Azure reference architecture, by acquiring public IP addresses from Azure and adding the internal IP addresses as Aliases to the CP Standalone CloudGuard firewall's external NIC. About 20 aliases 😞
The customer has deployed this same setup using R80.10, but wants us to deploy it with R80.20. What are the repercussions of doing this as it is not mentioned anywhere in the reference architecture.
Could hotfixes or patches kill this design ? on physical appliances this is supported, but no mention for CloudGuard.
Please advise on the same.
Thanks
Bhav
1 Reply
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The limitations are more on the Azure side.
That said, if this was working in R80.10 on Azure, I'm not aware of anything that would prevent it from being done in R80.20.
That said, if this was working in R80.10 on Azure, I'm not aware of anything that would prevent it from being done in R80.20.