Forum Discussion
Help configuring NAT64 on a BIG-IP LTM
- May 27, 2014
You may need to run packet captures at this point to determine why the page isn't loading:
tcpdump -nni 0.0:n -s0 host 2001:b3e:45f1:6121::7 (client side)
tcpdump -nni 0.0:n -s0 host 192.168.1.7 (server side)
You can have pool members or virtual servers specifying all ports, but your pool member can't be monitored on all ports. The monitor must be specific to a certain protocol/port. If this is an HTTP connection only, then it's best to have your pool member configured with port 80.
Here's an example sanitized config of one of our virtual servers taking IPv6 and converting to IPv4 on the back end:
ltm virtual www.company.com {
destination 2600:1000:0::1.http
ip-protocol tcp
pool www.company.com_pool
profiles {
http { }
tcp { }
}
source-address-translation {
type automap
}
vs-index 668
}
And the pool:
ltm pool www.company.com_pool {
members {
10.1.1.1:http {
address 10.1.1.1
session user-disabled
state down
}
10.2.2.2:http {
address 10.2.2.2
session user-disabled
state up
}
10.3.3.3:http {
address 10.3.3.3
session monitor-enabled
state up
}
}
monitor http
}
Have you tried just using SNAT automap?
Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com