Technical data

Table Of Contents
23
RFC 1483 or RFC 1490
Bridging
User data packets are prepended by the sequence 0xAAAA0300 0x80c20007 0x0000 followed by the
Ethernet frame containing the packet.
802.1D Spanning Tree packets are prepended with the header 0xAAAA0300 0x80C2000E.
Routing
IP packets are prepended with the header 0xAAAA0300 0x00000800.
IPX packets are prepended with the header 0xAAAA0300 0x00008137.
The commands for this encapsulation option are:
remote setProtocol
RFC1483
<
remoteName
> (for ATM)
remote setProtocol FR
<
remoteName
> (for Frame Relay - RFC 1490)
MAC Encapsulated Routing: RFC 1483MER (ATM) or RFC 1490MER
(Frame Relay)
MER encapsulation allows IP packets to be carried as bridged frames, but does not prevent bridged frames from
being sent as well, in their normal encapsulation format: RFC 1483 (ATM) or RFC 1490 (Frame Relay).
If IP routing is enabled, then IP packets are prepended with the sequence 0xAAAA0300 0x80c20007 0x0000 and
sent as bridged frames. If IP routing is not enabled, then the packets appear as bridged frames.
The commands for this encapsulation option are:
remote setProtocol RFC1483MER
<
remoteName
> (for ATM)
remote setProtocol
MER
(for Frame Relay)
FRF8
IP Packets have prepended to them the following sequence: 0x03CC.
The command for this encapsulation option is:
remote setprotocol
FRF8
<
remoteName
>
Note:
This protocol allows sending ATM over Frame Relay