From: gypsy <gypsy@iswest.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] tc rules and DGD patches
Date: Thu, 27 Oct 2005 15:31:02 +0000 [thread overview]
Message-ID: <4360F2B6.3C26FC18@iswest.com> (raw)
In-Reply-To: <20051027110249.12005.qmail@web8401.mail.in.yahoo.com>
Yogesh Hasabnis wrote:
>
> Hi All,
>
> I have one query which may be quite silly. My Linux
> internet gateway has Dead Gateway Detetction patches
> applied to it's kernel. If I am right, the DGD patches
> allow us to add static routes which are not destroyed
> even if the interface or the link goes down. I want to
> know whether, with the DGD patches applied, the
> traffic shaping rules defined using tc, added to an
> interface remain intact when a link/interface goes
> down (and comes up some time later) ?
>
> Thanks
>
> Yogesh
Yes, they remain intact. In fact, you can create rules for an interface
that does not even exist.
--
Gypsy
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
prev parent reply other threads:[~2005-10-27 15:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-27 11:02 [LARTC] tc rules and DGD patches Yogesh Hasabnis
2005-10-27 15:31 ` gypsy [this message]
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=4360F2B6.3C26FC18@iswest.com \
--to=gypsy@iswest.com \
--cc=lartc@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