VRF-Lite
U
SER
G
UIDE
350
VRF-L
ITE
The command for the Policy-Based-Routing combined with the VLANs and with the routing tables,
allows to define a Virtual Routing Forwarding scenario, used to separate the traffic between
different interfaces. To clarify the concept, have a look below:
In the figure above, you want to separate the traffic on VLAN 1 from the one coming from VLAN 2
and you need that all the VLAN1 packets go to the PVC1 as the packets coming from VLAN2 go to
the PVC2.
Suppose that you have the above configuration and that the two PVCs correspond to the two logical
ADSL channels, but they could also be two different GRE tunnels ore two different L2TPv3 tunnels,
and so on:
set vlan add vid 835 interface eth1
set vlan add vid 836 interface eth1
set vlan eth1.835 ipaddr 192.168.35.1 netmask 255.255.255.0
set vlan eth1.835 description VLAN-Cliente1
set vlan eth1.836 ipaddr 192.168.36.1 netmask 255.255.255.0
set vlan eth1.836 description VLAN-Cliente2
set adsl pvc atm0 encap rfc1483-llc
set adsl pvc atm0 description PVC-Cliente1
set adsl pvc atm0 vpi 8 vci 35
set adsl pvc atm0 ipaddr 10.8.35.2
set adsl pvc atm0 nexthop 10.8.35.1
set adsl pvc atm1 encap rfc1483-llc
set adsl pvc atm1 description PVC-Cliente2
set adsl pvc atm1 vpi 8 vci 36
set adsl pvc atm1 ipaddr 10.8.36.2
set adsl pvc atm1 nexthop 10.8.36.1
The network interfaces involved are respectively:
eth1.835 per la VLAN1
atm0 per il PVC1
eth1.836 per la VLAN2
atm1 per il PVC2
You have to create two different routing table, one for each PVC:
set route net 0.0.0.0 netmask 0.0.0.0 dev atm0 table 1
set route net 0.0.0.0 netmask 0.0.0.0 dev atm1 table 2