THOMSON R7.4 User manual

Power
Ethernet
WLAN
Plug-in
ISDN
Internet
DSL
VLAN Configuration Guide
R7.4 and higher
Thomson Gateway

Thomson Gateway
VLAN 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-0001
Short Title: Config Guide: VLAN R7.4 and higher

E-DOC-CTC-20080229-0001 v1.0 i
Contents
About this VLAN Configuration Guide ..................................... 1
1 Introduction.................................................................................. 3
2 VLAN Overview ........................................................................... 5
3 Creating VLANs on the Thomson Gateway.............................. 9
4 Ethernet Bridge and VLANs...................................................... 11
4.1 VLAN Learning Constraints........................................................................... 12
4.2 Static Entries with VLANs ............................................................................ 14
4.3 VLAN Awareness .......................................................................................... 16
4.4 Port VLAN Membership ................................................................................ 17
4.5 Optional Incoming Traffic Validation............................................................ 20
4.6 Dynamic VLAN Membership ......................................................................... 22
4.7 Unknown VID Policy ..................................................................................... 25
4.8 Extra Tagging (Stacked VLANs) .................................................................... 28
5 Logical Ethernet Interfaces and VLANs...................................33
5.1 WAN-side VLAN Tagging............................................................................... 34
5.2 VLAN Routing on the Thomson Gateway...................................................... 35

E-DOC-CTC-20080229-0001 v1.0
ii
Contents

E-DOC-CTC-20080229-0001 v1.0 1
About this VLAN Configuration Guide
About this VLAN Configuration Guide
Used Symbols
Terminology
Generally, the Thomson Gateway356 will be referred to as Wireless USB Adaptor in this VLAN 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.
A note provides additional information about a topic.
A caution warns you about potential problems or specific precautions that need to be taken.

E-DOC-CTC-20080229-0001 v1.0
2
About this VLAN Configuration Guide
Overview
First, this VLAN Configuration Guide shortly lists the VLAN features of the Thomson Gateway and the
relevant standards. Some background information on several VLAN-related concepts is also provided. Next,
this document describes the configuration of each VLAN feature on the Thomson Gateway in detail. CLI
(Command Line Interface) commands are used for the configuration.
This document is structured as follows:
Topi c Page
“1 Introduction” 3
“2 VLAN Overview” 5
“3 Creating VLANs on the Thomson Gateway” 9
“4 Ethernet Bridge and VLANs” 11
“5 Logical Ethernet Interfaces and VLANs” 33

E-DOC-CTC-20080229-0001 v1.0 3
1| Introduction
1 Introduction
Introduction
Virtual Local Area Networks, commonly known as VLANs, are the subject of this document. In this chapter,
we shortly list the VLAN features that are supported by the Thomson Gateway, the relevant standards and
related documents.
Supported VLAN features
Thomson Gateway devices support following VLAN features:
Creation of VLANs on the Thomson Gateway
VLAN features of the Ethernet bridge
VLAN learning constraints for dynamic entries
Creation of static entries with VLANs
VLAN awareness of the bridge
Tagged and untagged VLAN membership of bridge ports
Port VID of a bridge port
Acceptance of only VLAN-tagged frames
Ingress filtering of VLAN-tagged frames
Dynamic VLAN membership
Unknown VID policy
Extra tagging (stacked VLANs)
VLAN features of the logical Ethernet interfaces
WAN-side VLAN tagging
Support of VLAN routing on the Thomson Gateway
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.
Related documents
Other Layer 2 related features, such as Ethernet and Ethernet QoS, are described in other documents. See the
“Ethernet Configuration Guide” and the “Ethernet QoS Configuration Guide” for more information.

E-DOC-CTC-20080229-0001 v1.0
4
1| Introduction

E-DOC-CTC-20080229-0001 v1.0 5
2| VLAN Overview
2 VLAN Overview
What is a VLAN?
A VLAN is a Layer 2 method of creating independent logical networks within a single physical network. Hosts
in the same VLAN behave as if they are connected to the same LAN segment, even though they may be
physically connected to different LAN segments.
The primary use of VLANs is to split large switched networks, which are large broadcast domains. While
traditional LAN segmentation adds routers to the network to split a broadcast domain, VLAN segmentation
adds VLAN-aware switches. Routers are only needed to communicate between two VLANs.
Following illustration shows the difference between traditional physical LAN segmentation and logical VLAN
segmentation:
Advantages of using VLANs
The use of VLANs is very popular in today’s networks, because VLANs offer several advantages:
Increased performance:
VLANs increase the number of broadcast domains but reduce the size of each broadcast domain. As
this limits broadcast storms, multicast traffic, chatty protocols and so on, overall network traffic is
reduced.
VLAN-aware switches add no substantial latency compared to routers, as the amount of routing
(Layer 3 forwarding) is reduced.
Snooping is limited, which increases the network security.
Router
VLAN1 VLAN2
VLAN3
VLAN Switch
VLAN Switch
VLAN Switch
LAN3
Hub
Router
LAN1
Hub
LAN2
Hub
Traditional LAN segmentation VLAN segmentation

E-DOC-CTC-20080229-0001 v1.0
6
2| VLAN Overview
Topological independence: the use of VLANs allows non-physical grouping of nodes that share similar
resources. This results in the creation of logical networks, independent of the physical location of the
involved nodes. Hardware requirements are reduced, as networks can be separated logically instead of
physically.
Ease of administration: the management efforts to create (logical) networks are reduced:
Nodes can easily change their VLAN membership.
Network topology changes, for example a host moving to another location, no longer require
hardware changes but can be done via software.
Cost-effectiveness is improved: less routers, which are costly, are needed and VLAN-aware switches are
used instead. Routers are only needed to communicate between two VLANs.
Additional features: the VLAN user priority allows Layer 2 traffic separation.
VLAN-tagged frame format
In order to support VLANs, the Ethernet frame format is extended with a VLAN tag, indicated in red in the
following illustration:
A VLAN tag consists of following fields:
Tag Protocol Identifier (TPID): this field is located at the same place as the Length/Type field of untagged
frames. The value of the field is always equal to 0x8100, which indicates that the frame is tagged and that
the original Length/Type field is located after the VLAN tag.
Tag Control Information (TCI):
User Priority Field: this field indicates the 802.1p user priority.
Canonical Format Indicator (CFI)
VLAN Identifier (VID): this field identifies the VLAN to which the frame belongs.
Destination
MAC Address
Source
MAC Address
Length/
Type
TPID TCI FCS
662 422
PadData/LLC
0 .. 1500 46 .. 0 bytes
Min. 46 bytes - Max. 1500 bytes
Min. 68 bytes - Max. 1522 bytes
Priority CFI VID
3 1 12 bits
VLAN tag

E-DOC-CTC-20080229-0001 v1.0 7
2| VLAN Overview
Stacked VLAN frame format
VLAN stacking means that a frame contains two VLAN tags. An example of a stacked VLAN frame format is
shown in the following illustration:
An S-tag can be distinguished from a C-tag as follows:
The value of the TPID field of an S-tag is set to 0x88a8.
An S-tag contains a DEI (Drop Eligible Indicator) field instead of a CFI field.
Destination
MAC Address
Source
MAC Address
Length/
Type
TPID TCI FCS
662 422
PadData/LLC
0 .. 1500 46 .. 0 bytes
Min. 46 bytes - Max. 1500 bytes
Min. 72 bytes - Max. 1526 bytes
TPID TCI
22
Customer
VLAN tag
= C-tag
Service Provider
VLAN tag
= S-tag
Priority DEI VID
3 1 12 bits

E-DOC-CTC-20080229-0001 v1.0
8
2| VLAN Overview

E-DOC-CTC-20080229-0001 v1.0 9
3| Creating VLANs on the Thomson Gateway
3 Creating VLANs on the Thomson Gateway
Introduction
This chapter describes the creation of new VLANs on the Thomson Gateway. As soon as a VLAN is created, it
can be used for:
VLAN bridging by the Ethernet bridge.
WAN-side VLAN tagging by logical Ethernet interfaces.
VLAN routing.
The CLI commands explained in this chapter belong to the command group :eth vlan.
Creating a new VLAN
To create a new VLAN, use the command :eth vlan add.
Two parameters must be specified:
Name: the name of the new VLAN.
Vid (VLAN identifier): the VID of the new VLAN.
This VID corresponds to the value of the VID field of VLAN-tagged frames that belong to this VLAN. As
this VID field has a size of 12 bits, the VID can be a number within the range from 0 through 4095.
However, following VIDs are reserved and can not be used to create a new VLAN:
0: this value indicates that the VLAN tag contains only user priority information and no VID.
1: this value indicates the default VID. This value is already in use by the default VLAN on the bridge.
4095: this value is reserved.
Optionally, following parameter can be specified:
Addrule: this parameter indicates whether the default VLAN learning constraint is used. If the parameter
is not specified, the parameter is enabled.
If the parameter is enabled, the default VLAN learning constraint is used. This means that Shared
VLAN Learning (SVL) is being used between the new VLAN and the default VLAN.
If the parameter is disabled, a separate filtering database is created for the new VLAN and
Independent VLAN Learning (IVL) is being used implicitly.
For example, to create a data, video and voice VLAN, execute following commands:
It is recommended to disable this parameter when creating a new VLAN. In this case, the same
MAC address can be used in different VLANs. No MAC address conflicts occur when different
VLANs are connected to the same device (for example a router at the WAN side).
For more information on the configuration of VLAN learning constraints, see “4.1 VLAN
Learning Constraints” on page 12.
=>:eth vlan add name=data vid=2
=>:eth vlan add name=video vid=3 addrule=enabled
=>:eth vlan add name=voice vid=4 addrule=disabled

E-DOC-CTC-20080229-0001 v1.0
10
3| Creating VLANs on the Thomson Gateway
Listing all VLANs
To list all VLANs that were created in the previous example, execute following command:
Deleting a VLAN
To delete a specific VLAN, use the command :eth vlan delete.
One parameter must be specified:
Name: the name of the VLAN to be deleted.
For example, to delete the voice VLAN, execute following command:
Flushing all VLANs
To delete all VLANs at once, execute following command:
=>:eth vlan list
Vid Name
--- ----
1 default
2 data
3 video
4 voice
The number of active VLANs is the number of VLANs that are in use at a certain moment. The
maximum number of active VLANs that the bridge can support at any time is 15, including the
VLANs that are already created by default.
=>:eth vlan delete name=voice
=>:eth vlan list
Vid Name
--- ----
1 default
2 data
3 video
You cannot delete the default VLAN (VID=1).
Even if one or more bridge ports are member of the deleted VLAN, the VLAN is deleted without
warning. Each affected bridge port becomes untagged member of the default VLAN.
=>:eth vlan flush
=>:eth vlan list
Vid Name
--- ----
1 default
You cannot flush the default VLAN (VID=1).
Even if one or more bridge ports are member of the flushed VLANs, the VLANs are deleted without
warning. All bridge ports become untagged members of the default VLAN.

E-DOC-CTC-20080229-0001 v1.0 11
4| Ethernet Bridge and VLANs
4 Ethernet Bridge and VLANs
Introduction
This chapter describes the VLAN features of the Ethernet bridge in detail. These VLAN features can be
grouped as follows:
Ethernet bridge:
The learning process is extended with the use of VLAN learning constraints.
Static entries can be configured per VLAN or for all VLANs.
VLAN awareness of the bridge.
Ethernet bridge ports:
Tagged and untagged VLAN membership of the bridge ports.
Control of unexpected incoming frames on a bridge port.
Advanced VLAN features:
Dynamic VLAN membership.
Unknown VID policy.
Extra tagging.
Overview
This chapter is structured as follows:
Topi c Page
“4.1 VLAN Learning Constraints” 12
“4.2 Static Entries with VLANs” 14
“4.3 VLAN Awareness” 16
“4.4 Port VLAN Membership” 17
“4.5 Optional Incoming Traffic Validation” 20
“4.6 Dynamic VLAN Membership” 22
“4.7 Unknown VID Policy” 25
“4.8 Extra Tagging (Stacked VLANs)” 28

E-DOC-CTC-20080229-0001 v1.0
12
4| Ethernet Bridge and VLANs
4.1 VLAN Learning Constraints
Introduction
The supported self-learning VLAN bridge functionality operates according to IEEE 802.1Q. This learning
process creates the dynamic entries in the filtering data base(s) of the Ethernet bridge.
The CLI commands explained in this section belong to the command group :eth bridge rule.
Multiple filtering data bases
The Ethernet bridge supports multiple filtering data bases. Each filtering data base can be shared by multiple
VLANs.
VLAN learning constraints
The VLAN learning constraints used by the learning process determine which dynamic entries are created in
which filtering data bases.
Following VLAN learning constraints exist:
Shared VLAN Learning (SVL): only one filtering data base is supported, shared by all VLANs. This means
that if an individual MAC address is learned in one VLAN, that learned information can be used in
forwarding decisions taken for that address by all other VLANs.
In this case, only one entry for a specific MAC address can exist. The same MAC address can not be
forwarded differently in different VLANs.
Independent VLAN Learning (IVL): multiple filtering data bases are supported and each data base is used
by only one VLAN. This means that if an individual MAC address is learned in one VLAN, that learned
information is only used in forwarding decisions taken for that address by that VLAN.
In this case, the same MAC address can be used in different VLANs, as each filtering data base can
contain an entry for that MAC address. This way, the Thomson Gateway can be connected to the same
device via different connections.
Shared VLAN Learning/Independent VLAN Learning (SVL/IVL): this is a combination of SVL and IVL.
Creating a new VLAN learning constraint
To create a new VLAN learning constraint, use the command :eth bridge rule add.
Following two parameters must be specified:
Type: the type of the VLAN learning constraint. This type can be set to:
Shared
Independent
Vlan: the VLAN to which the constraint belongs.
Depending on the selected type, one of the following parameters must be specified:
Vlan2: if the type is set to shared, this parameter indicates a second VLAN. As a result, Shared VLAN
Learning is used between the VLANs identified by the pair of VLANs (Vlan and Vlan2).
Isi: if the type is set to independent, this parameter indicates the Independent Set Identifier (ISI). The ISI is
a number within the range from 0 through 32. As a result, Independent VLAN Learning is used between
all VLANs with the same ISI.

E-DOC-CTC-20080229-0001 v1.0 13
4| Ethernet Bridge and VLANs
For example, create VLAN learning constraints so that Shared VLAN Learning is used between the default,
data and video VLANs and Independent VLAN Learning is used between the video and voice VLAN:
Listing all VLAN learning constraints
To list all VLAN learning constraints, execute following command:
Deleting a VLAN learning constraint
To delete a VLAN learning constraint, use the command :eth bridge rule delete.
One parameter must be specified:
Index: this parameter indicates the index of the VLAN learning constraint to be deleted.
For example, delete the first two VLAN learning constraints as follows:
Flushing all VLAN learning constraints
To delete all VLAN learning constraints at once, execute following command:
=>:eth bridge rule add type=shared vlan=data vlan2=default
=>:eth bridge rule add type=shared vlan=video vlan2=default
=>:eth bridge rule add type=independent vlan=video isi=0
=>:eth bridge rule add type=independent vlan=voice isi=0
Be careful during the creation of VLAN learning constraints, as inconsistencies are not always
reported by the Thomson Gateway.
=>:eth bridge rule list
Index Type VLAN Parameter
----- ---- ---- ---------
1 shared data Shared with VLAN: default
2 shared video Shared with VLAN: default
3 independent video Independent set identifier: 0
4 independent voice Independent set identifier: 0
If the list has no entry for a specific VLAN, Independent VLAN learning (IVL) is being used implicitly.
=>:eth bridge rule delete index=1
=>:eth bridge rule delete index=2
=>:eth bridge rule list
Index Type VLAN Parameter
----- ---- ---- ---------
3 independent video Independent set identifier: 0
4 independent voice Independent set identifier: 0
Before deleting a constraint, list all VLAN learning constraints to obtain the correct index of the
constraint to be deleted.
=>:eth bridge rule flush
=>:eth bridge rule list
Index Type VLAN Parameter
----- ---- ---- ---------

E-DOC-CTC-20080229-0001 v1.0
14
4| Ethernet Bridge and VLANs
4.2 Static Entries with VLANs
Introduction
A static entry is defined as an entry that has not been obtained through the learning process. This section
describes the configuration of static entries in combination with VLANs.
Creating static entries
To create a static entry, use the command :eth bridge macadd.
Optionally, the parameter vlan can be specified:
If a VLAN is specified, one entry for that particular VLAN is added to the filtering database:
If no VLAN is specified, an entry for each VLAN is added to the filtering database:
On the assumption that only a default and video VLAN exist, the resulting filtering database looks as follows:
Deleting static entries
To delete a static entry, use the command :eth bridge macdelete.
Optionally, the parameter vlan can be specified:
If the entry was created for a specific VLAN, that VLAN must be specified when removing the entry from
the filtering database:
If the entry was created for all VLANs, no VLAN must be specified when removing the entries from the
filtering database:
=>:eth bridge macadd hwaddr=00:00:00:00:00:01 intf=ethport1 vlan=default
=>:eth bridge macadd hwaddr=00:00:00:00:00:01 intf=ethport3 vlan=video
=>:eth bridge macadd hwaddr=00:00:00:00:00:02 intf=ethport2
=>:eth bridge maclist
00:00:00:00:00:01 -- static, default, ethport1
00:00:00:00:00:01 -- static, video, ethport3
00:00:00:00:00:02 -- static, default, ethport2
00:00:00:00:00:02 -- static, video, ethport2
00:14:7f:01:dc:9e -- permanent, default
...
=>:eth bridge macdelete hwaddr=00:00:00:00:00:01
Failed to delete MAC address from database.
=>:eth bridge macdelete hwaddr=00:00:00:00:00:01 vlan=default
=>:eth bridge macdelete hwaddr=00:00:00:00:00:01 vlan=video
=>:eth bridge macdelete hwaddr=00:00:00:00:00:02 vlan=video
Failed to delete MAC address from database.
=>:eth bridge macdelete hwaddr=00:00:00:00:00:02