netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Erik Auerswald <auerswal@unix-ag.uni-kl.de>
To: Julian Anastasov <ja@ssi.bg>
Cc: Grant Taylor <gtaylor@tnetconsulting.net>,
	Akshat Kakkar <akshat.1984@gmail.com>,
	netdev <netdev@vger.kernel.org>,
	cronolog+lartc <cronolog+lartc@googlemail.com>,
	lartc <lartc@vger.kernel.org>
Subject: Re: Route fallback issue
Date: Sun, 24 Jun 2018 15:45:24 +0200	[thread overview]
Message-ID: <20180624134524.GA9925@unix-ag.uni-kl.de> (raw)
In-Reply-To: <alpine.LFD.2.20.1806212218070.2159@ja.home.ssi.bg>

Hello Julien,

On Thu, Jun 21, 2018 at 10:57:14PM +0300, Julian Anastasov wrote:
> On Wed, 20 Jun 2018, Grant Taylor wrote:
> > On 06/20/2018 01:00 PM, Julian Anastasov wrote:
> > > You can also try alternative routes.
> > 
> > "Alternative routes"?  I can't say as I've heard that description as a
> > specific technique / feature / capability before.
> > 
> > Is that it's official name?
> 
> 	I think so
> 
> > Where can I find out more about it?
> 
> 	You can search on net. I have some old docs on
> these issues, they should be actual:
> 
> http://ja.ssi.bg/dgd-usage.txt

Thanks for that info!

Can you tell us what parts from the above text is actually implemented
in the upstream Linux kernel, and starting with which version(s)
(approximately)? The text describes ideas and patches from nearly two
decades ago, is more recent documentation available somewhere?

Thanks,
Erik
-- 
In the beginning, there was static routing.
                        -- RFC 1118

  parent reply	other threads:[~2018-06-24 13:56 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAA5aLPhszyo1HBK8gOYZC35fuy_LW8Xw1CT_nob+CuZ0wf33zw@mail.gmail.com>
     [not found] ` <10767cab-7a21-faaf-e49e-4752c28d28b7@googlemail.com>
     [not found]   ` <20180620081916.GA30608@unix-ag.uni-kl.de>
2018-06-20  8:26     ` Route fallback issue Akshat Kakkar
2018-06-20 13:48       ` David Ahern
2018-06-20 15:18         ` Grant Taylor
2018-06-20 15:38           ` Grant Taylor
2018-06-20 19:00       ` Julian Anastasov
2018-06-21  5:13         ` Grant Taylor
2018-06-21 19:57           ` Julian Anastasov
2018-06-21 21:08             ` Grant Taylor
2018-06-25 18:50               ` Julian Anastasov
2018-06-25 20:07                 ` Grant Taylor
2018-06-24 13:45             ` Erik Auerswald [this message]
2018-06-25 19:02               ` Julian Anastasov

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=20180624134524.GA9925@unix-ag.uni-kl.de \
    --to=auerswal@unix-ag.uni-kl.de \
    --cc=akshat.1984@gmail.com \
    --cc=cronolog+lartc@googlemail.com \
    --cc=gtaylor@tnetconsulting.net \
    --cc=ja@ssi.bg \
    --cc=lartc@vger.kernel.org \
    --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).