Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: "Aron Brand" <Aron@sofaware.com>
To: lartc@vger.kernel.org
Subject: RE: [LARTC] RE: LARTC digest, Vol 1 #1558 - 9 msgs
Date: Tue, 27 Jan 2004 12:02:19 +0000	[thread overview]
Message-ID: <50F73B338A7FD943B7937BBCF99BFBDE33B0FF@mail.sofaware.com> (raw)
In-Reply-To: <50F73B338A7FD943B7937BBCF99BFBDE33B0D5@mail.sofaware.com>

I agree, but this is still better than crashing the machine...

Aron 

-----Original Message-----
From: Michael Renzmann [mailto:mrenzmann@otaku42.de] 
Sent: Tuesday, January 27, 2004 1:33 PM
To: Aron Brand
Cc: lartc@mailman.ds9a.nl; roy@xxx.lt
Subject: Re: [LARTC] RE: LARTC digest, Vol 1 #1558 - 9 msgs

Hi.

Aron Brand wrote:
> does this. Another option would be to trick the kernel that the packet

> has been transmitted, to prevent the immediate retries, while actually

> vanishing the packet.

I'm also no pro in this area, but I think this would be a bad idea. I
guess this would have impact on the interface's statistics about sent,
received and dropped packets, making it hard to look for network
configuration errors and similar things.

Bye, Mike


_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

  parent reply	other threads:[~2004-01-27 12:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-27  9:30 [LARTC] RE: LARTC digest, Vol 1 #1558 - 9 msgs Aron Brand
2004-01-27 11:32 ` Michael Renzmann
2004-01-27 12:02 ` Aron Brand [this message]
2004-01-27 12:09 ` Michael Renzmann
2004-01-28  4:57 ` Roy

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=50F73B338A7FD943B7937BBCF99BFBDE33B0FF@mail.sofaware.com \
    --to=aron@sofaware.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