From: David Miller <davem@davemloft.net>
To: shemminger@vyatta.com
Cc: joakim.tjernlund@transmode.se, netdev@vger.kernel.org
Subject: Re: [PATCH net-next-2.6] ipv4: sysctl to block responding on down interface
Date: Wed, 30 Jun 2010 13:58:16 -0700 (PDT) [thread overview]
Message-ID: <20100630.135816.106800276.davem@davemloft.net> (raw)
In-Reply-To: <20100630135535.0e3a5ea1@nehalam>
From: Stephen Hemminger <shemminger@vyatta.com>
Date: Wed, 30 Jun 2010 13:55:35 -0700
>> The fact that the syctl knob, when enabled, can't even function properly
>> in this "multiple interfaces with same address" case is another reason I
>> have decided to not apply this.
>
> We already have sysctl knobs that exist to work around broken printer TCP,
> middleboxes and other broken stacks; my opinion this is just another one
> of those types of workarounds.
But that sysctl knob for the printer workaround doesn't break legitimate
configurations like this one does.
next prev parent reply other threads:[~2010-06-30 20:58 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-11 12:24 Weak host model vs .interface down Joakim Tjernlund
2010-06-11 15:48 ` [PATCH net-next-2.6] ipv4: sysctl to block responding on down interface Stephen Hemminger
2010-06-22 17:15 ` David Miller
2010-06-30 20:55 ` Stephen Hemminger
2010-06-30 20:58 ` David Miller [this message]
2010-06-28 19:03 ` Joakim Tjernlund
2010-06-28 19:42 ` Eric Dumazet
2010-06-28 21:09 ` Joakim Tjernlund
2010-06-28 21:28 ` Mitchell Erblich
2010-06-28 21:58 ` Joakim Tjernlund
2010-06-28 21:57 ` David Miller
2010-06-28 23:30 ` Joakim Tjernlund
2010-06-29 3:01 ` David Miller
2010-07-01 11:23 ` Andi Kleen
2010-07-01 11:48 ` Joakim Tjernlund
2010-06-11 16:32 ` Weak host model vs .interface down Rick Jones
2010-06-11 17:06 ` Joakim Tjernlund
2010-06-11 17:13 ` Rick Jones
2010-06-11 19:41 ` Joakim Tjernlund
2010-06-11 23:57 ` Mark Smith
2010-06-12 9:34 ` Joakim Tjernlund
2010-06-11 19:50 ` Mitchell Erblich
2010-06-11 20:46 ` Joakim Tjernlund
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=20100630.135816.106800276.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=joakim.tjernlund@transmode.se \
--cc=netdev@vger.kernel.org \
--cc=shemminger@vyatta.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).