Community discussions

MikroTik App
 
blingblouw
Member
Member
Topic Author
Posts: 345
Joined: Wed Aug 25, 2010 9:43 am

IRR Advice

Wed Feb 06, 2019 6:14 pm

Hi

So I am aware this is not a Mikrotik related question, I just wanted to see if anyone here had some advise.

We recently received our ASN and public IP block.

My question is, what are you supposed to do with IRR and object creation. I plan to peer in a few exchanges and with my upstream (s)

Could anyone give a simple, to the point, explanation of what objects are and why you create them. Sorry if this sounds like the dumbest question ever
 
bbs2web
Member Candidate
Member Candidate
Posts: 232
Joined: Sun Apr 22, 2012 6:25 pm
Location: Johannesburg, South Africa
Contact:

Re: IRR Advice

Fri Feb 08, 2019 6:37 am

Internet Routing Registries provide methods via which others can retrieve information relating to how IPs, ASNs and other resources are delegated. It allows others to, for example, query who is responsible for an IP or subnet and what prefixes are authorised to be announced by what ASN.

Your regional resource authority would most probably already have created organisational and person objects on your behalf, associated an inetnum object detailing the allocated range to your organisation and an ASN object. You typically only have to create a route object authorising a prefix to be valid when it originates from a specified ASN.

Herewith an example:
[root@backup1 ~]# whois 41.79.20.0/22                                                          % This is the AfriNIC Whois server.

% Note: this output has been filtered.
%       To receive output for a database update, use the "-B" flag.

% Information related to '41.79.20.0 - 41.79.23.255'

% Abuse contact for '41.79.20.0 - 41.79.23.255' is 'abuse@syrex.co.za'

inetnum:        41.79.20.0 - 41.79.23.255
netname:        Syrex-Pty-Ltd
descr:          Syrex Pty Ltd
country:        ZA
org:            ORG-SI4-AFRINIC
admin-c:        BW4-AFRINIC
tech-c:         DH6-AFRINIC
status:         ALLOCATED PA
mnt-by:         AFRINIC-HM-MNT
mnt-lower:      SYREX-MNT
mnt-irt:        IRT-SYREX-ABUSE
source:         AFRINIC # Filtered
parent:         41.0.0.0 - 41.255.255.255

organisation:   ORG-SI4-AFRINIC
org-name:       Syrex Pty Ltd
org-type:       LIR
country:        ZA
address:        Curzon Place
address:        Turnberry Office Park
address:        48 Grosvenor Road
address:        Bryanston
address:        Johannesburg 2021
phone:          tel:+27-11-721-1900
phone:          tel:+27-86-117-9739
fax-no:         tel:+27-86-127-9739
fax-no:         tel:+27-11-721-1999
admin-c:        BW4-AFRINIC
tech-c:         DH6-AFRINIC
mnt-ref:        AFRINIC-HM-MNT
mnt-ref:        SYREX-MNT
mnt-by:         AFRINIC-HM-MNT
source:         AFRINIC # Filtered

person:         B Watson
address:        Curzon Place
address:        Turnberry Office Park
address:        48 Grosvenor Road
address:        Bryanston
address:        Johannesburg 2021
address:        South Africa
phone:          tel:+27-11-721-1900
fax-no:         tel:+27-11-721-1999
nic-hdl:        BW4-AFRINIC
mnt-by:         GENERATED-UZPES3BKQV1CLD0GTIP7JRMGDFPKZYED-MNT
source:         AFRINIC # Filtered

person:         D Herselman
address:        Curzon Place
address:        Turnberry Office Park
address:        48 Grosvenor Road
address:        Bryanston
address:        Johannesburg 2021
address:        South Africa
phone:          tel:+27-11-721-1900
fax-no:         tel:+27-11-721-1999
nic-hdl:        DH6-AFRINIC
mnt-by:         GENERATED-KD25BYRDIOZAJKGVM4HQL9YQDRSI0NOM-MNT
source:         AFRINIC # Filtered

% Information related to '41.79.20.0/22AS37314'

route:          41.79.20.0/22
descr:          Syrex (Pty) Ltd - South Africa
origin:         AS37314
mnt-by:         SYREX-MNT
source:         AFRINIC # Filtered

You can additionally create as-set objects which assist upstream providers and peers in automating prefix administration. This eases administration, should you start acting as a transit provider for other networks. For example:
[root@backup1 ~]# bgpq3 -3 -l syrex-as path -f 37314 as-syrex
no ip as-path access-list syrex-aspath
ip as-path access-list syrex-aspath permit ^37314(_37314)*$
ip as-path access-list syrex-aspath permit ^37314(_[0-9]+)*_(7926|37316|327781|328074)$
ip as-path access-list syrex-aspath permit ^37314(_[0-9]+)*_(328086|328130|328144|328164)$

[root@backup1 ~]# bgpq3 -3Ab -l syrex-ipv4 -m 24 as-syrex
syrex-ipv4 = [
    41.79.20.0/22,
    41.79.20.0/23{24,24},
    41.79.22.0/24,
    45.221.32.0/20,
    80.95.8.0/21,
    102.141.208.0/22,
    154.119.64.0/20,
    154.119.64.0/24,
    154.119.66.0/24,
    154.119.78.0/24,
    160.0.192.0/19,
    160.119.208.0/22,
    165.16.128.0/19,
    165.16.128.0/20,
    165.16.144.0/23,
    165.109.0.0/16,
    165.109.64.0/20,
    165.109.96.0/20,
    165.109.128.0/19,
    165.109.128.0/20,
    165.109.208.0/22,
    165.109.224.0/20,
    168.155.16.0/24,
    168.230.0.0/16,
    168.230.96.0/23{24,24},
    168.230.98.0/23,
    168.230.100.0/22{23,23},
    168.230.105.0/24,
    168.230.108.0/24,
    168.230.111.0/24,
    168.230.137.0/24,
    168.230.139.0/24,
    168.230.160.0/19,
    168.230.160.0/24,
    168.230.208.0/20,
    168.230.240.0/22{24,24},
    168.230.244.0/24,
    168.230.248.0/22{24,24},
    168.230.252.0/24,
    169.255.128.0/22,
    169.255.244.0/22,
    192.70.200.0/24,
    196.43.209.0/24,
    196.61.68.0/22,
    196.61.68.0/23{24,24},
    196.216.132.0/22,
    196.223.232.0/21
];

Who is online

Users browsing this forum: loloski and 8 guests