Hello Renato,

Are you sure about that?

Configuration is:
!
interface eth0
 ip address 192.0.2.2/30
!
interface lo
 ip address 192.0.2.8/32
!
router bgp 64497
 no bgp default ipv4-unicast
 coalesce-time 1000
 neighbor 192.0.2.1 remote-as 64496
 !
 address-family ipv4 unicast
  network 192.0.2.8/32
  redistribute connected
 exit-address-family
 !
 address-family ipv4 labeled-unicast
  neighbor 192.0.2.1 activate
 exit-address-family
!

And 192.0.2.1 is not receiving any routes

Regards

Marco

On Mon, Jul 23, 2018 at 6:18 PM Renato Westphal <renato@opensourcerouting.org> wrote:
Hi Marco,

In the FRR BGP-LU implementation, both the unicast and labeled-unicast
SAFIs share the same routing table. So if you use the "network" and
"redistribute" commands under "address-family ipv4 unicast", the
redistributed routes will be assigned a local label if one is
configured in zebra (BGP-LU doesn't support dynamic labels yet).

Example:
  address-family ipv4 unicast
   network 1.1.1.1/32
   no neighbor 10.0.1.2 activate
  exit-address-family
  !
  address-family ipv4 labeled-unicast
   neighbor 10.0.1.2 activate
   exit-address-family
  !

Unfortunately we don't have documentation for BGP-LU yet since it's a
relatively new feature. In case it helps, here's my BGP-LU test
topology: https://gist.github.com/rwestphal/9707df2ff6c2073c8b46a23e7d603859

Regards,
Renato.

On Fri, Jul 20, 2018 at 5:08 AM, Marco Marzetti <marco@lamehost.it> wrote:
> Dear members of the group,
>
> I've noticed neither "redistribute" nor "network" commands are supported by
> bgpd for AFI/SAFI ipv4 labeled-unicast.
>
> I took a look at github and i can't find the features in any of the
> milestones.
> Is there an underlying reason i can't spot or is it just the dev team hasn't
> found time yet?
>
> Thank you for your help.
>
> Regards
>
> _______________________________________________
> frog mailing list
> frog@lists.frrouting.org
> https://lists.frrouting.org/listinfo/frog
>



--
Renato Westphal


--
Marco