Forum Discussion
AltostratusAPM VPN LDAP POOL can't contact ldap server.
NacreousWhat seeting does your LDAP pool has.
Maybe you have define specific port there? For example LDAP but in LDAP auth you choose ldaps?
Usually, at least in ad auth, where you can create a pool directly through ad auth config, the pool actually be created with wildcard port
ShawnCThe setup uses LDAP on port 389 for everything. It works when configured as a 'direct' connection, but it fails when switching to the 'pool' configuration.
- Injeyan_Kostas
Have you done a tcpdump to check if the traffic is leaving f5 correctly?
- ShawnC
Using tcpdump, I discovered that when using a pool, port 389 always sends out through other floating IPs.
The problem was that the interface I needed to route to didn't have a floating IP configured, only its own IP. After configuring it, the connection worked.
I'm using two machines in HA mode. I found that using Direct routes sends the MGMT, while using Pool routes it sends the floating IP. I tried directly pointing the router to the VLAN, but without a floating IP, the data wasn't sent out at all.
The conclusion is that a floating IP must be configured. Thank you for your help.
