VLAN-Transparent Forwarding

Date:

March 2008

Version:

v1.0

Abstract:

This Application Notes describes the configuration of a specific feature of the Thomson
Gateway: VLAN-Transparent Forwarding. This feature is explained by integrating the Thomson
Gateway in a scenario where untagged, priority-tagged or VLAN-tagged frames have to be
bridged between the local Ethernet segment and the DSL line. The practical realization of the
scenario is described using CLI commands.

Applicability:

This Application Note applies to all Thomson DSL Gateways with R7.4 and higher.

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

Chapter 1

Introduction

Thomson Gateway as bridge

To set up the scenario of this document, the Thomson Gateway is configured as bridge. This means that
Ethernet frames are forwarded between the local Ethernet segment (LAN) and the WAN Ethernet segment
(PVCs on which RFC 1483 LLC encapsulation is used) on the link layer. In other words, the Thomson Gateway
does not terminate or route received Ethernet frames.

VLANs
The Ethernet frames that have to be forwarded may reside in different VLANs. This implies that all Ethernet
frames contain a (802.1Q) VLAN ID. Communication between different VLANs is not allowed on the link layer.
Only routers can make connections between different VLANs. VLANs create thus separated logical Ethernet
segments within a single physical segment.

Ethernet QoS
Ethernet frames optionally contain a (802.1p) user priority indication. If Ethernet QoS is taken into account
during bridging, it can be based on two steps:
1

Mapping the user priority of an incoming frame to an internal priority class. This classification can be
based on:
 The type of the interface on which the frame is entering the bridge.
 The (802.1p) user priority value.
 The IP Type of Service octet (TOS-byte) for IP packets, using the Precedence or DSCP notation.

Sending out the frame while taking into account its internal priority class. This class can be used to:
 Perform priority queuing on a single PVC.
 Perform traffic multiplexing over a range of PVCs.

Related documents
For detailed information on the features, CLI commands and parameters used in this document, see:


Thomson Gateway Ethernet Configuration Guide.

Thomson Gateway VLAN Configuration Guide.

Thomson Gateway Ethernet QoS Configuration Guide.

E-DOC-CTC-20080229-0006 v1.0

Chapter 2

VLAN-Transparent Forwarding

2.1

Scenario Overview

Introduction
In this scenario, the Thomson Gateway is intended to forward all VLAN-tagged frames between the local
Ethernet segment and a PVC transparently.
This scenario configures the Thomson Gateway as bridge with one PVC. All incoming frames on all local
interfaces have to be forwarded transparently to this PVC. The PVC to which all traffic has to be forwarded, is
chosen at configuration time. The exact value of the VLAN ID (VID) or the user priority indication should not
influence the result.
Following illustration shows the VLAN-transparent forwarding scenario:

Thomson Gateway

DSLAM

5
A

PVC1

VID

802.1p

7
B

3
C

WAN interface

Mechanism
To set up this scenario, we use following key mechanism: we explicitly define that the Ethernet bridge is not
VLAN aware. Ethernet frames coming in on the Thomson Gateway have a VLAN tag in their header. However,
neither the VLAN ID nor the user priority indication should be taken into account. If the Ethernet bridge is
VLAN aware, we have to define all VLANs that have to pass through the Thomson Gateway. Otherwise,
unknown VLANs are dropped.

2.2

Practical Realization

Configuration overview
Following configuration steps have to be performed to configure the Thomson Gateway for this scenario:

Define which PVC must be used by configuring an ATM interface for it.

Connect the ATM interface to the Ethernet bridge.

Define that the bridge is not VLAN aware.

Save the configuration.

E-DOC-CTC-20080229-0006 v1.0

Chapter 2

Before you start

Before you start to configure the Thomson Gateway, make following preparations:


Reset the Thomson Gateway to the factory defaults and reboot the device.

Make sure the telnet session with the Thomson Gateway never times out.

Remove the factory default interfaces and settings that you do not need for the configuration.

Make these changes permanent. Now, you can start from a clean situation.
=>:system reset factory=yes proceed=yes
=>:env set var=SESSIONTIMEOUT value=0
=>:ppp
=>:ppp
=>:eth
=>:atm
=>:atm

relay flush
flush
flush
flush
phonebook flush

=>:saveall

Configure an ATM interface

To create a phonebook entry for the PVC that must be used, execute following CLI command (the VPI/VCI
value is indicative):
=>:atm phonebook add name=phone_PVC1 addr=0.35

To create, configure and connect an ATM interface on top of this phonebook entry, execute following CLI
commands:
=>:atm ifadd intf=atm_PVC1
=>:atm ifconfig intf=atm_PVC1 dest=phone_PVC1 encaps=llc ulp=mac
=>:atm ifattach intf=atm_PVC1

Configure a bridge port

To connect the ATM interface to the Ethernet bridge, execute following CLI commands:
=>:eth bridge ifadd intf=bridge_PVC1
=>:eth bridge ifconfig intf=bridge_PVC1 dest=atm_PVC1
=>:eth bridge ifattach atm_PVC1

Disable VLAN awareness of the bridge

By default, the bridge is already not VLAN aware.
To check the current status of the Ethernet bridge, execute following CLI command:
=>:eth
Ageing
Filter
VLAN
...

bridge config
: 300
: no_WAN_broadcast
: disabled

E-DOC-CTC-20080229-0006 v1.0

Chapter 2

If necessary, disable the VLAN awareness of the Ethernet bridge executing following CLI command:
=>:eth bridge config vlan=disabled

Save the configuration

To make your changes permanent, execute following CLI command:
=>:saveall

Expected result
All incoming frames on a local interface are forwarded to the configured PVC. The same is true for frames
arriving on the Thomson Gateway via the DSL line: these frames are forwarded to the local Ethernet
segment.
Whether the frame has a VLAN tag or not is irrelevant for the current scenario. All frames are forwarded in
both directions.
In this statement, all frames has to be understood as all frames that should be forwarded by a
regular bridge. There are exceptions, for example, administered reserve multicast destination
addresses.

E-DOC-CTC-20080229-0006 v1.0

Visit us at:
www.thomson-broadband.com

Coordinates:
Thomson Telecom
Prins Boudewijnlaan 47
B-2650 Edegem
Belgium

Copyright
2008 Thomson. All rights reserved.
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. The information contained in this document represents the current view of Thomson on the issues discussed as of the
date of publication. Because Thomson must respond to changing market conditions, it should not be interpreted to be a commitment
on the part of Thomson, and Thomson cannot guarantee the accuracy of any information presented after the date of publication. This
document is for informational purposes only. Thomson MAKES NO WARRANTIES, EXPRESS OR IMPLIED, AS TO THE INFORMATION
IN THIS DOCUMENT.
The names of actual companies and products mentioned herein may be the trademarks of their respective owners.