From: Alex Zeffertt <ajz@cambridgebroadband.com>
To: Hai Wang <hwang@finepoint.com>
Cc: linux-atm-general@lists.sourceforge.net, bridge@lists.osdl.org
Subject: Re: [Bridge] [Linux-ATM-General] BR2684-rt and brctl
Date: Thu, 08 Mar 2007 10:06:34 +0000 [thread overview]
Message-ID: <45EFE02A.9010306@cambridgebroadband.com> (raw)
In-Reply-To: <DE026503646E7F40AF97BAB98334333B018A6F21@uss-republic.finepoint.com>
Hai Wang wrote:
> Hello,
>
>
>
> I am wondering if any of you knows how to add BR2684-rt nas
> interfaces into a Ethernet bridge, I know that brctl will work with
> BR2684-br, but not for BR2684-rt.
>
>
>
Hi Hai,
Looking at the RFC, it doesn't appear that the MAC address is even
present in routed RFC2684 PDUs. It would seem to me that this makes
it impossible to add routed interfaces to a bridge.
See below,
Alex
---snip---
5.1. LLC Encapsulation for Routed Protocols
In LLC Encapsulation, the protocol type of routed PDUs MUST be
identified by prefixing an IEEE 802.2 LLC header to each PDU. In
some cases, the LLC header MUST be followed by an IEEE 802.1a
SubNetwork Attachment Point (SNAP) header. In LLC Type 1 operation,
the LLC header MUST consist of three one octet fields:
+------+------+------+
| DSAP | SSAP | Ctrl |
+------+------+------+
In LLC Encapsulation for routed protocols, the Control field MUST be
set to 0x03, specifying a Unnumbered Information (UI) Command PDU.
The LLC header value 0xFE-FE-03 MUST be used to identify a routed PDU
in the ISO NLPID format (see [6] and Appendix B). For NLPID-formatted
routed PDUs, the content of the AAL5 CPCS-PDU Payload field MUST be
as follows:
Payload Format for Routed NLPID-formatted PDUs
+-------------------------------+
| LLC 0xFE-FE-03 |
+-------------------------------+
| NLPID (1 octet) |
+-------------------------------+
| . |
| PDU |
| (up to 2^16 - 4 octets) |
| . |
+-------------------------------+
--/snip---
> Many thanks!
>
>
>
>
>
> Hai
>
>
> ------------------------------------------------------------------------
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys-and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Linux-atm-general mailing list
> Linux-atm-general@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/linux-atm-general
prev parent reply other threads:[~2007-03-08 10:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-07 18:28 [Bridge] BR2684-rt and brctl Hai Wang
2007-03-08 10:06 ` Alex Zeffertt [this message]
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=45EFE02A.9010306@cambridgebroadband.com \
--to=ajz@cambridgebroadband.com \
--cc=bridge@lists.osdl.org \
--cc=hwang@finepoint.com \
--cc=linux-atm-general@lists.sourceforge.net \
/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