Imola/Lipari Quick Start Guide - · PDF filebasic operations & cli commands ... 5 gprs / edge / umts / hsdpa / hsupa / lte y ... (imola/lipari quick start guide ar cli p. imola/lipari

Imola/Lipari Quick Start Guide

Basic operations & CLI commands

ver. 1.1

IMOLA/LIPARI QUICK START GUIDE 2

Published by:

Tiesse S.p.A.

Headquarter, R&D, Production and Commercial offices 10015 Ivrea (TO) Via Asti, 4.

Tel: +39-0125-230544 Fax:+39-0125-631923

e-mail: [email protected] sito: www.tiesse.com

© Copyrights Tiesse S.p.A.

© Copyrights Tiesse S.p.A. - All rights reserved.

Any disclosure, derivation or reproduction of this document, even partial, is strictly prohibited without

prior written authorization by Tiesse S.p.A.

Intellectual property rights:

Registered trademarks, trademarks, authors‟ rights and all other names contained in this document are

property of their respective owners.

Tiesse S.p.A. respects others‟ intellectual property rights and asks its clients and users to do the same.

Last update: June 5th

2017

Attention! In this document are explained only a restricted and selected group of commands and features,

find more in the Imola/Lipari User Guide, available at www.tiesse.com

http://www.tiesse.com/



SAFETY INSTRUCTIONS

Use exclusively the power kit supplied. Plug the power directly into a wall socket properly earthed.

In case of a model without the ON/OFF switch, place the device as close as possible to the 230V wall outlet.

The mains plug must be easily accessible. To turn off the router, power connection must be removed from

the wall outlet.

Do not place the system where the power cable can be stepped on.

Do not place objects on the power cable.

If you need to disconnect the power for installation jobs, be sure to unplug the power from the wall socket.

GSM antennas and / or Wi-Fi, where the router model requires their use, must not be placed in a stable

manner at a distance of less than 20 cm from all persons.

In case of a model equipped with rear bush for grounding (see picture pag 14): connect the device to the

power system ground via lug and yellow-green cable.

SIM MANAGING

(Only for models in which it is provided)

Please, refer to the SIM Installation User Guide, available on Tiesse's website: http://www.tiesse.com

CAUTION! Before removing the cover:

Turn off the device

Unplug the telecommunication cables (xDSL, ISDN)

Unplug the power cable from the wall socket

Unplug GSM or Wi-Fi aerials if present

After you worked on the router:

Close the device and secure the cover as shown in the instructions

Plug the power cable into the wall socket

Plug the telecommunication cables (xDSL, ISDN)

Plug GSM or Wi-Fi aerials if present

Turn on the device

IF THE ROUTER DOESN’T WORK

Do not intervene, in any way, on the device

Contact Tiesse via e-mail at [email protected] to begin the process of repair or replacement

under warranty.



EMC, R&TTE AND RED CONFORMITY

Tiesse S.p.A. ensures that Imola products meet the essential requirements of European Directives:

2014/30/UE - EMC Directive

2014/35/UE – Low voltage Directive

2014/53/UE – RED Directive

2011/65/EU - RoHS directive (Restriction of Hazardous Substances) that limit the use of hazardous

materials in the manufacture of electric or electronic devices

and to the previously existing directive, as well as the relevant harmonized technical standards.

Features of the devices equipped with radio interface:

Frequency Range:

Mobile: 824 MHz – 2690 MHz

Wi-Fi: 2400 MHz – 2483 MHz

Maximum RF Tx Power: 2W

The products of Tiesse S.p.A. are manufactured to prevent behavior that does not comply with Directive

2014/53 / EU.

The full text of EU Declaration of Conformity and User Guides of Tiesse S.p.A.‟s products are available at

the following internet address: www.tiesse.com

RAEE CONFORMITY

USER INFORMATION

According to art. 26 of Legislative Decree March 14, 2014, n.49: "Implementation of the

Directives 2012/19/EU, on electrical and electronic equipment waste".

The crossed-out wheelie bin symbol (Waste Electrical and Electronic Equipment Directive –

WEEE Directive) on Tiesse's routers and packaging indicates that the product must be

collected separately from normal waste at the end of its life.

The recycling of this equipment at the end of its life is organized and managed by Tiesse

S.p.A..

The user who wishes to dispose of this equipment must contact Tiesse S.p.A. by e-mail at

[email protected] address and follow the system that Tiesse has adopted to allow the separate collection

of the device at end of life.

The separate collection for the subsequent recycling, treatment and environmentally compatible disposal

of the device, helps to prevent negative effects on the environment and health and promotes the reuse

and/or recycling of the materials making up the equipment.

Illegal dumping of the product by the owner involves the application of administrative sanctions provided

by law.

TERMS OF USE

The module Imola and all its components must be used solely and exclusively for the purpose for which

they were appointed. Tiesse disclaims any liability caused by improper or clumsy use of the module or one

or more parts of which it is composed.


mailto:[email protected]


SUMMARY

SAFETY INSTRUCTIONS .............................................................................................................................. 3

SIM MANAGING ................................................................................................................................................... 3

IF THE ROUTER DOESN‟T WORK ......................................................................................................................... 3

SUMMARY ............................................................................................................................................................5

MODELS TO WHICH THIS GUIDE IS APPLICABLE ..........................................................................1

INTRODUCTION ...............................................................................................................................................2

MAIN FUNCTIONALITIES ..................................................................................................................................... 4

ACCESSING ROUTER ......................................................................................................................................5

ACCESS VIA TTYS0 PORT .................................................................................................................................... 5

ttyS0 port settings ......................................................................................................................................... 5

ACCESS VIA ETH0 AND ETH1 PORTS ................................................................................................................. 5

eth0/eth1 default settings ............................................................................................................................ 6

APPROACH THE ROUTER ...........................................................................................................................7

USERNAME AND PASSWORD ............................................................................................................................... 7

PASSWORD RECOVERY PROCEDURE ................................................................................................................... 7

REBOOT OF THE ROUTER ................................................................................................................................... 7

SOFTWARE VERSION AND MODEL ...................................................................................................................... 8

BASIC ROUTER CONFIGURATION ..........................................................................................................9

CONFIGURATION PROCEDURE............................................................................................................................ 9

COMMAND-LINE INTERFACE (CLI) GUIDE ......................................................................................................... 10

ETHERNET INTERFACE.............................................................................................................................. 12

INTERFACE CONFIGURATION ........................................................................................................................... 12

DISPLAYING INTERFACE STATUS ...................................................................................................................... 12

ETHERNET LEDS MEANING................................................................................................................................ 13

ADSL INTERFACE.......................................................................................................................................... 14

CONFIGURATION .............................................................................................................................................. 14

DISPLAYING ADSL CONFIG, STATUS AND STATISTICS .................................................................................... 17

ADSL LEDS MEANING ........................................................................................................................................ 18

MOBILE INTERFACE .................................................................................................................................... 19

CONFIGURATION .............................................................................................................................................. 19

DISPLAYING GPRS CONFIGURATION, STATUS AND STATISTICS ..................................................................... 22

GPRS LEDS MEANING ........................................................................................................................................ 24

SMS HANDLING ................................................................................................................................................. 25

MOBILE SERVICE CONNECTION: THE HELLO COMMAND ................................................................................ 28

SIM PIN UNLOCK ............................................................................................................................................... 28

IMSI AND IMEI READING ................................................................................................................................... 29

WI-FI INTERFACE ........................................................................................................................................... 30

CONFIGURATION .............................................................................................................................................. 30

DHCP PROTOCOL ........................................................................................................................................ 33

DHCP-SERVER CONFIGURATION ....................................................................................................................... 33

MAC ADDRESS CONTROL ................................................................................................................................. 34


DHCP SERVICE‟S MULTIPLE INSTANCES ........................................................................................................... 34

STATIC ROUTES ............................................................................................................................................ 37

CONFIGURATION .............................................................................................................................................. 37

DISPLAYING STATIC ROUTES ............................................................................................................................ 37

SYSLOG .............................................................................................................................................................. 39

LOGGING FUNCTION CONFIGURATION............................................................................................................ 39

TIMEZONE ........................................................................................................................................................ 42

TIMEZONE CONFIGURATION ............................................................................................................................ 42

CONFIGURATION EXAMPLES ................................................................................................................. 43

DHCP SERVER .................................................................................................................................................... 43

ADSL NAT WITH AN IP LAN CUSTOMER WITH PUBLIC AND PRIVATE IP .......................................................... 43

ADSL IP WITH A POOL OF PUBLIC AND PRIVATE IP .......................................................................................... 44

GPRS ON PUBLIC APN (INTERNET NAVIGATION) .............................................................................................. 45

GPRS ON PRIVATE APN WITH GRE TUNNEL ...................................................................................................... 46

ADSL WITH RADIO MOBILE BACKUP ................................................................................................................. 48

Models to which this guide is applicable


MODELS TO WHICH THIS GUIDE IS APPLICABLE

This document is valid for all the models with the software version from 4.4.2-5 and onwards.

To check the software version, refer to the "Accessing Imola" chapter; if you find that your device has a

previous version than the 4.4.2-5, please contact Tiesse‟s support team to learn if you can update it or to

receive the User Guide of the software version you have (e-mail contact: [email protected]).

Attention!

This document is a Quick Start Guide, different from the complete User Guide.

Here are explained only a limited and selected group of commands and features, you can find them all in

the Imola/Lipari User Guide, available at www.tiesse.com

mailto:[email protected]


Introduction


INTRODUCTION

Download the complete Imola/Lipari User Guide at www.tiesse.com

Tiesse provides a range of network devices that offers typical Router functions in both wired and wireless

configurations (supporting ISDN/HDSL/ADSL/VDSL/G.SHDSL/GBE on fixed networks and GPRS/EDGE,

UMTS/HSDPA/HSUPA/LTE connections on mobile networks). Devices designed in order to connect local and

remote sites in particular when security, service availability and network performance are of prime

importance.

IMOLA and LIPARI routers are based on 3 functional modules, not necessarily physically separate: a module

containing the main features; a module hosting protocol controllers and WAN interface; a power supply

module which may supply both an AC/DC converter (Internal Power Supply) and a DC/DC converter

(External Power Supply).

In order to distinguish the different characteristics and communication interfaces, each model is identified

by the name Imola or Lipari XYZK, where:

X identifies the type of WAN connection on mobile network

Y identifies the type of local network connection

Z identifies the type of WAN connection on wired network

K identifies the type of LAN port (FE or GBE)

The values are as follows:

1 - In the model with 8 Ethernet ports, the 6, 7 and 8 are always FE independently of the other 5, which may be the FE or GBE

X

0 No mobile network connection

1 GPRS (models no longer in production)

2 GPRS / EDGE

3 GPRS / EDGE / UMTS / HSDPA

4 GPRS / EDGE / UMTS / HSDPA / HSUPA

5 GPRS / EDGE / UMTS / HSDPA / HSUPA / LTE

Y

0 1 Ethernet port present

1 2 Ethernet ports

2 5 switch Ethernet ports (4 ports in LX version)

3 1 Wi-Fi (besides Ethernet switch)

8 8 Ethernet ports1

Z

0 No WAN connection

1 ADSL

2 ADSL2+

3 HDSL

4 SHDSL

6 VDSL2

K 0 Ethernet ports FE 10/100 Mbps

2 Ethernet ports GBE 10/100/1000 Mbps

Introduction


Only for Imola models, some additional expansion cards can be mounted to provide:

asynchronous RS232 serial connectivity through two DB9 ports or a DB9 and a DB25 port, both for

connecting serial devices such as RTU, CBT, SCADA and various controllers (IKR)

direct connectivity on Fiber Optic via two SFP ports

V.35 connection interface (IKH)

Wi-Fi connectivity (IKW)

Imola models tipically has an internal power supply; to power-on the device, plug the cable power directly

into a wall socket properly earthed and push the I/0 button.

Some models are also available with external power supply, like some models with plastic chassis and

Imola LX and Lipari models. These models have not the ISDN BRI port and the number of Ethernet

Interfaces are limited to 1, 2, or 4 instead of 5.

Lipari has a module of external power supply AC/DC 5Vdc / 1A

It is possible to provide an external DC/DC 9-36V supply power, as in the image below.

In case of a model equipped with rear bush for grounding (see picture): connect the device to the

power system ground via lug and yellow-green cable.

EXT Power supply

EXT Power supply

EXT Power supply

EXT Power supply

INT Power supply

Introduction


MAIN FUNCTIONALITIES

Other functions may be associated to the communication services:

ACLs support

Authentication and accounting support via RADIUS

AAA support via Tacacs+

NAT/PAT functions

Stateful Firewalling functions

VRF-Lite support

VPN with IPSec 3DES Encryption

Tunnel GRE

L2TPv2 tunnel

L2TPv3 tunnel both static and dynamic

PPTP Tunneling

Open VPN Tunneling

Easy VPN Tunneling

Advanced Routing (Policy routing)

RIP, OSPF, BGP routing and BFD support

PIM protocol support (Protocol Independent Multicast) in Dense mode, Sparse mode and Source

Specific Multicast

IGMP Proxy and IGMP Snooping support

Band Optimization with QoS (Quality of Service)

VRRP support (Virtual Router Redundant Protocol)

Functions of IP SLA with Responder Time Reporter

SNMP v1/v2/v3

TR-069 support

Client and Server DHCP

Local and remote logging

Client and Server Telnet and SSH

Administration and control tools (ping, traceroute, debug ip packet, …)

The Command Line Interface (CLI), owned by Tiesse S.p.A., allows the configuration and management of

the system in a simple and guided way.


Accessing router


ACCESSING ROUTER


Access can be made via console port (can be DB9 male connector or RJ45 due to the model) on the front of

Imola, with a proper cable, using any program of terminal emulation (HyperTerminal, Minicom, Putty, ...) or

via a Telnet connection to one of the IP addresses present on Router.

Imola has a single Fast Ethernet port identified by the label eth0 and a 5 ports integrated switch (8 in some

models), where the ports are numbered 1 to 5 (or 8). In the factory configuration all the switch ports refers

to a single IP address and the logic interface is named eth1. The connection to this port can be made via

any of the available ports in the switch.

Imola LX models have only a 4 ports integrated switch, each numbered 1 to 4. The factory configuration,

all the ports refers to a single IP address on the logical interface eth0.

In case of direct connection to the eth0 port of Imola a LAN cross cable should be used. Thanks to the

auto-mdx function any kind of cable may be used in case of connection to any port of the integrated

switch.

ACCESS VIA TTYS0 PORT

Cable Type: null-modem DB9 or RJ45

IMOLA Port: ttyS0 port

Application: Windows HyperTerminal (or similar)

ttyS0 port settings

When using the ttyS0 port to access Imola, the system used for the connection has to be configured in the

following manner:

Bits per second: 9600

Data bits: 8

Parity: none

Stop bit(s): 1

Flow Control: N.A. (Not Applicable)

ACCESS VIA ETH0 AND ETH1 PORTS

Cable Type: LAN (Ethernet type)

IMOLA Port: eth0 or eth1 port

Application: Telnet (or similar)

Accessing router


eth0/eth1 default settings

eth0 port eth1 port

IP Address 10.10.113.1 172.151.113.1

Netmask 255.255.0.0 255.255.0.0

Broadcast 10.10.255.255 172.151.255.255

Network Address 10.10.0.0 172.151.0.0

Imola and Lipari default configuration includes:

eth0 address (service): 10.10.113.1/16

eth1 address (and integrated switch): 172.151.113.1/16

SNMP v1 and v2 enabled, with public community for read-only accesses and Tiesseadm for read-

write accesses.

syslog disabled

ADSL disabled

GPRS disabled

DHCP Client/Server disabled

Filters, ACL, Ip Rules disabled

Dynamic Routing and tunneling disabled

Tiesse spa - IMOLA Interworking Unit

No Radius configured. Using Local authentication

login: root

Password:

local: Authentication OK

Service Type is: Administrative-User

Idle timeout is set to 3600 seconds

Connected Users:

ttyp1 root

You are logged on ttyS0

The configuration environment presents this prompt: username@hostname where username is the login

and hostname is the configurable name of the system. Few session‟s informations like the service type

(Administrative-User or Login-User), the session inactivity timeout, the users connected and the

virtual tty used are show at the beginning.

Approach the Router


APPROACH THE ROUTER


USERNAME AND PASSWORD

In order to access router, login and password need to be specified.

Factory configuration is:

login: root

password: tiesseadm

It is possible to change the root user password thanks to the CLI command:

change_password root

which in interaction modality asks to introduce the new password.

PASSWORD RECOVERY PROCEDURE

On certain models of router, if you use a serial connection, you can apply as follow:

At the router prompt, press simultaneously the key “Shift” (uppercase button) and the key “z”

When the prompt is up, type the commands:

setenv config factory

saveenv

boot

With those commands the router reset itself to the factory configuration and the previous settings are lost.

REBOOT OF THE ROUTER

The router can be rebooted using the command:

reboot

After the reboot, all the unsaved changes (through the command save), will be lost.

A time programmed reboot can be configured, specifying after how many seconds this must be done. The

command is:

schedule-reboot wait N

The command prompt is returned to the user, so that other commands can be executed or to end the

current session.

The programmed reboot can be disabled with the command:

no-schedule-reboot

Approach the Router


SOFTWARE VERSION AND MODEL

It is possible to read the router‟s model through the command show model:

root@IMOLA> show model

Tiesse Imola 5262 Multiprotocol Router

The command show version shows the software‟s version.

root@IMOLA> show version

Imola version: 5.4.5-8

The version number adopts the naming convention: 5.x.y-N

The first number identifies the hardware platform used in the production.

The value of x indicates the major number, which changes in case of relevant functionality. The

value of y indicates the minor number, which increases when other independent functionality,

which do not affect other software‟s functions, are added.

The suffix N indicates the build number. It increases in case of small bug-fixing which do not

require non-regression tests.

Basic router configuration


BASIC ROUTER CONFIGURATION


In order to configure Imola the operator has a character interface known as Command Line Interface (CLI).

Using the CLI it is possible to configure, activate and check interfaces and available services present on

Router. This is a short quick guide where only few services and functionalities are explained, please refer

to full ImolaLipari_UserGuide available on Tiesse's website http://www.tiesse.com for a complete guide to

CLI commands and services.

CONFIGURATION PROCEDURE

The configuration of Imola/Lipari includes the following phases:

configuration

check

parameters activation

storing

To configure and activate you can use commands with the prefix:

set

To check the status you can use the command with prefix:

show

In order to save the complete and checked configuration the command:

save

The command:

restore

is used to recover specific configurations.

There are three different types of configuration:

current saved started

The current configuration contains all the values set during configuration.

The saved configuration is that saved in Imola non-volatile memory using the save command and will be

used during the next boot.

The started configuration is that which was activated in the last boot operation. At the end of the boot,

before configuration begins, the three configurations are identical.

During the configuration and check phases, saved and started configurations are identical.

After the save command, the current configuration also becomes saved. Through this configuration the

device will be activated at the next boot.

It is possible to check the content of the three different configurations by using the command:

show config current|saved|started




COMMAND-LINE INTERFACE (CLI) GUIDE

Tiesse CLI has an online help which helps the user in formulating all the available commands

in a way which is syntactically and semantically correct.

Pressing the <TAB> key twice or the “?” character, all the available commands will be displayed, followed by

a brief description.

Command-line completion or display of available alternatives is possible using the <TAB> key.

When the command is incomplete, a help function is automatically called: it provides all the necessary

information for a correct completion.

Tiesse spa - IMOLA Interworking Unit

No Radius configured. Using Local authentication

login: root

Password: *********

local: Authentication OK

Service Type is: Administrative-User

Idle timeout is set to 600 seconds

Connected Users:

ttyp0 recovery_user

root@Imola>

# download record show

add_user exit restore su

help traceroute

upload change_password

ping save version clear_counter

quit set who del_user

reboot shell

root@Imola>

Some of the available commands are displayed by pressing the <TAB> key twice or ? key

root@Imola> set ?

adsl Configure adsl

alias Configure secondary address

autocmd Configure Command executed automaticaly at boot time

backup Configure Backup procedure and criteria

banner Configure banner

bgp Configure BGP Protocol

ospf Configure OSP Protocol

rip Configure RIP Protocol

eth0 Configure eth0 parameter

vrrp Configure VRRP Protocol

gre Configure GRE tunneling

....

root@Imola>

Command-line completion and listing of parameters by pressing the <TAB> key.

root@Imola> set eth1 ?



set eth1 ipaddr Configure IP address

set eth1 broadcast Confgure Broadcast Address

set eth1 dhcp-client Enable DHCP Cleinte

set eth1 netmask Configure Netmask

set eth1 description Configure a description

set eth1 no-description

....

root@Imola>

Online help

The basic rules for the setup of an interface or a service include the configuration and activation of the

configured parameters.

The commands are divided in 3 groups:

configuration command set <options>

display command show <options>

management and administration commands.

It is very common to set the configuration command by Copy&Paste: you just have to copy the

configuration from a file on your computer and then paste it in the router‟s cli.

If the command lines are many, like more than 20, and the connection to the router is made by a serial

port o via a slow connection, it can happen that some of the pasted lines are not executed. To avoid this

problem, you can use the command set-config which puts the router in an “acquiring configuration”

state, so you can paste how many command line you need.

Here is the set-config screen:

root@IMOLA> set-config

Please Copy&Paste your configuration below and then

terminate with a single "." in a new line.

Your configuration will be imported and set as current.

To abort this session and let everything unchanged type "abort".

Put here your configuration:

Ethernet interface


ETHERNET INTERFACE


INTERFACE CONFIGURATION

Ethernet interfaces are called eth0 and eth1. The first is on the left and it is normally used as a service port

or as WAN port to connect to the network to external devices, leaving internal network tasks to the eth1

interface. The LAN switch (if present) is connected to the eth1 port.

In LX models the 4-port LAN switch is connected to the eth0 port.

In order to set the IP address of an Ethernet interface the following CLI command is used:

set eth0|eth1 ipaddr <ip_address> [netmask <netmask> broadcast <broadcast>]

For example, in order to configure an eth0 interface with 10.10.9.1/16 IP address, specifying the broadcast

mode, the command is:

set eth0 ipaddr 10.10.9.1 netmask 255.255.0.0 broadcast 10.10.255.255

It is possible to enable the dynamic NAT over all outbound packets from the interface using:

set eth0 masquerade

The DHCP Client service can be set or removed for each Ethernet interface using the commands:

set eth0|eth1 dhcp-client

set eth0|eth1 no-dhcp-client

It is possible to activate (or deactivate) a description of the Ethernet interface given back by the SNMP agent

(if configured and active), by querying the Mib_II ifDescr variable, using the following commands:

set eth0|eth1 description|no-description <value>

It is possible to set the type of Ethernet connection avoiding the auto negotiation process:

set eth0|eth1 speed <my description>

where value can have one of the following values:

100BaseT4 100BaseTx-FD 10BaseT 10BaseT-HD

100BaseTx 100BaseTx-HD 10BaseT-FD 1000BaseT-FD 1000BaseT-HD

In case the switch is present, the connection parameters must be set by specific commands, which are

described in the relative switch section.

On Imola-LX models and some Lipari as well, there is only the eth0 port.

DISPLAYING INTERFACE STATUS

In order to display the configuration of an interface, the following CLI command is used:

ifconfig eth0|eth1|ppp0|wwan0|…other interface|

Which shows:

IP address

Netmask

Broadcast

Ethernet interface


MAC address

Static meters

ETHERNET LEDS MEANING

The RJ45 connector of the Ethernet interface has two LEDs indicators: one yellow on the left and one green

on the right.

LED type LED COLOR BEHAVIOUR DESCRIPTION

Ethernet interface

(2 LEDs integrated in

the connector) Left Yellow

Off The interface is damage or the

connection is running at 10Mbps

On The Ethernet interface is connected at

100Mbps

Right Green Blinking LAN activity

Adsl interface


ADSL INTERFACE


CONFIGURATION

Imola XX10 models only support ADSL connections, while XX20 models support both ADSL and ADSL2+

connections.

In ADSL connections the maximum bandwidth is:

downstream speed up to 8 Mbps

upstream speed up to 1 Mbps

In ADSL2+ connection the maximum bandwidth is:

downstream speed up to 24 Mbps

upstream speed up to 3.5 Mbps

A maximum of 8 PVCs (Permanent Virtual Circuit) is supported.

Tiesse‟s Imola and Lipari router are subject to the following conformity standards:

ADSL: G.992.1 (G.dmt) - Annex A (ADSL over POTS), G992.2 (G.lite), ANSI T1.413 issue 2

ATM: ITU T-I.361, ITU T.I.363.5, ITU T-I.432, ITU T.I.610, ITU T-I.731

RFC 2684 (former RFC 1483 Multiprotocol over ATM)

RFC 2364 (PPP over ATM)

RFC 2516 (PPP over Ethernet)

In Imola XX20 models the following standards are also supported:

G.992.3 annexA, B, I, J, L (extended reach), M (double upstream)

G.992.4 – g.Lite.bis

G.992.5 annexA, B, C, I, J, M

It is possible to configure and activate the ADSL link by using CLI commands.

The command

set adsl on

activates the ADSL interface.

The command

set adsl off

deactivates the ADSL interface

The command

set no-adsl

deactivates the ADSL interface and disables the configuration.

Before the activation, the ADSL interface must be configured according to the contractual values provided

by the Service Provider.

To define the encapsulation type, the command to be used is:

Adsl interface


set adsl encap pppoa-llc|pppoa-vcmux|pppoe-llc|pppoe-vcmux rfc1483-llc|rfc1483-vcmux

To configure the number and the type of PVC , use:

set adsl pvc_number <value>

set adsl pvc atmX vpi <value> vci <value>

pvc_number can have a maximum value of 82

and atmX will be atm0, atm1,…atm7. The default value of

pvc_number is 1.

In order to configure vpi (value 8) and vci (value 35):

set adsl pvc atm0|…|atm7 vpi <value> vci <value> [pcr <value>]

If the encapsulation type is rfc1483-vcmux or rfc1483-llc (protocols described in RFC 1483, Multiprotocol

Encapsulation over ATM Adaptation Layer 5) it is necessary to define an IP address through the command:

set adsl pvc atm0|…|atm7 ipaddr <value>

To remove the IP address:

set adsl pvc atm0|…|atm7 no-ipaddr

Otherwise, according to the information received from the Service Provider, the following commands can

be used:

set adsl pvc atm0|…|atm7 ipaddr <value>

set adsl pvc atm0|…|atm7 nexthop

set adsl pvc atm0|…|atm7 netmask <value>

set adsl pvc atm0|…|atm7 mtu <value>

To assign an IPv6 address the command is:

set adsl pvc atm0|…|atm7 ipv6addr X:X::X:X/M

A default route could be required:

set adsl pvc atm0|…|atm7 default-route

To enable NAT functions:

set adsl pvc atm0|…|atm7 masquerade

And to remove the options:

set adsl pvc atm0|…|atm7 no-ipaddr

set adsl pvc atm0|…|atm7 no-nexthop

set adsl pvc atm0|…|atm7 no-mtu

set adsl pvc atm0|…|atm7 no-default-route

set adsl pvc atm0|…|atm7 no-masquerade

When PPPoA (PPP over ATM) or PPPoe (PPP over Ethernet) encapsulation types are used, the login and

password for authentication must be defined with:

set adsl login <value> password <value>

It is possible to configure the type of ATM traffic per PVC as follows:

set adsl pvc atm0|…|atm7 service <service-type>

2 - PPPoA and PPPoE connections can only have a single PVC.

Adsl interface


where service-type can be UBR, CBR, VBR or RTVBR. For the UBR and CBR traffic, it is possible to specify a

PCR value (Peak Cell Rate), while for VBR and RTVBR is possible to specify, in addition to PCR, the values for

SCR (Sustainable Cell Rate) and MBS (Maximum Burst Size), in the following way:

set adsl pvc atm0|…|atm7 pcr <value>

set adsl pvc atm0|…|atm7 scr <value>

set adsl pvc atm0|…|atm7 mbs <value>

The value provided for PCR and SCR is expressed in cells / sec, while the value for MBS is expressed in

bytes. To remove the options set:

set adsl pvc atm0|…|atm7 no-service

set adsl pvc atm0|…|atm7 no-pcr

set adsl pvc atm0|…|atm7 no-scr

set adsl pvc atm0|…|atm7 no-mbs

It is possible to vary the length of the transmission queue on the interface associated with the pvc, in the

following way:

set adsl pvc atm0|…|atm7 qlen <value>

To remove the options set:

set adsl pvc atm0|…|atm7 no-qlen

You can set the router so that it can send the Loopback (F4/F5) OAM cells on a particular PVC. In case there

is no reply, the PVC is put on a down state.

set adsl pvc atm0|…|atm7 oma-manage [interval N]

It is also possible to put down a specified PVC manually, using the command:

set adsl pvc atm0|…|atm7 shut

To set the mode of the standard ADSL line you can use the set command-line ADSL mode, which assumes

different options depending on the model of Imola.

On Imola XX10, the options can be: ITU (Europe), ANSI and AUTO (Multimode):

set adsl line-mode itu|ansi|auto

On Imola XX20, the options can be a combination of the possible ADSL standards, like:

set adsl line-mode ADSL2 | ADSL2+/ADSL2/G.DMT/T1.413 | ADSL2 AnnexM | ADSL2/G.DMT | ADSL2+/ADSL2 | G.DMT | ADSL2+/ADSL2/G.DMT | T1.413


set adsl no-line-mode

It is also possible specify a description of the ADSL interface, which will be given back by the SNMP agent

(if configured and active) by querying the Mib_II ifDescr variable with the following commands:

set adsl description|no-description <value>


set adsl no-description

set adsl pvc atm0 no-description

Here follows an example of a valid sequence of commands to configure the ADSL interface:

set ADSL encap rfc1483-llc

set ADSL pvc-number 1

set ADSL description muxadsl

Adsl interface


set ADSL pvc atm0 vpi 8 vci 35

set ADSL pvc atm0 pcr 0

set ADSL pvc atm0 default-route

set ADSL pvc atm0 ipaddr 1.1.1.1 nexthop 2.2.2.2

set ADSL on

DISPLAYING ADSL CONFIG, STATUS AND STATISTICS

It is possible to display information about configuration, PVCs, statistics and the status of the ADSL

interface by using the CLI command:

show interface adsl statistics|status

For example, the command:

show interface adsl status

produces the following output:

root@Imola> show interface adsl status

General Information

---------------------------------------------------------------------------

FW Revision: 0x061d 0x1235 0x0009

Near End Data Far End Data

Vendor country: 0xb5 0xb5

Vendor code: AWRE BDCM

Vendor product code: 0x5052 0xf2a1

Line Operational Data

---------------------------------------------------------------------------

ADSL Standard: ITU-T G.992.5 annex A


Attenuation (db): 40.5 22.7

Noise Margin (db): 11.1 14.2

Output Power (dbm): 12.3 19.1

Relative Capacity Occupancy (%): 92 101

Channel Operational Data

---------------------------------------------------------------------------


Datarate (Interl/Latency-0) (kb/s): 830 6546

Datarate (Fast/Latency-1) (kb/s): 0 0

Errors Data

---------------------------------------------------------------------------


CRC (Interl/Latency-0): 6793 0

CRC (Fast/Latency-1): 0 0

FEC (Interl/Latency-0): 64572 0

FEC (Fast/Latency-1): 0 0

HEC (Interl/Latency-0): 55677 0

HEC (Fast/Latency-1): 0 0

No cell delineation (Bearer-1): yes none

Atm Cell Counter Statistics

---------------------------------------------------------------------------

Adsl interface


Rx Tx

Total Cell Count (Bearer-0): 1809151150 229435580

Total Cell Count (Bearer-1): 0 0

User Total Cell Count (Bearer-0): 555032 563454

User Total Cell Count (Bearer-1): 0 0

---------------------------------------------------------------------------

Current modem state: SHOWTIME (for 1 day, 8 hr, 32 min, 57 sec)

ADSL LEDS MEANING

LED type LED COLOR BEHAVIOUR DESCRIPTION

ADSL/VDSL interface

(1 LED)

Imola XX20

Link Green

Blinking slowly Shows that the interface is ready to

establish a connection

Blinking fast

Shows that the communication with

the central has been established and

the connection is ongoing

On fixed The connection is established

ADSL interface

(3 LEDs)

Imola XX10

PW / ON

Green

On The ADSL internal modem is correctly

powered.

Link

Blinking Shows the sync phase with the central

On Shows that the synch phase has been

successful

Data Blinking Data traffic

Mobile interface


MOBILE INTERFACE


CONFIGURATION

Imola and Lipari can be used as a Router between an Ethernet and a mobile network. Imola 1XX0 supports

only GPRS connections, 2XX0 models support both EDGE and GPRS, 3XX0 models support both

UMTS/HSDPA and GPRS/EDGE, 4XX0 models support both GPRS/EDGE/UMTS/HSDPA/ and HSUPA, 5XX0

models support any mobile connection until LTE (Long Term Evolution). The choice of network is visible.

Configuration is set using the same CLI commands for a GPRS sessions.

In order to activate the Imola/Lipari mobile interface the following command is used:

set gprs on

In order to deactivate the Imola/Lipari mobile interface the following command is used:

set gprs off

In order to deactivate the GPRS interface and disable configuration the following CLI command is used:

set no-gprs

Before the activation of the GPRS interface it is necessary to configure functions and values supplied by the

Service Provider, using the following CLI commands.

APN configuration:

set gprs apn <value>

On router models 5xxx, the protocol IPv6 is supported on the mobile network and the available command

is:

set gprs apn-type <value>

where <value> can take the values: IPv4 to activate a Ipv4 session, IPv6 to activate a Ipv6 session or IPv4v6

to activate a Dual Stack IPv4-IPv6 session.

Login and password configuration for PPP authentication:

set gprs login <value> password <value>

In order to activate or deactivate the default route on GPRS connection the commands are:

set gprs default-route

set gprs no-default-route

In order to enable or disable Port Address Translation (PAT) on GPRS connection the commands are:

set gprs masquerade

set gprs no-masquerade

Once configured and started, the GPRS connection is always active. It is also possible to configure the

interface in this way: the connection ends after a specified idle time (expressed in seconds) and it is

possible to re-establish it at the next transmission request:

set gprs on-demand yes|no

set gprs idle <value>

Mobile interface


The idle parameter defines an idle time interval for the GPRS session: if no packet is transmitted or

received during this interval, the GPRS session is terminated. If the on-demand mode is not set, the session

is automatically re-established.

It is possible to calculate inactivity time only for received data and not considering transmitted data, by

using the commands:

set gprs idle 0

set gprs rx-idle <value>

In order to set the max bandwidth speed, the CLI command is (N is in Kbit/sec):

set gprs bandwidth-max N

The command:

set gprs mtu 1500

sets the Max Transfer Unit (MTU) of the GPRS interface. In some APN configurations the size of transmitted

packets is restricted to 1476. In these cases the following command is necessary:

set gprs mtu 1476

The following commands:

set gprs lcp-echo-interval

set gprs lcp-echo-failure

set the frequency of transmission of lcp echo request packets and the number of attempts before ending

the GPRS interface. It will be automatically re-established.

It is also possible to negotiate DNS parameters directly from the peer by using the command:

set gprs usepeerdns

In order to set the authentication mode on GPRS connections (the default is CHAP authentication), the

following command is used:

set gprs sgauth <auth_type_code>

Different authentication modes can be specified by using the following values:

0: no authentication

1: PAP authentication

2: CHAP authentication

3: PAP and CHAP authentication

In UMTS/HSDPA/HSUPA connection the following command should be used in order to set PAP

authentication:

set gprs directive refuse-chap

The Mobile Network (only for 2G or 3G modem) can be selected using appropriate commands:

set gprs auto-network

The Mobile Network choice is made by the radio module which automatically selects the best network at

that moment. According to the radio signal, the radio module will automatically pass from a network to

another using a roaming procedure.

set gprs umts

Mobile interface


The radio module tries to connect to the 3G Network; if it does not succeed, it tries to connect to the 2G

Network. Differently from the previous command, once the network type has been selected it does not

change until the radio module disconnection.

set gprs no-umts

Only the 2G network will be selected for radio module connection.

set gprs umts-only

Only the 3G network will be selected for radio module connection.

On the routers that have the LTE interface (like Imola 5xxx) you can use the command:

set gprs lte

that enables the modem to work on the LTE network, if available; otherwise the connectivity available in the

network cell (like 3G or 2G).

If you use set gprs lte you can specify other options to select the work frequencies or the radio

technology. In particular the command:

set gprs lte-band <value>

allows to select the working frequency on LTE network (admitted values are b1, b3, b7, b8, b20, b8-

900, b1-2100).

The command:

set gprs selrat <value>

where <value> can be:

2G-Only 3G-Only 2G-3G-Only LTE-Only LTE-Preferred 3G-LTE 2G-3G-LTE auto

allows to specify the radio access technology.

Usually, the value auto is used when you want to empower the modem to auto-select the best radio

technology to use.

If you specify the LTE-Preferred value, the router tries to register on a LTE cell and if the attempt fails, it

will do the Fall-Back over other technologies. In this case, you can use:

set gprs fallback-rat <value>

where <value> can be:

2G-Only 3G-Only 2G-3G-Only auto

In this way you determine which technology the router must use during the Fall-Back operation.

You can use the parameter lte-camping-timer in association to the value LTE-Preferred. Using this

parameter, you can specify an interval in seconds within which it is verified if the modem radio is

connected to a LTE cell. For example, you can use the syntax:

set gprs selrat LTE-Preferred

set gprs selrat lte-camping-timer 3600

Every 3600 seconds the router controls if the modem is connected to a LTE cell and if not, it tries to make

a new registration. You must remember that if the router is located in a 3G cell, the connection is

temporarily disabled.

It is possible to activate (or deactivate) a description of the GPRS interface that will be given back by the

SNMP agent (if configured and activated) by querying the Mib_II ifDescr variable through the following

commands:

Mobile interface


set gprs description <value>

set gprs no-description

Here follows an example configuration commands of a GPRS interface:

set gprs apn ibox.tim.it

set gprs login mylogin password mypasswd


set gprs masquerade

set gprs on

It is possible to activate a GSM V110 connection, instead of a GPRS one, through the following commands:

set gprs v110

set gprs apn <value>

in this case <value> is the telephone number to call.

The network interface for GPRS session is PPP and the assigned name is pppX, where X is an index which

usually has value 0 (ppp0). In the same way, an ADSL connection with PPP over ATM encapsulation (PPPoA)

is indicated by pppX. The choice of the index X depends on the order of activation of the connections: the

first connection to be activated will be ppp0 and the second one will be ppp1.

In order to avoid conflicts in the choice of name, when both ADSL PPPoA and mobile

(GPRS/EDGE/UMTS/HSDPA/HSUPA) connections are present, the following command is used:

set gprs directive unit N

The name of the interface associated with the mobile session will always be pppN, and the name of the

ADSL connection will always be ppp0. The value of N is between 1 and 9.

In 5XX0 models there is also the command:

set gprs direct-ip

It allows to use originally the mobile connection without using PPP protocol. In this case the mobile

interface is called wwan0.

On these models it is possible to configure a second APN, used simultaneously to the main one with the

commands:

set gprs apn2 <apn-name>

set gprs apn2-login <login-second-apn> password <password>

set gprs apn2type IPv4 | IPv4v6 | IPv6

In case this command is used, it is binding to set the command:

set gprs direct-ip

so that the network interface name that match the main APN would be wwan0, while wwan1 will be for the

second one.

DISPLAYING GPRS CONFIGURATION, STATUS AND STATISTICS

It is possible to display information about configuration, statistics and status of the GPRS interface. The

CLI command is:

show interface gprs config|statistics|status

For example, the command show interface gprs config produces the following output:

Mobile interface


show interface gprs config

root@Imola> show interface gprs config

Start GPRS: yes

APN: ibox.tim.it

PPP Login: mylogin

PPP Passwd: mypasswd

MTU: 576

Idle Timeout: 3600

Masquerade: yes

Deflt-Route: yes

The command show interface gprs status shows the status of the session. The video output produced

may change according to the access technology:

root@Imola> show interface gprs status

Signal Quality: +CSQ: 17,99

Network: HSDPA/UMTS

IMSI: 222017302670415 IMEI: 355841030174450

There is an active GPRS Connection:

31: ppp0: <POINTOPOINT,MULTICAST,NOARP,UP> mtu 1500 qdisc pfifo_fast qlen 3

link/ppp

RX: bytes packets errors dropped overrun mcast

40 4 0 0 0 0

TX: bytes packets errors dropped carrier collsns

77 6 0 0 0 0

inet 217.201.91.46 peer 192.168.254.254/32 scope global ppp0


Signal Power: CSQ = 23 => -67 dBm

Network: HSDPA/UMTS vodafone IT

HSDPA Category: 24 HSUPA Category: 6

Current Time: 75749 Temperature: 38

Bootup Time: 1 Mode: ONLINE

System mode: WCDMA PS state: Attached

WCDMA band: WCDMA 2100

WCDMA channel: 10838

GMM (PS) state: REGISTERED NORMAL SERVICE

MM (CS) state: IDLE NORMAL SERVICE

WCDMA L1 State:L1M_PCH_SLEEP RRC State: DISCONNECTED

RX level C0: -68 LAC: 3ABB (15035)

RX level C1: -106 Cell ID: 003A5837 (3823671)

Current Network Technology: 0,UMTS

Available Network Technology: 1,UMTS

Supported Network Technology: 2,GSM,GPRS,EDGE,UMTS,HSDPA/HSUPA,HSPA+,LTE

IMSI: 222101900000052 IMEI: 358178040098990

Mobile interface


When the Dual Carrier HSPA system is used, the line Current Network Technology

shows: DC-HSPA+.



Network: LTE I TIM




System mode: LTE PS state: Attached

LTE band: B7 LTE bw: 15 MHz

LTE Rx chan: 3175 LTE Tx chan: 21175

EMM state: Registered Normal Service

EMM connection: RRC Connected

RSSI (dBm): -53 Tx Power: -26

RSRP (dBm): -77 TAC: 0BDF (3039)

RSRQ (dB): -7 Cell ID: 0493ED01 (76803329)

SINR (dB): 30.0

Current Network Technology: 0,LTE

Available Network Technology: 1,GSM,GRS,EDGE,UMTS,HSDPA,HSUPA,HSPA+,LTE

Supported Network Technology: 2,GSM,GPRS,EDGE,UMTS,HSDPA/HSUPA,HSPA+,LTE

IMSI: 222018234762487 IMEI: 358178040098891

The strength field or dBm shown by the GPRS modem (the classic bars displayed by a GSM telephone) is

displayed among the information given by the command and it is identifiable, in the example above, by the

Signal Quality: +CSQ: 17,99.

The strength field value can also be obtained starting from the value CSQ. In the example above, the

strength field (dBm) is calculated by a simple arithmetic operation:

CSQ*2 - 113 = dBm

17 * 2 – 113 = -79

With the value obtained it is possible to understand the available signal level (the classic bars on a cell

phone display):

dBm No. bars

-105 to -100 0

-100 to -95 1

-95 to -90 2

-90 to -85 3

> -85 4

A CSQ value of 99,0 indicates no signal available (modem not connected to the network).

GPRS LEDS MEANING

Check the status of a GPRS connection by watching the led named Data.

Mobile interface


If is ON with a green light a GPRS connection is active and the interface has obtained an IP address.

SMS HANDLING

The package Tiesse SMS manages all the operations about the sending / receiving of Short Text Messages

by a router Tiesse, equipped with connection interface Mobile. Thanks to this software, it is possible to:

Send from the router SMS to one or more recipients at the same time

Receive simple SMS and display their content

Manage incoming messages that contain system commands and execute their instructions, even

responding with the output of the executed commands

The SMS manager software uses this commands:

set sms delay-time {seconds}

set sms no-delay-time

set sms password {password}

set sms no-password

set sms reply

set sms no-reply

set sms pin {PIN}

set sms no-pin

set sms helper-number {NUMBER1[,NUMBER2[,NUMBER3[,...]]]}

set sms no-helper-number

set sms [on|off]

With the parameter

set sms delay-time

you can set the control period (in seconds) by which the modem controls the incoming messages and

sends the ones still in the outgoing queue.

With the command

set sms password {password}

you states that the commands sent via SMS to Imola are authenticated with the password supplied as

argument, in order to execute them.

For example, suppose that you configured SMS messaging with the "Tiesse" password as authentication

argument:

set sms password TIESSE

and, wanting to start the modem remotely with a smartphone using the command CLI:

set gprs on

you will have to send the phone number of the SIM-board router an SMS containing the text:

TIESSE set gprs on

Every commands preceded by a different prefix from the password sent (or not preceded by any prefix) will

be discarded, because the authentication fails.

With the command

set sms reply

Mobile interface


you configure the router so that, upon receipt of an SMS Tiesse CLI commands, it also provides the same

output of any response to the sender. As an example, suppose you have configured the SMS messaging

with password "TIESSE" and assume that you have configured the router with the sms reply. If you want to

receive from remote information relating to the status of the phone, simply send an SMS to the router CLI

command:

TIESSE show interface gprs status

After the router received the message and processed its content, it will send to a SMS to the sender like

this output:

root@LTE> show interface gprs status


Network: HSDPA/UMTS I TIM




System mode: WCDMA PS state: Attached

WCDMA band: WCDMA 2100

WCDMA channel: 10638

GMM (PS) state:REGISTERED NORMAL SERVICE

MM (CS) state: IDLE NORMAL SERVICE

WCDMA L1 State:L1M_PCH_SLEEP LAC: EEB5 (61109)

RRC State: DISCONNECTED Cell ID: 0455346A (72692842)

RxM RSSI C0: -89 RxD RSSI C0: -106

RxM RSSI C1: -106 RxD RSSI C1: -106

Current Netwrk Technology: 0,HSDPA/HSUPA

Available Netwrk Technology: 1,UMTS,HSDPA/HSUPA

Supported Netwrk Technology: 2,GSM,GPRS,EDGE,UMTS,HSDPA/HSUPA,HSPA+,LTE

HSDPA/UMTS I TIM

GPRS subsystem is not active on this system.

set sms pin {PIN}

This command allows to send and/or receive SMS from the router even when the SIM card with a PIN code

is still on board. Thanks to this command, in fact, the messaging tool is able to enter the PIN each request

coming from the modem, the opening of each connection to it for the purpose of reading or sending

messages.

set sms helper-number {NUMBER1[,NUMBER2[,NUMBER3[,...]]]}

This command allows to forward every received message to the one or more telephone number specified

as argument.

In case of multiple telephone numbers, these must be separated by commas and without space between

them. In addition, a telephone number, must be strictly specified with the Country Code prefix (with or

without the + beginning). For example, to forward an SMS to two different telephone numbers like 335-

23054400 and 335-23223223, the helper command is:

set sms helper-number 3933523054400,3933523223223

or:

Mobile interface


set sms helper-number +3933523054400,+3933523223223

Finally, to enable the messaging service with the newly introduced parameter, you should run the CLI

command:

set sms on

Once the service is properly set up and activated, messages can be sent by the router, using the command:

send-sms -d {NUMBER1[,NUMBER2[,NUMBER3[,...]]]} {TEXT_MESSAGE}

It is possible to send a text message to multiple phone numbers, as long as these are specified by

separating commas and no spaces between them. In addition, a telephone number must be strictly

specified with the prefix Country Code (with or without the + beginning). For example, to forward an SMS

to two telephone numbers of mobile network 335-23054400 and 335-23223223, the helper command to

enter is:

send-sms -d 3933523054400,3933523223223 TEXT_MESSAGE

To send messages at certain stages of operation of the router or sending SMS to lift the occurrence of

certain events (see sections concerning the programming of triggers related to various interfaces and / or

services of the router), you can launch by sending SMS commands, associating the same commands to the

most appropriate triggers in relation to the circumstances of execution.

Example :

The Mobile modem is active and you wish to receive informations via SMS in relation to the time when the

modem connects, or it goes in stand-by mode; you can use commands like:

set trigger gprs up send-sms -d +3933523054400 Mobile Interface just connected

set trigger gprs down send-sms -d +3933523054400 Mobile Interface in stand-by now

The messaging service offers an interface for reading SMS conventional messages, by which is meant the

whole of those messages not containing executable commands from the router. It is possible to read

received messages from the modem using the following commands:

to view unread SMS: show sms new

to view read SMS: show sms read

to view all SMS: show sms all

For example with

show sms all

all received messages are displayed and the output will be similar to:

-------------------------

From: 393495311921

From_SMSC: 393258819001

Sent: 14-01-21 09:48:59

Received: 70-01-01 17:07:23

IMSI: 222016702779444

Length: 57

Text Message: Service communication go to sector A asap

-------------------------

Press Enter to continue...

-------------------------

From: 393495310926

From_SMSC: 393358819001

Mobile interface


Sent: 14-01-21 09:48:59

Received: 70-01-01 17:07:23

IMSI: 222016702779444

Length: 36

Text Message: Send confirmation sms just as you did

-------------------------

Press Enter to continue...

MOBILE SERVICE CONNECTION: THE HELLO COMMAND

Imola can send a message which contains some useful information about the mobile session to a remote

server, so that messages can be stored.

The command is:

hello <rem-host> <rem-port>

where:

<rem-host> is the remote server IP address.

<rem-port> is the IP port value on the remote host

The message sent will have following format:

00:0d:5a:07:01:13,222017392670415,355841030174450,6 CSQ (-101 dBm), HSDPA I TIM, [email protected]

The field separator is „,‟ (comma) and the fields are:

Router MAC Address

SIM Card IMSI installed on router

Mobile module IMEI

CSQ value (6) and dBm (-101) conversion

Connected network (HSDPA) and provider (TIM)

Router Hostname@ IP address

Using the following sequence of commands, the hello message can be regularly sent:

set timer-tick 600

set trigger timer-tick hello 85.34.166.18 22000

The message is sent as a UDP packet. If destination port specified is 514 (syslog service) and the syslog

server is enabled on the remote server, data will be directly collected from this syslog service.

SIM PIN UNLOCK

The activation of mobile session requires that the SIM is devoid of PIN code. When this code is set, it is

possible to deactivate it by using the command:

unlock-sim

This command checks the presence or lack of the PIN code. For example, if the PIN code is not present, the

result of the command is:

root@IMOLA> unlock-sim

AT+CPIN?

Mobile interface


+CPIN: READY

OK

Then, the GPRS module can be activated. If the result is:

root@IMOLA> unlock-sim

AT+CPIN?

+CPIN: PIN

OK

it is necessary to execute the command specifying the PIN as argument:

root@IMOLA> unlock-sim 1234

It is necessary that the modem is operational so that the command can be effective, otherwise the

command will not give any input.

IMSI AND IMEI READING

The command:

show interface gprs status

gives information about the performance of the mobile session and it also displays the IMEI code

associated with the modem and the IMSI code associated with the SIM. These information can be also

provided by the following commands:

root@IMOLA> gprsat at+cgsn

AT+CGSN

355841030879777

root@IPV6-DTE> gprsat at+cimi

AT+CIMI

222015902932414

Wi-Fi interface


WI-FI INTERFACE


CONFIGURATION

The Wi-Fi interface is available through a module which supports 802.11 a/b/g/n. It allows the router to

execute Access Point functionalities. It is possible to configure up to 8 Access Point (wlan0 .. wlan7) on the

same radio interface.

In order to activate the Wi-Fi interface and all wlan, the command is:

set wifi on

In order to deactivate the Wi-Fi interface, the command is:

set wifi off

In order to deactivate and delete the configuration of all wlan and radio interfaces:

set no-wifi

To work on a single wlan interface (wlan1..wlan7) use:

set wifi no-wlanx

The service configuration is composed by radio and logical interface. In the radio interface, to select

manually the channel, use:

set wifi channel <1,…,11>

To se the automatic selection of the channel

set wifi channel auto

To specifiy the operative mode

set wifi hw_mode <b,b-g,b-g-n,b-n,g,n>

To se the bandwidth

set wifi channel-width <HT20 | HT40+ | HT40->

N.B.: the 40Mhz mode are configurable only with the manual setting of the channel

In the logical interface, that is the wlanX, you can configure the ESSID parameters.

To set the role

set wifi wlanx mode ap

To set the identify string (ESSID)

set wifi wlanx essid <string>

To set the ESSID masking (default value is “no”)

set wifi wlanx hide_ssid [yes|no]

To configure the IP address

set wifi wlanx ipaddr A.B.C.D netmask M.N.F.G

To set the encryption type

Wi-Fi interface


set wifi wlanx encryp [open | wep | wpa-psk | wpa-eap]

Depending on the chosen encryption type, you can add other parameters. If the encryption is open, the

Wi-Fi network is "open", i.e. does not require authorization

set wifi wlanx encryp open

If the encryption is wep, the network is “closed”, it needs authorization with Pre-Shared-Key.

set wifi wlanX encryp wep [crypted-password | password] <STRING>

If the encryption is wpa-psk, the network is "closed" and requires authorization by the Pre-Shared-Key

set wifi wlanx encryp wpa-psk version [1|2|auto] [crypted-password | password] <STRING>

If the encryption is wpa-eap, the network is "closed": authentication, authorization and accounting are

given by the RADIUS Server

set wifi wlanx encryp wpa-eap <options>

Where <options> can be:

the address of the accounting server

set wifi wlanX encryp wpa-eap accthost <ADDRESS>

the port of the accounting server (default 1813)

set wifi wlanX encryp wpa-eap acctport <NUMBER>

secret shared key with the accounting server

set wifi wlanX encryp wpa-eap acctsecret <STRING>

authentication server address (default 127.0.0.1)

set wifi wlanX encryp wpa-eap authhost <ADDRESS>

authentication server port (default 1812)

set wifi wlanX encryp wpa-eap authport <NUMBER>

secret shared with the authentication server

set wifi wlanX encryp wpa-eap authsecret <STRING>

NAS identifier

set wifi wlanX encryp wpa-eap nas-identifier <STRING>

re-authentication interval (default 600 seconds)

set wifi wlanX encryp wpa-eap reauth-period <NUMBER>

source address for the NAS request to the RADIUS

set wifi wlanX encryp wpa-eap source-ipaddr <ADDRESS>

WPA protocol version

set wifi wlanX encryp wpa-eap version [1|2|auto]

N.B.: All the parameters are enabled only if the wlan is activated with:

set wifi wlanX enable [ yes | no]

The default value is "no". The first access point is (wlan0) is always enabled, so the enabling of a specific

wlan applies only at wlan1 to wlan7.

Wi-Fi interface


Another useful mechanism to filter accesses is the identification based on MAC address. To enable it, use

the following command:

set wifi wlanX mac-filter <deny|permit> enable yes

and to disable it:

set wifi wlanX mac-filter <deny|permit> enable no

The deny option inhibits the access to the access point for all the MAC addresses specified in the MAC

filter, while the permit option blocks the access to all MAC address except for the ones specified in the

MAC filter.

After enabling Mac Filter, we can add or remove a MAC address with the following syntax:

set wifi wlanX mac-filter add <MACADDRESS>

set wifi wlanX mac-filter del <MACADDRESS>

To delete all MAC addresses from the filter use:

set wifi wlanX mac-filter clean-all-mac

On the wlanX interface you can configure the DHCP server using3

:

set dhcp-server ... ...

You can set the logging level of the Wi-Fi module with:

set wifi wlanX debug-level [1|2|3|4|5]

The possible levels are:

1 → warning 2 → notification 3 → information 4 → debugging 5 → verbose debugging

With the previous command, the log levels will be set at the module start up. To change them, in persistent

mode, while you are using the Wi-Fi module, you can use:

debug wifi wlanX log-level [1|2|3|4|5]

There are two last commands that complete the Wi-Fi settings: one is used to de-authenticate and to

dissociate the client from the access point:

wifi wlanX disassociate <MAC-ADDRESS>

The second is useful to inspect the Wi-Fi interface:

show interface wifi ([all]|[wlanX]) ([statistics]|[status])

where:

info – displays the information about the interface and the connected stations

statistics – displays the interface status

status - displays the status of the interfaces and of the relative connected stations

3 - For more details, see the DHCP section of this guide. Be aware that the name of the Wi-Fi interface is wlanx

Dhcp protocol


DHCP PROTOCOL


DHCP-SERVER CONFIGURATION

To set the dhcp-server service on the Tiesse's router, you can use the command:

set dhcp-server <name> <options...>

where <name> is a DHCP pool, namely an instance of service, and <options> the parameters for the same

instance. By using:

set dhcp-server <name> interface <interface>

You set the specific interface on which the dhcp-server of the <name> process will act. In general, any

instance insists on a different network interface, typically a VLAN, but in some cases, it may be necessary

to have multiple instances on the same interface, in order to distinguish the parameters to be assigned to

the various clients.

The command:

set dhcp-server <name> description <string>

assigns a description to the service instance.

To specify the range of IP addresses available to the dhcp-server you can use:

set dhcp-server <name> start-address <ip-address>

set dhcp-server <name> end-address <ip-address>

At every request from the client, the router chooses and assigns one address between

start-address and end-address

The period of validity of the address assigned to the client is specified with the command:

set dhcp-server <name> lease-time <value(sec)>

It is possible to establish that some addresses will never be assigned by the command:

set dhcp-server <name> excluded-address <ip-address>

The addresses to be excluded can be put within a pool using:

set dhcp-server <name> start-excluded-address <ip-address>

set dhcp-server <name> end-exluded-address <ip-address>

while using:

set dhcp-server <name> static-lease <mac-address> <ip-address>

determines that the indicated address will only be assigned to the client with the specified MAC address.

It is possible to start the dhcp-server service with the command:

set dhcp-server <name> on

while the command:

set dhcp-server <name> off

turns off the dhcp-server service relative to the <name> process.

Dhcp protocol


Finally, with:

set no-dhcp-server

the dhcp-server service is disabled, also all the configurations relative to the

dhcp-server pools are removed.

Example:

set dhcp-server LAN0 interface eth0

set dhcp-server LAN0 start-range 172.151.1.1

set dhcp-server LAN0 end-range 172.151.1.100

set dhcp-server LAN0 router 172.151.10.10

set dhcp-server LAN0 dns 172.151.113.50

set dhcp-server LAN0 lease-time 6000

set dhcp-server LAN0 subnet 255.255.0.0

set dhcp-server LAN0 on

MAC ADDRESS CONTROL

It is possible to specify if the DHCP process must ignore the requests from a particular MAC and vice versa,

if it must accept the request coming from one or more prearranged MAC only:

set dhcp-server <name> ignore-mac <mac-address>

set dhcp-server <name> accept-mac <mac-address>

The command can be repeated for each MAC pondered.

The 'XX' in the MAC address is used as wildcard character to specify any value, in order to identify a group

of MAC address. For example, using the notation:

set dhcp-server <name> accept-mac 00:0D:5A:XX:XX:XX

you identify every Tiesse MAC address.

The sequence of characters 'XX' is significant only at the end of the sequence.

This function is particularly useful when, on the same network, there are devices that need to receive

different configurations, for example, when you want to distinguish between PCs and telephones. For

example:

set dhcp-server <name> no-ignore-mac <mac-address>

set dhcp-server <name> no-accept-mac <mac-address>

DHCP SERVICE’S MULTIPLE INSTANCES

By using the commands shown in the previous section, you can enable multiple instances of the DHCP

protocol and configure each one separately, using as usual commands with the syntax:

set dhcp-server <name> <options>

where <name> is an instance identifier and <options> are the parameters that relate to that

instance.

This feature is particularly useful in case VLANs are configured on the router and you want to activate the

service on all of them, or even in the general case in which you want to configure the dhcp-server on

different interfaces.

Dhcp protocol


For example, suppose that there are three VLAN identified as eth1.10, eth1.20 and eth1.30, having IP

addresses respectively: 172.16.1.1/24, 172.16.2.1/24 and 172.16.3.1/24. To enable the dhcp-server

on each of them, using the following set of commands:

set dhcp-server vlan10 interface eth1.10

set dhcp-server vlan10 start-range 172.16.1.50

set dhcp-server vlan10 end-range 172.16.1.100

set dhcp-server vlan10 router 172.16.1.1

set dhcp-server vlan10 dns 8.8.8.8 8.8.4.4

set dhcp-server vlan10 subnet 255.255.255.0

set dhcp-server vlan10 on





set dhcp-server vlan20 dns 8.8.8.8







set dhcp-server vlan30 dns 151.99.0.100



In case the network scenario does not foresee the possibility of using the VLANs and on the same network

there are simultaneously present both IP phones and PCs, to assign them different options, you have to

configure two DHCP instances and to select the traffic based on the phone's MAC address.

For example, the following commands configure the process to ignore requests from the MAC address

02:60:8C:01:02:01 and 02:60:8C:01:02:02 and after they assign addresses from 192.168.1.10 to

192.168.1.50, excluding the addresses 192.168.1.20 and 192.168.1.21:

set dhcp-server PC interface eth1

set dhcp-server PC description PoolDHCPperPC

set dhcp-server PC start-range 192.168.1.10

set dhcp-server PC end-range 192.168.1.50

set dhcp-server PC excluded-address 192.168.1.20

set dhcp-server PC excluded-address 192.168.1.21

set dhcp-server PC ignore-mac 02:60:8c:01:02:01

set dhcp-server PC ignore-mac 02:60:8c:01:02:02

set dhcp-server PC router 192.168.1.1

set dhcp-server PC dns 8.8.8.8

set dhcp-server PC lease-time 3600

set dhcp-server PC subnet 255.255.255.0

set dhcp-server PC on

Dhcp protocol


with the following commands you can configure an instance of the process that only considers requests

from the MAC address 02:60:8C:XX:XX:XX, assuming to identify the MAC addresses of IP phones and

sending them to the typical options for voice devices:

set dhcp-server ATA interface eth1

set dhcp-server ATA description PoolDHCPperTelefoni

set dhcp-server ATA start-range 192.168.1.100

set dhcp-server ATA end-range 192.168.1.120

set dhcp-server ATA accept-mac 02:68:8c:XX:XX:XX

set dhcp-server ATA router 192.168.1.1

set dhcp-server ATA dns 8.8.8.8

set dhcp-server ATA lease-time 28800

set dhcp-server ATA subnet 255.255.255.0

set dhcp-server ATA option 120 hex 010a0a0b0b

set dhcp-server ATA option 152 ip 10.10.10.11

set dhcp-server ATA option 160 ascii http://172.20.1.24

set dhcp-server ATA on

Static routes


STATIC ROUTES


CONFIGURATION

Static routing tables can be configured with the command:

set route net <dest> netmask <netmask> gw <ipaddr> [options]

set route net <dest> netmask <netmask> dev <interface> [options]

set route host <dest> gw <gw_ip_addr> [options]

set route host <dest> dev <interface> [options]

In order to remove a route the command is:

set no-route net <dest> netmask <netmask> gw <gw_ip_addr>

set no-route net <dest> netmask <netmask> dev <interface>

set no-route host <dest> gw <gw_ip_addr>

set no-route host <dest> dev <interface>

It is possible to give to the route several attributes through additional parameters.

DISPLAYING STATIC ROUTES

The static routes configured can be displayed using the following command:

show ip route

For example:

root@IMOLA> show ip route

Router# show ip route

Codes: K - kernel route, C - connected, S - static, R - RIP, O - OSPF,

B - BGP, > - selected route, * - FIB route

C>* 10.10.0.0/16 is directly connected, eth0

B>* 11.11.0.0/16 [20/0] via 172.151.113.100, eth1, 09:39:06

R 11.11.0.0/16 [120/2] via 172.151.113.100, eth1, 09:39:30

C>* 11.11.11.11/32 is directly connected, ippp1

C>* 100.100.100.0/30 is directly connected, tun0

R>* 111.111.111.111/32 [120/2] via 172.151.113.100, eth1, 09:39:30

C>* 127.0.0.0/8 is directly connected, lo

C>* 172.151.0.0/16 is directly connected, eth1

C>* 202.202.202.202/32 is directly connected, dummy0

Router#

root@IMOLA>

In this way the protocol of the routes acquisition is visible.

For IPv6 routes the command is: show ipv6 route.

The command show ip route can have options, the most commonly used are:

Static routes


show ip route static

show ip route bgp

show ip route ospf

show ip route rip

show ip route tag N

show ip route cache

Syslog


SYSLOG


LOGGING FUNCTION CONFIGURATION

Imola allows to collect messages showing the status of the system as events occur.

The collect of system messages by the Syslog service, can be executed either on a local server or on a

remote one. In order to configure a local log service the following command is used:

set log local

To configure a remote log service the following command is used:

set log remote <remote-ipaddr>

where <remote-ipaddr> is the IP address of the remote log server.

To specify which IP source should be used to send Syslog messages to the remote server, use the

command:

set log source <local-ip>

or

set log source loopback

to use the loopback address.

To avoid the file to expands excessively, it is possible to specify a maximum number of lines with the

following command:

set log max-lines <value>

It is also possible to specify the log level with the command:

set log level <value>

Log levels (from 1 to 4) allow to display system messages with different details:

LOG DESCRIPTION

level 1 Applications

level 2 Applications, users logon authentication, log of IP packets in transit and filtered by acl, dest-nat,

source-nat rules.

level 3 Applications, users logon authentication, log of IP packets in transit and filtered by access-list, dest-

nat, source-nat rules, Telnet and FTP accesses, dialer ISDN activation

level 4

Applications, users logon authentication, log of IP packets in transit and filtered by access-list, dest-

nat, source-nat rules, Telnet and FTP accesses, dialer ISDN activation with debug messages, ADSL link

activation

In order to activate the log service the following command is used:

set log on

In order to deactivate the log service the command is:

set log off

Local logging of system messages can be activated by using the CLI commands, for example:

Syslog


set log local

set log level 4

set log max-lines 4000

set log on

Remote logging of system messages can be activated by using the following CLI commands:

set log remote <IP>

set log level 4

set log on

It is possible to activate immediate displaying of log file with the following command:

show log

If logging is active, the output is as in the following figure.

In order to interrupt message displaying, it is necessary to type once the key combination <Ctrl+C>.

root@Imola> show log

Jan 1 06:36:38 localhost syslogd 1.4.1: restart.

Jan 1 06:37:12 localhost exiting on signal 15


Jan 1 06:37:18 localhost sshd[17904]: log: Closing connection to 10.10.10.19

Jan 1 06:37:26 localhost in.telnetd[17938]: connect from 10.10.10.19

Jan 1 06:37:26 localhost radlogin[17939]: //etc/radiusclient/radiusclient.conf: no authserver

specified

Jan 1 06:37:30 localhost radlogin[17939]: authentication OK, type local, username root

It is possible to display the entire log file with the command:

show log full

If the logging is active, the output is as in the following figure.

press “q” in order to interrupt the displaying

press “enter” in order to display each single line

press “space” in order to display the following page.

root@Imola> show log full


Jan 1 00:01:06 localhost kernel: Memory: 59672KB available (1688K code, 357K da

ta, 240K init)

Jan 1 00:01:06 localhost kernel: number of JEDEC chips: 1

Jan 1 00:01:06 localhost kernel: cfi_cmdset_0002: Disabling erase-suspend-progr

am due to code brokenness.

Jan 1 00:01:06 localhost kernel: Imola3 flash_0: Using Static image partition definition

Jan 1 00:01:06 localhost kernel: Creating 2 MTD partitions on "Imola3:0":

Jan 1 00:01:06 localhost kernel: 0x00000000-0x00070000 : "U-boot"

Jan 1 00:01:06 localhost kernel: 0x00070000-0x00080000 : "environment"

Jan 1 00:01:06 localhost kernel: imola3_init: mach-type=604

Jan 1 00:01:06 localhost kernel: 3 cmdlinepart partitions found on MTD device i

mola3-nand

Jan 1 00:01:06 localhost kernel: Creating 3 MTD partitions on "imola3-nand":

Jan 1 00:01:06 localhost kernel: 0x00000000-0x00100000 : "kernel"

Jan 1 00:01:06 localhost kernel: 0x00100000-0x00400000 : "initrd"

Jan 1 00:01:06 localhost kernel: 0x00400000-0x01000000 : "user"

Jan 1 00:01:06 localhost kernel: RAMDISK: Compressed image found at block 0

Jan 1 00:01:06 localhost kernel: ISDN subsystem Rev: 1.1.4.1/1.1.4.1/1.1.4.1/1.

Syslog


1.4.1/none/1.1.4.1 loaded

Jan 1 00:01:07 localhost ipppd[1696]: Found 1 device: /dev/ippp0

--More-- (70% of 1846 bytes)

Timezone


TIMEZONE


TIMEZONE CONFIGURATION

With the appropriate CLI commands it is possible to configure the time zone on Tiesse‟s routers.

The configurable time zones are:

CET GMT+12 GMT+7 GMT-11 GMT-4 GMT0 WET

GMT GMT+2 GMT+8 GMT-12 GMT-5 Greenwich Zulu

GMT+0 GMT+3 GMT+9 GMT-13 GMT-6 MET

GMT+1 GMT+4 GMT-0 GMT-14 GMT-7 UCT

GMT+10 GMT+5 GMT-1 GMT-2 GMT-8 UTC

GMT+11 GMT+6 GMT-10 GMT-3 GMT-9 Universal

The correct time zone for Italy is GMT-1 on DST (Daylight Saving Time) and GMT-2 during GMT Standard

Time.

Otherwise, MET or CET (Middle or Central European Time) can be used. They automatically execute the

passage from DST to GMT.

The time zone configuration can be executed with the following CLI commands:

set time zone <TZ>

set time zone on

To see which time zone is active, it is possible to use the CLI command:

show date

the output is as follows:

root@Imola> show date

Mon Oct 10 11:52:15 GMT-1 2005

Configuration examples


CONFIGURATION EXAMPLES


DHCP SERVER

Configuration of the DHCP service on one of the router's LAN interfaces (e.g. eth0) and distribution of IP

address, IP WINS, DNS, and Domain Info.

set dhcp-server <DHCP-POOL-NAME> interface <INTERFACE>

set dhcp-server <DHCP-POOL-NAME> start-address <IP-START-ADDRESS>

set dhcp-server <DHCP-POOL-NAME> end-address <IP-END-ADDRESS>

set dhcp-server <DHCP-POOL-NAME> router <GATEWAY-IP>

set dhcp-server <DHCP-POOL-NAME> subnet <SUBNET-MASK>

set dhcp-server <DHCP-POOL-NAME> lease-time <LEASETIME(s)>

set dhcp-server <DHCP-POOL-NAME> dns <DNS1-IP-ADDR> <DNS2-IP-ADDR>

set dhcp-server <DHCP-POOL-NAME> wins <WINS-IP-ADDR>

set dhcp-server <DHCP-POOL-NAME> directive option domain <MYDOMAIN>

set dhcp-server <DHCP-POOL-NAME> on

If you need to specify more WINS addresses to be distributed, instead of the previous command:

set dhcp-server <DHCP-POOL-NAME> wins <WINS-IP-ADDRESS>

it is better to use

set dhcp-server <DHCP-POOL-NAME> directive option wins <IPADDR1> <IPADDR2>

While configuring the service for more than one <DHCP-POOL-NAME>, it is possible to activate the multiple

DHCP servers, but on different interfaces. For example:

set dhcp-server pool1 interface eth0

set dhcp-server pool1 start-address 192.168.24.50

set dhcp-server pool1 end-address 192.168.24.70

set dhcp-server pool1 router 192.168.24.1

set dhcp-server pool1 subnet 255.255.255.128

set dhcp-server pool1 lease-time 864000

set dhcp-server pool1 dns 10.1.82.6 10.1.84.5

set dhcp-server pool1 directive option wins 10.1.80.38 10.1.80.39

set dhcp-server pool1 directive option domain tiesse.com

set dhcp-server pool1 on

To use the possible options of the DHCP server, see the next chapter.

ADSL NAT WITH AN IP LAN CUSTOMER WITH PUBLIC AND PRIVATE IP

In this chapter it is described a base configuration of the ADSL (RFC 1483) interface with a NAT on the

Peer-To-Peer and a default route on the interface. A private IP address is set on the eth1 interface and a

management IP address is set on the eth0.

set eth0 ipaddr 10.10.113.1 netmask 255.255.255.252

set eth0 on



set eth1 ipaddr <PRIVATE-IP> netmask <PRIVATE-NETMASK>

set eth1 on

set adsl encap rfc1483-llc

set adsl pvc-number 1

set adsl pvc atm0 pcr 0

set adsl pvc atm0 vpi 8 vci 35

set adsl pvc atm0 ipaddr <PTP-IP-ADDRESS>

set adsl pvc atm0 no-nexthop

set adsl pvc atm0 netmask 255.255.255.252

set adsl pvc atm0 default-route

set adsl pvc atm0 masquerade

set adsl on

Practical example:


set eth0 on


set eth1 on



set adsl pvc atm0 ipaddr 85.34.147.98






set adsl pvc atm0 masquerade

set adsl on

ADSL IP WITH A POOL OF PUBLIC AND PRIVATE IP

It is described a basic configuration for the ADSL interface with private IP on the LAN interface eth1 and an

IP address of the pool of public addresses on the interface eth0.

In order to enable data exchange with the outside a NAT rule is set for packets from the private LAN.

set eth0 ipaddr <PUBLIC-IP> netmask <NETMASK-IP-PUBLIC>

set eth0 on

set eth1 ipaddr <PRIVATE-IP> netmask <NETMASK-IP-PRIVATE>

set eth1 on




set adsl pvc atm0 service UBR





set adsl pvc atm0 no-masquerade




set adsl on

set iptables -t nat -A POSTROUTING -s <PRVAT_LAN>/N -o atm0 -j SNAT --to <PUBLIC-IP>

Practical example:


set eth0 on


set eth1 on



set adsl description 054113517692








set adsl on

set iptables -t nat -A POSTROUTING -s 192.168.1.0/24 -o atm0 -j SNAT --to 80.21.88.177

GPRS ON PUBLIC APN (INTERNET NAVIGATION)

It is described here a base configuration of the GPRS interface with a public (internet) connection profile,

with the management IP on the eth0 interface and a private IP on the eth1 LAN.

To allow the data exchange with the outside (internet), the GPRS interface is configured so that it make

PAT.


set eth0 on


set eth1 on



set gprs idle 0

set gprs rx-idle 1800



set gprs masquerade


set gprs mtu 1500

set gprs usepeerdns

set gprs debug

set gprs sgauth 1

set gprs speed 230400

set gprs pwroff-modem

set gprs on

Practical example:


set eth0 on


set eth1 on



set gprs idle 0


set gprs masquerade


set gprs mtu 1500

set gprs usepeerdns

set gprs debug

set gprs vjc

set gprs sgauth 1



set gprs on

GPRS ON PRIVATE APN WITH GRE TUNNEL

It is described here a base configuration of the GPRS interface with a connection profile based on a private

APN, with a management IP address on the eth0 and a private IP on the eth1 LAN. The private internal LAN

connection, with the Master in its center, is being realized with a GRE tunnel (keepAlive), with a default

route.

To have the tunnel work correctly, the IP address released by the mobile interface must be static.


set eth0 on


set eth1 on

set gprs apn <PRIVATE-APN>

set gprs login <APN-USER> password <APN-PASSWORD>



set gprs idle 0


set gprs mtu 1476

set gprs usepeerdns

set gprs debug

set gprs vjc





set gprs no-sms-handle

set gprs on

set gre tun0 tunnel-source ppp0

set gre tun0 tunnel-destination <GRE-DESTINATION>

set gre tun0 tunnel-address <GRE-IP-ADDRESS>/30

set gre tun0 tunnel-peer <GRE-PEER-IP-ADDRESS>/30

set gre tun0 multicast

set gre tun0 ttl 64

set gre tun0 mtu 1452

set gre tun0 keepalive-intval 10

set gre tun0 keepalive-retries 6

set gre tun0 on

set route host <GRE-DESTINATION> dev ppp0

set route net 0.0.0.0 netmask 0.0.0.0 dev tun0

set trigger gprs up set gre tun0 on

The authentication oh the RADIUS takes place both in dynamic mode and in CHAP or PAP mode. If the

RADIUS does not support only the PAP authentication and not the CHAP one, then you need to add the

following commands:

set gprs sgauth 1

set gprs directive refuse-chap

Practical example:


set eth0 on


set eth1 on

set gprs apn intranet.tim.it

set gprs login tiesse1 password tiesse2

set gprs idle 0


set gprs mtu 1476

set gprs usepeerdns



set gprs debug

set gprs sgauth 1





set gprs no-sms-handle

set gprs on

set gre tun0 tunnel-source 172.30.16.2

set gre tun0 tunnel-destination 10.1.50.29

set gre tun0 tunnel-address 172.30.0.9/30

set gre tun0 tunnel-peer 172.30.0.10/30

set gre tun0 multicast

set gre tun0 ttl 64

set gre tun0 mtu 1452

set gre tun0 keepalive-intval 10

set gre tun0 keepalive-retries 6

set gre tun0 on

set route host 10.1.50.29 dev ppp0

set route net 0.0.0.0 netmask 0.0.0.0 dev tun0

set trigger gprs up set gre tun0 on

ADSL WITH RADIO MOBILE BACKUP

It is described here a base configuration to link a primary public ADSL with GPRS backup. It is configured a

private address on eth1 LAN and an IP address of the public addresses pool on the eth0 interface.

To allow the data exchange with the outside, a NAT rule is been set for the packets coming from the

private LAN.


set eth0 on


set eth1 on


set gprs idle 0



set gprs masquerade

set gprs mtu 1500

set gprs usepeerdns

set gprs debug

set gprs sgauth 1




set gprs off






set adsl pvc atm0 no-default-route





set adsl on

set backup checking-ipaddr <PUBLIC-IP> via bfd through-interface atm0

set backup check-interval 30

set backup check-retries 3

set backup check-wait 5

set backup deactivate-delay 30

set backup on

set trigger backup up set gprs on

set trigger backup down set gprs off

set route net 0.0.0.0 netmask 0.0.0.0 dev atm0 distance 10

set route net 0.0.0.0 netmask 0.0.0.0 dev ppp0 distance 5

set iptables -t nat -A POSTROUTING -s <PRIVATE-LAN>/N -o atm0 -j SNAT --to < PUBLC-

IP>

set autocmd set backup on

set autocmd set gprs off

Practical example:


set eth0 on


set eth1 on


set gprs idle 0



set gprs masquerade

set gprs mtu 1500

set gprs usepeerdns

set gprs debug



set gprs sgauth 1


set gprs off






set adsl pvc atm0 no-default-route





set adsl on

set backup checking-ipaddr 2.21.172.162 via bfd through-interface atm0

set backup check-interval 30

set backup check-retries 3

set backup check-wait 5

set backup deactivate-delay 30

set backup on

set trigger backup up set gprs on

set trigger backup down set gprs off

set route net 0.0.0.0 netmask 0.0.0.0 dev atm0 distance 10

set route net 0.0.0.0 netmask 0.0.0.0 dev ppp0 distance 5

set iptables -t nat -A POSTROUTING -s 192.168.1.0/24 -o atm0 -j SNAT --to

2.21.172.162

set autocmd set backup on

set autocmd set gprs off

Documents

Imola/Lipari Quick Start Guide - · PDF filebasic operations & cli commands ... 5 gprs / edge / umts / hsdpa / hsupa / lte y ... (imola/lipari quick start guide ar cli p. imola/lipari