Page MenuHomeVyOS Platform

Add L2vpn instance for mpls
Open, NormalPublicFEATURE REQUEST

Description

For L2tpv3 has syntax:

set interfaces l2tpv3 <interface> description <description>

L2vpn interfaces have a similar use , so add ability to set :

set interfaces l2vpn "name" type vpls 
set interface  l2vpn  "name" bridge "name" member interface "interface"
set interface  l2vpn  "name"  pseudowire member "name" 
set interface  l2vpn  "name"  pseudowire "name"  neighbor lsr-i "ip address"
set interface  l2vpn  "name"  pseudowire "name" neighbor address "ip address"
set interface  l2vpn  "name"  pseudowire "name" pw-id "id"

Frr config

l2vpn vpls1 type vpls
 bridge br0
 member interface eth1
 !
 member pseudowire dum5
  neighbor lsr-id 30.30.30.30
  neighbor address 30.30.30.30
  pw-id 10
 !

Details

Difficulty level
Unknown (require assessment)
Version
-
Why the issue appeared?
Will be filled on close
Is it a breaking change?
Unspecified (possibly destroys the router)
Issue type
Unspecified (please specify)

Event Timeline

Before that configuration , we should add the mpls settings in our cli-vyos , it is an example:

vyos@rt-pe-1:~$ sho configuration commands | match "mpls|ospf"
set protocols mpls interface 'eth0'
set protocols mpls ldp discovery transport-ipv4-address '30.30.30.30'
set protocols mpls ldp interface 'eth0'
set protocols mpls ldp parameters transport-prefer-ipv4
set protocols mpls ldp router-id '30.30.30.30'
set protocols ospf area 0 network '0.0.0.0/0'
set protocols ospf parameters abr-type 'cisco'
set protocols ospf parameters router-id '30.30.30.30'
set protocols ospf passive-interface-exclude 'eth0'

vyos@rt-pe-1:~$ sho configuration commands | match "br0"
set interfaces bridge br0 description 'test-vpls on vyos'
set interfaces bridge br0 member interface dum5
set interfaces bridge br0 member interface eth1

@fernando, this was something I was looking into adding but it'll be in 1.4 One day.....I hope soonish....maybe in a few months.

dmbaturin triaged this task as Normal priority.Jan 9 2024, 8:55 PM
dmbaturin set Issue type to Unspecified (please specify).

The kernel is not supporting pseudowire/VPLS now
this patch was never merged into the kernel

Are we going to just let EVPN be the L2VPN technology of choice and not go down the VPWS/VPLS route for L2VPN? EVPN is the future anyway, so going and adding VPWS/VPLS is kind of doing legacy work.