From: Lutz Jaenicke <ljaenicke@innominate.com>
To: bridge@lists.osdl.org
Subject: Re: [Bridge] Passing vlan tagged packets through linux bridge
Date: Mon, 27 Nov 2006 13:31:03 +0100 [thread overview]
Message-ID: <20061127123102.GA15052@innominate.com> (raw)
In-Reply-To: <20061126060423.50525.qmail@web54212.mail.yahoo.com>
On Sat, Nov 25, 2006 at 10:04:23PM -0800, kasra kangavari wrote:
> Dear Roman
>
> If I don't use trunk over linux bridges(packets without vlan tag) then I can ping more than 1500bytes(MTU).the problem is vlan tagged packets. r u sure about jumbo frames that solve this problem ?
Did you have a look at the MTUs of the interfaces? If you need to
support VLAN tagged frames, at least the physical interfaces
need to accept frames with additional 4 bytes on the wire.
If this is not handled in the driver the 1500+ETH+VLAN-frames will
already be dropped (not even be received) at the physical interfaces.
You may have to allow an MTU of 1504 for this reason.
Regards,
Lutz
--
Dr.-Ing. Lutz Jänicke
CTO
Innominate Security Technologies AG /protecting industrial networks/
tel: +49.30.6392-3308
fax: +49.30.6392-3307
Albert-Einstein-Str. 14
D-12489 Berlin, Germany
www.innominate.com
---------------------------------------------------------------
Visit us at the SPS/IPC/Drives in Nuernberg
28 - 30 November 2006, Hall 9, Stand 9-125
---------------------------------------------------------------
next prev parent reply other threads:[~2006-11-27 12:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-26 6:04 [Bridge] Passing vlan tagged packets through linux bridge kasra kangavari
2006-11-27 12:31 ` Lutz Jaenicke [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-12-01 21:19 Fulvio Ricciardi
2006-12-01 17:09 Fulvio Ricciardi
2006-12-01 18:29 ` Stephen Hemminger
2006-11-27 19:12 Fulvio Ricciardi
2006-11-25 15:22 Fulvio Ricciardi
2006-11-25 16:13 ` Roman Chertov
2006-11-25 12:12 Fulvio Ricciardi
2006-11-27 17:59 ` Ben Greear
2006-11-25 7:44 kasra kangavari
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=20061127123102.GA15052@innominate.com \
--to=ljaenicke@innominate.com \
--cc=bridge@lists.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 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.