From: Jarek Poplawski <jarkao2@gmail.com>
To: Ben Gamari <bgamari@gmail.com>
Cc: Mike Caoco <caoco2002@yahoo.com>,
Stephen Hemminger <shemminger@vyatta.com>,
Netdev <netdev@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: Unplug ethernet cable, the route persists. Why?
Date: Thu, 25 Nov 2010 23:18:35 +0100 [thread overview]
Message-ID: <4CEEE0BB.6020509@gmail.com> (raw)
In-Reply-To: <87bp5df9j9.fsf@gmail.com>
Ben Gamari wrote:
> On Wed, 24 Nov 2010 12:29:43 -0800 (PST), Mike Caoco <caoco2002@yahoo.com> wrote:
>> So if you rely on NetworkManager or Connman or Quagga to remove the
>> route, the routing daemons will recompute the route table anyway. So
>> why cannot this be done in the kernel?
>
> This is policy. In the Linux world we generally strive to separate
> policy from mechanism, leaving the former to userspace. This allows
> (potentially complex) policy decisions to be made in user-space. The
> reason for this is two-fold: First, every line of kernel code introduces
> the potentially for a bug and error handling in the kernel is generally
> more complex than it is in user-space. Secondly, allowing user-space to
> handle policy allows users to do things with the kernel that kernel
> developers did not envision. This flexibility is one reason why the
> kernel is so suited for running on anything from your cell-phone to 4000
> processor big iron.
Secondly and a half, if you add a specific route you may really
mean it, and prefer not to send at all than use default.
Cheers,
Jarek P.
next prev parent reply other threads:[~2010-11-25 22:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-24 19:48 Unplug ethernet cable, the route persists. Why? Mike Caoco
2010-11-24 20:18 ` Stephen Hemminger
2010-11-24 20:29 ` Mike Caoco
2010-11-24 20:44 ` David Miller
2010-11-25 20:11 ` Ben Gamari
2010-11-25 22:18 ` Jarek Poplawski [this message]
2010-11-25 19:10 ` Hans de Bruin
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=4CEEE0BB.6020509@gmail.com \
--to=jarkao2@gmail.com \
--cc=bgamari@gmail.com \
--cc=caoco2002@yahoo.com \
--cc=linux-kernel@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.