From: Bart De Schuymer <bdschuym@pandora.be>
To: pankaj jain <jainp1979@gmail.com>
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: ebtables v/s arptables
Date: Thu, 14 Jun 2007 18:16:44 +0200 [thread overview]
Message-ID: <1181837804.2972.16.camel@localhost.localdomain> (raw)
In-Reply-To: <d41814cf0706140125i52cef5a6u6e73ab3395290e35@mail.gmail.com>
Op do, 14-06-2007 te 13:55 +0530, schreef pankaj jain:
> Hi Bart,
> I am quite new to these concepts and tools,
> It would be great if you could please elaborate the statement and
> throw some light on arptables also.
> I believe for ebtables to work , we have to create a bridge interface also.
> without creating a bridge I was not able to respond to arp requests
> for IPs which are with me but are not plumbed on any interface.
That's correct. If you don't need a bridge (you're not forwarding based
on MAC addresses) you should probably not use one. It's possible to get
packets sent to ebtables on a device with only one network interface,
though. See http://ebtables.sourceforge.net/examples.html#ex_nobridge
> Does ip_forwarding have any impact on arptables and ebtables.
No.
cheers,
Bart
next prev parent reply other threads:[~2007-06-14 16:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-13 8:20 ebtables v/s arptables pankaj jain
[not found] ` <1181755998.2976.1.camel@localhost.localdomain>
2007-06-14 8:25 ` pankaj jain
2007-06-14 16:16 ` Bart De Schuymer [this message]
2007-06-15 5:21 ` pankaj jain
2007-06-15 6:35 ` Jan Engelhardt
2007-06-15 6:41 ` pankaj jain
2007-06-15 6:55 ` "C. Bergström"
2007-06-15 7:08 ` pankaj jain
2007-06-15 7:19 ` "C. Bergström"
2007-06-15 7:05 ` Jan Engelhardt
2007-06-18 12:17 ` pankaj jain
2007-06-18 12:25 ` Jan Engelhardt
[not found] ` <4678C3F1.5000804@plouf.fr.eu.org>
2007-06-20 11:26 ` pankaj jain
2007-06-20 14:33 ` Petr Pisar
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=1181837804.2972.16.camel@localhost.localdomain \
--to=bdschuym@pandora.be \
--cc=jainp1979@gmail.com \
--cc=netfilter-devel@lists.netfilter.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.