3.Bridge Console commands
3.1device add
3.1.1Syntax
device add <device>
3.1.2 Description
This command adds a device to the bridge configuration. Attempts to add the bridge itself or an existing device to the bridge are rejected.
Attempts to add devices which don’t support the Cyan interface are rejected. There is a limit on the number of devices that can be attached to the bridge. If the device being added is from a process which supports multiple devices, the /DEVICE attribute must be specified as part of the device name. The table below shows devices which may be attached to the bridge, although not all systems may support all devices.
Device | Remarks | Source |
|
|
|
Edd | Ethernet driver | bun_ethernet |
|
|
|
r1483 | RFC1483 protocol (PVC) | rfc1483 |
|
|
|
Ppp | pp | |
|
|
|
Configuration saving saves this information. See the section entitled Implementation Constraints in the ATMOS Transparent Bridge Specification,
3.1.3 Example
Simple examples
device add edd
device add ppp/DEVICE=2
Using the BUN RFC1483 driver
This example shows how to add the BUN RFC1483 driver, dynamically from the console. You need to define and configure a device and a port.
Normally, the RFC1483 BUN device will pass all data straight through, untouched. This means that even though you have changed your port definition to include the RFC1483 driver, you can still use other protocols on the same port. In order to enable RFC1483 encapsulation, the RFC1483 attribute on the channel must be set to true.
The channel attribute mode dictates the functional behaviour of the driver, in terms of encapsulation method to use and traffic nature (bridged/routed). The channel
