- CheckMates
- :
- Products
- :
- CloudMates Products
- :
- Cloud Network Security
- :
- Discussion
- :
- Additional External IP (AWS)
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Are you a member of CheckMates?
×- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Additional External IP (AWS)
The customers has a cluster R80.10 on AWS environment.
The front-end 172.31.19.x with public IP address (eth0)
The back-en 172.31.18.x (eth1)
On the front-end interfaces are configured severals subiterfaces to public services, something like this
ETH0
172.31.19.x public1
172.31.19.y public2
172.31.19.z public3
172.31.19.v public4
172.31.19.q public5
But the customer reach the limit of interface to associate public IP address and need to public more.
We try to do that add another external interface but it does not work.
Anyone how which is the procedure in this case??
Leaderboard
Epsum factorial non deposit quid pro quo hic escorol.
User | Count |
---|---|
2 | |
2 | |
1 | |
1 | |
1 |
Thu 09 May 2024 @ 05:00 PM (CEST)
Under the Hood: Automate Azure Virtual WAN security deployments with Terraform