Open moozer opened 5 years ago
@kramse This is settled already, right?
Could you add a link or simlar with the ip range and such?
@kramse nice.
I have put it on the noc pages for easy access: https://bornhack.gitlab.io/noc/2019,/ip,/ripe/2018/07/07/IP-adresses.html
I read it as if we have permanent IPv6 addresses. Is that correct?
We have the resources needed, see below.
Need to do route-objects. RPKI?
RIPE NCC assigned the following Autonomous System Number:
AS208647 to BornHack IVS
The RIPE Database shows the following information:
aut-num: AS208647 as-name: BORNHACK org: ORG-BI77-RIPE sponsoring-org: ORG-ZA135-RIPE import: from AS57860 accept ANY export: to AS57860 announce AS208647 import: from AS24800 accept ANY export: to AS24800 announce AS208647 admin-c: HK5541-RIPE tech-c: HK5541-RIPE status: ASSIGNED mnt-by: RIPE-NCC-END-MNT mnt-by: dk-zencurity-1-mnt created: 2019-06-27T15:13:39Z last-modified: 2019-06-27T15:13:39Z source: RIPE 2001:678:9ec::/48 to BornHack IVS
The RIPE database shows the following information:
inet6num: 2001:678:9ec::/48 netname: DK-ZENCURITY-20190627 country: DK org: ORG-BI77-RIPE sponsoring-org: ORG-ZA135-RIPE admin-c: HK5541-RIPE tech-c: HK5541-RIPE status: ASSIGNED PI mnt-by: RIPE-NCC-END-MNT mnt-by: dk-zencurity-1-mnt created: 2019-06-27T15:15:49Z last-modified: 2019-06-27T15:15:49Z source: RIPE
Those are ours now! and a temp IPv4 space: 151.216.0.0/20 to BornHack IVS
The prefix will be returned to the RIPE NCC on 2019-08-25.
The RIPE database shows the following information:
inetnum: 151.216.0.0 - 151.216.15.255 netname: DK-ZENCURITY-20190627 country: DK org: ORG-BI77-RIPE sponsoring-org: ORG-ZA135-RIPE admin-c: HK5541-RIPE tech-c: HK5541-RIPE status: ASSIGNED PI remarks: Temporary assignment (start date: 2019/07/18, end date: 2019/08/25 and duration 38 days) mnt-by: dk-zencurity-1-mnt mnt-by: RIPE-NCC-END-MNT created: 2019-06-27T15:00:12Z last-modified: 2019-06-27T15:00:12Z source: RIPE