Source Port Mangled down OSPF Tunnel

Hi Nom,

Did you actually find a solution to this. I have almost the same issue, that is, the source port in DNS reply is changed from 53 to something else as it passes through the F5. The weird part is that i cannot see that packet leaving the internal vlan via tcpdump but the packet shows up in the server's tcpdump (mis-ported). The server drops that packet and is not getting built (since DNS replies are getting mangled as they pass through F5). I have tried the "autolast hop" feature but that didn't work out.

PS: Our deployment has an active/standby viprion pair and two Juniper routers in full-mesh OSPF for link redundancy. There is no routing internally, all done using floating-IP.

Would greatly appreciate any help. Has been driving me nuts for a week now.

Thanks!