From: Dax Kelson <Dax@GuruLabs.com>
To: netdev@oss.sgi.com
Subject: echo 0 > send_redirects broken?
Date: Thu, 04 Sep 2003 15:04:02 -0600 [thread overview]
Message-ID: <1062709441.2884.34.camel@mentor.gurulabs.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 738 bytes --]
192.168.0.0/24
.9 .10 .254
==|======|=======|====
[A] [B] [Router]
Hosts A and B running RHL9 with kernel 2.4.20-8.
1. Start pinging the .254 IP from host A
2. Enable ip_forwarding on host B
3. Run arpspoof on host B to poison the arp cache on host A and the
router
4. On host B Turn off icmp redirects with the command:
echo 0 > /proc/sys/net/ipv4/conf/eth0/send_redirects
Problem: Host B *still* sends ICMP redirects. Initially many redirects
are sent, then the rate at which ICMP redirects are sent slows down
until redirects only trickle out every few minutes.
In older 2.4 kernels (2.4.9 for example) this did not happen. Turning
off ICMP redirects really turned them off.
Comments?
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
reply other threads:[~2003-09-04 21:04 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1062709441.2884.34.camel@mentor.gurulabs.com \
--to=dax@gurulabs.com \
--cc=netdev@oss.sgi.com \
/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;
as well as URLs for NNTP newsgroup(s).