IP
IP support on AT-iMG Models
iMG/RG Software Reference Manual (IPNetwork Functions)
4-2
4.1.3
IP support on AT-iMG Models
In order to use the IP stack, one or more interfaces must be added to the IP stack and attached to a transport.
Each interface must be configured with an IP address and a subnet mask. Together, these define the range of
addresses that can be reached via the interface without passing through any other routers.
Each interface (real and virtual) must have a unique subnet; the range of addresses on each interface must not
overlap with any other interface. In situations where there is no local subnet associated with an interface,
unnumbered interfaces may be used.
4.1.3.1 Adding and attaching IP interfaces
IP interfaces are added and attached using the commands provided in the IP and Ethernet module respectively.
IP interfaces use typically the services provided by Ethernet transports. Ethernet transport is an abstraction
layer used to classify the format of the IP packets that will be transferred through the network. Another type of
transport is, for example, is PPPoE. Packets transmitted through a PPPoE connection or Ethernet connection
will have different frame format even if the convey the same type of information to the IP layer.
Because the system supports VLANs, the same Ethernet port can be shared between different VLANs. There-
fore it's not possible map an Ethernet transport directly to a physical Ethernet port.
Instead Ethernet transports are mapped to VLANs that from a logical point of view they act like an Ethernet
segment, as an Ethernet port would do in a simple system without VLANs
The way a transport is attached to the gateway depends on the kind of core switching type.
On FIBER A/C and ADSL A devices
it happens like depicted in steps here below.
•
Create an Ethernet transport using the command:
ethernet add transport eth1 myvlan
•
Create an interface to the IP stack: using, for example, the command:
ip add interface ip1 192.168.101.2 255.255.255.0
•
Attach the transport to the interface using the command:
ip attach ip1 eth1
Things are slightly different on the remaining models. A Vlan is handled as a bridgeport. Each bridgeport is a
transport of type Qbridge. therefore step 1) is not necessary.
•
Create an interface to the IP stack: using, for example, the command:
ip add interface ip1 192.168.101.2 255.255.255.0
•
Attach the transport to the interface using the command:
ip attach ip1 myvlan
19216811.live