All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Humme <jan.humme@xs4all.nl>
To: Ramin Alidousti <ramin@cannon.eng.us.uu.net>,
	Jan Humme <jan.humme@xs4all.nl>
Cc: netfilter@lists.samba.org
Subject: Re: icmp redirect
Date: Wed, 10 Jul 2002 19:48:43 +0200	[thread overview]
Message-ID: <0207101948430B.04513@Lms> (raw)
In-Reply-To: <20020710173930.GD25368@cannon.eng.us.uu.net>

On Wednesday 10 July 2002 19:39, Ramin Alidousti wrote:
> On Wed, Jul 10, 2002 at 07:11:21PM +0200, Jan Humme wrote:
> > I am developing an application that will eventually run on a PC with two
> > ethernet cards; unfortunately the development PC that I use has only one
> > ethernet card (eth0) and no available slots (except for one that I need
> > for another purpose).
> >
> > Doesn't matter, during the development I can have both applications use
> > eth0 instead, if I can only stop the icmp redirect messages that the
> > kernel sends back to the source, whenever it finds out that it is
> > forwarding a packet via the same eth0 interface on which it came in.
> >
> > Of course, I can choke the icmp redirect message using iptables, but is
> > there a better (proper) way, to prevent the message from being generated?
>
> On the sending host:
> # echo 0 > /proc/sys/net/ipv4/conf/*/send_redirects
>
> On the receiving host:
> # echo 0 > /proc/sys/net/ipv4/conf/*/accept_redirects
>
> should do it.

Thanks a lot; I knew there was an elegant way :-) !

Jan Humme.


  reply	other threads:[~2002-07-10 17:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-10 17:11 icmp redirect Jan Humme
2002-07-10 17:39 ` Ramin Alidousti
2002-07-10 17:48   ` Jan Humme [this message]
2002-07-10 17:46 ` Antony Stone
2002-07-10 18:31   ` Jan Humme
  -- strict thread matches above, loose matches on Subject: below --
2005-03-18 15:29 ICMP REDIRECT vardhaman.m
2006-05-07  7:19 ICMP Redirect R. Rajasekaran
2006-05-09 12:25 ` Cedric Blancher

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=0207101948430B.04513@Lms \
    --to=jan.humme@xs4all.nl \
    --cc=netfilter@lists.samba.org \
    --cc=ramin@cannon.eng.us.uu.net \
    /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.