From: Suthep Vichiendilokkul vich0003@tc.umn.edu
To: lartc@vger.kernel.org
Subject: [LARTC] Re: Preventing ICMP Redirects?
Date: Tue, 13 Feb 2001 09:02:00 +0000 [thread overview]
Message-ID: <marc-lartc-98373940417013@msgid-missing> (raw)
<PRE>On Sun, Feb 11, 2001 at 02:36:43AM -0200, Rogerio Brito wrote:
><i> I've been bitten by these ICMP Redirects once. Is there any
</I>><i> way to prevent them from being sent out? Perhaps doing some
</I>
Hmmm. I never tried this before, but how about setting these kernel
variables to 0? (depending on what you want):
/proc/sys/net/ipv4/conf/<if>/accept_redirects
/proc/sys/net/ipv4/conf/<if>/send_redirects
Note that I'm using kernel 2.4. I'm not sure they are available in 2.2,
though.
Suthep
><i> packet filtering of the ICMP Redirects? Even if this works,
</I>><i> this sure sounds like a dirty solution... :-(
</I>><i>
</I>><i> In that occasion, I was trying to set up a masquerading box
</I>><i> with only one NIC and two IP addresses (the Internet-valid one
</I>><i> and the private one), hooking everything in a single hub and
</I>><i> routing accordingly.
</I>><i>
</I>><i> I don't remember the details (since this was many months ago),
</I>><i> but the only solution that I could make work was to buy
</I>><i> another NIC for the masquerading box and put one IP in each
</I>><i> NIC, doing everything as usual. :-(
</I>><i>
</I>><i> As I don't remember more details of the situation, I'm just
</I>><i> hoping that this description rings a bell for someone. Any
</I>><i> explanation of how to make this setup with just one NIC or
</I>><i> comments on why this shouldn't be done are immensely
</I>><i> appreciated.
</I>><i>
</I>><i>
</I>><i> Thanks in advance, Roger...
</I>><i>
</I>><i> --
</I>><i> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-</I>><i> Rogerio Brito - <A HREF="mailto:rbrito@iname.com">rbrito@iname.com</A> - <A HREF="http://www.ime.usp.br/~rbrito/">http://www.ime.usp.br/~rbrito/</A>
</I>><i> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-</I>><i>
</I>><i> _______________________________________________
</I>><i> LARTC mailing list / <A HREF="mailto:LARTC@mailman.ds9a.nl">LARTC@mailman.ds9a.nl</A>
</I>><i> <A HREF="http://mailman.ds9a.nl/mailman/listinfo/lartc">http://mailman.ds9a.nl/mailman/listinfo/lartc</A> HOWTO: <A HREF="http://ds9a.nl/2.4Routing/">http://ds9a.nl/2.4Routing/</A>
</I>
</PRE>
next reply other threads:[~2001-02-13 9:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-13 9:02 Suthep [this message]
2001-02-13 20:06 ` [LARTC] Re: Preventing ICMP Redirects? Rogerio
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=marc-lartc-98373940417013@msgid-missing \
--to=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 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.