weizen_42 wrote:
Use tcpdump and wireshark to follow the packets.
I ran tcpdump and it showed me the result listed below:
Code:
21:45:20.502324 ARP, Request who-has 10.1.0.2 tell 10.1.0.1, length 28
21:45:20.502482 ARP, Reply 10.1.0.2 is-at 00:1b:21:4d:40:0d, length 46
21:45:20.502491 IP 123.123.123.123.50326 > 10.1.0.2.80: Flags [S], seq 4202633727, win 65535, options [mss 1460,nop,wscale 3,nop,nop,TS val 900930635 ecr 0,sackOK,eol], length 0
21:45:21.520654 IP 123.123.123.123.50326 > 10.1.0.2.80: Flags [S], seq 4202633727, win 65535, options [mss 1460,nop,wscale 3,nop,nop,TS val 900931657 ecr 0,sackOK,eol], length 0
21:45:22.524947 IP 123.123.123.123.50326 > 10.1.0.2.80: Flags [S], seq 4202633727, win 65535, options [mss 1460,nop,wscale 3,nop,nop,TS val 900932658 ecr 0,sackOK,eol], length 0
21:45:23.530630 IP 123.123.123.123.50326 > 10.1.0.2.80: Flags [S], seq 4202633727, win 65535, options [mss 1460,nop,wscale 3,nop,nop,TS val 900933658 ecr 0,sackOK,eol], length 0
21:45:24.634612 IP 123.123.123.123.50326 > 10.1.0.2.80: Flags [S], seq 4202633727, win 65535, options [mss 1460,nop,wscale 3,nop,nop,TS val 900934747 ecr 0,sackOK,eol], length 0
21:45:25.737098 IP 123.123.123.123.50326 > 10.1.0.2.80: Flags [S], seq 4202633727, win 65535, options [mss 1460,nop,wscale 3,nop,nop,TS val 900935836 ecr 0,sackOK,eol], length 0
21:45:27.846572 IP 123.123.123.123.50326 > 10.1.0.2.80: Flags [S], seq 4202633727, win 65535, options [mss 1460,nop,wscale 3,nop,nop,TS val 900937934 ecr 0,sackOK,eol], length 0
21:45:32.358796 IP 123.123.123.123.50326 > 10.1.0.2.80: Flags [S], seq 4202633727, win 65535, options [mss 1460,sackOK,eol], length 0
21:45:40.871035 IP 123.123.123.123.50326 > 10.1.0.2.80: Flags [S], seq 4202633727, win 65535, options [mss 1460,sackOK,eol], length 0
21:45:56.955469 IP 123.123.123.123.50326 > 10.1.0.2.80: Flags [S], seq 4202633727, win 65535, options [mss 1460,sackOK,eol], length 0
21:45:57.524752 IP 10.1.0.2.138 > 10.1.0.255.138: UDP, length 229
21:45:57.524812 IP 10.1.0.2.138 > 10.1.0.255.138: UDP, length 206
21:46:01.952288 ARP, Request who-has 10.1.0.2 tell 10.1.0.1, length 28
21:46:01.952430 ARP, Reply 10.1.0.2 is-at 00:1b:21:4d:40:0d, length 46
It looks to me that the 10.1.0.2 server doesn't reply? I'm no networking "specialist" so I'm not sure whether my interpretation is right...
Any ideas? I had this working in an other setting where I used just iptables statements to redirect to this server (and that worked fine).