Community discussions

MikroTik App
 
gechev
just joined
Topic Author
Posts: 19
Joined: Mon Jul 18, 2016 7:51 pm

v7: BGP mikrotik<-->junos: Unsupported capability received, code: 128

Wed Jan 12, 2022 10:45 pm

Hello!
Trying to establish BGP connection to Junos without success.
Mikrotik config:
...
 3  name="peer-int" 
     remote.address=10.200.1.10 .as=XXXX .ttl=2 
     local.ttl=2 .role=ebgp-customer 
     connect=yes listen=yes routing-table=main as=YYYY nexthop-choice=force-self multihop=no
     output.filter-chain=IB_OUT .network=bgp_nets .default-originate=never
The problem:
 21:31:44 route,bgp,debug,packet OPEN Message capabilities optionLenght=6
 21:31:44 route,bgp,debug,packet OPEN Message capabilityCode=multiprotocol capabilityLenght=4
 21:31:44 route,bgp,debug,packet OPEN Message capabilities optionLenght=6
 21:31:44 route,bgp,debug,packet OPEN Message capabilityCode=128Lenght=0
 21:31:44 route,bgp,debug Unsupported capability received, code: 128BgpStarter{ c=Connection{ ConnId{ 10.200.1.3:39655 -> 10.200.1.10:179 } Socket{ 5[00IN] onClose } out } readsz=59 } cancel
 21:31:44 route,bgp,debug,packet OPEN Message capabilities optionLenght=6
 21:31:44 route,bgp,debug,packet OPEN Message capabilityCode=route refresh capabilityLenght=0
 21:31:44 route,bgp,debug,packet OPEN Message capabilities optionLenght=6
 21:31:44 route,bgp,debug,packet OPEN Message capabilityCode=64Lenght=2
 21:31:44 route,bgp,debug,packet OPEN Message capabilities optionLenght=6
 21:31:44 route,bgp,debug,packet OPEN Message capabilityCode=AS 4-octet capabilityLenght=4
 21:31:44 route,bgp,debug,state Entering OpenConfirm state BgpStarter{ c=Connection{ ConnId{ 10.200.1.3:39655 -> 10.200.1.10:179 } Socket{ 5[00IN] onClose } out } readsz=59 } cancel
Mikrotik BGP session:
 3   remote.address=10.200.1.10 .refused-cap-opt=no 
     local.address=10.200.1.3

The problem is how to find a workaround for code 128 ("Prestandard Route Refresh (deprecated)") - Capability Codes
There was another error too: "Unsupported capability received, code: 71", but disabling "graceful-restart" on Junos solved it.
On junos "bgp-orf-cisco-mode;" is not enabled.
routeros version: 7.1.1
junos version: 17.4R2.4

Another routerboard with routeros v6 has no problems connecting to both these peers.
Linux with quagga has no problems connecting to both these peers too.
 
User avatar
mrz
MikroTik Support
MikroTik Support
Posts: 6821
Joined: Wed Feb 07, 2007 12:45 pm
Location: Latvia
Contact:

Re: v7: BGP mikrotik<-->junos: Unsupported capability received, code: 128

Thu Jan 13, 2022 9:40 am

Record packets of BGP session with packet sniffer and send pcap file and supout file to support.
 
gechev
just joined
Topic Author
Posts: 19
Joined: Mon Jul 18, 2016 7:51 pm

Re: v7: BGP mikrotik<-->junos: Unsupported capability received, code: 128

Sat Jan 15, 2022 8:52 pm

Sent.
 
method
newbie
Posts: 39
Joined: Fri Mar 25, 2005 3:29 pm

Re: v7: BGP mikrotik<-->junos: Unsupported capability received, code: 128

Fri Feb 11, 2022 5:19 pm

I supose you have in winbox session highlighted to red, just uncheck listen , only check connect and save. Should work.
 
gechev
just joined
Topic Author
Posts: 19
Joined: Mon Jul 18, 2016 7:51 pm

Re: v7: BGP mikrotik<-->junos: Unsupported capability received, code: 128

Wed Feb 16, 2022 7:25 pm

No, doesn't work. Obviously it doesn't matter who is initiator of the session.
 
DubiousBen
just joined
Posts: 1
Joined: Mon Feb 21, 2022 2:28 am

Re: v7: BGP mikrotik<-->junos: Unsupported capability received, code: 128

Mon Feb 21, 2022 2:30 am

Hi all,
I am also having this same issue.
Did anyone find a solution?
 
brainy
Member Candidate
Member Candidate
Posts: 155
Joined: Fri Sep 29, 2006 3:08 pm
Location: Unterschleissheim, Germany
Contact:

Re: v7: BGP mikrotik<-->junos: Unsupported capability received, code: 128

Sat Jun 18, 2022 6:59 pm

Any news here? It's still not fixed ...
 
sep
newbie
Posts: 25
Joined: Thu Nov 28, 2013 2:34 pm

Re: v7: BGP mikrotik<-->junos: Unsupported capability received, code: 128

Mon Oct 31, 2022 5:08 pm

Dropping a session due to a unknown capability announcement, in the negotiation, Is a critical bug that needs fixing.

But while we are waiting for that, do anyone know how to disable pre-standard route refresh capability 80 (128) and only use the standard 02 (2) ? on cisco XR ?

best regards
 
User avatar
mrz
MikroTik Support
MikroTik Support
Posts: 6821
Joined: Wed Feb 07, 2007 12:45 pm
Location: Latvia
Contact:

Re: v7: BGP mikrotik<-->junos: Unsupported capability received, code: 128

Tue Nov 01, 2022 9:02 am

Received unsupported capability is not the cause of the session not working. Unsupported capabilities are ignored.
Most likely there is misconfiguration, typically BFD enabled or non-matching local or remote addresses configured either on ROS or on the remote peer.

You can send a supout file and pcap file from a non-working session to the support. And we can check if everything is correct on the ROS side.
 
sep
newbie
Posts: 25
Joined: Thu Nov 28, 2013 2:34 pm

Re: v7: BGP mikrotik<-->junos: Unsupported capability received, code: 128

Tue Nov 01, 2022 4:11 pm

Thanks for the reply.

I saw the bfd checkbox and assumed it was supported. reading on the forum, seems not yet.
disabled bfd on the session, and it came up.


for other people googling, the error message was:
Unsupported capability received, code: 128BgpStarter{ c=Connection{ ConnId{ 192.0.2.1:45561 -> 192.0.2.2:179 } Socket{ 11 ida } out } readsz=61 } cancel
Entering OpenConfirm state BgpStarter{ c=Connection{ ConnId{ 192.0.2.1:45561 -> 192.0.2.2:179 } Socket{ 11 ida } out } readsz=61 } cancel

Who is online

Users browsing this forum: No registered users and 7 guests