no bgp default ipv4-unicast

NetFreak

Can you please implement a possibility to disable IPv6 sessions within the IPv4 address family?

In FRR it looks like this:

c01.fra.de.as49697.net# show bgp summary 

IPv4 Unicast Summary:
BGP router identifier 185.121.69.70, local AS number 49697 vrf-id 0
BGP table version 1047794
RIB entries 1494151, using 262 MiB of memory
Peers 2, using 41 KiB of memory

Neighbor              V         AS MsgRcvd MsgSent   TblVer  InQ OutQ  Up/Down State/PfxRcd
81.94.61.2            4      39912  391592     659        0    0    0 05:26:47       818127
2a01:100:1027:1337::2 4      39912  114294     661        0    0    0 05:26:48 NoNeg

Total number of neighbors 2

IPv6 Unicast Summary:
BGP router identifier 185.121.69.70, local AS number 49697 vrf-id 0
BGP table version 247765
RIB entries 181100, using 32 MiB of memory
Peers 1, using 20 KiB of memory

Neighbor              V         AS MsgRcvd MsgSent   TblVer  InQ OutQ  Up/Down State/PfxRcd
2a01:100:1027:1337::2 4      39912  114294     661        0    0    0 05:26:48        95543

In versions prior TNSR 20.x it was possible to do the following:

conf t
(config)# route bgp 3158
(config-router)# address-family ipv4
(config-router-af)# no neighbor 2a06:e81:119:b::2 activate
(config-router-af)# end

But since the big change in version 20 even this is not longer possible.

I was evaluating TNSR a longer time ago, the last info I got was that this has been noted in a redmine case (RM 4399) and someone is working on that.

Please either implement this command (see topic name) or re-implement the workaround that worked before.

Thanks!

Joey

audian

@NetFreak said in no bgp default ipv4-unicast:

4399

Thanks Joey, the original request is still on our backlog, no roadmap ETA at the moment though.