From: Rogerio Brito rbrito@iname.com
To: lartc@vger.kernel.org
Subject: Preventing ICMP Redirects? (was: Re: [LARTC] HTTP only works on second try from doublely NAT'ed wi
Date: Sun, 11 Feb 2001 04:36:43 +0000 [thread overview]
Message-ID: <marc-lartc-98373940417007@msgid-missing> (raw)
<PRE>On Feb 10 2001, bert hubert wrote:
><i> You can, I think, but you need to be very sure that your NAT machine
</I>><i> isn't sending out any ICMP Redirects.
</I>
I've been bitten by these ICMP Redirects once. Is there any
way to prevent them from being sent out? Perhaps doing some
packet filtering of the ICMP Redirects? Even if this works,
this sure sounds like a dirty solution... :-(
In that occasion, I was trying to set up a masquerading box
with only one NIC and two IP addresses (the Internet-valid one
and the private one), hooking everything in a single hub and
routing accordingly.
I don't remember the details (since this was many months ago),
but the only solution that I could make work was to buy
another NIC for the masquerading box and put one IP in each
NIC, doing everything as usual. :-(
As I don't remember more details of the situation, I'm just
hoping that this description rings a bell for someone. Any
explanation of how to make this setup with just one NIC or
comments on why this shouldn't be done are immensely
appreciated.
Thanks in advance, Roger...
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- 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>
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
</PRE>
next reply other threads:[~2001-02-11 4:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-11 4:36 Rogerio [this message]
2001-02-15 4:44 ` Preventing ICMP Redirects? (was: Re: [LARTC] HTTP only Dan
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-98373940417007@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.