Protocol direct

[Daniel Czerwonk]

Hi Milosz,

I had the same problem yesterday. Direct protocol did not learn routes
either with implicit or explicit multichannel configuration. After
splitting it in 2 protocols, it worked for me. Maybe that's a feasible
workaround for you, too.

protocol direct direct4 {
  ipv4;
  interface "*";
};

protocol direct direct6 {
  ipv6;
  interface "*";
};

Best regards,
Daniel
> Miłosz Oller <mailto:milosz at sys-com.pl>
> 22. December 2017 at 00:46
> protocol direct {
>     ipv4;
>     ipv6;
>     interface "*";
> }
>
> And it doesn't announced any local prefix to upstream peers, only to
> ibgp peer.
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://trubka.network.cz/pipermail/bird-users/attachments/20171222/90478cf2/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 926 bytes
Desc: OpenPGP digital signature
URL: <http://trubka.network.cz/pipermail/bird-users/attachments/20171222/90478cf2/attachment.asc>