From: Sam.Bingner@hickam.af.mil
To: cfriesen@nortelnetworks.com, sampsa@netsonic.fi
Cc: linux-kernel@vger.kernel.org, linux-net@vger.kernel.org
Subject: RE: ARP responses broken!
Date: Tue, 17 Apr 2001 08:25:21 -1000 [thread overview]
Message-ID: <3adc8a91.db.0@hawaii.rr.com> (raw)
Correction, that was on kernel v2.2.19
Sam
****** Forwarded Message Follows *******
>To: "'Christopher Friesen'" <cfriesen@nortelnetworks.com>, Sampsa Ranta
<sampsa@netsonic.fi>
>From: "Bingner Sam J. Contractor RSIS" <Sam.Bingner@hickam.af.mil>
>Date: Tue, 17 Apr 2001 18:07:41 -0000
>
>I tested this with kernel version 2.2.18 and arp_filter appeared to be
>broken... I enabled it for /proc/sys/net/ipv4/conf/all/arp_filter,
>/proc/sys/net/ipv4/conf/eth0/arp_filter and
>/proc/sys/net/ipv4/conf/eth1/arp_filter and it did not change the arp
>behavior at all. I enabled hidden and it worked, is there a know problem
>with this functionality?
>
> Sam Bingner
> PACAF CSS/SCHE
> Contractor RSIS
> DSN 315 449-7889
> COMM 808 449-7889
>
next reply other threads:[~2001-04-17 18:30 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-17 18:25 Sam.Bingner [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-04-18 1:05 ARP responses broken! Julian Anastasov
2001-04-18 22:02 ` Sampsa Ranta
2001-04-19 1:46 ` Julian Anastasov
2001-04-17 18:07 Bingner Sam J. Contractor RSIS
[not found] <E14pWQ2-0005LM-00@calista.inka.de>
2001-04-17 14:31 ` Bernd Eckenfels
[not found] <4CDA8A6D03EFD411A1D300D0B7E83E8F6972AC@FSKNMD07.hickam.af.mil>
2001-04-17 13:56 ` Eric Weigle
2001-04-16 21:26 Eric Weigle
2001-04-17 14:19 ` Andi Kleen
2001-04-17 14:53 ` Martin Josefsson
2001-04-17 15:01 ` Andi Kleen
2001-04-17 15:07 ` Martin Josefsson
2001-04-17 16:05 ` Alan Cox
2001-04-17 21:43 ` Rogier Wolff
2001-04-16 20:49 Sampsa Ranta
2001-04-16 22:47 ` Bernd Eckenfels
2001-04-17 14:24 ` Christopher Friesen
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=3adc8a91.db.0@hawaii.rr.com \
--to=sam.bingner@hickam.af.mil \
--cc=cfriesen@nortelnetworks.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@vger.kernel.org \
--cc=sampsa@netsonic.fi \
/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.