NG_ATMLLC(4) BSD Kernel Interfaces Manual NG_ATMLLC(4)NAME
ng_atmllc -- ATM LLC netgraph node type
SYNOPSIS
#include <netgraph/ng_atmllc.h>
DESCRIPTION
The atmllc node type translates frames in to and out of ATM LLC encapsulation, as specified by RFC 1483. In LLC encapsulation the protocol
of a given protocol data unit (PDU) is specified by an IEEE 802.2 LLC header, possibly followed by an IEEE 802.1a SubNetwork Attachment Point
(SNAP) header. This node currently handles the Ethernet and FDDI protocols.
The node transmits and receives ATM PDUs on the atm hook. Received PDUs are decoded and forwarded to the ether or fddi hooks as appropriate.
Data received on the ether or fddi hooks are assumed to be full Ethernet or FDDI packets as appropriate and are encapsulated into a PDU and
transmitted via the atm hook.
HOOKS
This node type supports the following hooks:
atm ATM connection. Typically, this hook would be connected to a ng_atm(4) node, which handles transmission of ATM PDUs over an ATM
device.
ether Ethernet connection. This hook sends and receives Ethernet frames. This would normally be connected to an ng_eiface(4) node if in
use.
fddi FDDI connection. This hook sends and receives FDDI frames.
CONTROL MESSAGES
This node type supports the generic control messages.
SHUTDOWN
This node shuts down upon receipt of a NGM_SHUTDOWN control message, or when all hooks have been disconnected.
SEE ALSO netgraph(4), ng_atm(4), ng_eiface(4), ngctl(8)
J. Heinanen, Multiprotocol Encapsulation over ATM Adaptation Layer 5, RFC 1483.
AUTHORS
Benno Rice <benno@FreeBSD.org>
BSD March 8, 2004 BSD
Check Out this Related Man Page
NG_ATMLLC(4) BSD Kernel Interfaces Manual NG_ATMLLC(4)NAME
ng_atmllc -- ATM LLC netgraph node type
SYNOPSIS
#include <netgraph/ng_atmllc.h>
DESCRIPTION
The atmllc node type translates frames in to and out of ATM LLC encapsulation, as specified by RFC 1483. In LLC encapsulation the protocol
of a given protocol data unit (PDU) is specified by an IEEE 802.2 LLC header, possibly followed by an IEEE 802.1a SubNetwork Attachment Point
(SNAP) header. This node currently handles the Ethernet and FDDI protocols.
The node transmits and receives ATM PDUs on the atm hook. Received PDUs are decoded and forwarded to the ether or fddi hooks as appropriate.
Data received on the ether or fddi hooks are assumed to be full Ethernet or FDDI packets as appropriate and are encapsulated into a PDU and
transmitted via the atm hook.
HOOKS
This node type supports the following hooks:
atm ATM connection. Typically, this hook would be connected to a ng_atm(4) node, which handles transmission of ATM PDUs over an ATM
device.
ether Ethernet connection. This hook sends and receives Ethernet frames. This would normally be connected to an ng_eiface(4) node if in
use.
fddi FDDI connection. This hook sends and receives FDDI frames.
CONTROL MESSAGES
This node type supports the generic control messages.
SHUTDOWN
This node shuts down upon receipt of a NGM_SHUTDOWN control message, or when all hooks have been disconnected.
SEE ALSO netgraph(4), ng_atm(4), ng_eiface(4), ngctl(8)
J. Heinanen, Multiprotocol Encapsulation over ATM Adaptation Layer 5, RFC 1483.
AUTHORS
Benno Rice <benno@FreeBSD.org>
BSD March 8, 2004 BSD
Can somebody help me on IVM? I have installed vio 2.2 on a js21 server.
It has 2 physical ether ports, what I want to do is create ether channel say
en15 and en16 are physical and en17 is ether channel. I have created 2 clients on this server, now the question is can I map this en17 to both... (1 Reply)
More old kit .....
We have a bunch of old Sun kit E4500, E450 etc that are currently running on ATM nic's and need to be put on the the onboard Ethernet ports....
Anyone know how to do this without downtime?
It'd be better if I can keep the original Ip Addresses though it may be possible to... (2 Replies)