Forum Discussion
Heidi_35827
Aug 03, 2012Nimbostratus
Thanks for the feedback.
We believe this is more likely a arp/routing issue. But still strange. Why can the browser packet get there, but not the cURL?
This is what the infrastructure looks like:
client ---------- router ---------------- firewall ------------ F5 ----------- servers
Tcpdump from client shows with his cURL - ack, syn-ack, ack, HTTP GET....wait.....retransmit HTTP GET
On a capture at the firewall, we see - ack, syn-ack, ack.
The HTTP GET never gets there.
But why? From the same laptop we can send the same HTTP request with a browser, and it makes it there and back. Somewhere the cURL HTTP is gets lost. And how does ACK get there and HTTP can't? The routing looks good from his subnet to DMZ, I traced it hop by hop. We would have many more issues if that were broken.
MAC/ARP issue possibly? But how would the browser call ever work if that were the case??