From: Benny Amorsen <benny+usenet@amorsen.dk>
To: bridge@osdl.org
Subject: Re: [Bridge] VLAN headers disappearing
Date: 30 Jan 2007 22:31:39 +0100 [thread overview]
Message-ID: <m3y7nkurpg.fsf@ursa.amorsen.dk> (raw)
In-Reply-To: H000006900127bb1.1170115520.mail.pacificwireless.net.au@MHS
>>>>> "LS" == Leigh Sharpe <lsharpe@pacificwireless.com.au> writes:
LS> Results in lots of log entries in /var/log/messages, as one would
LS> expect. However,
LS> ebtables -F ebtables -A FORWARD -p 8021q --log -j ACCEPT
LS> Results in absolutely nothing in /var/log/messages, which would
LS> indicate that at some point, the VLAN headers are disappearing
LS> from my bridged packets.
Cards with hardware accelerated VLAN's eat the 802.1q headers. It is
very annoying. You can recompile the driver with VLAN acceleration
turned off in most cases, but that is hardly a nice solution.
/Benny
next prev parent reply other threads:[~2007-01-30 21:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-30 0:05 [Bridge] VLAN headers disappearing Leigh Sharpe
2007-01-30 21:31 ` Benny Amorsen [this message]
2007-01-30 21:51 ` Leigh Sharpe
2007-01-30 22:01 ` Benny Amorsen
2007-01-31 4:54 ` Leigh Sharpe
2007-01-31 8:07 ` Benny Amorsen
2007-01-31 18:43 ` Andy Gospodarek
2007-01-31 20:42 ` Andy Gospodarek
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=m3y7nkurpg.fsf@ursa.amorsen.dk \
--to=benny+usenet@amorsen.dk \
--cc=bridge@osdl.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