Ilo Lorusso a écrit : > Yes I can see the traffic coming back when I do a tcpdump... > > you can see 172.69.128.107 access 74.125.79.104.http and then > 74.125.79.104.http talks back to 172.69.128.107 , > now this is encapsulated in a GRE tunnel as my alt interface is a GRE > tunnel but it works for the local box.. as per my previous post a > couple days ago... > > below is the sample of the tcpdump, > > 18:26:21.722567 IP 172.69.128.98 > 57.24.98.42: GREv0, length 52: IP > 172.69.128.107.elatelink > 74.125.79.104.http: Flags [S], seq > 224859509, win 65535, options [mss 1460,nop,nop,sackOK], length 0 > 18:26:21.982269 IP 57.24.98.42 > 172.69.128.98: GREv0, length 52: IP > 74.125.79.104.http > 172.69.128.107.elatelink: Flags [S.], seq > 192453115, ack 224859510, win 5720, options [mss 1380,nop,nop,sackOK], > length 0 > 18:26:21.982316 IP 172.69.128.98 > 57.24.98.42: GREv0, length 52: IP > 74.125.79.104.http > 172.69.128.107.elatelink: Flags [S.], seq > 192453115, ack 224859510, win 5720, options [mss 1380,nop,nop,sackOK], > length 0 This is the same SYN/ACK segment that was just received, encapsulated and sent again and received again and sent again... Looks like you have a loop. Check your routing rules. -- To unsubscribe from this list: send the line "unsubscribe netfilter" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
