From: Tomasz Chmielewski <mangoo@wpkg.org>
To: Marek Kierdelewicz <marek@piasta.pl>
Cc: netfilter@vger.kernel.org
Subject: Re: using iptables with tun/tap interfaces? no rule sees tun/tap interface traffic
Date: Sun, 29 Aug 2010 13:50:10 +0200 [thread overview]
Message-ID: <4C7A4972.4020304@wpkg.org> (raw)
In-Reply-To: <20100829131559.23abd652@catus>
On 29.08.2010 13:15, Marek Kierdelewicz wrote:
> Hi Tomasz,
>
>> tcpdump: WARNING: tap0: no IPv4 address assigned
>
> So you're bridging.
>
> Make sure /proc/sys/net/bridge/bridge-nf-call-iptables is set to 1.
# cat /proc/sys/net/bridge/bridge-nf-call-iptables
1
Using 2.6.35 kernel.
Should I use ebtables for this? iptables seem more flexible here.
--
Tomasz Chmielewski
http://wpkg.org
next prev parent reply other threads:[~2010-08-29 11:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-29 11:03 using iptables with tun/tap interfaces? no rule sees tun/tap interface traffic Tomasz Chmielewski
2010-08-29 11:15 ` Marek Kierdelewicz
2010-08-29 11:50 ` Tomasz Chmielewski [this message]
2010-08-29 12:21 ` Marek Kierdelewicz
2010-08-29 12:38 ` Tomasz Chmielewski
2010-08-29 15:01 ` Pascal Hambourg
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=4C7A4972.4020304@wpkg.org \
--to=mangoo@wpkg.org \
--cc=marek@piasta.pl \
--cc=netfilter@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