8 Mar
2018
8 Mar
'18
12:59 p.m.
TNX Marius.
No way from here to route towards that addresses;
I see that other similar situations are managed
OK. However the ampr-ripd has been effective to
delete that routes and so peace is done :)
73 and ciao, gus i0ojj/ir0aab
On 03/08/2018 09:03 AM, marius(a)yo2loj.ro wrote:
Those are no errors.
You need to route the endpoints (which are BGP published) individually via
your gateway to the internet and it will work.
Ampr-ripd does this if you set the proper parameters.
Marius, YO2LOJ
> Hi, to all concerned,
>
> found the following errors by making the 'source' of the
> actual 'encap.txt' file.
>
> Can't add route to 44.24.172.40/29 via encap 44.24.172.41
> Can't add route to 44.130.104/24 via encap 44.130.104.1
> Can't add route to 44.130.105/24 via encap 44.130.105.1
> Can't add route to 44.130.106/24 via encap 44.130.106.1
> Can't add route to 44.130.107/24 via encap 44.130.107.1
> Can't add route to 44.131.14.252/31 via encap 44.131.14.253
> Can't add route to 44.136.150/23 via encap 44.136.150.2
>
> --
> 73 and ciao, gus i0ojj/ir0aab