-
Notifications
You must be signed in to change notification settings - Fork 4
/
Copy pathnagpeer.imail.tt2
51 lines (39 loc) · 1.38 KB
/
nagpeer.imail.tt2
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
From: Marco d'Itri <[email protected]>
To: [% peeremail +%]
[% IF param.bcc %]
Bcc: [% param.bcc +%]
[% END %]
Subject: networks announced by AS[% as +%]
User-Agent: nagpeer/1.0
(This is a standard text, generated semi-automatically.)
After a periodical revision of our BGP filters, we determined some
inconsistencies between the set of networks announced by your
autonomous system AS[% as %] and those registered in the RIPE
database with the expansion of your [% IF top_object.match('^AS-') -%]
as-set[% ELSE %]aut-num[% END %] object [% top_object %].
Specifically:
[% IF asn.size %]
* the following autonomous systems of customers of yours are not listed
in the as-set:
[% FOREACH a = asn.asnsort %]
[% a +%]
[% END %]
If an as-set object does not list all the autonomous systems actually
announced then peers will not be able to automatically generate their
BGP filters.
[% END %]
[% IF routes.size %]
* there are no route objects for the following networks:
[% FOREACH r = routes.ipsort %]
[% r %][% IF paths.$r %] ([% paths.$r %])[% END +%]
[% END %]
The purpose of route objects is to document which autonomous system is
authorized to announce a network. Registering them allows your peers to
automatically generate their BGP filters, allowing timely updates
without the need for manual changes.
[% END %]
Please let me know if you have any questions, and thank you for your
help.
--
ciao,
Marco