All of lore.kernel.org
 help / color / mirror / Atom feed
From: Julian Anastasov <ja@ssi.bg>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] modifying ethernet header dst mac with ebtables?
Date: Sat, 05 Apr 2003 00:27:07 +0000	[thread overview]
Message-ID: <marc-lartc-104953116029889@msgid-missing> (raw)
In-Reply-To: <marc-lartc-104947553719906@msgid-missing>


	Hello,

On Fri, 4 Apr 2003, Martin A. Brown wrote:

>  : I´m working in a briding enviroment and i want to be sure that my arp
>  : requests outgoing a bridge interface will be hear by only one specific
>  : device (because of security reason)

	Victor, what about trying something similar to the example
in the ebtables docs:

ebtables -t nat -A PREROUTING -d ff:ff:ff:ff:ff:ff -i eth0 -j dnat --to-destination 54:44:33:22:11:00

>  : are there any way to re-write the ff:ff:ff:ff:ff:ff on this arp request
>  : so they appears like a unicast?
>
> I imagine that Julian will jump in here and reply to you, but I thought
> I'd point you to ip arp, an add-on tool Julian has written for iproute2.
>
>   http://www.ssi.bg/~ja/#iparp

	iparp can not see these packets (layer 2) but for other
purposes probes can be originated with unicast dst MAC in this way:

ip arp add table output to 1.2.3.4 lldst 00:11:22:33:44:55

>  : Do de ip stack understand this "unicast" arp request?

	Yes but at MAC level the ARP code cares only for
unicast/broadcast, no matter the actual dst MAC of the received
packet.

Regards

--
Julian Anastasov <ja@ssi.bg>

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

  parent reply	other threads:[~2003-04-05  0:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-04 16:56 [LARTC] modifying ethernet header dst mac with ebtables? Victor Cassar
2003-04-04 17:08 ` Martin A. Brown
2003-04-05  0:27 ` Julian Anastasov [this message]
2003-04-08 20:13 ` Victor Cassar

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-104953116029889@msgid-missing \
    --to=ja@ssi.bg \
    --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 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.