From: David Miller <davem@davemloft.net>
To: greearb@candelatech.com
Cc: netdev@vger.kernel.org, kaber@trash.net
Subject: Re: Missing device binding relating to tcp_v4_send_reset?
Date: Tue, 10 Aug 2010 01:48:46 -0700 (PDT) [thread overview]
Message-ID: <20100810.014846.258126767.davem@davemloft.net> (raw)
In-Reply-To: <4C603EF2.9010902@candelatech.com>
From: Ben Greear <greearb@candelatech.com>
Date: Mon, 09 Aug 2010 10:46:26 -0700
> This snippet is from some patches Patrick did for me some time
> back. I think the rest of his work has been merged upstream, but
> this patch was not. I'm honestly not sure if it's needed or not,
> but we've been running with it for at least a year or so and it's
> been working fine for us.
There is no reason at all to force a reply to a packet to
go out of the same interface as the packet which triggered
that reply arrived upon.
next prev parent reply other threads:[~2010-08-10 8:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-09 17:46 Missing device binding relating to tcp_v4_send_reset? Ben Greear
2010-08-10 8:48 ` David Miller [this message]
2010-08-10 14:22 ` Ben Greear
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=20100810.014846.258126767.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=greearb@candelatech.com \
--cc=kaber@trash.net \
--cc=netdev@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).