Forum Discussion
longnv
Cirrus
CirrusF5 Bigip LTM NAT64 config
Hi everybody,
I have a problem with VS using IPv6 and Pool, Node IPv4.
My config :
- VS type is Performance Layer 4;
- Source Address Translation: none
- Address Translation: enable
- Port Translation: enable
-NAT64: enable
With same Pool member for VS using ipv4 then VS working, but when I connection to VS ipv6 then have error : ERR_CONNECTION_REFUSED
Have any ideal for this problem? Thanks
This problem has resolved. TCP conection from F5 to internal over 64k connection, so a new tcp session is started with the same ports => tcp connection reset. Need SNAT with other self ip connection to internal.
mihaicMVP
If the logs/tcpdump don't offer any more info, than you probably need to open a ticket with F5.
I am curious what the issue is. So please share it.
longnvMy device has expired license support, so I can't open support case. 😞
If i can resolve this problem, I will share for you
- longnv
I tried create 2 VS diffirent are VS_IPv6_1 and VS_IPv6_2 with same pool P_p6435 but VS_IPv6_1 working and VS_IPv6_2 not work with message ERR_CONNECTION_REFUSED. I don't understand where the problem lies
ltm virtual VS_IPv6_1 {
destination xxxx:xxxx:xxx::77.https
ip-protocol tcp
pool P_p6435
profiles {
fastL4 { }
}
translate-address enabled
translate-port enabled
vs-index 1160
}ltm virtual VS_IPV6_2 {
destination xxxx:xxxx:xxx::11.https
ip-protocol tcp
pool P_p6435
profiles {
fastL4 { }
}
translate-address enabled
translate-port enabled
vs-index 808 - mihaic
Found this article.
https://support.f5.com/csp/article/K9279
It seems you don't need any special license. Also, you don't need SNAT.
