Ethernet Bridge development
 help / color / mirror / Atom feed
From: Udo Hortian <udo_hortian@web.de>
To: bridge@lists.linux-foundation.org
Subject: [Bridge] Bridging problems after Upgrade to Debian Lenny
Date: Sun, 22 Feb 2009 13:32:49 +0100	[thread overview]
Message-ID: <20090222123249.GA21690@an> (raw)

Hello all,

I subscribed newly to this list, since I got an bridging problem after an
upgrade from Debian etch to Debian lenny (before everything worked fine).

The situation is as follows:

# brctl show
bridge name     bridge id               STP enabled     interfaces
br0             8000.000347729835       no              eth0
                                                        tap0

tap0 is associated with an OpenVPN tunnel.

The strange thing now is the following:

Packets from eth0 to IP addresses within tap0 pass the bridge and reach
the destination (the other side of an OpenVPN tunnel).

But packets from the other side of the OpenVPN tunnel do not reach
destinations behind eth0. I think this is not an OpenVPN problem, since
I can see packets, as described here, using "tcpdump -i tap0" and also
using "tcpdump -i br0". But I do not see them using "tcpdump -i eth0".

The only thing which happens is that there are sometimes packets like
this on eth0: "igmp v3 report, 1 group record(s)" (from tcpdump) with
source address the one from the OpenVPN client. I do now know where
these packets come from.

There is now firewall activated.

Here are a few informations about my system:
Debian lenny
Linux 2.6.18-6-686 (Debian Kernel)
bridge-utils 1.4-5 (Debian packet)

Any ideas what might be the reason for this and how to solve it?

Best regards
Udo

             reply	other threads:[~2009-02-22 12:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-22 12:32 Udo Hortian [this message]
2009-02-27 20:54 ` [Bridge] Bridging problems after Upgrade to Debian Lenny Udo Hortian

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=20090222123249.GA21690@an \
    --to=udo_hortian@web.de \
    --cc=bridge@lists.linux-foundation.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