From: Patrick McHardy <kaber@trash.net>
To: "Damien Thébault" <damien.thebault@gmail.com>
Cc: linux-net@vger.kernel.org, netfilter-devel@vger.kernel.org,
"David S. Miller" <davem@davemloft.net>
Subject: Re: conntrack doesn't always work when a bridge is used
Date: Thu, 20 Dec 2007 11:06:11 +0100 [thread overview]
Message-ID: <476A3E93.3010400@trash.net> (raw)
In-Reply-To: <9a4a382a0712200030w5502c312k33b330e03e0e8555@mail.gmail.com>
Damien Thébault wrote:
> On Dec 19, 2007 8:03 PM, Patrick McHardy <kaber@trash.net> wrote:
>> Could you capture the conntrack events of the non-working
>> case with (run in parallel):
>>
>> conntrack -E
>> conntrack -E expect
>>
>
> Sure, here it is :
That actually looks like it works properly.
New control connection:
> [NEW] tcp 6 120 SYN_SENT src=192.168.1.5 dst=192.168.2.250
> sport=45090 dport=21 [UNREPLIED] src=192.168.2.50 dst=192.168.2.70
> sport=21 dport=45090
> [UPDATE] tcp 6 60 SYN_RECV src=192.168.1.5 dst=192.168.2.250
> sport=45090 dport=21 src=192.168.2.50 dst=192.168.2.70 sport=21
> dport=45090
> [UPDATE] tcp 6 432000 ESTABLISHED src=192.168.1.5
> dst=192.168.2.250 sport=45090 dport=21 src=192.168.2.50
> dst=192.168.2.70 sport=21 dport=45090 [ASSURED]
New expectation for data connection:
> conntrack -E expect :
>
> 300 proto=6 src=192.168.2.50 dst=192.168.2.70 sport=0 dport=33344
New data connection machting expectation, both source and
destination properly NATed:
> [NEW] tcp 6 120 SYN_SENT src=192.168.2.50 dst=192.168.2.70
> sport=20 dport=33344 [UNREPLIED] src=192.168.1.5 dst=192.168.2.250
> sport=33344 dport=20
> [UPDATE] tcp 6 60 SYN_RECV src=192.168.2.50 dst=192.168.2.70
> sport=20 dport=33344 src=192.168.1.5 dst=192.168.2.250 sport=33344
> dport=20
> [UPDATE] tcp 6 432000 ESTABLISHED src=192.168.2.50
> dst=192.168.2.70 sport=20 dport=33344 src=192.168.1.5
> dst=192.168.2.250 sport=33344 dport=20 [ASSURED]
> [UPDATE] tcp 6 120 FIN_WAIT src=192.168.2.50 dst=192.168.2.70
> sport=20 dport=33344 src=192.168.1.5 dst=192.168.2.250 sport=33344
> dport=20 [ASSURED]
> [UPDATE] tcp 6 60 CLOSE_WAIT src=192.168.2.50 dst=192.168.2.70
> sport=20 dport=33344 src=192.168.1.5 dst=192.168.2.250 sport=33344
> dport=20 [ASSURED]
> [UPDATE] tcp 6 10 CLOSE src=192.168.2.50 dst=192.168.2.70
> sport=20 dport=33344 src=192.168.1.5 dst=192.168.2.250 sport=33344
> dport=20 [ASSURED]
Data connection closed
> [UPDATE] tcp 6 120 FIN_WAIT src=192.168.1.5 dst=192.168.2.250
> sport=45090 dport=21 src=192.168.2.50 dst=192.168.2.70 sport=21
> dport=45090 [ASSURED]
> [UPDATE] tcp 6 60 CLOSE_WAIT src=192.168.1.5 dst=192.168.2.250
> sport=45090 dport=21 src=192.168.2.50 dst=192.168.2.70 sport=21
> dport=45090 [ASSURED]
> [UPDATE] tcp 6 30 LAST_ACK src=192.168.1.5 dst=192.168.2.250
> sport=45090 dport=21 src=192.168.2.50 dst=192.168.2.70 sport=21
> dport=45090 [ASSURED]
> [UPDATE] tcp 6 120 TIME_WAIT src=192.168.1.5 dst=192.168.2.250
> sport=45090 dport=21 src=192.168.2.50 dst=192.168.2.70 sport=21
> dport=45090 [ASSURED]
> [UPDATE] tcp 6 10 CLOSE src=192.168.1.5 dst=192.168.2.250
> sport=45090 dport=21 src=192.168.2.50 dst=192.168.2.70 sport=21
> dport=45090 [ASSURED]
Control connection closed
> [DESTROY] tcp 6 src=192.168.2.50 dst=192.168.2.70 sport=20
> dport=33344 packets=4 bytes=559 src=192.168.1.5 dst=192.168.2.250
> sport=33344 dport=20 packets=4 bytes=216
> [DESTROY] tcp 6 src=192.168.1.5 dst=192.168.2.250 sport=45090
> dport=21 packets=17 bytes=916 src=192.168.2.50 dst=192.168.2.70
> sport=21 dport=45090 packets=12 bytes=1162
Both connections destroyed
-
To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2007-12-20 10:06 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <9a4a382a0712180648i7fc958edt6f0d9db83f574c77@mail.gmail.com>
2007-12-19 17:00 ` conntrack doesn't always work when a bridge is used Damien Thébault
2007-12-19 19:03 ` Patrick McHardy
2007-12-20 8:30 ` Damien Thébault
2007-12-20 10:06 ` Patrick McHardy [this message]
2007-12-20 11:06 ` Damien Thébault
2007-12-20 11:07 ` Patrick McHardy
2007-12-20 11:20 ` Damien Thébault
2007-12-20 11:25 ` Patrick McHardy
2007-12-20 13:21 ` Damien Thébault
2007-12-20 16:08 ` Damien Thébault
2007-12-22 7:56 ` Patrick McHardy
2007-12-26 9:54 ` Damien Thébault
2007-12-30 17:53 ` Patrick McHardy
[not found] ` <9a4a382a0801020118n4166e505l5eb84a9f07f620be@mail.gmail.com>
2008-01-11 8:10 ` Damien Thébault
2008-01-11 12:24 ` Patrick McHardy
2008-01-11 12:53 ` Damien Thébault
2008-01-11 12:57 ` Patrick McHardy
2008-01-11 13:25 ` Patrick McHardy
2008-01-11 15:16 ` Damien Thébault
2008-01-11 17:33 ` Patrick McHardy
2007-12-28 14:39 ` Damien Thébault
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=476A3E93.3010400@trash.net \
--to=kaber@trash.net \
--cc=damien.thebault@gmail.com \
--cc=davem@davemloft.net \
--cc=linux-net@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
/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).