I'm trying to configure a Wildcard forwarding virtual server on AWS (0.0.0.0:0) in order to communicate a bunch of clients with different destinations.
For example, i need clients with the next ip addresses 10.2.2.0/24 and 10.2.3.0/24 being able to communicate with some services with different IP's and ports (10.55.55.23:14502, 10.55.55.76:14502, 10.55.56.27:14501)
Its a 2-NIC deployment (1 NIC for management and 1 NIC for Traffic).
In the traffic NIC i only have configured the self IP (No secondary IP addresses assigned on this AWS interface)
I already disabled source/destination check on the F5 instance.
After some tests i cant see any data from clients reaching the big ip.
Do i need to assign a secondary IP address in the traffic NIC so the big ip can use this IP to capture the traffic ?
Is there something else i'm missing in my configuration?
Every suggestion is welcome.
Thanks in advance guys!
Hi @VictorRuiz ,
So you're working in one-arm deployment.
you need to assign at least 1 Vlan ( untagged ) and assign it within selfip address , you can also check the auto last hop feature.
if this hasn't solce your issue , please tell me more about your network design.