From: "Martin A. Brown" <mabrown-lartc@securepipe.com>
To: lartc@vger.kernel.org
Subject: Re: ARP Help (was - [LARTC] snooping - plan B)
Date: Thu, 31 Jul 2003 02:37:31 +0000 [thread overview]
Message-ID: <marc-lartc-105961912916454@msgid-missing> (raw)
In-Reply-To: <marc-lartc-105958098107343@msgid-missing>
Jim,
I must be uncommonly dense, because I still haven't a clue what you are
trying to do. I'll take one last stab at it, though.
: host0
: 192.168.253.1----snoopy(eth0 192.168.253.254)
:
: Now ping 192.168.253.2 and get snoopy to respond. This can be done
: with netfilter (but not, apparently with ip).
Accurate, as far as I know.
: iptables -A PREROUTING -t nat -p icmp -d 192.168.253.2 -j DNAT --to 192.168.253.254
Sure.
: /sbin/arp -i eth0 -Ds 192.168.253.2 eth0 pub
: gets you a "host unreachable" from 192.168.253.1
Have you tried this?
arp -s 192.168.253.2 -i eth0 -D eth0 pub
Sadly, /sbin/arp (at least on my test boxen) seems to be persnickety about
the order of arguments and options.
: BUT if on host0 you:
: /sbin/arp -s 192.168.253.2 HWADDR
:
: then ping goes through.
: Help from ARP experts (or others!) much appreciated.
If you really wish to get your hands dirty with ARP, you can always have
ultimate control with "ip arp", a kernel + iproute2 patch.
http://www.ssi.bg/~ja/#iparp
Bonne chance,
-Martin
--
Martin A. Brown --- SecurePipe, Inc. --- mabrown@securepipe.com
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2003-07-31 2:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-30 16:01 ARP Help (was - [LARTC] snooping - plan B) Jim Redman
2003-07-31 2:37 ` Martin A. Brown [this message]
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-105961912916454@msgid-missing \
--to=mabrown-lartc@securepipe.com \
--cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox