
User manual XC-32 XC-320 XC-4200
Before sending an IP frame, Xcell consults its routing table in order to find an entry
indicating the route to use.
In the following example, terminals connect to server thanks to Xcell.
Note that the server is to be found on the sub-network
192.168.1.0
at the address
192.168.1.2
and that Xcell belongs to the sub-network
192.168.2.0
at the address
192.168.2.2
. A bridge helps to the interconnection of the two sub-networks :
Figure 5 - Network example to make a routing table
To send IP frames to server, you must necessarily inform Xcell that these frames run
through the
192.168.2.1
router.
There are three manners for this :
The first consists in informing Xcell that all IP frames intended for the
192.168.1.2
server
have to be sent to the
192.168.2.1
router :
ROOT>> route add host eth0 192.168.1.2 192.168.2.1 255.255.255.255
Ok!
ROOT>> route static
Kernel routing table
Destination Gateway Genmask Typ Iface
192.168.1.2 192.168.2.1 255.255.255.255 host eth0
The second consists in informing Xcell that all IP frames intended for the
192.168.1.0
network have to be transmitted to the
192.168.2.1
router :
ROOT>> route add net eth0 192.168.1.0 192.168.2.1 255.255.255.0
Ok!
ROOT>> route static
Kernel routing table
Destination Gateway Genmask Typ Iface
192.168.2.0 0.0.0.0 255.255.255.0 net eth0
-20-