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
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 _________________________________________ 44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
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@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
Ah ok. Now I see those routes have their gateway in their own subnet.
This is one situation where the routes are dropped since we have no solution for them and get dropped (implemented since 1.13 up to 1.16). In newer versions than 1.16, there should be 2 route entries created by ampr-ripd:
44.24.172.40/29 via 44.24.172.41 44.24.172.41/32 via default gateway as defined by the -g option (encap would be NAT-ed by your router and sent to the endpoint via internet).
if -g is not set, those subnets will be dropped.
On 08.03.2018 20:59, Gustavo Ponza wrote:
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@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
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
Very clear explanation,TNX!
73 and ciao, gus i0ojj/ir0aab
On 03/08/2018 11:08 PM, Marius Petrescu wrote:
Ah ok. Now I see those routes have their gateway in their own subnet.
This is one situation where the routes are dropped since we have no solution for them and get dropped (implemented since 1.13 up to 1.16). In newer versions than 1.16, there should be 2 route entries created by ampr-ripd:
44.24.172.40/29 via 44.24.172.41 44.24.172.41/32 via default gateway as defined by the -g option (encap would be NAT-ed by your router and sent to the endpoint via internet).
if -g is not set, those subnets will be dropped.
On 08.03.2018 20:59, Gustavo Ponza wrote:
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@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
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
-
Gustavo Ponza -
Marius Petrescu -
marius＠yo2loj.ro