From: Bart De Schuymer <bart.de.schuymer@pandora.be>
To: "Jorge# ./S" <jorge@kernel-panik.org>, bridge@math.leidenuniv.nl
Cc: Antony@Soft-Solutions.co.uk, netfilter@lists.samba.org
Subject: Re: I can't vpn ! - ebtables can forward GRE?
Date: Thu, 30 May 2002 05:21:50 +0200 [thread overview]
Message-ID: <aeambk$rn9$2@main.gmane.org> (raw)
In-Reply-To: <200205291810.53634.jorge@kernel-panik.org>
On Thursday 30 May 2002 00:10, Jorge# ./S wrote:
> Any ebtables expert can help us solve this:
>
> Can GRE packets be forwarded on a linux box using ebtables?
>
> ---------- Forwarded Message ----------
>
> Subject: Re: I can't vpn ! - ebtables can forward GRE?
> Date: Thu, 30 May 2002 00:09:11 +0100
> From: Antony Stone <Antony@Soft-Solutions.co.uk>
> To: netfilter@lists.samba.org
>
> On Wednesday 29 May 2002 11:00 pm, Jorge Sarmiento wrote:
> > With ebtables you can block protocols that are not TCP, and let pass TCP,
> > ICMP and UDP to your network... you can also redirect TCP packets to do
> > an "invisible transparent proxy", mixing bridging and ebtables... then
> > why couldn't GRE packets be forwarded??
If you know the protocol number of these GRE packets you can filter on the
protocol number. ebtables -p IPv4 --ip-protocol 47. There is only support for
ip header filtering. E.g. no TCP port filtering, certainly no GRE specific
filtering. These things belong in iptables.
With ebtables you can only change the MAC source and destination address. A
redirect in ebtables only means the MAC destination of the frame is changed
to that of the bridge, causing the frame to be routed or delivered to the
bridge itself. You can also make a brouter with ebtables. IP redirects
obviously belong in iptables.
I'm not subscribed to the netfilter users list. For ebtables questions there
is a mailing list too. See the ebtables hp.
cheers,
Bart
parent reply other threads:[~2002-05-30 3:21 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <200205291810.53634.jorge@kernel-panik.org>]
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='aeambk$rn9$2@main.gmane.org' \
--to=bart.de.schuymer@pandora.be \
--cc=Antony@Soft-Solutions.co.uk \
--cc=bridge@math.leidenuniv.nl \
--cc=jorge@kernel-panik.org \
--cc=netfilter@lists.samba.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.