7.19.4 ISIS evaluation but really need *unnumbered/interface* routes

RouterOS Forwarding Protocols
1

I have a small GNS3 build with CHR and I configured ISIS in two ways:

/routing isis instance
add areas=49.0001 disabled=no l2.redistribute=connected,static name=isis-l2 system-id=0001.0000.0001
/routing isis interface-template
add instance=isis-l2 interfaces=ether3 levels=l2 ptp
add instance=isis-l2 interfaces=ether2 levels=l2 ptp

or

/routing isis instance
add areas=49.0001 disabled=no l2.redistribute=connected,static name=isis-l2 system-id=0001.0000.0001
/routing isis interface-template
add instance=isis-l2 interfaces=ether2,ether3,ether4,ether5,ether6 levels=l2

ie, the most basic setup possible to simplify testing.

ISIS comes up, but unless I put a shared subnet between interfaces it wont insert routes. It's doing IP%interface routes so that sort of makes sense, but ISIS should allow for just interface routes.

One of the main benefits to using ISIS is to use unnumbered interfaces for a lighter configuration.

Does anyone know if unnumbered interfaces is coming anytime soon?

2

Hi. We use unnumbered addresses with isis+ldp at 7.19.1
/ip address add address=<router loopback address> comment=test interface=bridge1.484 network=<unnambered user address>
But somewhere after addition new address its does not work. Even mikrotik have ping from loopback address to new customer pc and customer pc take traceroute to mikrotik loopback, but no far nexthop. Then we make /routing/isis/instance/set 0 disable=yes and /routing/isis/instance/set 0 disable=no and new address is being accessible :grinning_face:
isis config:
/routing isis instance add afi=ip areas=44.0001 disabled=no l2.redistribute=connected name=isis-instance-1 system-id=0044.4444.4444 /routing isis interface-template add instance=isis-instance-1 interfaces=sfp-sfpplus12 levels=l2 add instance=isis-instance-1 interfaces=sfp28-1 levels=l2