From: Pascal Hambourg <pascal.mail@plouf.fr.eu.org>
To: Ilo Lorusso <sneak147@gmail.com>
Cc: netfilter@vger.kernel.org
Subject: Re: port based routing - help with tcpdump
Date: Tue, 09 Nov 2010 20:43:09 +0100 [thread overview]
Message-ID: <4CD9A44D.80504@plouf.fr.eu.org> (raw)
In-Reply-To: <AANLkTikTJqQj7ARSbr4XrK6oUwQiZDQmQjBUuSR6u3yG@mail.gmail.com>
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.
prev parent reply other threads:[~2010-11-09 19:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-08 9:51 port based routing - help with tcpdump Ilo Lorusso
2010-11-08 10:14 ` Pascal Hambourg
[not found] ` <AANLkTimeCfv9i13L9PFpOxTRbzG4c4Qpa7XO5quK2CEY@mail.gmail.com>
2010-11-09 13:19 ` Ilo Lorusso
2010-11-09 16:05 ` Pascal Hambourg
2010-11-09 16:34 ` Ilo Lorusso
2010-11-09 19:43 ` Pascal Hambourg [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4CD9A44D.80504@plouf.fr.eu.org \
--to=pascal.mail@plouf.fr.eu.org \
--cc=netfilter@vger.kernel.org \
--cc=sneak147@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).