# v7.18rc \[testing\] is released!

**URL:** <https://forum.mikrotik.com/t/v7-18rc-testing-is-released/182052>\
**Category:** Announcements\
**Created:** [February 18, 2025, 10:13am UTC](https://forum.mikrotik.com/t/v7-18rc-testing-is-released/182052 "2025-02-18T10:13:00Z")\
**Posts on this page:** 20\
**Page:** 6

<div class="post-metadata">

**Author:** ![oreggin](https://forum.mikrotik.com/letter_avatar/oreggin/32/6_449c533f586939b6e5f246632a46421f.png) [@oreggin](https://forum.mikrotik.com/u/oreggin)\
**Post date:** [February 21, 2025, 1:55pm UTC](https://forum.mikrotik.com/t/v7-18rc-testing-is-released/182052/101 "2025-02-21T13:55:54Z")

</div>

> [@](#):
>
> LDP signaled VPLS works  
> BGP signaled VPLS works  
> VPNv6 works
> 
> either misconfiguration or very specific setup.

Its totally basic setup in labs, both CHR and physical routerboards. There is a P router in the middle and 3 PE on that.  
This is the MPLS and Routing config from first PE router (RB750Gr3):

```plaintext
[oreggin@rtr1.CPE] > /mpls/export 
/mpls interface
add interface=all mpls-mtu=1500
/mpls ldp
add afi=ip,ipv6 disabled=no lsr-id=10.0.10.11 preferred-afi=ipv6 transport-addresses=10.0.10.11,b00b::10:0:10:11
/mpls ldp interface
add accept-dynamic-neighbors=yes afi=ip,ipv6 disabled=no interface=ether2

[oreggin@rtr1.CPE] > /routing/export 
/routing bgp template
set default disabled=no router-id=10.0.10.11
/routing ospf instance
add disabled=no name=ospfv2 router-id=10.0.10.11
add disabled=no name=ospfv3 router-id=10.0.10.11 version=3
/routing ospf area
add disabled=no instance=ospfv2 name=backbone4
add disabled=no instance=ospfv3 name=backbone6
/routing bgp connection
add address-families=ip,l2vpn,l2vpn-cisco,vpnv4 as=65530 connect=no disabled=no listen=yes local.address=10.0.10.11 .role=ibgp-rr name=rrcl4 nexthop-choice=force-self \
    output.default-originate=if-installed .redistribute=connected remote.address=10.0.10.0/24 .as=65530 router-id=10.0.10.11 routing-table=main
add address-families=ipv6,vpnv6 as=65530 connect=no disabled=no listen=yes local.address=b00b::10:0:10:11 .role=ibgp-rr name=rrcl6 output.default-originate=always .redistribute=connected \
    remote.address=b00b::10:0:10:0/112 .as=65530 router-id=10.0.10.11 routing-table=main
/routing bgp vpls
add bridge=VPLS_B bridge-horizon=4 comment="BGP signaled VPLS" disabled=no export-route-targets=65530:4 import-route-targets=65530:4 name=VPLS_B pw-type=vpls rd=65530:4 site-id=11
add bridge=VPLS_A bridge-horizon=3 cisco-id=33.33.33.11 comment="LDP signaled VPLS" disabled=no export-route-targets=65530:3 import-route-targets=65530:3 name=VPLS_A pw-type=vpls rd=\
    65530:3
/routing bgp vpn
add disabled=no export.redistribute=connected .route-targets=65530:1 import.route-targets=65530:1 .router-id=VRF_A label-allocation-policy=per-vrf name=bgp-mpls-vpn-1 route-distinguisher=\
    65530:1 vrf=VRF_A
add disabled=no export.redistribute=connected .route-targets=65530:2 import.route-targets=65530:2 .router-id=VRF_B label-allocation-policy=per-prefix name=bgp-mpls-vpn-2 \
    route-distinguisher=65530:2 vrf=VRF_B
/routing filter rule
add chain=BGP_out rule=accept
/routing ospf interface-template
add area=backbone4 cost=1000 disabled=no interfaces=ether2 type=ptp
add area=backbone6 cost=1000 disabled=no interfaces=ether2 type=ptp
add area=backbone4 disabled=no interfaces=Loopback0 passive
add area=backbone6 disabled=no interfaces=Loopback0 passive
[oreggin@rtr1.CPE] >

```

Maybe misconfiguration, but I can’t figure out what or where. If you have any proposal, it would be appreciated.

```plaintext
[oreggin@rtr1.CPE] > /interface/vpls/print        
Flags: R - RUNNING; D - DYNAMIC
Columns: NAME, PEER, BGP-VPLS
# NAME PEER BGP-VPLS
0 RD vpls1 10.0.10.13 VPLS_B  
1 RD vpls2 10.0.10.12 VPLS_B  
2 D vpls3 10.0.10.13 VPLS_A  
3 D vpls4 10.0.10.12 VPLS_A  
[oreggin@rtr1.CPE] > /mpls/forwarding-table/print 
Flags: L - LDP, P - VPN, V - VPLS
Columns: LABEL, VRF, PREFIX, NEXTHOPS, VPLS
 # LABEL VRF PREFIX NEXTHOPS VPLS 
 0 P 32 VRF_A                                                                                     
 1 P 33 VRF_B 10.0.12.0/29                                                                       
 2 P 34 VRF_B b00b:10:11:12::/64                                                                 
 3 L 42 main b00b::10:0:10:1 { nh=fe80::20c:42ff:fe53:1491%ether2; interface=ether2 }       
 4 L 39 main 10.0.10.1 { label=impl-null; nh=10.0.0.25; interface=ether2 }            
 5 L 40 main 10.0.10.12 { label=21; nh=10.0.0.25; interface=ether2 }                   
 6 L 41 main 10.0.10.13 { label=20; nh=10.0.0.25; interface=ether2 }                   
 7 L 37 main 10.0.0.0/30 { label=impl-null; nh=10.0.0.25; interface=ether2 }            
 8 L 38 main 10.0.1.0/30 { label=impl-null; nh=10.0.0.25; interface=ether2 }            
 9 V 29 vpls1
10 V 28 vpls2
11 L 43 main b00b::10:0:10:12 { nh=fe80::20c:42ff:fe53:1491%ether2; interface=ether2 }       
12 L 44 main b00b::10:0:10:13 { nh=fe80::20c:42ff:fe53:1491%ether2; interface=ether2 }       
[oreggin@rtr1.CPE] >

```

Thanks!

---

<div class="post-metadata">

**Author:** ![EdPa](https://forum.mikrotik.com/letter_avatar/edpa/32/6_449c533f586939b6e5f246632a46421f.png) [@EdPa](https://forum.mikrotik.com/u/EdPa)\
**Post date:** [February 21, 2025, 1:56pm UTC](https://forum.mikrotik.com/t/v7-18rc-testing-is-released/182052/102 "2025-02-21T13:56:25Z")

</div>

**What’s new in 7.18rc2 (2025-Feb-21 12:50):**  
\*) cloud - added “Back To Home Files” feature (additional fixes);  
\*) dhcpv6-relay - added option to create routes for bindings passing through relay (additional fixes);  
\*) disk - do not allow adding device in raid when major settings mismatch in superblock and config;  
\*) disk - fixed removing device from raid while resyncing;  
\*) ethernet - fixed issue with default-names for RB4011, RB1100Dx4, RB800 devices (additional fixes);  
\*) ethernet - fixed link-down on startup for ARM64 devices (introduced in v7.16);  
\*) l3hw - added initial HW offloading for VXLAN on compatible switches (additional fixes);  
\*) lte - added initial eSIM management support (additional fixes);  
\*) lte - fix R11e-4G modem initialization (introduced in v7.18beta4);  
\*) lte - fixed cases where the MBIM dialer could get stuck;  
\*) lte - fixed interface recovery in mixed multiapn setup for MBIM modems (additional fixes);  
\*) lte - improved initialization for external USB modems;  
\*) ptp - improved system stability;  
\*) qos-hw - fixed wred-threshold (introduced in v7.18beta2);  
\*) ssh - improved channel resumption after rekey and eof handling;  
\*) wifi-qcom - prevent AP from transmitting broadcast data unencrypted during authentication of first client;  
\*) winbox - added missing options under “System/Disk” menu (additional fixes);

---

<div class="post-metadata">

**Author:** ![oreggin](https://forum.mikrotik.com/letter_avatar/oreggin/32/6_449c533f586939b6e5f246632a46421f.png) [@oreggin](https://forum.mikrotik.com/u/oreggin)\
**Post date:** [February 21, 2025, 2:00pm UTC](https://forum.mikrotik.com/t/v7-18rc-testing-is-released/182052/103 "2025-02-21T14:00:04Z")

</div>

> [@](#):
>
> **What’s new in 7.18rc2 (2025-Feb-21 12:50):**

Oh man, I started to upgrade my routers 5 minutes ago to RC1 😃

---

<div class="post-metadata">

**Author:** ![BartoszP](https://forum.mikrotik.com/user_avatar/forum.mikrotik.com/bartoszp/32/1386_2.png) [@BartoszP](https://forum.mikrotik.com/u/BartoszP)\
**Post date:** [February 21, 2025, 2:07pm UTC](https://forum.mikrotik.com/t/v7-18rc-testing-is-released/182052/104 "2025-02-21T14:07:22Z")

</div>

> [@](#):
>
> **What’s new in 7.18rc2 (2025-Feb-21 12:50):**  
> \*) lte - added initial eSIM management support (additional fixes);

Just 0.02$ … initial + fixes do not fit releasing stable version. That should be in 7.19beta.

---

<div class="post-metadata">

**Author:** ![sirbryan](https://forum.mikrotik.com/user_avatar/forum.mikrotik.com/sirbryan/32/2586_2.png) [@sirbryan](https://forum.mikrotik.com/u/sirbryan)\
**Post date:** [February 21, 2025, 2:44pm UTC](https://forum.mikrotik.com/t/v7-18rc-testing-is-released/182052/105 "2025-02-21T14:44:22Z")

</div>

> [@](#):
>
> You have to make sure you’re comparing pears to pears (not going to mention apples 😉 ). ROS in principle does firewalling as well and connection tracking machinery (identifying connections to which each packet belongs) is pretty costly operation. OTOH linux kernel might not be doing it. IIRC connection tracking is enabled whenever there’s even a single firewall filter rule configured …

It’s a blank install of CHR, so no rules, no filters, nothing. Simply doing bandwidth tests from the VM’s to my 2116 and to each other. I’ll have to see if I can get 7.16 or 7.15 to work, just for fun.

RPi5 is a Broadcom BCM2712 quad-core Arm Cortex A76 processor @ 2.4GHz. That’s better than the 1.4GHz quad-core processor in RB4011 and RB5009, the 1.7GHz processor in CCR2004, and the 2GHz processor in CRS526. The 2004 can bridge and route (fast path) 19Gbps (it obviously has more PCIe lanes to the switch from the CPU), so I would hope to get at least the full 6Gbps out of the CHR on the Pi and 10Gbps out of the Intel processor (4 cores at 3GHz).

---

<div class="post-metadata">

**Author:** ![holvoetn](https://forum.mikrotik.com/letter_avatar/holvoetn/32/6_449c533f586939b6e5f246632a46421f.png) [@holvoetn](https://forum.mikrotik.com/u/holvoetn)\
**Post date:** [February 21, 2025, 3:06pm UTC](https://forum.mikrotik.com/t/v7-18rc-testing-is-released/182052/106 "2025-02-21T15:06:33Z")

</div>

> [@](#):
>
> > [@](#):
> >
> > **What’s new in 7.18rc2 (2025-Feb-21 12:50):**  
> > \*) lte - added initial eSIM management support (additional fixes);
> 
> Just 0.02$ … initial + fixes do not fit releasing stable version. That should be in 7.19beta.

And no device yet which supports this ?

---

<div class="post-metadata">

**Author:** ![buset1974](https://forum.mikrotik.com/letter_avatar/buset1974/32/6_449c533f586939b6e5f246632a46421f.png) [@buset1974](https://forum.mikrotik.com/u/buset1974)\
**Post date:** [February 21, 2025, 4:00pm UTC](https://forum.mikrotik.com/t/v7-18rc-testing-is-released/182052/107 "2025-02-21T16:00:06Z")

</div>

> [@](#):
>
> **What’s new in 7.18rc2 (2025-Feb-21 12:50):**  
> \*) cloud - added “Back To Home Files” feature (additional fixes);  
> \*) dhcpv6-relay - added option to create routes for bindings passing through relay (additional fixes);  
> \*) disk - do not allow adding device in raid when major settings mismatch in superblock and config;  
> \*) disk - fixed removing device from raid while resyncing;  
> \*) ethernet - fixed issue with default-names for RB4011, RB1100Dx4, RB800 devices (additional fixes);  
> \*) ethernet - fixed link-down on startup for ARM64 devices (introduced in v7.16);  
> \*) l3hw - added initial HW offloading for VXLAN on compatible switches (additional fixes);  
> \*) lte - added initial eSIM management support (additional fixes);  
> \*) lte - fix R11e-4G modem initialization (introduced in v7.18beta4);  
> \*) lte - fixed cases where the MBIM dialer could get stuck;  
> \*) lte - fixed interface recovery in mixed multiapn setup for MBIM modems (additional fixes);  
> \*) lte - improved initialization for external USB modems;  
> \*) ptp - improved system stability;  
> \*) qos-hw - fixed wred-threshold (introduced in v7.18beta2);  
> \*) ssh - improved channel resumption after rekey and eof handling;  
> \*) wifi-qcom - prevent AP from transmitting broadcast data unencrypted during authentication of first client;  
> \*) winbox - added missing options under “System/Disk” menu (additional fixes);

I can’t find any LTE interface on my dozens of CCRs.  
CCR owners don’t lose your hope and keep your spirits up

---

<div class="post-metadata">

**Author:** ![pe1chl](https://forum.mikrotik.com/user_avatar/forum.mikrotik.com/pe1chl/32/55588_2.png) [@pe1chl](https://forum.mikrotik.com/u/pe1chl)\
**Post date:** [February 21, 2025, 4:45pm UTC](https://forum.mikrotik.com/t/v7-18rc-testing-is-released/182052/108 "2025-02-21T16:45:45Z")

</div>

> [@](#):
>
> I can’t find any LTE interface on my dozens of CCRs.  
> CCR owners don’t lose your hope and keep your spirits up

Of course not… until you plug in a LTE USB stick (when your CCR has an USB port).  
Unfortunately there is no line with “\*) bgp - improved stability;” in sight… that is what CCR users are hoping for.

---

<div class="post-metadata">

**Author:** ![bajodel](https://forum.mikrotik.com/user_avatar/forum.mikrotik.com/bajodel/32/1285_2.png) [@bajodel](https://forum.mikrotik.com/u/bajodel)\
**Post date:** [February 21, 2025, 4:55pm UTC](https://forum.mikrotik.com/t/v7-18rc-testing-is-released/182052/109 "2025-02-21T16:55:48Z")

</div>

@Mikrotik - since you just restored in this version the forgotten “/ip/route/check” feature for ipv4 (similar to “ip route get” in linux), why not complete the task and give ipv6 the same love ?  
Thanks.

---

<div class="post-metadata">

**Author:** ![buset1974](https://forum.mikrotik.com/letter_avatar/buset1974/32/6_449c533f586939b6e5f246632a46421f.png) [@buset1974](https://forum.mikrotik.com/u/buset1974)\
**Post date:** [February 21, 2025, 6:18pm UTC](https://forum.mikrotik.com/t/v7-18rc-testing-is-released/182052/110 "2025-02-21T18:18:39Z")

</div>

> [@](#):
>
> LDP signaled VPLS works  
> BGP signaled VPLS works  
> VPNv6 works
> 
> either misconfiguration or very specific setup.

Hi mrz, any reason why MT still hide vpn6 afi from winbox?  
If there any limitation should we know about?

---

<div class="post-metadata">

**Author:** ![felixka](https://forum.mikrotik.com/user_avatar/forum.mikrotik.com/felixka/32/55669_2.png) [@felixka](https://forum.mikrotik.com/u/felixka)\
**Post date:** [February 21, 2025, 6:35pm UTC](https://forum.mikrotik.com/t/v7-18rc-testing-is-released/182052/111 "2025-02-21T18:35:29Z")

</div>

My IPsec tunnels broke on my RB5009 with 7.18rc1. I had to disable the IPv4 forwarding fasttrack rule to fix it for now. I opened ticket SUP-180137.

---

<div class="post-metadata">

**Author:** ![infabo](https://forum.mikrotik.com/user_avatar/forum.mikrotik.com/infabo/32/55692_2.png) [@infabo](https://forum.mikrotik.com/u/infabo)\
**Post date:** [February 21, 2025, 7:07pm UTC](https://forum.mikrotik.com/t/v7-18rc-testing-is-released/182052/112 "2025-02-21T19:07:20Z")

</div>

Strange. There is not even any ipsec related change in rc1.

---

<div class="post-metadata">

**Author:** ![fischerdouglas](https://forum.mikrotik.com/user_avatar/forum.mikrotik.com/fischerdouglas/32/2357_2.png) [@fischerdouglas](https://forum.mikrotik.com/u/fischerdouglas)\
**Post date:** [February 21, 2025, 7:12pm UTC](https://forum.mikrotik.com/t/v7-18rc-testing-is-released/182052/113 "2025-02-21T19:12:22Z")

</div>

> [@](#):
>
> Hi mrz, any reason why MT still hide vpn6 afi from winbox?  
> If there any limitation should we know about?

By the way, it is worth mentioning that the syntax between routing and routes is still incongruent:

```plaintext
[administrator@fischerdouglas] > /routing/bgp/connection/print where address-families=
ip ipv6 l2vpn l2vpn-cisco vpnv4 vpnv6

```

```plaintext
[administrator@fischerdouglas] > /routing/route/print where afi=  
bad ip4 ip6 l2vpn l2vpn-cisco l2vpn-link link mip4 mip6 vpn4 vpn6

```

- “address-families=” vs “afi=”
- “vpnv4” vs “vpn4”
- “vpnv6” vs “vpn6”

---

<div class="post-metadata">

**Author:** ![Amm0](https://forum.mikrotik.com/user_avatar/forum.mikrotik.com/amm0/32/1630_2.png) [@Amm0](https://forum.mikrotik.com/u/Amm0)\
**Post date:** [February 21, 2025, 8:01pm UTC](https://forum.mikrotik.com/t/v7-18rc-testing-is-released/182052/114 "2025-02-21T20:01:31Z")

</div>

> [@](#):
>
> > [@](#):
> >
> > \*) console - put !empty sentence when API query returns nothing;
> 
> And why was this change even made?? Only in response to some customer who does not understand that an empty response could be returned on a query?

If only Mikrotik would actually write in more than partial sentence or have a proper KB-like system for these questions… My only guess is the API changed are for _internal_ use with REST API. I think REST API just proxies to API, but uses cached/pipelined connection (based on login in log)… in which case knowing a _tagged_ API request was !empty might be useful. But just guessing.

> [@](#):
>
> \*) lte - added initial eSIM management support (additional fixes);

I have ask several times about what modems this works with, no response, now half-dozen times. The lack of clarity around eSIM is quite annoying. From reading the docs, it seems like a working feature on something. If it’s nothing, then say that in docs! Since I read the docs, and [eSIM came up in another thread](http://forum.mikrotik.com/t/esim-in-7-18rc/182138/1), the [eSIM docs](https://help.mikrotik.com/docs/spaces/ROS/pages/30146563/LTE#LTE-LTEesim) don’t mention if the QR code had a $$1 at the end. Which, I think, means the

```plaintext
confirmation-code=

```

be required… and the $$1 part should NOT be in the

```plaintext
matching-id=

```

- but it wasn’t clear at all… And working in theory here…  
  
  

> [@](#):
>
> \*) console - added dsv.remap to :serialize command to unpack array of maps from print as-value (additional fixes);  
> \*) console - allow tab as dsv delimiter;

Now the bright spot is the new scripting changes are just wonderful. They made quick work of the theoretical problem eSIM activation codes use the $ dollar as the delimiter. So on the theoretical modem that support eSIM, you can cut-and-paste the eSIM code to CLI. This is possible by the new :deserialize delimiter=“$” specifically to deal with eSIM LPA format (with the new-ish /terminal/ask allowing cut-and-paste). See [Interactively parsing eSIM Activation from LPA in QRCode...](http://forum.mikrotik.com/t/interactively-parsing-esim-activation-from-lpa-in-qrcode/182146/1) for example.

But there should be something like /ip/dhcp-server/setup for the eSIM. Or, Winbox4 could natively use camera to capture the QR code, too.

---

<div class="post-metadata">

**Author:** ![engycz](https://forum.mikrotik.com/letter_avatar/engycz/32/6_449c533f586939b6e5f246632a46421f.png) [@engycz](https://forum.mikrotik.com/u/engycz)\
**Post date:** [February 21, 2025, 10:08pm UTC](https://forum.mikrotik.com/t/v7-18rc-testing-is-released/182052/115 "2025-02-21T22:08:55Z")

</div>

> [@](#):
>
> > [@](#):
> >
> > \*) dhcpv6-relay - add routes for bindings passing through relay;
> 
> i’d really appreciate an option to disable this for both relay and server (unless one already exists and i couldn’t find it) – when using DHCPv6 for IA\_NA, there’s often no need to add these routes and they clog up the routing table.

There it is  
 ![relay.png](https://data-discourse.cdn.mikrotik.com/original/3X/5/2/52d46e4015c0ca4774704ed2ddad55409b73634b.png)

---

<div class="post-metadata">

**Author:** ![felixka](https://forum.mikrotik.com/user_avatar/forum.mikrotik.com/felixka/32/55669_2.png) [@felixka](https://forum.mikrotik.com/u/felixka)\
**Post date:** [February 22, 2025, 12:20am UTC](https://forum.mikrotik.com/t/v7-18rc-testing-is-released/182052/116 "2025-02-22T00:20:22Z")

</div>

> [@](#):
>
> My IPsec tunnels broke on my RB5009 with 7.18rc1. I had to disable the IPv4 forwarding fasttrack rule to fix it for now. I opened ticket SUP-180137.

Looks like this actually was a configuration error.  
The “defconf: fasttrack” rule somehow ended up above the “defconf: accept in ipsec policy” and “defconf: accept out ipsec policy” rules. When I moved the fasttrack rule below those two rules (like they are in defconf) it started working again. Not sure if this is documented anywhere, but that’s what is required.

---

<div class="post-metadata">

**Author:** ![buset1974](https://forum.mikrotik.com/letter_avatar/buset1974/32/6_449c533f586939b6e5f246632a46421f.png) [@buset1974](https://forum.mikrotik.com/u/buset1974)\
**Post date:** [February 22, 2025, 12:46am UTC](https://forum.mikrotik.com/t/v7-18rc-testing-is-released/182052/117 "2025-02-22T00:46:32Z")

</div>

> [@](#):
>
> > [@](#):
> >
> > Hi mrz, any reason why MT still hide vpn6 afi from winbox?  
> > If there any limitation should we know about?
> 
> By the way, it is worth mentioning that the syntax between routing and routes is still incongruent:
> 
> ```plaintext
> [administrator@fischerdouglas] > /routing/bgp/connection/print where address-families=
> ip ipv6 l2vpn l2vpn-cisco vpnv4 vpnv6
> 
> ```
> 
> ```plaintext
> [administrator@fischerdouglas] > /routing/route/print where afi=  
> bad ip4 ip6 l2vpn l2vpn-cisco l2vpn-link link mip4 mip6 vpn4 vpn6
> 
> ```
> 
> - “address-families=” vs “afi=”
> - “vpnv4” vs “vpn4”
> - “vpnv6” vs “vpn6”

+1 , Yes i also notice this

---

<div class="post-metadata">

**Author:** ![buset1974](https://forum.mikrotik.com/letter_avatar/buset1974/32/6_449c533f586939b6e5f246632a46421f.png) [@buset1974](https://forum.mikrotik.com/u/buset1974)\
**Post date:** [February 22, 2025, 1:42am UTC](https://forum.mikrotik.com/t/v7-18rc-testing-is-released/182052/118 "2025-02-22T01:42:51Z")

</div>

> [@](#):
>
> > [@](#):
> >
> > LDP signaled VPLS works  
> > BGP signaled VPLS works  
> > VPNv6 works
> > 
> > either misconfiguration or very specific setup.
> 
> Could you please share an example config with at least 4 devices RouterOS, being at least one on P.Router Only, with the v7.18rc ?

Up

---

<div class="post-metadata">

**Author:** ![buset1974](https://forum.mikrotik.com/letter_avatar/buset1974/32/6_449c533f586939b6e5f246632a46421f.png) [@buset1974](https://forum.mikrotik.com/u/buset1974)\
**Post date:** [February 22, 2025, 1:43am UTC](https://forum.mikrotik.com/t/v7-18rc-testing-is-released/182052/119 "2025-02-22T01:43:51Z")

</div>

> [@](#):
>
> > [@](#):
> >
> > LDP signaled VPLS works  
> > BGP signaled VPLS works  
> > VPNv6 works
> > 
> > either misconfiguration or very specific setup.
> 
> Its totally basic setup in labs, both CHR and physical routerboards. There is a P router in the middle and 3 PE on that.  
> This is the MPLS and Routing config from first PE router (RB750Gr3):
> 
> ```plaintext
> [oreggin@rtr1.CPE] > /mpls/export 
> /mpls interface
> add interface=all mpls-mtu=1500
> /mpls ldp
> add afi=ip,ipv6 disabled=no lsr-id=10.0.10.11 preferred-afi=ipv6 transport-addresses=10.0.10.11,b00b::10:0:10:11
> /mpls ldp interface
> add accept-dynamic-neighbors=yes afi=ip,ipv6 disabled=no interface=ether2
> 
> [oreggin@rtr1.CPE] > /routing/export 
> /routing bgp template
> set default disabled=no router-id=10.0.10.11
> /routing ospf instance
> add disabled=no name=ospfv2 router-id=10.0.10.11
> add disabled=no name=ospfv3 router-id=10.0.10.11 version=3
> /routing ospf area
> add disabled=no instance=ospfv2 name=backbone4
> add disabled=no instance=ospfv3 name=backbone6
> /routing bgp connection
> add address-families=ip,l2vpn,l2vpn-cisco,vpnv4 as=65530 connect=no disabled=no listen=yes local.address=10.0.10.11 .role=ibgp-rr name=rrcl4 nexthop-choice=force-self \
> output.default-originate=if-installed .redistribute=connected remote.address=10.0.10.0/24 .as=65530 router-id=10.0.10.11 routing-table=main
> add address-families=ipv6,vpnv6 as=65530 connect=no disabled=no listen=yes local.address=b00b::10:0:10:11 .role=ibgp-rr name=rrcl6 output.default-originate=always .redistribute=connected \
> remote.address=b00b::10:0:10:0/112 .as=65530 router-id=10.0.10.11 routing-table=main
> /routing bgp vpls
> add bridge=VPLS_B bridge-horizon=4 comment="BGP signaled VPLS" disabled=no export-route-targets=65530:4 import-route-targets=65530:4 name=VPLS_B pw-type=vpls rd=65530:4 site-id=11
> add bridge=VPLS_A bridge-horizon=3 cisco-id=33.33.33.11 comment="LDP signaled VPLS" disabled=no export-route-targets=65530:3 import-route-targets=65530:3 name=VPLS_A pw-type=vpls rd=\
> 65530:3
> /routing bgp vpn
> add disabled=no export.redistribute=connected .route-targets=65530:1 import.route-targets=65530:1 .router-id=VRF_A label-allocation-policy=per-vrf name=bgp-mpls-vpn-1 route-distinguisher=\
> 65530:1 vrf=VRF_A
> add disabled=no export.redistribute=connected .route-targets=65530:2 import.route-targets=65530:2 .router-id=VRF_B label-allocation-policy=per-prefix name=bgp-mpls-vpn-2 \
> route-distinguisher=65530:2 vrf=VRF_B
> /routing filter rule
> add chain=BGP_out rule=accept
> /routing ospf interface-template
> add area=backbone4 cost=1000 disabled=no interfaces=ether2 type=ptp
> add area=backbone6 cost=1000 disabled=no interfaces=ether2 type=ptp
> add area=backbone4 disabled=no interfaces=Loopback0 passive
> add area=backbone6 disabled=no interfaces=Loopback0 passive
> [oreggin@rtr1.CPE] >
> 
> ```
> 
> Maybe misconfiguration, but I can’t figure out what or where. If you have any proposal, it would be appreciated.
> 
> ```plaintext
> [oreggin@rtr1.CPE] > /interface/vpls/print        
> Flags: R - RUNNING; D - DYNAMIC
> Columns: NAME, PEER, BGP-VPLS
> # NAME PEER BGP-VPLS
> 0 RD vpls1 10.0.10.13 VPLS_B  
> 1 RD vpls2 10.0.10.12 VPLS_B  
> 2 D vpls3 10.0.10.13 VPLS_A  
> 3 D vpls4 10.0.10.12 VPLS_A  
> [oreggin@rtr1.CPE] > /mpls/forwarding-table/print 
> Flags: L - LDP, P - VPN, V - VPLS
> Columns: LABEL, VRF, PREFIX, NEXTHOPS, VPLS
> # LABEL VRF PREFIX NEXTHOPS VPLS 
> 0 P 32 VRF_A                                                                                     
> 1 P 33 VRF_B 10.0.12.0/29                                                                       
> 2 P 34 VRF_B b00b:10:11:12::/64                                                                 
> 3 L 42 main b00b::10:0:10:1 { nh=fe80::20c:42ff:fe53:1491%ether2; interface=ether2 }       
> 4 L 39 main 10.0.10.1 { label=impl-null; nh=10.0.0.25; interface=ether2 }            
> 5 L 40 main 10.0.10.12 { label=21; nh=10.0.0.25; interface=ether2 }                   
> 6 L 41 main 10.0.10.13 { label=20; nh=10.0.0.25; interface=ether2 }                   
> 7 L 37 main 10.0.0.0/30 { label=impl-null; nh=10.0.0.25; interface=ether2 }            
> 8 L 38 main 10.0.1.0/30 { label=impl-null; nh=10.0.0.25; interface=ether2 }            
> 9 V 29 vpls1
> 10 V 28 vpls2
> 11 L 43 main b00b::10:0:10:12 { nh=fe80::20c:42ff:fe53:1491%ether2; interface=ether2 }       
> 12 L 44 main b00b::10:0:10:13 { nh=fe80::20c:42ff:fe53:1491%ether2; interface=ether2 }       
> [oreggin@rtr1.CPE] >
> 
> ```
> 
> Thanks!

Up

---

<div class="post-metadata">

**Author:** ![buset1974](https://forum.mikrotik.com/letter_avatar/buset1974/32/6_449c533f586939b6e5f246632a46421f.png) [@buset1974](https://forum.mikrotik.com/u/buset1974)\
**Post date:** [February 22, 2025, 1:45am UTC](https://forum.mikrotik.com/t/v7-18rc-testing-is-released/182052/120 "2025-02-22T01:45:15Z")

</div>

> [@](#):
>
> VPNv6 does indeed work, but only partially, as it does not support an IPv4 backbone as a transport layer.

Up

[Previous page](https://forum.mikrotik.com/t/v7-18rc-testing-is-released/182052.md?page=5)

[Next page](https://forum.mikrotik.com/t/v7-18rc-testing-is-released/182052.md?page=7)
