* Re: [Bridge] BR2684-rt and brctl
@ 2007-03-07 18:28 Hai Wang
2007-03-08 10:06 ` [Bridge] [Linux-ATM-General] " Alex Zeffertt
0 siblings, 1 reply; 2+ messages in thread
From: Hai Wang @ 2007-03-07 18:28 UTC (permalink / raw)
To: bridge, linux-atm-general
[-- Attachment #1: Type: text/plain, Size: 228 bytes --]
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.
Many thanks!
Hai
[-- Attachment #2: Type: text/html, Size: 2801 bytes --]
^ permalink raw reply [flat|nested] 2+ messages in thread* Re: [Bridge] [Linux-ATM-General] BR2684-rt and brctl
2007-03-07 18:28 [Bridge] BR2684-rt and brctl Hai Wang
@ 2007-03-08 10:06 ` Alex Zeffertt
0 siblings, 0 replies; 2+ messages in thread
From: Alex Zeffertt @ 2007-03-08 10:06 UTC (permalink / raw)
To: Hai Wang; +Cc: linux-atm-general, bridge
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
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2007-03-08 10:06 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-03-07 18:28 [Bridge] BR2684-rt and brctl Hai Wang
2007-03-08 10:06 ` [Bridge] [Linux-ATM-General] " Alex Zeffertt
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox