Sponsorizare LIR
LIR-ul tau curent se inchide, cere prea mult sau nu raspunde la tichete? Muta sponsorizarea prefixelor IPv4 si IPv6 existente sau a ASN-ului tau la LIR RIPE NCC al DreamServer printr-o singura schimbare coordonata. Anunturile tale raman pe tabela de rutare, ROA-urile RPKI raman semnate, doar atributele mnt-by, org si de sponsorizare se schimba in baza de date.
- Fara taxa de transfer RIPE din partea noastra
- Continuitate RPKI pastrata
- Audit anual RIPE gestionat
- Anulare oricand, poti pleca inapoi
- Proprietate completa pastrata
Patru motive pentru care LIR-ul tau curent a devenit o problema
LIR-ul se inchide. Statutul de membru RIPE NCC este un cost recurent; LIR-urile mai mici care raman fara clienti isi inchid uneori operatiunile. Daca sponsorul tau se inchide fara sa aranjeze un transfer, resursele tale pot ajunge in limb.
Pretul a crescut nejustificat. Taxele anuale de sponsorizare de 1000-2000 lei per resursa sunt comune. Daca platesti mult peste pretul pietei pentru munca administrativa pe care LIR-ul tau curent a automatizat-o, este timpul sa compari din nou.
Neglijenta operationala. Actualizari intarziate ale ROA RPKI, rotatii abuse-c ignorate, raspunsuri tardive la audit sau absenta suportului in timpul urgentelor de rutare - oricare dintre acestea semnaleaza ca LIR-ul tau nu investeste in infrastructura de care depind resursele tale.
Concentrare strategica. Deja rulezi servicii pe infrastructura DreamServer sau faci peering cu noi la DSIX, iar consolidarea administrarii LIR simplifica amprenta de furnizori si bucla de suport.
- Numarul ASN si fiecare prefix IPv4 sau IPv6 raman identice
- Anunturile tale BGP nu se opresc niciodata
- Admin-c, tech-c si proprietatea legala raman la tine
- ROA-urile RPKI raman publicate fara intrerupere
- Relatiile de peering existente raman pe loc
mnt-by, org si de sponsorizare la RIPE se schimba. Routerele si peer-ii tai nu observa nimic.Panoul de administrare RIPE ASN, click pe fiecare tab
Din momentul in care ASN-ul tau e activ, panoul acesta de self-service e al tau. Fiecare tab de mai jos chiar comuta, exact ca cel real. Da click pe AS-SET, Details & Contacts, IRR Policy, BGP Config sau orice alt tab ca sa vezi ce administrezi din contul tau.
Route Objects (IRR)
Register the prefixes you announce in the RIPE routing registry. Upstreams and IX route servers use these to validate your BGP announcements.
Active Route Objects
| Prefix | Type | Origin | Status | |
|---|---|---|---|---|
| 212.81.56.0/24 | route | AS57050 | active | Delete |
| 2a10:fa80:12::/48 | route6 | AS57050 | active | Delete |
AS-SET Management
An AS-SET groups your ASN with your downstream customers. Upstreams build prefix filters from it. It is always created under your own ASN.
Details & Contacts
Live in RIPEThe fields currently on your aut-num. Edit and Save to change them. admin-c and tech-c must point to a person or role that already exists.
Abuse contact (abuse-c)
Your Contacts
| Handle | Created | |
|---|---|---|
| JD1503-RIPE | 2026-06-14 10:22 | Use Edit Delete |
BGP Visibility & Announced Prefixes
Live data from RIPE RIS route collectors. Check whether your ASN is seen in the global routing table.
Check BGP VisibilityRouting Policy
Live in RIPEThe policy currently published for AS57050. Edit the RPSL statements, one per line, and Save to update it in the RIPE DB.
Generate policy lines from peers
Build RPSL import/export from a peer list, then insert it straight into the boxes above.
BGP Configuration Generator
Ready-to-paste BGP configuration for your router platform, built from your peer list.
# BIRD 2.x BGP Configuration for AS57050
protocol bgp upstream_dreamserver {
local as 57050;
neighbor 212.81.56.1 as 174; # Replace IP
ipv4 {
import all;
export filter export_own;
};
}! FRRouting BGP Configuration for AS57050 router bgp 57050 bgp router-id 212.81.56.10 neighbor 212.81.56.1 remote-as 174 neighbor 212.81.56.1 description DreamServer-upstream ! address-family ipv4 unicast network 212.81.56.0/24 exit-address-family exit
# MikroTik RouterOS v7 BGP for AS57050
/routing bgp template
add name=default as=57050 router-id=212.81.56.10
/routing bgp connection
add name=upstream remote.as=174 \
remote.address=212.81.56.1 \
local.role=customer templates=default!! Cisco IOS-XR BGP for AS57050 router bgp 57050 bgp router-id 212.81.56.10 neighbor 212.81.56.1 remote-as 174 address-family ipv4 unicast route-policy ACCEPT-ALL in route-policy EXPORT-OWN out ! !
RIPE WHOIS Lookup
Look up your own RIPE DB objects. Queries are restricted to your ASN and related objects.
aut-num: AS57050 as-name: EXAMPLE-NET org: ORG-EX12-RIPE import: from AS174 accept ANY export: to AS174 announce AS-SELF admin-c: JD1503-RIPE tech-c: JD1503-RIPE status: ASSIGNED mnt-by: RIPE-NCC-END-MNT mnt-by: DreamServer mnt-by: EXAMPLE-MNT source: RIPE
Preview read-only. Toate numele, handle-urile si numerele afisate sunt fictive. Panoul tau real e populat live din baza de date RIPE.
Ce administrezi din panou
Din momentul in care ASN-ul e livrat, fiecare obiect de care are nevoie e editabil din contul tau DreamServer. Fara logari in RIPE Portal, fara tichete pe email ca sa schimbi un contact sau un route object.
Route Objects (IRR)
Creezi sau stergi obiecte route si route6 pentru fiecare prefix pe care il anunti, ca upstream-urile si route serverele de la IX sa-ti accepte anunturile BGP. Originea AS e completata automat.
AS-SET
Construiesti si intretii customer cone-ul tau (AS57050:AS-CUSTOMERS) ca providerii sa-ti filtreze downstream-urile. E mereu sub propriul ASN, deci nu poti atinge al altcuiva.
Details & Contacts
Editezi descr, admin-c si tech-c pe aut-num, vezi abuse-c, si creezi sau administrezi contacte RIPE (person), cu verificare de existenta ca un handle sa nu pice in tacere.
BGP Status
Vizibilitate live de la route collectorii RIPE RIS: cati peers iti vad ASN-ul pe IPv4 si IPv6, ce prefixe sunt anuntate, si cand a fost vazut prima si ultima oara.
IRR Policy
Citesti si editezi politica import/export/mp-import/mp-export publicata pe aut-num, sau generezi RPSL-ul dintr-o lista simpla de peers si il bagi direct in casete.
BGP Config
Configuratie BGP gata de copy-paste pentru BIRD, FRRouting, MikroTik RouterOS si Cisco IOS-XR, generata din lista ta de peers ca prima sesiune sa dureze minute.
WHOIS
Cauti ASN-ul tau si obiectele conexe direct din baza de date RIPE, fara sa pleci din panou sau sa inveti linia de comanda whois.
Panoul de Administrare RIPE IPv4 si IPv6, Apasa Pe Fiecare Tab
Din momentul in care prefixul tau IPv4 sau IPv6 trece sub sponsorizarea noastra, acest panou self-service devine al tau. Fiecare tab de mai jos comuta efectiv, exact ca cel real. Apasa ROA / RPKI, Reverse DNS, inetnum / inet6num, WHOIS sau orice alt tab ca sa vezi interfata pe care o administrezi pentru fiecare prefix sponsorizat, IPv4 sau IPv6.
| Prefix | Origin AS | Status | Creat | Actiuni |
|---|---|---|---|---|
| 2a10:fa80:aaaa::/40 | AS213123 | Active | 2026-04-08 10:42 | VeziSterge |
| 2a10:fa80:aaaa:1000::/44 | AS213123 | Active | 2026-04-12 15:08 | VeziSterge |
| 185.72.40.0/24 | AS213123 | Active | 2026-04-09 09:15 | VeziSterge |
| Prefix | Max Length | ASN | Status | Creat | Actiuni |
|---|---|---|---|---|---|
| 2a10:fa80:aaaa::/40 | /48 | AS213123 | Active | 2026-04-08 10:44 | Sterge |
| 2a10:fa80:aaaa:1000::/44 | /48 | AS213123 | Active | 2026-04-12 15:10 | Sterge |
| 2a10:fa80:aaaa::/40 | /40 | AS65001 | Active | 2026-04-14 09:21 | Sterge |
| 185.72.40.0/24 | /24 | AS213123 | Active | 2026-04-09 09:17 | Sterge |
| Zona | Nameservere | Status | Actiuni |
|---|---|---|---|
| a.a.a.a.0.4.b.6.b.0.a.2.ip6.arpa | ns1.example.comns2.example.com | Active | EditeazaSterge |
| 40.72.185.in-addr.arpa | ns1.example.comns2.example.com | Active | EditeazaSterge |
IPv6 inet6num (2a10:fa80:aaaa::/40)
| inet6num | 2a10:fa80:aaaa::/40 |
| netname | EXAMPLE-NET |
| descr | Alocare IPv6 Example Ltd. |
| country | RO |
| org | ORG-EXML1-RIPE |
| admin-c | JD1234-RIPE |
| tech-c | JD1234-RIPE |
| status | ALLOCATED-BY-LIR |
| mnt-by | MNT-EXAMPLE |
| source | RIPE |
IPv4 inetnum (185.72.40.0/24)
| inetnum | 185.72.40.0 - 185.72.40.255 |
| netname | EXAMPLE-NET |
| descr | Asignare PA IPv4 Example Ltd. |
| country | RO |
| org | ORG-EXML1-RIPE |
| admin-c | JD1234-RIPE |
| tech-c | JD1234-RIPE |
| status | ASSIGNED PA |
| mnt-by | MNT-EXAMPLE |
| source | RIPE |
Actualizeaza Campuri
| Tip | Cheie | Handle | Status | Actiuni |
|---|---|---|---|---|
| inet6num | 2a10:fa80:aaaa::/40 | EXAMPLE-NET | Active | VeziRIPE → |
| inetnum | 185.72.40.0/24 | EXAMPLE-NET | Active | VeziRIPE → |
| organisation | ORG-EXML1-RIPE | Example Ltd. | Active | VeziRIPE → |
| mntner | MNT-EXAMPLE | MNT-EXAMPLE | Active | VeziRIPE → |
| role | JD1234-RIPE | J. Doe | Active | VeziRIPE → |
| route6 | 2a10:fa80:aaaa::/40 | AS213123 | Active | VeziRIPE → |
| route6 | 2a10:fa80:aaaa:1000::/44 | AS213123 | Active | VeziRIPE → |
| route | 185.72.40.0/24 | AS213123 | Active | VeziRIPE → |
| Subnet | Eticheta | Descriere | Status | Actiuni |
|---|---|---|---|---|
| 2a10:fa80:aaaa:0::/48 | Servere Web | Cluster web public | Used | EditeazaSterge |
| 2a10:fa80:aaaa:1::/48 | SMTP / IMAP / MX | Used | EditeazaSterge | |
| 2a10:fa80:aaaa:100::/56 | Staging | Rezervat pentru mediul de staging | Reserved | EditeazaSterge |
# Primele 5 din 256 subnet-uri 2a10:fa80:aaaa:0000::/48 → first: 2a10:fa80:aaaa:: last: 2a10:fa80:aaaa:ffff:ffff:ffff:ffff:ffff 2a10:fa80:aaaa:0001::/48 → first: 2a10:fa80:aaaa:1:: last: 2a10:fa80:aaaa:1:ffff:ffff:ffff:ffff:ffff 2a10:fa80:aaaa:0002::/48 → first: 2a10:fa80:aaaa:2:: last: 2a10:fa80:aaaa:2:ffff:ffff:ffff:ffff:ffff 2a10:fa80:aaaa:0003::/48 → first: 2a10:fa80:aaaa:3:: last: 2a10:fa80:aaaa:3:ffff:ffff:ffff:ffff:ffff 2a10:fa80:aaaa:0004::/48 → first: 2a10:fa80:aaaa:4:: last: 2a10:fa80:aaaa:4:ffff:ffff:ffff:ffff:ffff ... inca 251
# BIRD 2.x IPv6 BGP catre AS6939 router id 213.214.215.216; protocol static { ipv6 { table master6; }; route 2a10:fa80:aaaa::/40 blackhole; } protocol bgp peer_he6 { local as 213123; neighbor 2001:470:1f0a::1 as 6939; ipv6 { import filter { reject; }; export filter { if net = 2a10:fa80:aaaa::/40 then accept; reject; }; }; }
! FRRouting IPv6 BGP router bgp 213123 bgp router-id 213.214.215.216 no bgp default ipv4-unicast neighbor 2001:470:1f0a::1 remote-as 6939 ! address-family ipv6 unicast network 2a10:fa80:aaaa::/40 neighbor 2001:470:1f0a::1 activate neighbor 2001:470:1f0a::1 prefix-list PL-OUT out neighbor 2001:470:1f0a::1 prefix-list PL-IN in exit-address-family ! ipv6 prefix-list PL-OUT seq 5 permit 2a10:fa80:aaaa::/40 ipv6 prefix-list PL-IN seq 5 deny any
# MikroTik RouterOS 7.x /routing bgp template add name=peer-he6 as=213123 router-id=213.214.215.216 \ output.filter-chain=bgp-out input.filter-chain=bgp-in /routing bgp connection add name=he6 template=peer-he6 remote.as=6939 \ remote.address=2001:470:1f0a::1 /routing filter rule add chain=bgp-out rule="if (dst in 2a10:fa80:aaaa::/40) { accept }" add chain=bgp-out rule="reject" add chain=bgp-in rule="reject"
! Cisco IOS / IOS-XE router bgp 213123 bgp router-id 213.214.215.216 no bgp default ipv4-unicast neighbor 2001:470:1f0a::1 remote-as 6939 address-family ipv6 network 2a10:fa80:aaaa::/40 neighbor 2001:470:1f0a::1 activate neighbor 2001:470:1f0a::1 prefix-list PL-OUT out neighbor 2001:470:1f0a::1 prefix-list PL-IN in exit-address-family ! ipv6 prefix-list PL-OUT seq 5 permit 2a10:fa80:aaaa::/40 ipv6 prefix-list PL-IN seq 5 deny any
% Informatii legate de '2a10:fa80:aaaa::/40' inet6num: 2a10:fa80:aaaa::/40 netname: EXAMPLE-NET descr: Alocare IPv6 Example Ltd. country: RO org: ORG-EXML1-RIPE admin-c: JD1234-RIPE tech-c: JD1234-RIPE status: ALLOCATED-BY-LIR mnt-by: ro-dreamserver-1-mnt mnt-by: MNT-EXAMPLE created: 2026-04-08T10:41:22Z last-modified: 2026-04-08T10:41:22Z source: RIPE route6: 2a10:fa80:aaaa::/40 origin: AS213123 mnt-by: MNT-EXAMPLE source: RIPE
| Data | Actiune | Obiect | Rezultat | Detalii |
|---|---|---|---|---|
| 2026-04-14 09:21 | create_roa | roa 2a10:fa80:aaaa::/40 | ✓ OK | AS65001 /40 |
| 2026-04-12 15:10 | create_roa | roa 2a10:fa80:aaaa:1000::/44 | ✓ OK | AS213123 /48 |
| 2026-04-12 15:08 | create_route6 | route6 2a10:fa80:aaaa:1000::/44 | ✓ OK | origin AS213123 |
| 2026-04-09 09:17 | create_roa | roa 185.72.40.0/24 | ✓ OK | AS213123 /24 |
| 2026-04-09 09:15 | create_route | route 185.72.40.0/24 | ✓ OK | origin AS213123 |
| 2026-04-09 11:02 | update_rdns | rdns a.a.a.a.0.4.b.6.b.0.a.2.ip6.arpa | ✓ OK | ns1, ns2.example.com |
| 2026-04-08 10:44 | create_roa | roa 2a10:fa80:aaaa::/40 | ✓ OK | AS213123 /48 |
| 2026-04-08 10:42 | create_route6 | route6 2a10:fa80:aaaa::/40 | ✓ OK | origin AS213123 |
| 2026-04-08 10:41 | provision | inet6num 2a10:fa80:aaaa::/40 | ✓ OK | ALLOCATED-BY-LIR, mnt-by MNT-EXAMPLE |
Plecarea de la LIR-ul curent nu trebuie sa doara
Trimite-ne lista de resurse si pregatim planul de migrare in aceeasi zi.
