Forum Discussion
OK, I see the issue, the VS on the internal network needs to be 0.0.0.0:0, not 172.16.88.224:0. Remember the VS is the destination, not the source.
Unfortunately, that doesn't seem to work either. The result is the same.
As an additional datapoint, here's what it looks like if I try to ping or SSH from my workstation to a server behind the F5:
[user@f5lb-1:Active] ~ tcpdump -i Adobe_Connect -n host 128.6.210.75
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on Adobe_Connect, link-type EN10MB (Ethernet), capture size 96 bytes
14:38:03.654655 IP 172.16.88.227 > 128.6.210.75: ICMP echo reply, id 52897, seq 0, length 64
14:38:04.655426 IP 172.16.88.227 > 128.6.210.75: ICMP echo reply, id 52897, seq 1, length 64
14:38:05.656156 IP 172.16.88.227 > 128.6.210.75: ICMP echo reply, id 52897, seq 2, length 64
14:38:06.657307 IP 172.16.88.227 > 128.6.210.75: ICMP echo reply, id 52897, seq 3, length 64
14:38:07.658310 IP 172.16.88.227 > 128.6.210.75: ICMP echo reply, id 52897, seq 4, length 64
14:38:08.659407 IP 172.16.88.227 > 128.6.210.75: ICMP echo reply, id 52897, seq 5, length 64
14:38:09.660519 IP 172.16.88.227 > 128.6.210.75: ICMP echo reply, id 52897, seq 6, length 64
14:38:14.462946 IP 172.16.88.227.ssh > 128.6.210.75.49178: R 0:0(0) ack 3909000084 win 0
14:38:15.468394 IP 172.16.88.227.ssh > 128.6.210.75.49178: R 0:0(0) ack 1 win 0
14:38:16.573520 IP 172.16.88.227.ssh > 128.6.210.75.49178: R 0:0(0) ack 1 win 0
14:38:17.674576 IP 172.16.88.227.ssh > 128.6.210.75.49178: R 0:0(0) ack 1 win 0
14:38:18.777940 IP 172.16.88.227.ssh > 128.6.210.75.49178: R 0:0(0) ack 1 win 0
14:38:19.885833 IP 172.16.88.227.ssh > 128.6.210.75.49178: R 0:0(0) ack 1 win 0
^C
13 packets captured
13 packets received by filter
0 packets dropped by kernel
So, obviously, the server is receiving the initial packets and trying to respond. The External interface, however, shows nothing being sent out; neither does the switch it is connected to, for that matter. Just for testing, I also setup packet filtering rules; the logs indicate that packets in both directions (from my workstation to the server, and vice-versa) are being accepted, not dropped. So there's something between the transition from Adobe_Connect to External that's getting dropped somewhere, it appears. Do I need to add a specific route or something similar to that network, to direct it out the External interface?