ConfigGuide - Ethernet Thomson Adsl Modem

Thomson Gateway
rnet
er
Pow
-in
Ethe
WLA
Plug
ISDN
rnet
DSL
Inte
Ethernet Configuration Guide

R7.4 and higher
Thomson Gateway
Ethernet Configuration Guide
R7.4 and higher
Copyright
Copyright ©1999-2008 Thomson. All rights reserved.

Distribution and copying of this document, use and communication of its contents is not permitted without written authorization
from Thomson. The content of this document is furnished for informational use only, may be subject to change without notice,
and should not be construed as a commitment by Thomson. Thomson assumes no responsibility or liability for any errors or
inaccuracies that may appear in this document.
Thomson Telecom Belgium
Prins Boudewijnlaan, 47
B-2650 Edegem
Belgium
http://www.thomson-broadband.com
Trademarks
The following trademarks may be used in this document:

DECT is a trademark of ETSI.
Bluetooth® word mark and logos are owned by the Bluetooth SIG, Inc.
Ethernet™ is a trademark of Xerox Corporation.
Wi-Fi® and the Wi-Fi logo are registered trademarks of the Wi-Fi Alliance. "Wi-Fi CERTIFIED", "Wi-Fi ZONE", "Wi-Fi Alli-
ance", their respective logos and "Wi-Fi Protected Access" are trademarks of the Wi-Fi Alliance.
UPnP™ is a certification mark of the UPnP™ Implementers Corporation.
Microsoft®, MS-DOS®, Windows®, Windows NT® and Windows Vista® are either registered trademarks or trademarks
of Microsoft Corporation in the United States and/or other countries.
Apple® and Mac OS® are registered trademarks of Apple Computer, Incorporated, registered in the United States and
other countries.
UNIX® is a registered trademark of UNIX System Laboratories, Incorporated.
Adobe®, the Adobe logo, Acrobat and Acrobat Reader are trademarks or registered trademarks of Adobe Systems, Incor-
porated, registered in the United States and/or other countries.
Other brands and product names may be trademarks or registered trademarks of their respective holders.
Document Information
Status: v1.0 (March 2008)

Reference: E-DOC-CTC-20080229-0003
Short Title: Config Guide: Ethernet R7.4 and higher
Contents
About this Ethernet Configuration Guide ................................ 1
1 Introduction.................................................................................. 3
2 Interface Architecture.................................................................. 5
3 Physical Ethernet Interfaces ..................................................... 11

3.1 Background Information ............................................................................... 11
3.2 Configuring Physical Ethernet Interfaces ..................................................... 13
4 Ethernet Switch ......................................................................... 15

4.1 Port Mirroring ............................................................................................... 15
4.2 Port Grouping and Port Isolation .................................................................. 17
4.3 Port Sharing .................................................................................................. 20
5 Ethernet Bridge.......................................................................... 23
5.1 The Bridge and the Interface Architecture ................................................... 23
5.2 The Self-Learning Transparent Bridge........................................................... 27
5.2.1 Filtering Database................................................................................................................................. 28

5.2.2 Learning Process .................................................................................................................................. 30
5.2.3 Forwarding Process.............................................................................................................................. 31
5.3 Multiple Bridge Instances ............................................................................. 32
5.3.1 Creating Multiple Bridge Instances ..................................................................................................... 32

5.3.2 Configuring a Bridge Instance ............................................................................................................. 34
5.4 Ethernet Bridge Ports.................................................................................... 38
5.5 No-WAN Broadcast Filter .............................................................................. 43
5.6 Multicast Filter .............................................................................................. 44
5.7 BPDU Filtering .............................................................................................. 46
6 Logical Ethernet Interfaces ....................................................... 49

6.1 Logical Ethernet and the Interface Architecture .......................................... 49
6.2 Configuring Logical Ethernet Interfaces ....................................................... 53
E-DOC-CTC-20080229-0003 v1.0
i
Contents
ii E-DOC-CTC-20080229-0003 v1.0
About this Ethernet Configuration Guide
Used Symbols
A note provides additional information about a topic.
A caution warns you about potential problems or specific precautions that need to be taken.
Terminology
Generally, the Thomson Gateway356 will be referred to as Wireless USB Adaptor in this Ethernet
Configuration Guide.
Typographical Conventions
Following typographical convention is used throughout this manual:
Sample text indicates a hyperlink to a Web site.
Example: For more information, visit us at www.thomson-broadband.com.
Sample text indicates an internal cross-reference.
Example: If you want to know more about guide, see “1 Introduction” on page 7”.
Sample text indicates an important content-related word.
Example: To enter the network, you must authenticate yourself.
Sample text indicates a GUI element (commands on menus and buttons, dialog box elements, file
names, paths and folders).
Example: On the File menu, click Open to open a file.
Documentation and software updates

Thomson continuously develops new solutions, but is also committed to improving its existing products.
For more information on Thomson's latest technological innovations, documents and software releases, visit
us at http://www.thomson-broadband.com.
E-DOC-CTC-20080229-0003 v1.0
1
Overview
First, this Ethernet Configuration Guide shortly lists the Ethernet features of the Thomson Gateway and the
relevant standards. Some background information on several Ethernet-related concepts is also provided.
Next, this document describes the configuration of each Ethernet feature on the Thomson Gateway in detail.
Command-Line Interface (CLI) commands are used for the configuration.
This document is structured as follows:
Topic Page
“1 Introduction” 3
“2 Interface Architecture” 5
“3 Physical Ethernet Interfaces” 11
“4 Ethernet Switch” 15
“5 Ethernet Bridge” 23
“6 Logical Ethernet Interfaces” 49
2 E-DOC-CTC-20080229-0003 v1.0
1| Introduction
1 Introduction
Introduction
The Ethernet (Layer 2) features of our Thomson Gateway are the subject of this document. In this chapter, we
shortly list the Ethernet features that are supported by the Thomson Gateway, the relevant standards and
related documents.
Supported Ethernet features

Thomson Gateway devices support following Ethernet features:
Physical Ethernet interfaces:
Auto-MDI/MDI-X
Link integrity and activity indication
Auto-negotiation
Manual configuration of the communication speed and duplex mode
Ethernet switch:
Port grouping
Port mirroring
Port sharing
Ethernet bridge:
Self-learning transparent bridge functionality according to IEEE 802.1D
! Configuration of static entries
! Configurable lifetime of dynamic entries
Multiple bridge instances
Ethernet bridge ports
No-WAN broadcast filter
Multicast filter
BPDU filtering
Logical Ethernet interfaces:
Configuration of the logical Ethernet interfaces
Standards compliancy
Thomson Gateway devices are compliant with following standards, which are relevant to Ethernet, Ethernet
bridging, VLAN bridging, VLAN user priorities and stacked VLANs:
IEEE Std 802.3 - 2000: Part 3: Carrier sense multiple access with collision detection (CSMA/CD) access
method and physical layer specifications.
IEEE Std 802.1D - 2004: IEEE standard for local and metropolitan area networks - Media Access Control
(MAC) bridges.
IEEE Std 802.1Q - 1998: IEEE standard for local and metropolitan area networks - Virtual bridged local
area networks.
IEEE Std 802.1p: Traffic Class Expediting and Dynamic Multicast Filtering. This standard is merged into
802.1D-2004.
IEEE Std 802.1ad - 2005: IEEE standard for local and metropolitan area networks - Virtual bridged local
area networks - Amendment 4: Provider bridges.
E-DOC-CTC-20080229-0003 v1.0
3
1| Introduction
Related documents
Other Layer 2 related features, such as Ethernet QoS and VLANs, are described in separate documents. See
the “Ethernet QoS Configuration Guide” and the “VLAN Configuration Guide” for more information.
4 E-DOC-CTC-20080229-0003 v1.0
2| Interface Architecture
2 Interface Architecture
Thomson Gateway interface architecture

Following illustration shows the Thomson Gateway interface architecture.
The interfaces that are within the scope of this document are indicated in red. These interfaces are:
Physical Ethernet interfaces
Switch ports of the Ethernet switch
Bridge ports of the Ethernet bridge
Logical Ethernet interfaces
LoopBack
IP Forwarding
IP Interface(s)
ARP PPP
iARP
Multilink
IPoE / PPPoE PPPoE RELAY IPoA
PPP
IPoEoA
Ethernet Interface(s) PPPoA
VLAN
Bridge EthoA
ATM Interface(s)
ATM Bundle
Physical Ports ATM VP/VC

ISDN
(Eth, USB, WLAN, BT...) (Over DSL / ATM-F)
E-DOC-CTC-20080229-0003 v1.0
5
Ethernet switch and Ethernet bridge

A Thomson Gateway device contains two Layer 2 switches. We refer to these elements as the Ethernet switch
and the Ethernet bridge. Following illustration shows how these two Layer 2 elements work together. The red
arrow indicates the traffic flow between two physical Ethernet interfaces.
Two cases are possible for traffic between two physical Ethernet interfaces:
Basic forwarding functionality: in this case, frames are handled by the Ethernet switch at high speed.
Speeds up to 100 Mbps are possible.
Advanced functionality: for more advanced features (dynamic VLANs, VLAN tagging, priority tagging,
priority transparency and so on) frames are handled by the Ethernet bridge. The price for these features
is the lower speed.
OBC OBC
Bridge Bridge
ethport1 ethport2 ethport3 ethport4 WLAN ethport1 ethport2 ethport3 ethport4 WLAN
Switch Switch
ethif1 ethif2 ethif3 ethif4 wlif1 ethif1 ethif2 ethif3 ethif4 wlif1
- High speed - Lower speed

- Basic forwarding functionality - Advanced functionality
Displaying the list of interfaces

To display the interfaces on a Thomson Gateway, execute the command :interface list.
Optionally, two parameters can be specified:
Expand:
If the parameter is disabled, basic information is listed, including interface type, interface state, use
and the lower/upper layer interfaces.
If the parameter is enabled, the list is expanded with additional information, for example interface
flags, speed of physical interfaces and so on.
By default, this parameter is disabled.
Reverse:
If the parameter is disabled, the list indicates for each interface the upper layer (UL) interface.
If the parameter is enabled, the list indicates the lower layer (LL) interface instead of the upper layer
interface.
By default, this parameter is disabled.
For example, to obtain a detailed list with the LL interfaces, execute following command:
=>:interface list expand=enabled reverse=enabled
6 E-DOC-CTC-20080229-0003 v1.0
Defaults on residential devices

The default interfaces on a residential device (e.g. the THOMSON ST780) are displayed as follows:
=>:interface list expand=disabled reverse=disabled

Name Type State Use UL Interfaces
loop ip connected 0
ethif1 physical connected 1 ethport1
wlif1 physical connected 1 WLAN
ceoc dsl connected 0
bridge eth connected 2 RELAY, LocalNetwork
OBC bridge connected 1 bridge
ethport1 bridge connected 1 bridge
RELAY eth connected 1 Internet_ppp
FXO physical connected 0
atm_8_35 atm connected 1 ethoa_8_35
WLAN bridge connected 1 bridge
ethoa_8_35 eth connected 1 RELAY
Internet_ppp ppp not-connected 1 Internet
Internet *ip not-connected 0
LocalNetwork ip connected 0
FXS1 physical connected 0
FXS2 physical connected 0
Based on this information, the configuration of the device can be figured out. The part that is relevant for this
document is shown in following illustration:
Router
LocalNetwork Internet
Internet_ppp
RELAY
ethoa_8_35
OBC
Bridge
ethport1 ethport2 ethport3 ethport4 WLAN
ethif1 ethif2 ethif3 ethif4 wlif1 atm_8_35
E-DOC-CTC-20080229-0003 v1.0
7
Defaults on a business device

The default interfaces on a business device (e.g. the THOMSON ST620) are displayed as follows:
=>:interface list expand=disabled reverse=disabled

Name Type State Use UL Interfaces
loop ip connected 0
wlif1 physical connected 1 WLAN
ceoc dsl connected 0
bridge eth connected 5 eth_dmz1, eth_guest1,
eth_wan1, RELAY, lan1
OBC bridge connected 1 bridge
RELAY eth connected 1 Internet_ppp
atm_8_35 atm connected 1 ethoa_8_35
ISDN isdn not-connected 1 ISDN_backup_ppp
WLAN bridge connected 1 bridge
ethoa_8_35 eth connected 1 RELAY
eth_wan1 eth connected 2 RELAY, wan1
eth_dmz1 eth connected 1 dmz1
eth_guest1 eth connected 1 guest1
Internet_ppp ppp not-connected 1 Internet
Internet *ip not-connected 0
ISDN_backup_ppp ppp not-connected 1 ISDN_backup
ISDN_backup ip not-connected 0
ISDN_backup_trigger ip connected 0
lan1 ip connected 0
wan1 ip connected 0
dmz1 ip connected 0
guest1 ip connected 0
8 E-DOC-CTC-20080229-0003 v1.0
Based on this information, the configuration of the device can be figured out. The part that is relevant for this
document is shown in following illustration:
Router
lan1 guest1 dmz1 wan1 Internet
Internet_ppp
RELAY
eth_guest1 eth_dmz1 eth_wan1 ethoa_8_35
OBC
Bridge
ethport1 ethport2 ethport3 ethport4 WLAN
ethif1 ethif2 ethif3 ethif4 wlif1 atm_8_35
E-DOC-CTC-20080229-0003 v1.0
9
10 E-DOC-CTC-20080229-0003 v1.0
3| Physical Ethernet Interfaces
3 Physical Ethernet Interfaces
3.1 Background Information
Introduction
The physical Ethernet interfaces support wireline Ethernet. It operates over two wire pairs: one for
transmission, another for reception. To improve signal characteristics, the two wires in each pair are twisted
together. Two Ethernet varieties are supported:
10Base-T Ethernet, which provides a bandwidth up to 10 Mbps.
100Base-T Ethernet, which provides a bandwidth up to 100 Mbps.
The “T” in 10Base-T and 100Base-T stands for “Twisted”.
Signal-to-pin mapping
Both 10Base-T and 100Base-T Ethernet use the same 8-pin connector, also referred to as the RJ-45 jack.
Although the RJ-45 jack is an 8-pin connector, only 4 pins are used by 10Base-T and 100Base-T Ethernet:
2 pins for transmission and 2 pins for reception. Two different signal-to-pin mappings exist:
Medium Dependent Interface (MDI)
Crossed Medium Dependent Interface (MDI-X)
Following table indicates which pins are used for transmission and which ones are used for reception:
Pin MDI Ethernet interface MDI-X Ethernet interface

1 Send (positive signal) Receive (positive signal)
2 Send (negative signal) Receive (negative signal)
3 Receive (positive signal) Send (positive signal)
4 Not used Not used
5 Not used Not used
6 Receive (negative signal) Send (negative signal)
7 Not used Not used
8 Not used Not used
Cabling
Irrespective the used signal-to-pin mapping, the pins used for transmission on one side of an Ethernet
segment must be connected to the pins used for reception on the other side. 10Base-T and 100Base-T
Ethernet use an Unshielded Twisted Pair (UTP) cable to connect two RJ-45 jacks. Such a cable is made of four
twisted pairs of copper wire, terminated by RJ-45 jacks. Two types of cable exist:
Straight-through
Crossover
E-DOC-CTC-20080229-0003 v1.0
11
Following table indicates which type of cable must be used to connect two RJ-45 jacks correctly:
Ethernet interface on device A Ethernet interface on device B Type of cable

MDI-X MDI Straight-through
MDI-X Crossover
MDI MDI Crossover
MDI-X Straight-through
On the Thomson Gateway, auto-MDI/MDI-X is used: each physical Ethernet interface is able to
auto-sense whether it should operate as MDI or MDI-X.
LEDs
The physical Ethernet interfaces are provided with a visual indicator, referred to as the link LED. This LED can
indicate both link integrity and activity and can be used for troubleshooting:
Link integrity: if two physical Ethernet interfaces are properly connected, the LEDs of both interfaces light
up. If one of these interfaces is not properly connected, the LEDs of both interfaces will not light up.
Link activity: the LED indicates the transmission and/or reception of data.
If a physical Ethernet interface is provided with a second LED, this LED indicates whether the interface is
operating at 10 Mbps (LED off) or 100 Mbps (LED on).
12 E-DOC-CTC-20080229-0003 v1.0
3.2 Configuring Physical Ethernet Interfaces
Introduction
The configuration of a physical Ethernet interface can be modified to specify a specific communication speed
and duplex mode.
The CLI commands described in this section are part of the command group :eth device.
Communication speed
For end-users, the most important parameter of a physical Ethernet interface is its communication speed,
that is the maximum bandwidth it supports. This parameter is expressed in megabits per second (Mbps).
The Thomson Gateway supports 10 or 100 Mbps for twisted pair cabling.
10Base-T Ethernet provides a bandwidth up to 10 Mbps.
100Base-T Ethernet provides a bandwidth up to 100 Mbps.
Duplex mode
The duplex mode of a physical Ethernet interface refers to its capabilities to transmit and receive
simultaneously.
Two different duplex modes exist:
Half duplex: an interface in half duplex mode can not transmit and receive data simultaneously.
Full duplex: an interface in full duplex mode can transmit and receive data simultaneously.
The duplex mode has an impact on the aggregate bandwidth of an Ethernet segment. 10 Mbps full
duplex results in an aggregate bandwidth of 20 Mbps, while 10 Mbps half duplex results in only
10 Mbps aggregate bandwidth.
Auto-negotiation
Auto-negotiation is a function allowing two physical Ethernet interfaces sharing an Ethernet segment to
exchange capability information and subsequently select and configure a common mode of operation. As a
result, the communication speed and duplex mode are automatically configured at both ends of the Ethernet
segment.
Several situations can occur:
The two interfaces support auto-negotiation: auto-negotiation assures that the “highest” common mode
of operation is selected.
Only one interface supports auto-negotiation: the interface supporting auto-negotiation automatically
switches to the mode of the other interface (provided it can handle this mode).
Auto-negotiation fails: if auto-negotiation fails to converge to a common mode, one can override the
auto-negotiation function by setting the communication speed and duplex mode manually.
E-DOC-CTC-20080229-0003 v1.0
13
Configuring physical Ethernet interfaces

For each physical Ethernet interface, two parameters can be configured with the command
:eth device ifconfig.
One parameter must be specified:
Intf: the name of the interface to be configured.
Following optional parameters can be used to configure the interface:
Type: this parameter specifies the communication speed (10Base-T or 100Base-T) and the duplex mode
(full duplex or half duplex) of the interface.
Several values are possible:
Auto: by default, the type is set to auto (or 0) in order to use auto-negotiation. The default value
should not be changed, except in case of communication problems.
10BaseTHD/10BaseTFD/100BaseTHD/100BaseTFD: if one of these values is used, auto-negotiation is
not used and the interface is configured with a specific speed and duplex mode.
State: it is possible to enable or disable the interface with this parameter. By default, all interfaces are
enabled.
For example, configure the interfaces as follows:
1 Connect the physical Ethernet interface ethif1 with the interface of a PC supporting auto-negotiation.
This requires no additional configuration.
2 Connect the physical Ethernet interface ethif2 with the interface of a PC supporting auto-negotiation.
Set the communication speed of interface ethif2 to 10 Mbps and the duplex mode to half duplex.
=>:eth device ifconfig intf=ethif3 type=10BaseTHD
3 Connect the physical Ethernet interface ethif3 with the interface of a PC. Set the communication speed
of this PC to 10 Mbps and the duplex mode to half duplex. This requires no additional configuration of
interface ethif3.
4 Disable interface ethif4:
=>:eth device ifconfig intf=ethif1 state=disabled
Displaying interface information

To check the resulting status of the physical Ethernet interfaces, execute following command:
=>:eth device iflist

Interface Type Result State
ethif1 auto 100BaseTFD UP [forwarding]
ethif2 10BaseTHD 10BaseTHD UP [forwarding]
ethif3 auto 10BaseTHD UP [forwarding]
ethif4 auto Not connected DOWN [disabled]
Result indicates the effective operating status if Type is set to auto.
14 E-DOC-CTC-20080229-0003 v1.0
4| Ethernet Switch
4 Ethernet Switch
4.1 Port Mirroring
Introduction
The CLI commands described in this section are part of the command group :eth switch mirror.
What is port mirroring?

Port mirroring is used to monitor traffic on an Ethernet switch port by forwarding that traffic to another port.
Two special ports are defined:
Mirror capture port: all traffic that you want to monitor is forwarded to this port.
Only one port can be configured as mirror capture port at a time.
Mirrored port: the traffic that you want to monitor is the traffic on this port. A distinction is made between
ingress traffic and egress traffic.
Mirrored ingress port: traffic received on this port is forwarded to the mirror capture port.
Only one port can be configured as mirrored ingress port at a time.
Mirrored egress port: traffic transmitted from this port is forwarded to the mirror capture port.
Only one port can be configured as mirrored egress port at a time.
A port can be configured as mirrored ingress port and mirrored egress port simultaneously.
Port mirroring is typically used for debugging. To this end, a PC is connected to the mirror capture
port.
It is possible to configure multi-port mirroring, i.e. the mirrored ingress port differs from the
mirrored egress port. As this can cause congestion, multi-port mirroring should not be used.
Ingress and egress traffic

The difference between ingress and egress traffic is shown in following illustration:
Mirror capture port
Mirrored port
Egress traffic
Ingress traffic
E-DOC-CTC-20080229-0003 v1.0
15
4| Ethernet Switch
Configuring port mirroring

To configure port mirroring on the Thomson Gateway, you must define the mirror capture port and the
mirrored ports:
Configure ethif1 as mirror capture port with following command:
=>:eth switch mirror capture port=1
Configure ethif3 as mirrored ingress port with following command:
=>:eth switch mirror ingress port=3
Configure ethif3 as mirrored egress port with following command:
=>:eth switch mirror egress port=3
The resulting configuration can be checked as follows:
=>:eth switch mirror capture

Mirror capture port = 1
=>:eth switch mirror ingress
Ingress mirror port = 3
=>:eth switch mirror egress
Egress mirror port = 3
To change the mirrored ingress/egress port, you must explicitly disable the old mirrored ingress/egress port:
=>:eth switch mirror ingress port=3 state=disabled

=>:eth switch mirror ingress port=4
16 E-DOC-CTC-20080229-0003 v1.0
4| Ethernet Switch
4.2 Port Grouping and Port Isolation
Introduction
The CLI commands described in this section are part of the command group :eth switch group.
What is port grouping?

The four ports of the Ethernet switch can be placed in different groups.
To configure port grouping, two parameters are important:
Group: this parameter indicates the number of the group, which is a number from 0 through 3.
By default, each port is a member of Group 0.
Port: this parameter indicates the number of the port, which is a number from 1 through 4.
A port can be a member of only one group at a time.
What is port isolation?

Port isolation is based on port grouping. Port isolation aims to block traffic sent from one group to another
group. Ports in the same group can communicate with each other. Ports that are part of different groups
cannot communicate with each other.
Port isolation uses the following traffic forwarding algorithm:
Only if a frame is transmitted from a source port that is a member of a specific group (not Group 0) to a
destination port that is a member of another group (not Group 0), the frame is dropped.
A destination port accepts frames from any source port that is a member of the same Group.
Frames from a source port that is a member of Group 0, are forwarded to any destination port.
A destination port that is a member of Group 0 accepts frames from any source port.
Configuring port grouping

To reset the groups to the default configuration, execute following command:
=>:eth switch group flush
To check the current configuration, list the configured groups as follows:
=>:eth switch group list

Group 0 Ports: 1 2 3 4
E-DOC-CTC-20080229-0003 v1.0
17
4| Ethernet Switch
Examples
Several scenarios are possible. We give some examples:
To configure two group isolation, execute following commands:
=>:eth switch group move group=1 port=1

This results in the following configuration:

Group 0 Ports: 3 4
Group 1 Ports: 1
Group 2 Ports: 2
The following illustration indicates which ports can communicate with each other and which ports are
isolated from each other:
Port 2
Group 2
op
Fo
Dr
rw
ar
d
Port 1 Forward Port 3

Group 1 Group 0
Forward
d
ar
Fo
w
r
r
w
Fo
ar
d
Port 4
Group 0
18 E-DOC-CTC-20080229-0003 v1.0
4| Ethernet Switch
To configure three group isolation, execute following commands:

This results in the following configuration:

Group 0 Ports: 4
Group 1 Ports: 1
Group 2 Ports: 2
Group 3 Ports: 3
The following illustration indicates which ports can communicate with each other and which ports are
isolated from each other:
Port 2
Group 2
op
Dr
Dr
op
Port 1 Drop Port 3

Group 1 Group 3
Forward
d
ar
Fo
w
r
r
w
Fo
ar
d
Port 4
Group 0
The configuration of four group isolation or all port isolation is not always possible and depends on the
used platform. Four group isolation is only possible if the group parameter is a number from 0 through 4.
E-DOC-CTC-20080229-0003 v1.0
19
4| Ethernet Switch
4.3 Port Sharing
Introduction
The CLI commands described in this section are part of the command group :eth switch share.
What is port sharing?

Port sharing is used to share a port of the Ethernet switch with other ports of the Ethernet switch, even when
the group membership or VLAN membership is different.
To configure port sharing, two parameters are important:
Port: this parameter indicates the number of the port, which is a number from 1 through 4.
Shared: this parameter indicates the number of the shared port, which is a number from 1 through 4.
Port sharing must be used with caution, because this command can break port isolation or VLAN
isolation.
Configuring port sharing

By default, there are no shared ports.
To allow traffic to be sent from port 1 towards port 2, execute following command:
=>:eth switch share add port=1 shared=2
To obtain an overview of the shared ports, execute following command:
=>:eth switch share list

Port Shared ports
1 2
To remove shared ports from the list, execute following command:
=>:eth switch share delete port=1 shared=2
20 E-DOC-CTC-20080229-0003 v1.0
4| Ethernet Switch
Example: port sharing and port grouping

Following example illustrates how port sharing allows communication between two ports with a different
group membership.
The test setup is shown in the following illustration:
PC 2
Port 2
Port 1
PC 1
Proceed as follows:
Configure two group isolation:
=>:eth switch group move group 1 port 1

=>:eth switch group move group 2 port 2
Group 0 Ports: 3 4
Group 1 Ports: 1
Group 2 Ports: 2
As a result, no communication is possible between port 1 and port 2. It is not possible to ping from PC 1
to PC 2.
In order to allow traffic from port 1 to port 2, port 2 must be configured as a shared port:
=>:eth switch share add port 1 shared 2

Port Shared ports
1 2
As a result, Ping requests sent by PC 1 are received by PC 2. However, Ping replies are still not forwarded
from port 2 to port 1.
In order to allow traffic from port 2 to port 1, port 1 must also be configured as a shared port:
=>:eth switch share add port 2 shared 1

Port Shared ports
1 2
2 , 1
Now Ping requests and Ping replies can be exchanged between PC 1 and PC 2.
Communication between the two ports remains possible, even when the entries are removed
from the list. Port sharing has broken the port isolation and it is necessary to configure the port
isolation again to disable communication between the two ports.
E-DOC-CTC-20080229-0003 v1.0
21
4| Ethernet Switch
22 E-DOC-CTC-20080229-0003 v1.0
5| Ethernet Bridge
5 Ethernet Bridge
5.1 The Bridge and the Interface Architecture
Introduction
This section situates the bridge in the interface architecture of the Thomson Gateway. Simple configuration
examples illustrate the connection of the bridge to other interfaces of the architecture.
Interface architecture
Following illustration situates the bridge in the interface architecture of the Thomson Gateway. The Ethernet
bridge is indicated in red:
LoopBack
IP Forwarding
IP Interface(s)
ARP PPP
iARP
Multilink
PPP
IPoEoA
VLAN
Bridge EthoA
ATM Interface(s)
ATM Bundle

ISDN
E-DOC-CTC-20080229-0003 v1.0
23
5| Ethernet Bridge
Lower layer interfaces

According to the interface architecture, the bridge can be connected to different types of lower layer (LL)
interfaces:
Physical Ethernet interface
Physical wireless interface
ATM interface
ATM interface bundle
The bridge is connected to a lower layer interface via a bridge port.
Upper layer interfaces

According to the interface architecture, the bridge can be connected to different types of upper layer (UL)
interfaces:
Logical Ethernet interface
PPP relay interface
LocalNetwork IP interface
The bridge is configured as the destination of an upper layer interface.
A special bridge port is the OBC, which is an internal bridge port and can be seen as the port to the network
layer.
Configuring the bridge and lower layer interfaces

Proceed as follows to connect the bridge to a specific lower layer interface:
1 Create a new bridge port.
2 Configure this bridge port: define the lower layer interface as the destination of the bridge port.
3 Attach the bridge port.
The configuration is very similar for the different lower layer interface types:
Physical Ethernet interface:
By default, the bridge ports ethport1, ethport2, ethport3 and ethport4 are connected to the physical
Ethernet interfaces ethif1, ethif2, ethif3 and ethif4 respectively. If one of these bridge ports is deleted
(ethport1 can not be deleted), you can connect the bridge to a physical Ethernet interface as follows:
=>:eth bridge ifdelete intf=ethport2

=>:eth bridge ifadd intf=eth_local
=>:eth bridge ifconfig intf=eth_local dest=ethif2
=>:eth bridge ifattach intf=eth_local
Physical wireless interface:

By default, the bridge port WLAN is connected to the physical wireless interface wlif1. If this bridge port is
deleted, you can connect the bridge to the physical wireless interface as follows:
=>:eth bridge ifdelete intf=WLAN

=>:eth bridge ifadd intf=wireless
=>:eth bridge ifconfig intf=wireless dest=wlif1
=>:eth bridge ifattach intf=wireless
24 E-DOC-CTC-20080229-0003 v1.0
5| Ethernet Bridge
ATM interface:
You can connect the bridge to an ATM interface. The creation of this ATM interface is also described in
following CLI commands:
=>:atm phonebook add name=atm_pvc_data addr=8.35

=>:atm ifadd intf=atm_data
=>:atm ifconfig intf=atm_data dest=atm_pvc_data ulp=mac
=>:atm ifattach intf=atm_data
=>:eth bridge ifadd intf=eth_data
=>:eth bridge ifconfig intf=eth_data dest=atm_data
=>:eth bridge ifattach intf=eth_data
ATM interface bundle:

You can connect the bridge to an ATM interface bundle. The creation of this ATM interface bundle is also
described in following CLI commands:

=>:atm bundle add name=atm_bundle_data
=>:atm bundle ifadd name=atm_bundle_data intf=atm_data
=>:atm bundle attach name=atm_bundle_data
=>:eth bridge ifadd intf=eth_data
=>:eth bridge ifconfig intf=eth_data dest=atm_bundle_data
=>:eth bridge ifattach intf=eth_data
The ATM interface bundles feature is only available on selected products.
For a detailed description of all parameters of the command eth bridge ifconfig, see
“5.4 Ethernet Bridge Ports” on page 38.
Configuring the bridge and upper layer interfaces

The bridge can be the destination of different upper layer interface types.
Logical Ethernet interface:
To connect the bridge to a logical Ethernet interface, proceed as follows:
1 Create a new logical Ethernet interface.
2 Configure the logical Ethernet interface: define the bridge as destination of this new interface and
specify to which VLAN the logical Ethernet interface must be assigned. Only one logical Ethernet
interface can be assigned to each VLAN. As the default VLAN is already assigned to the bridge itself,
you must create a new VLAN first.
3 Attach the logical Ethernet interface.
=>:eth vlan add name=video vid=2

=>:eth ifadd intf=eth_video
=>:eth ifconfig intf=eth_video dest=bridge vlan=video
=>:eth ifattach intf=eth_video
E-DOC-CTC-20080229-0003 v1.0
25
5| Ethernet Bridge
PPP relay interface:

By default, the bridge is added to the PPP relay agent list. If the bridge is not yet in the agent list, execute
following command:
=>:ppp relay ifadd intf=bridge
LocalNetwork IP interface:
By default, the IP interface LocalNetwork is directly connected to the bridge via an invisible logical
Ethernet interface. If this interface was removed, one (and only one) IP interface can be created and
directly connected to the bridge.
=>:ip ifadd intf=ip_test dest=bridge

=>:ip ifattach intf=ip_test
For a detailed description of all parameters of the command :eth ifconfig, see
“6.2 Configuring Logical Ethernet Interfaces” on page 53.
26 E-DOC-CTC-20080229-0003 v1.0
5| Ethernet Bridge
5.2 The Self-Learning Transparent Bridge
Introduction
The basic bridge mechanisms are implemented according to IEEE 802.1D, which is the MAC bridge standard.
Amongst other things, IEEE 802.1D describes the self-learning transparent bridge functionality:
Transparent means that the hosts, which are connected to the network, do not notice the presence of the
bridge in the network.
Self-learning means that the bridge itself creates and updates entries in the filtering database.
This functionality consists of three main parts:
Filtering database: the filtering database stores all information that the bridge needs in order to forward
received MAC frames.
Learning process: during the learning process, the bridge creates and updates entries in the filtering
database. The learning process is based on received MAC frames.
Forwarding process: during the forwarding process, the filtering database is consulted to decide whether
a received MAC frame is forwarded or dropped. If a MAC frame is forwarded, the forwarding process also
decides to which bridge ports the frame is forwarded.
Port states
A bridge port can be in one of the following three port states:
Learning: this port state is assigned to a port that learns from MAC frames but does not forward any MAC
frames.
Forwarding: this port state is assigned to a port that both learns from MAC frames and forwards MAC
frames.
Disabled: any port that is not enabled has the port state disabled.
By default, all ports are in the forwarding state.
=>:eth bridge ifconfig intf=ethport1 portstate=forwarding
To change the port state to the learning state, execute following command:
=>:eth bridge ifconfig intf=ethport1 portstate=learning
To disable the port, execute following command:
=>:eth bridge ifconfig intf=ethport1 portstate=disabled
E-DOC-CTC-20080229-0003 v1.0
27
5| Ethernet Bridge
5.2.1 Filtering Database
Introduction
The filtering database contains different types of entries:
Permanent entries: these entries have priority over the static and dynamic entries.
Static entries: these entries have priority over the dynamic entries.
Dynamic entries
The CLI commands described in this section are part of the command group :eth bridge.
Permanent entries
A permanent entry is defined as an entry stored in the permanent database. Permanent entries can not be
removed. These entries are stored during production.
These permanent entries are:
00:14:7F:01:DC:9E: the MAC address of the Thomson Gateway itself.
To check the MAC address of your Thomson Gateway, execute following command:
=>:env get var=_MACADDR

00-14-7F-01-DC-9E
01:80:C2:00:00:[00-0F] and 01:80:C2:00:00:10: these entries are added to the permanent database in
accordance with the standard IEEE 802.1D.
01:80:C2:00:00:[20-2F]: these entries are added to the permanent database in accordance with the
standard IEEE 802.1Q.
FF:FF:FF:FF:FF:FF: the MAC broadcast address.
Static entries
A static entry is defined as an entry that has not been obtained through the learning process. Two types of
static entries are distinguished:
Default static entries: these entries are added to the filtering database by default and can not be removed
from the filtering database. The Thomson Gateway has static entries for the following destination MAC
addresses:
00:14:7F:01:DD:00: the MAC address of the wireless interface.
To check the MAC address of the wireless interface, execute following command:
=>:env get var=_WL_MACADDR

00-14-7F-01-DD-00
01:00:5E:00:00:67: this multicast MAC address corresponds to the IP address 224.0.0.103, used by the
Multi-Directory Access Protocol (MDAP).
01:00:5E:7F:FF:FA: this multicast MAC address corresponds to the IP address 239.255.255.250, used
by the Simple Service Discovery Protocol (SSDP), which is the basis of UPnP.
Configured static entries: these entries are created using CLI commands.
28 E-DOC-CTC-20080229-0003 v1.0
5| Ethernet Bridge
Configuring static entries

Static entries can be configured using CLI commands:
To add a static entry to the filtering database, execute following command:
=>:eth bridge macadd hwaddr=00:00:00:00:00:01 intf=ethport1
As a result, when the bridge receives a frame with destination MAC address 00:00:00:00:00:01, this frame
is forwarded to the destination port ethport1. Both the parameters hwaddr and intf must be specified.
For each destination MAC address, only one static entry can be created.
To remove a static entry from the filtering database, execute following command:
=>:eth bridge macdelete hwaddr=00:00:00:00:00:01
This command removes the entry with destination MAC address 00:00:00:00:00:01.
Static entries can also be added and removed when multiple bridge instances or VLANs exist. In this
case, additional parameters can be specified:
Brname: if multiple bridge instances exist, a specific bridge instance can be specified.
Vlan: if multiple VLANs exist, a specific VLAN can be specified.
Dynamic entries
Dynamic entries are created and updated by the learning process. See “5.2.2 Learning Process” on page 30
for a detailed description of the learning process.
Displaying the filtering database

To display the filtering database of the Thomson Gateway, execute following command:
=>:eth bridge maclist

00:14:7f:01:dc:9e -- permanent, default
00:14:7f:01:dd:00 -- static, default, OBC
01:00:5e:00:00:67 -- static, default
01:00:5e:7f:ff:fa -- static, default
01:80:c2:00:00:00 -- permanent
01:80:c2:00:00:01 -- permanent
01:80:c2:00:00:02 -- permanent
01:80:c2:00:00:03 -- permanent
01:80:c2:00:00:04 -- permanent
01:80:c2:00:00:05 -- permanent
01:80:c2:00:00:06 -- permanent
01:80:c2:00:00:07 -- permanent
...
E-DOC-CTC-20080229-0003 v1.0
29
5| Ethernet Bridge
5.2.2 Learning Process
Introduction
The learning process creates and updates the dynamic entries in the filtering database.
A dynamic entry is learned by observing the frames received by the bridge ports. The entry associates the
source MAC address of the received frame with the receiving port. The entries are learned automatically and
are removed using an ageing mechanism.
Ageing time
Each dynamic entry in the filtering database has an ageing time or lifetime. This lifetime can range from 10 s
to 1 000 000 s (approximately 12 days) with a granularity of 1 s. The default value is 300 s (5 minutes). When
the lifetime of a dynamic entry expires, that entry is removed from the filtering database.
To display the lifetime of dynamic entries in the Thomson Gateway, execute following command:
=>:eth bridge config

Ageing : 300
Filter : no_WAN_broadcast
VLAN : disabled
IPQoS precedence map for TOS:
IP priority QoS internal class
0 4
1 7
2 9
3 11
4 13
5 14
6 15
7 15
To modify the value of the lifetime, execute following command:
=>:eth bridge config age=350
Dynamic entry
A dynamic entry looks as follows:
00:19:b9:2d:0f:c1 -- dynamic, default, ethport4, 297 seconds
MAC address Entry type VLAN Port Remaining lifetime
30 E-DOC-CTC-20080229-0003 v1.0
5| Ethernet Bridge
5.2.3 Forwarding Process
Introduction
The forwarding process decides whether a received frame is forwarded or dropped (filtered). If a frame is
forwarded, the forwarding process also indicates to which ports the frame is forwarded.
Basic filtering
Basic filtering is defined as filtering on the destination MAC address. When a port receives a frame (= source
port), the filtering database is consulted to find an entry for the destination MAC address.
Three situations are possible:
The filtering database has no entry for the destination MAC address.
The filtering database has a static or permanent entry for the destination MAC address.
The filtering database has a dynamic entry for the destination MAC address.
No entry
If no entry is found, the frame is sent to all ports except the source port. This is called flooding.
Static or permanent entry

For each permanent or static entry, the bridge has an internal table, indicating for each possible source port
to which destination ports the frame must be forwarded.
Dynamic entry
If the entry is a dynamic entry, the frame is sent to the learned port. This is called forwarding. However, if the
learned port is the same as the source port, the frame is dropped or filtered.
E-DOC-CTC-20080229-0003 v1.0
31
5| Ethernet Bridge
5.3 Multiple Bridge Instances
5.3.1 Creating Multiple Bridge Instances
Introduction
When multiple bridge instances are created, each bridge instance acts as an independent bridge. This means
that no Ethernet traffic exists between two bridge instances.
Configuring multiple bridge instances

To configure a bridge instance, proceed as follows:
To create a new bridge instance, execute following command:
=>:eth bridge add brname=new_bridge
To select a bridge instance as the default bridge instance, execute following command:
=>:eth bridge select brname=new_bridge
This default bridge instance will be used to configure the bridge ports if the parameter brname is not
specified, for example in the commands :eth bridge ifconfig, :eth bridge maclist,...
To delete a bridge instance, execute following command:
=>:eth bridge delete brname=new_bridge
The original bridge instance bridge cannot be deleted.
Example
Following example illustrates the use of multiple bridge instances:
The default bridge instance is used for data traffic.
A second bridge instance is created and used for video traffic.
32 E-DOC-CTC-20080229-0003 v1.0
5| Ethernet Bridge
The target configuration of the Thomson Gateway is depicted in the following illustration:
OBC
to router
ethport1 OBC1
physical
ATM
ethport2 ethernet br_wan
ports
ethport3 ports BRIDGE “bridge”
to router
physical ATM
ethport4 ethernet ports br_video
ports
BRIDGE “videobridge”
To set up this example, proceed as follows:

Create the ATM connections for data traffic and video traffic:
=>:atm phonebook add name=pvc_data addr=8.35

=>:atm ifconfig intf=atm_data dest=pvc_data
=>:atm phonebook add name=pvc_video addr=0.38
=>:atm ifadd intf=atm_video
=>:atm ifconfig intf=atm_video dest=pvc_video
=>:atm ifattach intf=atm_video
Add a bridge port to the default bridge for the WAN data connection:
=>:eth bridge ifadd brname=bridge intf=br_wan

=>:eth bridge ifconfig brname=bridge intf=br_wan dest=atm_data
=>:eth bridge ifattach brname=bridge intf=br_wan
Create a new bridge instance and add a bridge port to this instance for the WAN video connection:
=>:eth bridge add brname=videobridge

=>:eth bridge ifadd brname=videobridge intf=br_video
=>:eth bridge ifconfig brname=videobridge intf=br_video dest=atm_video
=>:eth bridge ifattach brname=videobridge intf=br_video
By default, ethport4 is attached to the default bridge. Delete this bridge port from the default bridge and
create a new bridge port to be attached to the video bridge:
=>:eth bridge ifdetach brname=bridge intf=ethport4

=>:eth bridge ifdelete brname=bridge intf=ethport4
=>:eth bridge ifadd brname=videobridge intf=ethport4
=>:eth bridge ifconfig brname=videobridge intf=ethport4 dest=ethif4
=>:eth bridge ifattach brname=videobridge intf=ethport4
E-DOC-CTC-20080229-0003 v1.0
33
5| Ethernet Bridge
5.3.2 Configuring a Bridge Instance
Introduction
Listing bridge information

The bridge information that can be displayed consists of:
Configuration flags: for example the configuration of the multicast filter, IGMP snooping,...
Connection information: for example the connection state, the interface state,...
Statistics: for example the number of received bytes, transmitted bytes,...
To obtain an overview of all bridge instances and their bridge ports, execute following command:
=>:eth bridge list
If you want to display more specific information, additional parameters can be specified:
Brname: the list is restricted to the specified bridge instance and its bridge ports.
=>:eth bridge list brname=newbridge

bridge configuration for "newbridge" :
OBC1 : dest : Internal
Connection State: not-connected Retry: 10
Priority Tagging: Disabled
Port: (Unassigned) PortNr: (Unknown)
String: the list is restricted to the lines that contain the specified string.
=>:eth bridge list string=eth

ethport1 : dest : ethif1
Port: ethport1 PortNr: 1 PortState: forwarding Interface: down
Port: ethport2 PortNr: 2 PortState: forwarding Interface: down
Port: ethport3 PortNr: 3 PortState: forwarding Interface: unknown
Port: ethport5 PortNr: 5 PortState: forwarding Interface: up
34 E-DOC-CTC-20080229-0003 v1.0
5| Ethernet Bridge
Beginstring: the list is restricted to the part of the list that starts with the specified string.
=>:eth bridge list beginstring=WLAN

WLAN : dest : wlif1
Connection State: connected Retry: 10
Multicast filter: disabled Dynamic VLAN : disabled
WAN : disabled
IGMP snooping : enabled
Transparent Prio: disabled
BPDU Filtering : disabled
Extra Tagging : none
VLAN: Default VLAN: default Ingressfiltering: disabled
Acceptvlanonly: disabled
VLAN: Priority: disabled IP Prec: disabled Priority: 0
Regeneration table: 0 1 2 3 4 5 6 7
RX bytes: 0 frames: 0
TX bytes: 5531 frames: 44 dropframes: 0
You can also use a combination of the parameters brname, string and beginstring.
Configuring a bridge instance

To configure a bridge instance, execute the command :eth bridge config.
If no parameters are specified, the configuration of the bridge is displayed:

Ageing : 300
Filter : no_WAN_broadcast
VLAN : disabled
0 4
1 7
2 9
3 11
4 13
5 14
6 15
7 15
Optionally, several parameters can be specified to configure a bridge instance. Most of these parameters are
described in detail in other sections or documents:
Brname: the name of the bridge instance you want to configure. If this parameter is not specified, the
default bridge instance is selected.
Age: see “ Ageing time” on page 30 for more information.
Filter: see “ Configuring the broadcast filter” on page 43 for more information.
Vlan: see the “VLAN Configuration Guide” for more information.
Precedencemap: see the “Ethernet QoS Configuration Guide” for more information.
E-DOC-CTC-20080229-0003 v1.0
35
5| Ethernet Bridge
Flushing bridge ports

The command :eth bridge flush is used to detach and delete all bridge ports of a bridge instance. If no
bridge instance is specified, the bridge ports of the default bridge instance are flushed.
=>:eth bridge flush

=>:eth bridge list
OBC : dest : Internal
Port: OBC PortNr: 0 PortState: forwarding Interface: up
WAN : enabled
VLAN: Default VLAN: default Ingressfiltering: disabled Acceptvlanonly: disabled

Priority Tagging: NA (destination switch interface)
WAN : disabled
The bridge ports OBC and ethport1 can not be flushed.
Clearing bridge port statistics

The command :eth bridge clear is used to clear all bridge port statistics of a bridge instance. If no
bridge instance is specified, the default bridge instance is selected.
36 E-DOC-CTC-20080229-0003 v1.0
5| Ethernet Bridge
If a bridge instance is cleared, the send (TX), receive (RX) and drop statistics of the bridge ports are set to 0.
=>:eth bridge iflist intf=ethport1

WAN : disabled
=>:eth bridge clear
WAN : disabled
E-DOC-CTC-20080229-0003 v1.0
37
5| Ethernet Bridge
5.4 Ethernet Bridge Ports
Introduction
Listing bridge ports

To obtain an overview of the default bridge instance and its bridge ports, execute following command:
=>:eth bridge iflist
If you want to display more specific information, additional parameters can be specified:
Brname: this parameter is used to list the bridge ports of a bridge instance that is not the default bridge
instance.
String: same behaviour as in case of the command :eth bridge list.
Beginstring: same behaviour as in case of the command :eth bridge list.
Intf: the list is restricted to the specified bridge port.

WAN : disabled
VLAN: Default VLAN: default Ingressfiltering: disabled
Acceptvlanonly: disabled
You can also use a combination of the parameters brname, string, beginstring and intf.
Creating bridge ports

To create a new bridge port on the bridge, execute the command :eth bridge ifadd.
Following parameter must be specified:
Intf: the name of the new bridge port.
38 E-DOC-CTC-20080229-0003 v1.0
5| Ethernet Bridge
Optionally, following parameter can be specified:

Brname: the name of the bridge instance to which the new bridge port is added. If this parameter is not
specified, the default bridge instance is selected.
=>:eth bridge ifadd intf=eth_test

=>:eth bridge iflist intf=eth_test
eth_test : dest : (none)
Configuring bridge ports

To configure a newly created bridge port or to modify the existing configuration of a bridge port, execute the
command :eth bridge ifconfig.
Specify the required parameters:
Mandatory parameters: following parameters must be specified:
Intf: the name of the bridge port to be configured.
Brname: the name of the bridge instance to which the bridge port belongs. If the bridge port is not a
member of the default bridge instance, this parameter must be specified. If this parameter is not
Optional parameters: optionally, several parameters can be specified to configure the bridge port:
Dest: this parameter indicates the destination of the bridge port. The type of the destination interface
must be one of the following lower layer interface types: physical Ethernet interface, physical
wireless interface, ATM interface or ATM interface bundle.
Retry: the value of this parameter is a number within the range of 0 through 65535. The value
indicates the number of times the Thomson Gateway retries to set up a WAN connection before
giving up. The default value is 10.
Wan: this parameter indicates whether the bridge port is located at the WAN side (enabled) or at the
LAN side (disabled). The bridge does not forward traffic between two bridge ports with the WAN
parameter enabled.
! If the destination is an ATM interface, the parameter is enabled by default.
! If the destination is a physical Ethernet or wireless interface, the parameter is disabled by default.
If you want to use a physical Ethernet port as WAN port, it is recommended to enable the
WAN parameter of the corresponding bridge port. Doing so, Ethernet frames are handled
by the Ethernet bridge instead of the switch (see “ Ethernet switch and Ethernet bridge” on
page 6).
Portstate: see “ Port states” on page 27.
Parameters for specific features (optional): following parameters relate to specific features of the bridge
ports and are described in separate sections of this chapter.
Mcastfilter: see “ Configuring the multicast filter” on page 44.
Igmpsnooping: this parameter is used to enable or disable IGMP snooping on the bridge port.
Bpdufiltering: see “ Enabling BPDU filtering” on page 47.
VLAN related parameters (optional): following parameters relate to the configuration of VLANs and are
described in detail in the “VLAN Configuration Guide“.
Vlan
Ingressfiltering
Acceptvlanonly
Dynvlan
Xtratagging
E-DOC-CTC-20080229-0003 v1.0
39
5| Ethernet Bridge
Quality of Service related parameters (optional): following parameters relate to the configuration of QoS
and are described in detail in the “Ethernet QoS Configuration Guide“.
Regenprio
Ipprec
Priority
Prioconfig
Priotag
Priotransparent
=>:eth bridge ifconfig intf=eth_test dest=atm_8_35 retry=20

eth_test : dest : atm_8_35
Attaching bridge ports

When a bridge port is attached, the port tries to set up an Ethernet connection with the specified
configuration. A bridge port can be attached using the command :eth bridge ifattach.
Intf: the name of the bridge port to be attached.
Optionally, following parameter can be specified:
Brname: the name of the bridge instance to which the bridge port is added. If this parameter is not
=>:eth bridge ifattach intf=eth_test

eth_test : dest : atm_8_35
Port: wan0 PortNr: 6 PortState: forwarding Interface: unknown
WAN : enabled
Detaching and deleting bridge ports

If a bridge port is detached, this interface is disconnected from the bridge.
=>:eth bridge ifdetach intf=ethport3

Port: (Unassigned) PortNr: (Unknown)
40 E-DOC-CTC-20080229-0003 v1.0
5| Ethernet Bridge
If a bridge port is deleted, this interface is removed from the bridge.

Invalid interface name.
Bad value for parameter 'intf'
You can delete a bridge port without detaching it first.
You cannot detach nor delete the bridge ports OBC and ethport1.
Flushing bridge ports

The command :eth bridge ifflush is used to detach and delete all bridge ports of a bridge instance. If
no bridge instance is specified, the bridge ports of the default bridge instance are flushed.
=>:eth bridge ifflush

=>:eth bridge iflist
OBC : dest : Internal
Port: OBC PortNr: 0 PortState: forwarding Interface: up
WAN : enabled

WAN : disabled
You cannot flush the bridge ports OBC and ethport1.
E-DOC-CTC-20080229-0003 v1.0
41
5| Ethernet Bridge
Modifying the configuration of a bridge port

To modify the existing configuration of a bridge port, execute the command :eth bridge ifconfig. For
more information, see “ Configuring bridge ports” on page 39.
Most parameters can be changed without detaching the bridge port first. However, there are some
exceptions. For example, it is necessary to detach a bridge port before its destination can be modified:
=>:eth bridge ifconfig intf=ethport4 dest=ethif2

Unable to set dest because link is busy.
=>:eth bridge ifdetach intf=ethport4
=>:eth bridge ifconfig intf=ethport4 dest=ethif2
=>:eth bridge ifattach intf=ethport4
=>:eth bridge iflist intf ethport4
WAN : disabled
42 E-DOC-CTC-20080229-0003 v1.0
5| Ethernet Bridge
5.5 No-WAN Broadcast Filter
Filtering WAN broadcast traffic

The bridge has a broadcast filter that has an impact on all WAN bridge ports. This filter can have two states:
If the filter state is set to no_WAN_broadcast, the bridge operates as follows:
Broadcasts originated by the Thomson Gateway and send to a WAN bridge port are dropped.
Broadcasts received by a WAN bridge port are not sent to the Thomson Gateway (via the OBC).
Broadcasts are still forwarded from a LAN bridge port to a WAN bridge port and vice versa.
If the filter state is set to none, no broadcasts are dropped. All broadcasts are passed through.
Configuring the broadcast filter

By default, the broadcast filter is set to no_WAN_broadcast.
To change the state of the broadcast filter, execute following command:
=>:eth bridge config filter=none
To check the state of the broadcast filter, execute following command:

Ageing : 300
Filter : none
VLAN : disabled
0 4
1 7
2 9
3 11
4 13
5 14
6 15
7 15
Example
The state of the broadcast filter must be set to none if, for example, the Thomson Gateway is configured with:
A DHCP client for an IP interface that is connected to the bridge: the DHCP requests sent by the DHCP
client are broadcasts originated at the Thomson Gateway itself and must be forwarded to the WAN
bridge ports.
A PPP interface to set up a PPPoE connection via the bridge: the PADI (PPPoE Active Discovery Initiation)
frames sent by the PPP interface are broadcasts originated at the Thomson Gateway itself and must be
forwarded to the WAN bridge ports.
E-DOC-CTC-20080229-0003 v1.0
43
5| Ethernet Bridge
5.6 Multicast Filter
Filtering multicast traffic

For each bridge port, a multicast filter can be enabled or disabled:
If the multicast filter is enabled, all multicast packets that the bridge port receives from the bridge are
dropped. Multicast packets received from a host or router connected to the bridge port are still
forwarded.
If the multicast filter is disabled, also the multicast packets that the bridge port receives from the bridge
are forwarded to the hosts and/or routers connected to that bridge port.
Some devices of the Thomson Gateway family have the following limitation:
For bridge ports that are connected to the Ethernet switch, the multicast filter can not be enabled
per port. The multicast filter must be enabled on each bridge port that is connected to the Ethernet
switch and to which a host or router is connected.
Multicast filtering or IGMP snooping?

Multicast filtering should not be used in combination with IGMP snooping.
Both features prevent that a multicast stream is sent to hosts that are not interested in receiving that stream.
However, IGMP snooping acts in a different way. While the multicast filter drops all multicast packets that a
bridge port receives from the bridge, IGMP snooping can be used to drop a specific multicast stream if only
hosts (no routers) are connected to that port and no host has joined the multicast group.
Configuring the multicast filter

By default, the multicast filter is disabled on all bridge ports.
To enable the multicast filter on a specific bridge port, execute following command:
=>:eth bridge ifconfig intf=ethport1 mcastfilter=enabled
To check the state of the multicast filter, list the configuration of the bridge port as follows:

Multicast filter: enabled Dynamic VLAN : disabled
WAN : disabled
44 E-DOC-CTC-20080229-0003 v1.0
5| Ethernet Bridge
Example
Consider a simple network setup:
A bridged scenario is used on the Thomson Gateway.
A video server is connected via an ATM connection to the bridge port eth_video.
A STB (Set Top Box), which is used to receive multicast streams, is connected via an Ethernet connection
to the bridge port ethport1.
A data PC, which is not interested in receiving any multicast streams, is connected via an Ethernet
connection to the bridge port ethport2.
By enabling the multicast filter on the bridge port ethport2, multicast packets are only forwarded to the STB
and are not forwarded to the data PC.
The network setup is shown in the following illustration:
Ethernet connection
ATM connection
eth_video
Ethernet connection
ethport2
ethport1
E-DOC-CTC-20080229-0003 v1.0
45
5| Ethernet Bridge
5.7 BPDU Filtering
Introduction
A bridge filter consists of a set of filter rules. Each filter rule consists of:
Matching criteria: when the bridge receives a frame, the matching criteria are checked.
Actions: if a matching criterion is fulfilled, the corresponding actions are applied.
Currently, the Thomson Gateway supports a preconfigured BPDU bridge filter.
BPDU filtering
The following preconfigured BPDU filtering table specifies how specific BPDU (Bridge Protocol Data Unit)
frames must be handled:
Features SNAP code MAC address Action

PAgP 0x104 01-00-0C-CC-CC-CC Drop
PVSTP+ 0x10B 01-00-0C-CC-CC-CD Forward
UDLD 0x111 01-00-0C-CC-CC-CC Drop
CDP 0x2000 01-00-0C-CC-CC-CC Forward
LLDP 01-80-C2-00-00-02 Forward
STP 01-80-C2-00-00-00 Forward
VTP 0x2003 01-00-0C-CC-CC-CC Forward
GARP 01-80-C2-00-00-2x Forward
802.3x 01-80-C2-00-00-0F Drop
In addition, the following frames are dropped:
MAC address Ether type Sub-type Protocol

01-80-C2-00-00-02 0x8809 0x01, 0x02 802.3 LACP and LAMP
01-80-C2-00-00-02 0x8809 0x03 802.3 EFM OAM
01-80-C2-00-00-02 0x8809 0x04..0x0A Reserved for 802.3 slow protocols
01-80-C2-00-00-02 0x8809 Other Illegal value
This BPDU filtering table is implemented in the Thomson Gateway and is not configurable.
46 E-DOC-CTC-20080229-0003 v1.0
5| Ethernet Bridge
Enabling BPDU filtering

The BPDU filtering table can be enabled or disabled per bridge port.
By default, BPDU filtering is disabled on all bridge ports.
BPDU filtering is intended to be enabled on bridge ports with an ATM interface as destination. To enable
BPDU filtering on such a bridge port, execute following command:
=>:eth bridge ifconfig intf=eth_data bpdufiltering=enabled
E-DOC-CTC-20080229-0003 v1.0
47
5| Ethernet Bridge
48 E-DOC-CTC-20080229-0003 v1.0
6| Logical Ethernet Interfaces
6 Logical Ethernet Interfaces
6.1 Logical Ethernet and the Interface Architecture
Introduction
This section situates the logical Ethernet interfaces in the interface architecture of the Thomson Gateway.
Simple configuration examples illustrate the connection of a logical Ethernet interface to other interfaces of
the architecture.
Interface architecture
Following illustration situates the logical Ethernet interfaces in the interface architecture of the Thomson
Gateway. The logical Ethernet interfaces are indicated in red:
LoopBack
IP Forwarding
IP Interface(s)
ARP PPP
iARP
Multilink
PPP
IPoEoA
VLAN
Bridge EthoA
ATM Interface(s)
ATM Bundle

ISDN
E-DOC-CTC-20080229-0003 v1.0
49
Lower layer interfaces

According to the interface architecture, logical Ethernet interfaces can be connected to different types of
lower layer (LL) interfaces:
Ethernet bridge
ATM interface
Upper layer interfaces

According to the interface architecture, logical Ethernet interfaces can be connected to different types of
lower layer (UL) interfaces:
IP interface
PPP interface
PPP relay interface
Configuring logical Ethernet and lower layer interfaces

Proceed as follows to connect a logical Ethernet interface to a specific lower layer interface:
1 Create a new logical Ethernet interface.
2 Configure this interface: define the lower layer interface as the destination of the logical Ethernet
interface.
3 Attach the logical Ethernet interface.
The configuration is very similar for the different lower layer interface types:
Physical Ethernet interface:
By default, the bridge ports ethport1, ethport2, ethport3 and ethport4 are connected to the physical
Ethernet interfaces ethif1, ethif2, ethif3 and ethif4 respectively. If one of these bridge ports is deleted
(ethport1 can not be deleted), you can connect a logical Ethernet interface to a physical Ethernet interface
as follows:

=>:eth ifadd intf=eth_local
=>:eth ifconfig intf=eth_local dest=ethif2
=>:eth ifattach intf=eth_local
Physical wireless interface:

By default, the bridge port WLAN is connected to the physical wireless interface wlif1. If this bridge port is
deleted, you can connect a logical Ethernet interface to the physical wireless interface as follows:
=>:eth bridge ifdelete intf=WLAN

=>:eth ifadd intf=eth_wireless
=>:eth ifconfig intf=eth_wireless dest=wlif1
=>:eth ifattach intf=eth_wireless
50 E-DOC-CTC-20080229-0003 v1.0
Ethernet bridge:
In order to connect a logical Ethernet interface to the bridge, the bridge must be defined as destination of
the interface. In addition, it must be specified to which VLAN the logical Ethernet interface belongs. Only
one logical Ethernet interface can be assigned to each VLAN. As the default VLAN is already assigned to
the bridge itself, you must create a new VLAN first.

=>:eth ifadd intf=eth_tobridge
=>:eth ifconfig intf=eth_tobridge dest=bridge vlan=video
=>:eth ifattach intf=eth_tobridge

You can connect a logical Ethernet interface to another logical Ethernet interface. This way, logical
Ethernet interfaces can be stacked on top of each other. This feature is used at the WAN side to configure
several logical Ethernet interfaces with different VLANs (tagged) on top of a single logical Ethernet
interface with default VLAN (untagged).

=>:eth vlan add name=voice vid=3
=>:eth ifadd intf=eth_total
=>:eth ifconfig intf=eth_total dest=atm_data
=>:eth ifattach intf=eth_total
=>:eth ifadd intf=eth_1
=>:eth ifconfig intf=eth_1 dest=eth_total vlan=video
=>:eth ifattach intf=eth_1
=>:eth ifadd intf=eth_2
=>:eth ifconfig intf=eth_2 dest=eth_total vlan=voice
=>:eth ifattach intf=eth_2
ATM interface:
You can connect a logical Ethernet interface to an ATM interface. The creation of this ATM interface is also
described in following CLI commands:

=>:eth ifadd intf=eth_data
=>:eth ifconfig intf=eth_data dest=atm_data
=>:eth ifattach intf=eth_data
ATM interface bundle:

You can connect a logical Ethernet interface to an ATM interface bundle. The creation of this ATM
interface bundle is also described in following CLI commands:

=>:atm bundle add name=atm_bundle_data
=>:atm bundle ifadd name=atm_bundle_data intf=atm_data
=>:atm bundle attach name=atm_bundle_data
=>:eth ifadd intf=eth_data
=>:eth ifconfig intf=eth_data dest=atm_bundle_data
=>:eth ifattach intf=eth_data
The ATM interface bundles feature is only available on selected products.
E-DOC-CTC-20080229-0003 v1.0
51
For a detailed description of all parameters of the command :eth ifconfig, see “ Configuring
logical Ethernet interfaces” on page 54.
Configuring logical Ethernet and upper layer interfaces

A logical Ethernet interface can be connected to different upper layer interface types:
IP interface:
You can connect the logical Ethernet interface eth_local to an IP interface as follows:
=>:ip ifadd intf=ip_local dest=eth_local

=>:ip ifattach intf=ip_local
The Address Resolution Protocol (ARP) translates network layer addresses (for example IP
addresses) to hardware addresses (for example Ethernet MAC addresses). These mappings are
stored in the ARP cache of the Thomson Gateway.
PPP interface:
You can connect the logical Ethernet interface eth_data to a PPP interface as follows:
=>:ppp ifadd intf=ppp_data

=>:ppp ifconfig intf=ppp_data dest=eth_data user=user@inet password=pwinet
=>:ppp ifattach intf=ppp_data
PPP relay interface:

You can add the logical Ethernet interface eth_wireless to the PPP relay agent list as follows:
=>:ppp relay ifadd intf=eth_wireless

You can connect a logical Ethernet interface to another logical Ethernet interface. For more information,
see “ Configuring logical Ethernet and lower layer interfaces” on page 50.
52 E-DOC-CTC-20080229-0003 v1.0
6.2 Configuring Logical Ethernet Interfaces
Introduction
The CLI commands described in this section are part of the command group :eth.
Listing logical Ethernet interfaces

To list all logical Ethernet interfaces, execute following command:
=>:eth iflist
Optionally, if you want to display more specific information, additional parameters can be specified:
Intf: this parameter restricts the list to the specified interface. In this case, the displayed information is
extended with statistics about received and sent traffic.
=>:eth iflist intf=eth_dmz1

eth_dmz1 : Dest: bridge
WAN: Disabled
PortNr: 2
VLAN: dmz
Tx/Rx frames: 322/0
Tx/Rx octets: 119860/0
Rx discarded: 0
Tx/Rx multicasts: 322/0
Tx/Rx broadcasts: 0/0
Invalid length: 0
Invalid destination address: 0
Invalid VLAN id: 0
Unknown protocols: 0
String: this parameter restricts the list to the lines that contain the specified string.
=>:eth iflist string=dest

ethoa_8_35 : Dest: atm_8_35
eth_wan1 : Dest: bridge
eth_guest1 : Dest: bridge
Beginstring: this parameter restricts the list to the part of the list that starts with the specified string.
=>:eth iflist beginstring=eth_dmz1

WAN: Disabled
PortNr: 2
VLAN: dmz
eth_guest1 : Dest: bridge
WAN: Disabled
PortNr: 3
VLAN: guest
E-DOC-CTC-20080229-0003 v1.0
53
Creating logical Ethernet interfaces

To create a new logical Ethernet interface, execute the command :eth ifadd.
Only one parameter must be specified:
Intf: the name of the new interface.
=>:eth ifadd intf=eth_wan

=>:eth iflist intf=eth_wan
eth_wan : Dest: (none)
WAN: Disabled
PortNr: (unassigned)
VLAN: default
Configuring logical Ethernet interfaces

To configure a logical Ethernet interface, execute the command :eth ifconfig.
Intf: the name of the interface to be configured.
Optionally, several parameters can be specified to configure the interface:
Dest: this parameter indicates the destination of the interface. The type of the destination interface must
be one of following lower layer interface types:
Ethernet bridge
ATM interface
Retry: the value of this parameter is a number within the range from 0 through 65535. The value indicates
the number of times the Ethernet connection setup retries before giving up. The default value is 10.
Wan: this parameter indicates whether the interface is located at the WAN side (enabled) or at the LAN
side (disabled). By default, the parameter is disabled.
Priotag: this parameter indicates whether the priority tagging feature is enabled or not. By default,
priority tagging of egress traffic is disabled. The priority tagging feature of logical Ethernet interfaces is
very similar to the priority tagging feature of bridge ports.
Vlan : this parameter indicates the VLAN to which the interface belongs. By default, the logical Ethernet
interface is assigned to the default VLAN.
If the parameter is set to the default VLAN, the logical Ethernet interface transmits untagged frames.
If the parameter is set to another VLAN, the frames transmitted by the logical Ethernet interface are
tagged with the specified VLAN.
=>:eth ifconfig intf=eth_wan dest=atm_wan retry=20 wan=enabled priotag=enabled vlan=wan

eth_wan : Dest: atm_wan
WAN: Enabled
Priority Tagging: Enabled
VLAN: wan
54 E-DOC-CTC-20080229-0003 v1.0
Attaching logical Ethernet interfaces

When a logical Ethernet interface is attached, the interface tries to set up an Ethernet connection with the
specified configuration. You can attach a logical Ethernet interface with the command :eth ifattach.
Intf: the name of the interface to be attached.
=>:eth ifattach intf=eth_wan

Connection State: retrying Retry: 20
WAN: Enabled
VLAN: wan
Detaching logical Ethernet interfaces

When an attached logical Ethernet interface is detached, the Ethernet connection is stopped. The
configuration of the interface is still preserved. An interface can be detached using the command
:eth ifdetach.
Intf: the name of the interface to be detached.
=>:eth ifdetach intf=eth_wan

WAN: Enabled
VLAN: wan
Deleting logical Ethernet interfaces

When a logical Ethernet interface is deleted, the interface including its configuration is removed. To delete an
interface, execute the command :eth ifdelete.
Intf: the name of the interface to be deleted.
=>:eth ifdelete intf=eth_wan
You can not delete a logical Ethernet interface if it is the destination of an upper layer interface.
E-DOC-CTC-20080229-0003 v1.0
55
Flushing all logical Ethernet interfaces

To delete all logical Ethernet interfaces, execute the command :eth flush:
=>:eth flush
You can not delete a logical Ethernet interface if it is the destination of an upper layer interface.
56 E-DOC-CTC-20080229-0003 v1.0
THOMSON Telecom Belgium
Prins Boudewijnlaan 47
2650 Edegem
www.thomson-broadband.com
© Thomson 2008. All rights reserved.
E-DOC-CTC-20080229-0003 v1.0.

ConfigGuide - Ethernet Thomson Adsl Modem

Uploaded by

Copyright:

Available Formats

ConfigGuide - Ethernet Thomson Adsl Modem

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

ConfigGuide - Ethernet Thomson Adsl Modem

Uploaded by

Copyright:

Available Formats

Thomson Gateway

Ethernet Configuration Guide

Copyright ©1999-2008 Thomson. All rights reserved.

The following trademarks may be used in this document:

Status: v1.0 (March 2008)

About this Ethernet Configuration Guide ................................ 1

3 Physical Ethernet Interfaces ..................................................... 11

3.2 Configuring Physical Ethernet Interfaces ..................................................... 13

4 Ethernet Switch ......................................................................... 15

4.2 Port Grouping and Port Isolation .................................................................. 17

4.3 Port Sharing .................................................................................................. 20

5.2 The Self-Learning Transparent Bridge........................................................... 27

5.2.1 Filtering Database................................................................................................................................. 28

5.3 Multiple Bridge Instances ............................................................................. 32

5.3.1 Creating Multiple Bridge Instances ..................................................................................................... 32

5.4 Ethernet Bridge Ports.................................................................................... 38

5.5 No-WAN Broadcast Filter .............................................................................. 43

5.6 Multicast Filter .............................................................................................. 44

5.7 BPDU Filtering .............................................................................................. 46

6 Logical Ethernet Interfaces ....................................................... 49

6.2 Configuring Logical Ethernet Interfaces ....................................................... 53

About this Ethernet Configuration Guide

A note provides additional information about a topic.

Documentation and software updates

“3 Physical Ethernet Interfaces” 11

“6 Logical Ethernet Interfaces” 49

Supported Ethernet features

Thomson Gateway interface architecture

Ethernet Interface(s) PPPoA

Physical Ports ATM VP/VC

Ethernet switch and Ethernet bridge

- High speed - Lower speed

Displaying the list of interfaces

=>:interface list expand=enabled reverse=enabled

Defaults on residential devices

=>:interface list expand=disabled reverse=disabled

ethport1 ethport2 ethport3 ethport4 WLAN

ethif1 ethif2 ethif3 ethif4 wlif1 atm_8_35

Defaults on a business device

=>:interface list expand=disabled reverse=disabled

lan1 guest1 dmz1 wan1 Internet

eth_guest1 eth_dmz1 eth_wan1 ethoa_8_35

ethport1 ethport2 ethport3 ethport4 WLAN

ethif1 ethif2 ethif3 ethif4 wlif1 atm_8_35

3 Physical Ethernet Interfaces

3.1 Background Information

The “T” in 10Base-T and 100Base-T stands for “Twisted”.

Pin MDI Ethernet interface MDI-X Ethernet interface

2 Send (negative signal) Receive (negative signal)

3 Receive (positive signal) Send (positive signal)

4 Not used Not used

5 Not used Not used

6 Receive (negative signal) Send (negative signal)

7 Not used Not used

8 Not used Not used

Ethernet interface on device A Ethernet interface on device B Type of cable

MDI MDI Crossover

3.2 Configuring Physical Ethernet Interfaces

Configuring physical Ethernet interfaces

Configure ethif3 as mirrored ingress port with following command:

Configure ethif3 as mirrored egress port with following command:

To configure three group isolation, execute following commands:

Physical wireless interface:

ATM interface bundle:

PPP relay interface: