- •Table of Contents
- •Quick Reference to Commands
- •Quick List of Examples
- •Preface
- •Intended Audience
- •Organization of This Guide
- •Document Conventions
- •Vyatta Publications
- •Chapter 1: Serial Interfaces
- •Serial Interface Configuration
- •Virtual Interfaces on Serial Interfaces
- •Enabling Interfaces
- •Viewing Available Serial Interfaces
- •Serial Interface Commands
- •clear interfaces serial
- •interfaces serial <wanx>
- •interfaces serial <wanx> description <desc>
- •interfaces serial <wanx> encapsulation <type>
- •show interfaces serial
- •show interfaces serial <wanx>
- •show interfaces serial <wanx> capture
- •show interfaces serial <wanx> log
- •show interfaces serial <wanx> loopback
- •show interfaces serial <wanx> physical
- •show interfaces serial <wanx> ppp
- •show interfaces serial <wanx> queue
- •show interfaces serial <wanx> trace
- •Chapter 2: Testing Serial Lines
- •Serial Line Testing Overview
- •Serial Line Loopbacks
- •Loopback Tests
- •Bit Error Rate Tests
- •Serial Line Testing Commands
- •loopback down
- •loopback test
- •loopback up
- •Chapter 3: DSL Interfaces
- •DSL Configuration
- •ADSL Interfaces Overview
- •ADSL Configuration Example
- •DSL Commands
- •interfaces adsl <adslx>
- •interfaces adsl <adslx> watchdog <state>
- •Chapter 4: Wireless Modem Interfaces
- •Wireless Modem Configuration
- •Wireless Modem Interface Commands
- •clear interfaces connection <wlmx>
- •connect interface <wlmx>
- •disconnect interface <wlmx>
- •interfaces wirelessmodem <wlmx>
- •interfaces wirelessmodem <wlmx> backup
- •interfaces wirelessmodem <wlmx> description <desc>
- •interfaces wirelessmodem <wlmx> device <device>
- •interfaces wirelessmodem <wlmx> mtu <mtu>
- •interfaces wirelessmodem <wlmx> network <scriptfile>
- •interfaces wirelessmodem <wlmx> ondemand
- •show interfaces wirelessmodem
- •Glossary of Acronyms
Chapter 1: Serial Interfaces |
Serial Interface Configuration 2 |
|
|
|
|
Serial Interface Configuration
This section presents the following topics:
•Virtual Interfaces on Serial Interfaces
•Enabling Interfaces
•Viewing Available Serial Interfaces
Virtual Interfaces on Serial Interfaces
The Vyatta system distinguishes between physical interfaces (interfaces), and logical interfaces (virtual interfaces, or vifs).
Every physical network device in the system is considered to be an “interface.” An example of a interface is a physical port on a serial card. Every serial interface has zero or more corresponding vifs.
On serial interfaces, physical line characteristics are specific for the interface, but encapsulation (Cisco HDLC, Frame Relay, or Point-to-Point Protocol) is specified for vifs.
Unlike Ethernet interfaces, a physical serial interface cannot directly have a configured IP address. Instead, the IP address must be assigned to the vif.
Note that each serial vif can support exactly one IP address.
Enabling Interfaces
The Vyatta system will automatically discover any available physical serial interfaces on startup. Before you can apply any configuration to a serial interface, a vif must be “created” for the interface and its encapsulation specified in the configuration tree.
For serial interfaces, physical line characteristics are applied to the interface as a whole. Encapsulation characteristics are applied to the vif, as shown in the configuration hierarchy below:
interfaces { serial wan0 {
ppp {
vif 1 {
}
}
}
}
WAN Interfaces |
R6.3 v01 |
Vyatta |
Chapter 1: Serial Interfaces |
Serial Interface Configuration 3 |
|
|
|
|
The current implementation supports Cisco HDLC, Frame Relay, and Point-to-Point Protocol encapsulation.
•Cisco HDLC and point-to-point interfaces support only one vif, and this vif must have the identifier 1.
•The identifier for Frame Relay vifs is the DLCI number. This can range from 16 through 991.
•Currently, any vif on a serial interface can support exactly one IP address.
Viewing Available Serial Interfaces
You can only configure interfaces that actually are available to the operating system on the hardware you are using.
To view all the interfaces known to the operating system, use the show interfaces system command in operational mode, as shown in Example 1-1:
Example 1 1 Viewing available system interfaces
vyatta@vyatta> show interfaces system
eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
link/ether 00:15:c5:fb:ba:e8 brd ff:ff:ff:ff:ff:ff |
|
|||||
inet |
10.1.0.44/24 brd 10.1.0.255 scope global eth0 |
|
||||
inet6 fe80::215:c5ff:fefb:bae8/64 scope link |
|
|
||||
valid_lft forever preferred_lft forever |
|
|
||||
RX: |
bytes |
packets |
errors |
dropped |
overrun |
mcast |
|
18469 |
257 |
0 |
0 |
0 |
1 |
TX: |
bytes |
packets |
errors |
dropped |
carrier collisions |
|
|
17434 |
170 |
0 |
0 |
0 |
0 |
eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
link/ether 00:15:c5:fb:ba:e9 brd ff:ff:ff:ff:ff:ff inet6 fe80::215:c5ff:fefb:bae9/64 scope link
|
valid_lft forever preferred_lft forever |
|
|
|||
RX: |
bytes |
packets |
errors |
dropped |
overrun |
mcast |
|
0 |
0 |
0 |
0 |
0 |
0 |
TX: |
bytes |
packets |
errors |
dropped |
carrier collisions |
|
|
424 |
4 |
0 |
0 |
0 |
0 |
lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
WAN Interfaces |
R6.3 v01 |
Vyatta |
