From: Carsten <fbndd@oleco.net>
To: bridge@lists.linux-foundation.org
Subject: [Bridge] Problem Forwarding Bridge to Tap Device
Date: Wed, 7 Oct 2009 13:43:16 +0200 [thread overview]
Message-ID: <48270.1254915796@oleco.net> (raw)
Hello,
I have a problem with bridge and tap network where I can't find a solution
first my scenario
[ETHx][PC1] <-> [Switch] <-> [PC2][ETHx][VLANx][BR0][TAP0][VBox]
Switchport of PC1 is untagged in VLANx, Switchport of PC2 is tagged in the same VLAN. I can see the packets running as I want over all components.
Now my Problem
I send a Ping from VBox to PC1 all works fine, while the ping is running I restart PC1, as suggested ping now fail.
After PC1 is up again packet transport should work correctly, but it doesn't (exactly some times is ok, some times problem comes after 5th reboot or so but is coming if I have enough reboots of PC1) .
So find the problem I dump the traffic of VLANx, BR0 and TAP0.
What I see:
@VLANx: arp request and reply
@ BR0: arp request and reply
@ TAP0: arp request
So I think the bridge stop forwarding packets to the TAP device and I don't understand why. Have anyone an idea?
Thx for help
----
versendet mit www.oleco.de Mail - Anmeldung und Nutzung kostenlos!
Oleco www.netlcr.org - jetzt auch mit Spamschutz.
reply other threads:[~2009-10-07 11:43 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=48270.1254915796@oleco.net \
--to=fbndd@oleco.net \
--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