Forum Discussion
AK_1947
Nimbostratus
NimbostratusPublic IP address display
Hello guys, I have question about one situation. I actually for own partner, they use tool (url) to display the public IP address. They got two F5 ASM, for one, everything is OK the public Ip is d...
Hi AK_1947 ,
It’s a strange thing , because you can’t see the Self/floating ip addresses instead of the public or original source ip of the client.
The only way to see that if you have TWO f5 in one path or behind each other Like the below snap-shot :I think there is a misconfiguration in network design , because the above snap shot is the only possibility to see the self/floating sends traffic if you use the ( SNAT ->> auto map ) option in the first F5-ASM1 Appliance.
So check it again , no further configuration to do from F5 side , the only thing is to check and review your network design configuration and traffic flow paths.Hi AK_1947 - did Mohamed_Ahmed_Kansoh or Paulius's replies help you out, or are you still struggling? If one of their replies helped solve your issue, please click "Accept as Solution" so other users with the same issue can find the answer in the future. 🙂
AK_1947Nimbostratus
NimbostratusLet's try to explain it.
We got a cluster in active/passive mode , active member the self-Ip address is display. When the second one is active and the first is passive mode, all is Ok. We got the right information (the public ip address) when we try to access on the link.
Both are behind the Firewall, we use NAT rule, we got the same configuration. The only change is, the first one, we flow in dedicated WAN line. But that would not be the cause I think so.
Apologize for my English, I do my best. If the context isn't clear, I will add more to make it clear.
Thank you for you help
Hi AK_1947 ,
Is IP : 10.135.0.53 the self ip address that you mean it appears to you instead public ip address ?
Also , Do you mean that Public IP of user should be appear instead of self ip address ?
Also , Do you monitor this behavior by ASM Event logs or explain how does the tool (url) work ?
I will follow up your request after clarifying more.
- AK_1947
Hello
Sorry for the delay I was out off.Find my answers below on yours questions :
Is IP : 10.135.0.53 the self ip address that you mean it appears to you instead public ip address ?
Yes, that's not good for us.
Also , Do you mean that Public IP of user should be appear instead of self ip address ?
Yes, it should be
Also , Do you monitor this behavior by ASM Event logs or explain how does the tool (url) work ?
Yes, it's . Like I said earlier, we got another F5 ASM and when the traffic is on that one, all works.
Both ASM configuration are the same, I got suspicion on ASM network configuration (Interfaces, self IP address and VLAN ) on the one we got the issue.
Best regardsHi AK_1947 ,
It’s a strange thing , because you can’t see the Self/floating ip addresses instead of the public or original source ip of the client.
The only way to see that if you have TWO f5 in one path or behind each other Like the below snap-shot :I think there is a misconfiguration in network design , because the above snap shot is the only possibility to see the self/floating sends traffic if you use the ( SNAT ->> auto map ) option in the first F5-ASM1 Appliance.
So check it again , no further configuration to do from F5 side , the only thing is to check and review your network design configuration and traffic flow paths.