Generally, only two IP routing types exist: the static and the dynamic one. The main difference between the two types is the method of construction of the routing tables.
A table dynamic IP routings is made and automatically updated by the specialized software processes of IP Router. Through opportune routing protocols such processes provide periodic exchange of routing information with the others router present in the network, their processing and inserting of the obtained routing in the suitable routing table.
A table of static IP routings is made and manually managed by the network manager and it needs of being stored in a support of not volatile memory, in case the system is switched off.
In Abilis CPX the IP routings table contains all the routing topologies, leaving however the distinction between the types. In the current version Abilis CPX allows to add manually static routing, routing connected (to a subset of the static routing), and to acquire dynamic routing through protocols RIP1 and RIP2 and OSPF.
In this section, IP routings table and the modality of configuration of saved static routings will be described.
Refer to the chapter Configuration of IP ports for connected routing and to chapters The Routing Information Protocol (RIP) port for dynamic routing retrieved by the RIP routing protocol and The Open Shortest Path First Protocol (OSPF) port for dynamic routing retrieved by the OSPF routing protocol.
In IP routings table, static routings can be added/modified/deleted while the Abilis CPX works without needing to restart it, changes are active immediately.
When the command SAVE CONF is executed, only static routings that are currently presents in the table are saved in the configuration file.
The maximum size of the IP routings table can be configured through the parameter MAXROUTE: of the IP Router port, whose default value is 500. However, in the configuration files up to 255 static routings are saved, while the connected routing are derived from the configurations of IP ports.
All the commands for managing the IP routings are described in the section IP routings of the chapter Commands relating to IP Router.
The available commands are the following:
A IPRHere is an example of displaying all the IP routings:
[11:18:14] ABILIS_CPX: D IPR Unconditional source routes: +-------+--------------------+--------------------+-----------------+----+---+ | | NET:/MASK: | MASK: or | GW: |IPP:| | | | | SRNET:/SRMASK: | | | | +-------+--------------------+--------------------+-----------------+----+---+ | | 002.002.000.000/16 | 255.255.000.000 | | | | | | | 005.005.005.005/32 | |D 2| | | | | 005.005.005.005/32 | |D 1| | +-------+--------------------+--------------------+-----------------+----+---+ Destination routes and conditional source routes: +-+-+-+-+--------------------+--------------------+-----------------+----+---+ |B|P|S|H| NET:/MASK: | MASK: or | GW: |IPP:|AD:| | | | | | | SRNET:/SRMASK: | | | | +-+-+-+-+--------------------+--------------------+-----------------+----+---+ |*|S| | | 001.001.001.001/32 | 255.255.255.255 | |D 1| 1| | |S| | | 001.001.001.001/32 | 255.255.255.255 | |NONE| 1| | | | | | | 005.005.005.005/32 | |NONE| | |*|S| | | 001.005.005.005/32 | 255.255.255.255 | |NONE| 1| |*|S| |*| 002.002.002.002/32 | 255.255.255.255 | | 10| 1| |*|S| | | 002.002.002.003/32 | 255.255.255.255 | | 10| 1| |*|S| |*| 005.005.005.005/32 | 255.255.255.255 | | 5| 1| |*|S| | | 005.005.005.006/32 | 255.255.255.255 | | 6| 1| |*|S| | | 009.009.009.009/32 | 255.255.255.255 | |NONE| 1| |*|S| | | 010.000.000.001/32 | 255.255.255.255 | | 5| 5| |*|S| | | 032.032.032.032/32 | 255.255.255.255 | | 32| 1| |*|S| | | 192.168.000.005/32 | 255.255.255.255 | | 15| 1| |*|R| | | 192.168.000.060/32 | 255.255.255.255 | 192.168.000.060 | 0|120| |*|C| | | 192.168.000.213/32 | 255.255.255.255 | |R-ID| 0| |*|C| | | 192.168.010.001/32 | 255.255.255.255 | | 30| 0| |*|C| | | 192.168.031.213/32 | 255.255.255.255 | | 31| 0| |*|C| | | 212.025.018.178/32 | 255.255.255.255 | | 30| 0| |*|C| | | 006.006.006.000/24 | 255.255.255.000 | |D 63| 0| |*|C| | | 192.168.000.000/24 | 255.255.255.000 | | 0| 0| |*|R| | | 192.168.001.000/24 | 255.255.255.000 | 192.168.000.060 | 0|120| |*|S| | | 192.168.006.000/24 | 255.255.255.000 | 192.168.000.251 | 0| 1| |*|S| | | 192.168.008.000/24 | 255.255.255.000 | 192.168.000.251 | 0| 1| |*|C| | | 002.002.000.000/16 | 255.255.000.000 | | 40| 0| | |S| | | 002.002.000.000/16 | 255.255.000.000 | | 40| 1| | | | | | | 005.005.005.005/32 | | 0| | | | | | | | 005.005.005.005/32 | |NONE| | |*|S| | | 010.000.000.000/16 | 255.255.000.000 | 192.168.000.253 | 0| 1| +-+-+-+-+--------------------+--------------------+-----------------+----+---+
In the following example, only those routings matching the specified "filter" (MASK:255.255.255.0) are shown:
[18:14:08] ABILIS_CPX: D IPR MASK:255.255.255.0 Unconditional source routes: +-------+--------------------+--------------------+-----------------+----+---+ | | NET:/MASK: | MASK: or | GW: |IPP:| | | | | SRNET:/SRMASK: | | | | +-------+--------------------+--------------------+-----------------+----+---+ Destination routes and conditional source routes: +-+-+-+-+--------------------+--------------------+-----------------+----+---+ |B|P|S|H| NET:/MASK: | MASK: or | GW: |IPP:|AD:| | | | | | | SRNET:/SRMASK: | | | | +-+-+-+-+--------------------+--------------------+-----------------+----+---+ |*|C| | | 006.006.006.000/24 | 255.255.255.000 | |D 63| 0| |*|C| | | 192.168.000.000/24 | 255.255.255.000 | | 0| 0| |*|R| | | 192.168.001.000/24 | 255.255.255.000 | 192.168.000.060 | 0|120| |*|S| | | 192.168.006.000/24 | 255.255.255.000 | 192.168.000.251 | 0| 1| |*|S| | | 192.168.008.000/24 | 255.255.255.000 | 192.168.000.251 | 0| 1| +-+-+-+-+--------------------+--------------------+-----------------+----+---+
In the Unconditional source routes section of the displayed information, unconditional source routings are listed; while in the Destination routes and conditional source routes section, both destination routings and conditional source routings are displayed.
| B: | Best routing |
| no value | ' '=NO, *=YES |
This parameter has only an informative value and it cannot be modified. In the case that two or more routings with the same NET: value are present, it identifies the best one.
| P: | Origin of routing |
| no value | C=CONNECTED, S=STATIC, O=OSPF, R=RIP |
This parameter has only an informative value and it cannot be modified. It shows the origin of the routing.
The following table lists allowed values and their meaning:
| Value | Meaning |
|---|---|
| C | The routing has been obtained from the configuration table of the IP ports; this kind of routing is referred as directly connected or, simply, connected. |
| S | It is a static routing, obtained from the table of saved static IP routings. |
| R | The routing has been obtained from the RIP protocol. |
| O | The routing has been obtained from the OSPF protocol. |
| S: | Status of the routing. |
| no value | ' '=NORMAL, A=ADDED, C=CHANGED, D=DELETING, H=HIDDEN |
This parameter has only an informative value and it cannot be modified. It indicates the state of the single routing. Every time some changes occurs to IPRTR table, routings could change their state. This could be due to changes into IP ports, changes with static and dynamic routings.
| Value | Meaning |
|---|---|
| Normal state: routings is in normal state, nothing has been changing. | |
| A | Added state: routing is just added into table and is going to be accepted. Once confirmed by IPRTR, it will go into normal state. |
| C | Changed state: routing has changed some parameters and is going to be accepted. Once confirmed by IPRTR, it will go into normal state. |
| D | Deleted state: routing is just requested for being deleted from table. Once request is confirmed by IPRTR, routing will be removed from table. |
| H | Hidden state: routing hidden parameter is changed from NO to YES. Once request is confirmed by IPRTR, routing will go into normal state. |
| H: | Hiding static routings from dynamic routing protocols like RIP and OSPF. |
| NO | ' '=NO, *=YES |
It sets whether the static routing has to be hidden to the other dynamic routing protocols like RIP and OSPF.
If the parameter is set to "NO", the field will be empty and the routing will be inserted in the RIP and OSPF local table.
Setting the parameter to "YES", the character '*' will be shown, meaning that the routing won't be inserted in the RIP and OSPF local table.
| NET: | Destination network |
| no value | see below |
It sets the destination network of the routing.
The destination network address and the related mask can be specified either using the in Slash Notation (e.g. NET:x.x.x.x/yy) or using the Dotted Decimal Notation for both the network address and the related mask (e.g. NET:x.x.x.x MASK:y.y.y.y).
Allowed values for the destination network address are shown in the following table:
| HEX: | 00000000 | 01000000 - 7EFFFFFF | 80000000 - DFFFFFFF |
|---|---|---|---|
| DDN: | 0.0.0.0 | 1.0.0.0 - 126.255.255.255 | 128.0.0.0 - 223.255.255.255 |
IP addresses of class D and E are not currently supported.
When Slash Notation is used, valid values for the network mask must contain sequence of bit set to 1, estimated leaving from the most meaningful bit towards the less meaningful one; therefore they must be in the range [0..32].
Doing the "logical AND" between the destination network address and the MASK: value, the result should be the destination network itself; if not the message "INVALID STATIC NETWORK" will be shown and the value refused.
| MASK: | Mask related to the destination network |
| no value | 0.0.0.0 - 255.255.255.255 |
It sets the mask related to the destination network.
The parameter must be expressed in Dotted Decimal Notation and can only be configured to values that contain sequence of bit set to 1, estimated leaving from the most meaningful bit towards the less meaningful one.
Doing the "logical AND" between this parameter and the related network address (see NET:), the result should be the destination network itself; if not the message "INVALID STATIC NETWORK" will be shown and the value refused.
The destination network mask is also displayed in the table, together with the related network address using the Slash Notation, in the NET: field.
The MASK: filed of the table can also display the Source routing network (see SRNET:).
| SRNET: | Source routing network |
| no value | see below |
It display the Source routing network address and the related mask, expressed in Slash Notation.
Allowed values for the Source routing network address, in Dotted Decimal Notation, are shown in the following table:
| HEX: | 00000000 | 01000000 - 7EFFFFFF | 80000000 - DFFFFFFF |
|---|---|---|---|
| DDN: | 0.0.0.0 | 1.0.0.0 - 126.255.255.255 | 128.0.0.0 - 223.255.255.255 |
IP addresses of class D and E are not currently supported.
The mask related to the Source routing network, must be a value that contains sequence of bit set to 1, estimated leaving from the most meaningful bit towards the less meaningful one. Therefore it will be a value in the range [1-32].
Doing the "logical AND" between the Source routing network and the related mask, the result should be the Source routing network itself.
| GW: | IP address of the destination gateway [1] |
| no value | ' '=0.0.0.0, see below |
It sets the address of the destination gateway, in Dotted Decimal Notation. The allowed values are shown in the following table:
| HEX: | 00000000 | 01000000 - 7EFFFFFF | 80000000 - DFFFFFFF |
|---|---|---|---|
| DDN: | 0.0.0.0 | 1.0.0.0 - 126.255.255.255 | 128.0.0.0 - 223.255.255.255 |
IP addresses of class D and E are not currently supported.
If the parameter is set to "0.0.0.0", the field will be empty in the table.
| IPP: | IP port where to route to |
| no value | 0..63, NONE, R-ID=Router-ID |
It sets the IP port where to route the IP datagram.
If, at the moment of the visualization, the IP port that is referenced by the routing is in "DOWN" state, beside the port index, the character "D" will appear.
The value "NONE" stands for "no IP port"; it can be used for deactivating the IP routing without canceling it.
The value "R-ID", stands for "Router-ID"; it cannot be manually set and it means that the specified routing is the Router ID.
| AD: | Administrative distance |
| no value | 0 - 255 |
Distance used for route priority into IP Routing table.
This is a particular metric used to indicate priorities between routings of the same and different protocol route.
The less is the AD value and the better will be the routing priority.
This value is assigned in this way: once a routing must be added into IPRTR table, first must be checked if there is a record
into Administrative Distance Table that matches with route.
If matches, the specific AD will be assigned, else will be taken from its
IPR_DEF-LOC-AD: parameter
This table contains information about rules for routes priority into IP Routing table.
Commands for managing the IP Routing Administrative Distances Table are described in the section IP Routing administrative distances of Commands relating to IP Router.
The following commands are available:
A IPADHere is an example of how to display IP Routing Administrative Distances Table:
[10:49:13] ABILIS_CPX: D IPAD +--------------------+----------+-----------+--------+ | NET: | PROT: | DISTANCE: | IPP: | +--------------------+----------+-----------+--------+ | 192.168.006.002/32 | RIP | 110 | | | 192.168.006.000/24 | RIP | 120 | | | 192.168.006.000/24 | OSPF | 100 | | | 010.000.000.000/8 | STATIC | 10 | NONE | | 000.000.000.000/0 | LOCAL | 5 | | +--------------------+----------+-----------+--------+
Here is an example of how to display a specific entry of the table:
[16:54:38] ABILIS_CPX: D IPAD NET:192.168.006.002/32 PROT:RIP +--------------------+----------+-----------+--------+ | NET: | PROT: | DISTANCE: | IPP: | +--------------------+----------+-----------+--------+ | 192.168.006.002/32 | RIP | 110 | | +--------------------+----------+-----------+--------+
The IP Routing Administrative Distances Table can store up to 256 entries.
Every entry in the table is unambiguously identified by its NET: and PROT: parameters values, i.e. NET: can be duplicated only for different PROT: value.
Entries are kept sorted by NET: and PROT: values: longer Network Mask first and lower Network address first.
| NET: | Destination network |
| no value | see below |
It specifies the destination network IP address and mask used for setting administrative distance, in Slash Notation (i.e. x.x.x.x/yy).
The allowed values for network addresses are shown in the following table:
| HEX: | 00000000 | 01000000 - 7EFFFFFF | 80000000 - DFFFFFFF |
|---|---|---|---|
| DDN: | 0.0.0.0 | 1.0.0.0 - 126.255.255.255 | 128.0.0.0 - 223.255.255.255 |
Valid values for the network mask must contain sequence of bit set to 1, estimated leaving from the most meaningful bit towards the less meaningful one; therefore they must be in the range [0..32].
By doing the "logical And" between the destination network IP address and the related network mask, the result should be the destination network itself; if not the message "INVALID VALUE 'NET:x.x.x.x/yy'" will be shown and the value refused.
| PROT: | Routing protocol |
| NONE | NONE, LOCAL, STATIC, OSPF, RIP |
This parameter defines a routing protocol for which this distance will be applied.
| Value | Meaning |
|---|---|
| NONE | IPRTR doesn't consider this record. |
| LOCAL | Administrative distance is referred to LOCAL routing protocol. |
| STATIC | Administrative distance is referred to STATIC routing protocol. |
| OSPF | Administrative distance is referred to OSPF routing protocol. |
| RIP | Administrative distance is referred to RIP routing protocol. |
| DISTANCE: | Administrative distance |
| 255 | 0 - 255 |
This parameter defines the distance that will be used for route priority into IP Routing table.
| IPP: | IP port |
| See below | 0..63, NONE, * |
This parameter defines the IP port value. It is allowed only when PROT: parameter is set to STATIC.
The value "NONE" stands for "no IP port".
The value "*" stands for "any IP port".
In Abilis CPX all routing types are managed through a single IP routings table, which is built in memory adding the static, connected and dynamic routing.
Contrarily to the dynamic routing, static and connected ones must be stored into a not volatile support (i.e. into the floppy disk) in order to be re-used after each Abilis CPX restart.
Connected routing are obtained from the IP ports configurations, therefore they are implicitly saved in a permanent way in the same configuration set of IP ports.
On the other hand, static routings are separately saved by the Abilis CPX through the table of saved static IP routings.
The table of saved static IP routings can hold up to 255 routings; it is automatically kept aligned with the IP routings table content and it is automatically saved on the floppy disk by the execution of SAVE CONF command.
On running Abilis CPXs it is also possible to inspect the content of the table of saved static IP routings, without being able to modify it directly.
On the contrary, using the off-line configurator command interpreter, it is possible to display and modify the content of the table of saved static IP routings freely.
All commands for managing table of saved static IP routings are described in the section Saved static IP routing of the chapter Commands relating to the IP Router.
Commands that are available from the command interpreter of working Abilis CPXs are:
D IPRS and D SIPRCommands that are available from off-line configuration command interpreter are:
A IPRS and A SIPRHere is an example of the visualization of all the saved static IP routings. Shown values are only examples:
[18:14:08] ABILIS_CPX: D SIPR +-----+-------+-----------------+-----------------+-----------------+------+ | ID: | HIDE: | NET: | MASK: | GW: | IPP: | +-----+-------+-----------------+-----------------+-----------------+------+ | 0 | NO | 001.001.001.001 | 255.255.255.255 | 000.000.000.000 | 1 | | 1 | NO | 001.001.001.001 | 255.255.255.255 | 000.000.000.000 | NONE | | 3 | NO | 002.002.002.002 | 255.255.255.255 | 000.000.000.000 | NONE | | 5 | YES | 002.002.002.002 | 255.255.255.255 | 000.000.000.000 | 10 | | 6 | NO | 002.002.002.003 | 255.255.255.255 | 000.000.000.000 | 10 | | 8 | YES | 005.005.005.005 | 255.255.255.255 | 000.000.000.000 | 5 | | 9 | NO | 005.005.005.006 | 255.255.255.255 | 000.000.000.000 | 6 | | 10 | NO | 010.000.000.001 | 255.255.255.255 | 000.000.000.000 | 5 | | 11 | NO | 032.032.032.032 | 255.255.255.255 | 000.000.000.000 | 32 | | 13 | NO | 192.168.006.000 | 255.255.255.000 | 192.168.000.251 | 0 | | 14 | NO | 192.168.008.000 | 255.255.255.000 | 192.168.000.251 | 0 | | 15 | NO | 002.002.000.000 | 255.255.000.000 | 000.000.000.000 | 40 | | 16 | NO | 010.000.000.000 | 255.255.000.000 | 192.168.000.253 | 0 | +-----+-------+-----------------+-----------------+-----------------+------+
As it is possible to note, the static IP routing identifiers do not have to be strictly sequential.
| ID: | IP routing identifier |
| no value | from 0 up to 254 |
It is the identifier of the saved static IP routing. It unambiguously identifies the routing entry and it is used for any operations of insertion, modification, deleting.
The table of saved static IP routings can hold up to 255 routings. They are indexed starting from 0 up to 254.
Identifiers do not have to be strictly sequential, i.e. the table can contain "empty" places.
Deleting operations do not cause a table re-sorting, but simply leave the entry of the removed routing free. Vacancies are re-assigned when a new static IP routing is going to be created.
The order of the saved static IP routings is not meaningful: at every CPX start or every time the command INIT IPR is executed, the saved static IP routings are added the IP routings table and inserted into in the correct position.
| HIDE: | Hiding static routings from dynamic routing protocols like RIP and OSPF. |
| NO | NO, YES |
It sets whether the static routing has to be hidden to the other dynamic routing protocols like RIP and OSPF.
If the parameter is set to "NO", the routing will be inserted in the RIP and OSPF local table.
Setting the parameter to "YES", the routing won't be inserted in the RIP and OSPF local table.
| NET: | IP address identifying the destination network |
| 000.000.000.000 | see table |
It sets the destination network IP address. The allowed values are shown in the following table:
| HEX: | 00000000 | 01000000 - 7EFFFFFF | 80000000 - DFFFFFFF |
|---|---|---|---|
| DDN: | 0.0.0.0 | 1.0.0.0 - 126.255.255.255 | 128.0.0.0 - 223.255.255.255 |
IP addresses of class D and E are not currently supported.
Doing the "logical AND" between values of this parameter and MASK:, the result should be the destination network itself, if not the message "CONFLICTING VALUE" will be shown and the value refused.
| MASK: | Destination network mask |
| 255.255.255.255 | 0 - 255.255.255.255 |
It sets the mask related to the destination network. The parameter can only be configured to values that contain sequence of bit set to 1, estimated leaving from the most meaningful bit towards the less meaningful one.
Doing the "logical AND" between values of this parameter and NET:, the result should be the destination network itself if not the message "CONFLICTING VALUE" will be shown and the value refused.
| GW: | IP address of the destination gateway [1] |
| 000.000.000.000 | see table |
It sets the IP address of the destination gateway. The allowed values are shown in the following table:
| HEX: | 00000000 | 01000000 - 7EFFFFFF | 80000000 - DFFFFFFF |
|---|---|---|---|
| DDN: | 0.0.0.0 | 1.0.0.0 - 126.255.255.255 | 128.0.0.0 - 223.255.255.255 |
IP addresses of class D and E are not currently supported.
| IPP: | IP port where to route to |
| NONE | 0 - 63, NONE |
It sets the IP port where to route the IP datagram.
The value "NONE" stands for "no IP port" it can be used for deactivating the IP routing without deleting it.
IP source routing is an extended way to define paths to reach hosts and networks.
Usually routing behaviour consists of checking the destination address for each incoming IP datagram or
internally generated IP datagram that must be forwarded to a network.
The list of entries that specify the path for every destination is present into Abilis CPX IP routings table and moreover static routings are separately saved by the Abilis CPX through the table of saved static IP routings. These tables can be considered as a destination routing tables.
The table of IP source routings is similar to the table of saved static IP
routings; but it allows the specification of the source routing network address/mask, in addition to the
destination network address/mask, to the destination gateway IP address and to the outgoing IP port.
This is an important addition because it allows to specify which source addresses can match the routing.
Rules for IP datagrams forwarding are the same of a destination table, plus an additional match with the IP source address.
List of addresses is strictly sorted in order to assign the most selective address/mask for routing detection.
The sorting rules are the following:
The interaction between IP source routings and destination routings is very important.
In the case case of matching in both source and destination routings tables
(and the destination net/mask matching of both tables are the same), the source routing has an higher priority.
The table of IP source routings can hold up to 255 entries; it is automatically kept aligned with the IP routings table content and it is automatically saved on the floppy disk by the execution of SAVE CONF command.
On running Abilis CPXs it is also possible to inspect the content of the table of IP source routings, without being able to modify it directly.
On the contrary, using the off-line configurator command interpreter, it is possible to display and modify the content of the table of IP source routings freely.
All commands for managing table of IP source routings are described in the section IP source routing of the chapter Commands relating to the IP Router.
Command that is available from the command interpreter of working Abilis CPXs is:
D IPSRCommands that are available from off-line configuration command interpreter are:
A IPSRHere is an example of the visualization of all the IP source routings. Shown values are only examples:
[11:02:59] ABILIS_CPX: D IPSR
+-----+--------------------+--------------------+-----------------+------+----+
| ID: | NET:/MASK: | SRNET:/SRMASK: | GW: | IPP: | UN:|
+-----+--------------------+--------------------+-----------------+------+----+
| 0 | 001.001.001.001/32 | 005.005.005.005/32 | 000.000.000.000 | NONE | NO |
| 1 | 002.002.000.000/16 | 005.005.005.005/32 | 000.000.000.000 | 0 | NO |
| 2 | 002.002.000.000/16 | 005.005.005.005/32 | 000.000.000.000 | NONE | NO |
| 3 | 002.002.000.000/16 | 005.005.005.005/32 | 000.000.000.000 | 2 | YES|
| 4 | 002.002.000.000/16 | 005.005.005.005/32 | 000.000.000.000 | 1 | YES|
+-----+--------------------+--------------------+-----------------+------+----+
As it is possible to note, the IP source routing identifiers do not have to be strictly sequential.
| ID: | IP routing identifier |
| no value | from 0 up to 254 |
It is the identifier of the IP source routing. It unambiguously identifies the routing entry and it is used for any operations of insertion, modification, deleting.
The table of IP source routings can hold up to 255 routings. They are indexed starting from 0 up to 254.
Identifiers do not have to be strictly sequential, i.e. the table can contain "empty" places.
Deleting operations do not cause a table re-sorting, but simply leave the entry of the removed routing free. Vacancies are re-assigned when a new IP source routing is going to be created.
The order of the IP source routings is not meaningful: at every CPX start or every time the command INIT IPR is executed, the IP source routings are added the IP routings table and inserted into in the correct position.
| NET: | Destination network |
| 000.000.000.000 | see table |
It sets the destination network.
The destination network address and the related mask can be specified either using the in Slash Notation (e.g. NET:x.x.x.x/yy) or using the Dotted Decimal Notation for both the network address and the related mask (e.g. NET:x.x.x.x MASK:y.y.y.y).
Allowed values for the destination network address are shown in the following table:
| HEX: | 00000000 | 01000000 - 7EFFFFFF | 80000000 - DFFFFFFF |
|---|---|---|---|
| DDN: | 0.0.0.0 | 1.0.0.0 - 126.255.255.255 | 128.0.0.0 - 223.255.255.255 |
IP addresses of class D and E are not currently supported.
When Slash Notation is used, valid values for the network mask mast be in the range [0-32]; while values in the range [0.0.0.0 - 255.255.255.255] are accepted in Dotted Decimal Notation. Valid mask values must contain sequence of bit set to 1, estimated leaving from the most meaningful bit towards the less meaningful one.
Doing the "logical AND" between destination network address and the mask values, the result should be the destination network address itself; if not the message "CONFLICTING VALUE" will be shown and the value refused.
| MASK: | Destination network mask |
| 255.255.255.255 | 0.0.0.0 - 255.255.255.255 |
It sets the mask related to the destination network, expressed in Dotted Decimal Notation.
Valid mask values must contain sequence of bit set to 1, estimated leaving from the most meaningful bit towards the less meaningful one.
Doing the "logical AND" between values of this parameter and NET:, the result should be the destination network itsef; if not the message "CONFLICTING VALUE" will be shown and the value refused.
The destination network mask value can also be configured using the NET: parameter, using the Slash Notation. In this case the network mask mast be a value in the range [0-32].
| SRNET: | Source network |
| 000.000.000.000 | see table |
It sets the source network.
The source network address and the related mask can be specified either using the in Slash Notation (e.g. SRNET:x.x.x.x/yy) or using the Dotted Decimal Notation for both the network address and the related mask (e.g. SRNET:x.x.x.x SRMASK:y.y.y.y).
Allowed values for the source network address are shown in the following table:
| HEX: | 00000000 | 01000000 - 7EFFFFFF | 80000000 - DFFFFFFF |
|---|---|---|---|
| DDN: | 0.0.0.0 | 1.0.0.0 - 126.255.255.255 | 128.0.0.0 - 223.255.255.255 |
IP addresses of class D and E are not currently supported.
When Slash Notation is used, valid values for the network mask mast be in the range [0-32]; while values in the range [0.0.0.0 - 255.255.255.255] are accepted in Dotted Decimal Notation. Valid mask values must contain sequence of bit set to 1, estimated leaving from the most meaningful bit towards the less meaningful one.
Doing the "logical AND" between source network address and the mask values, the result should be the source network address itself; if not the message "CONFLICTING VALUE" will be shown and the value refused.
| SRMASK: | Source network mask |
| 255.255.255.255 | 0 - 255.255.255.255 |
It sets the mask related to the source network, expressed in Dotted Decimal Notation.
Valid mask values must contain sequence of bit set to 1, estimated leaving from the most meaningful bit towards the less meaningful one.
Doing the "logical AND" between values of this parameter and SRNET:, the result should be the source network itsef; if not the message "CONFLICTING VALUE" will be shown and the value refused.
The source network mask value can also be configured using the SRNET: parameter, using the Slash Notation. In this case the network mask mast be a value in the range [0-32].
| GW: | IP address of the destination gateway [1] |
| 000.000.000.000 | see table |
It sets the IP address of the destination gateway. The allowed values are shown in the following table:
| HEX: | 00000000 | 01000000 - 7EFFFFFF | 80000000 - DFFFFFFF |
|---|---|---|---|
| DDN: | 0.0.0.0 | 1.0.0.0 - 126.255.255.255 | 128.0.0.0 - 223.255.255.255 |
IP addresses of class D and E are not currently supported.
| IPP: | IP port where to route to |
| NONE | 0 - 63, NONE |
It sets the IP port where to route the IP datagram.
The value "NONE" stands for "no IP port" it can be used for deactivating the IP routing without deleting it.
| UN: | Unconditional source routing |
| NO | NO, YES |
It sets the source routing to unconditional.
Print this page