Re: [AfrIPv6-Discuss] Business Case for Moving to IPV6

2020-02-20 Thread Nishal Goburdhan
On 19 Feb 2020, at 13:35, JORDI PALET MARTINEZ via AfrIPv6-Discuss 
wrote:



Hi Collin,
IPv4 addresses are no longer available. If you want to keep networks 
growing, you have basically two choices:
Buy IPv4 addresses (that come in part from those that have already 
deployed IPv6) and maybe CGNs. This is a short-term solution. You will 
be behind the rest of the world.

Deploy IPv6. This is the only long-term solution.

So the business case is: Do you want to sustain your grow, and 
consequently the viability of your network or business?



colin,

to add to what jordi has just told you ..
how much do you think you are currently paying for an ip address, to be 
able to provide your users with service  (big hint:  go do the math, 
it’s necessary, and important).  then, how much do you think you’ll 
be paying in the future, once afrinic can no longer give you any more 
address space?
you don’t need to guess an answer to the second part;  here’s one 
view:  https://auctions.ipv4.global/prior-sales


now ask yourself, what’s going to be cheaper - consistently - for you? 
 feel free to look around and see what the other address brokers say.  
i’m sure the numbers will be enlightening.


if you can’t see the business case here, then that is good news for 
your competitors.


-n.

___
AfrIPv6-Discuss mailing list
AfrIPv6-Discuss@afrinic.net
https://lists.afrinic.net/mailman/listinfo/afripv6-discuss


Re: [AfrIPv6-Discuss] SAFNOG-4/EANOG/tzNOG: 4 Days To Go!

2018-09-20 Thread Nishal Goburdhan
On 20 Sep 2018, at 9:14, Stephen Honlue wrote:

> Check the link, it's not responding for me.

https://downforeveryoneorjustme.com/safnog.org

it’s you.
:-)

—n.

___
AfrIPv6-Discuss mailing list
AfrIPv6-Discuss@afrinic.net
https://lists.afrinic.net/mailman/listinfo/afripv6-discuss


Re: [AfrIPv6-Discuss] Is Your IPv6 Space Still Unannounced? Here’s your chance to fix it!

2018-03-26 Thread Nishal Goburdhan

On 26 Mar 2018, at 10:07, Bruno Stevant wrote:

* L'automatisation du déploiement devrait aussi être pris en compte 
et
encore, le modelage et la transportation de modèle personnalisable. 
Ainsi,
Ansible et Docker avec VirtualBox et peut-être GNS3, sans chercher 
à
influencer quoi que ce soit sur la structure de vos bancs d'essai 
actuels (Banc

d'essai IPv6 - AFRINIC Training

| learn.afrinic.net/fr/evenements/book-ipv6-testbed ).



Bonjour,

Sur ce point, je tiens à vous informer de la disponibilité d'un 
projet

initié lors d'un hackathon RIPE-NCC :
https://github.com/inognet/pocketinternet
Ce projet a notamment été prévu pour faire un mini-lab IPv6/BGP où 
les

hôtes et routeurs sont virtualisés sous forme de container.



mukom is on a plane somewhere, and he will likely feedback in more 
detail when he is on the ground, but the idea is not so much to have 
this work in a *lab*, but to make it work on your actual network.


lab sims are great;  if you want to get that done, go ahead :-)
but from what he explained to me, the idea behind this “deployathon” 
is to have network operators take that final step to actually get their 
network space announced, and to turn up, at least one live service on 
ipv6.


that’s why the entry criteria for this this workshop, are different 
from the regular IPv6 workshops that afrinic runs.


—n.

___
AfrIPv6-Discuss mailing list
AfrIPv6-Discuss@afrinic.net
https://lists.afrinic.net/mailman/listinfo/afripv6-discuss


Re: [AfrIPv6-Discuss] IPv6 packets from Chad

2018-03-05 Thread Nishal Goburdhan
On 5 Mar 2018, at 13:38, Willy MANGA wrote:

> Hello,
> just to let you know that, we, as an end-user, have requested from our
> ISP to provide us with  an IPv6 prefix for our office in Chad.
> It took them 1 month to work on it and assign us a /56
> (2a02:6600:8001:200::/56 ) .
> We would have been more than happy if a local provider was able to
> provide us a good connectivity and IPv6. However , it's not (yet)
> possible in Chad.

hrm.
what’s interesting, is that this isn’t out of the afrinic ipv6 pools ..
not that this is a problem.  but odd anyway,

—n.

___
AfrIPv6-Discuss mailing list
AfrIPv6-Discuss@afrinic.net
https://lists.afrinic.net/mailman/listinfo/afripv6-discuss


[AfrIPv6-Discuss] Fwd: [IOZ.tech] if you weren't an early adopter of IPv6 ..

2016-10-03 Thread Nishal Goburdhan
Forwarded message:

> From: Nishal Goburdhan <nis...@controlfreak.co.za>
> To: IOZ Technical Discussion <t...@internet.org.za>
> Subject: [IOZ.tech] if you weren't an early adopter of IPv6 ..
> Date: Mon, 03 Oct 2016 11:22:14 +0200
>
> .. you can still win with #IPv10.
>
> https://twitter.com/hashtag/IPv10?src=hash
> https://twitter.com/The_Road_Series
> http://internetprotocolv10.blogspot.com
>
> we now return you to you regular monday morning’s programming ..
>
> —n.
> ___
> tech mailing list
> t...@internet.org.za
> http://lists.internet.org.za/mailman/listinfo/tech

___
AfrIPv6-Discuss mailing list
AfrIPv6-Discuss@afrinic.net
https://lists.afrinic.net/mailman/listinfo/afripv6-discuss


Re: [AfrIPv6-Discuss] AfrIPv6-Discuss DHCPv6 Server Declaration

2016-06-14 Thread Nishal Goburdhan

On 14 Jun 2016, at 10:43, DICK,  L. (MR.) wrote:


Morning

DHCHp6 Server only recognises the subnet declaration of same network 
with
the Ethernet Interface of the server. How do I make DHCP6 to issue 
Ipv6

addresses of other VLANS or subnets as well? Please assist me. Thank
you



take it back a step;  you have some infrastructure for your network 
(running ipv4) now, right?

how do you solve your current dhcp issues for ipv4?

as stephen and john said, either your dhcp server needs to be connected 
to each network subnet (which is potentially wasteful, and unnecessarily 
complex), or you need to configure a dhcp relay agent on the network 
(router) devices in the middle, so that they know where to send dhcp 
requests to.


consider:

N1_R1___
|
N2_R2___|
|R4S
N3_R3___|


so, take the simple picture above;  you have three networks (N1-3) and a 
dhcp server (S) somewhere on your network, separated by some routing 
devices (R).   server S is not on the same logical subnet (ie. not in 
networks 1-3).  on the intermediate routers (R1-3) you’d have to 
configure a dhcp-relay agent, pointing to S, for the interfaces that 
connect to N1-3.


your favourite search engine will help you find the specific commands 
for your hardware, if you search for “dhcp relay agent”.
incidentally, you’d have to do the same thing in IPv4 as well.  so 
this is not a dhcp6 specific issue.


—n.

___
AfrIPv6-Discuss mailing list
AfrIPv6-Discuss@afrinic.net
https://lists.afrinic.net/mailman/listinfo/afripv6-discuss


Re: [AfrIPv6-Discuss] Call for contributions for IPv6 Deployment Guidelines for Africa region

2016-01-22 Thread Nishal Goburdhan

On 22 Jan 2016, at 10:37, Mukom Akong T. wrote:

Before we put out training material on our training website, it has to 
meet
criterial that the team has agree upon and for now that's not the 
case.


whilst i may respect your adherence to quality control, i’m in general 
agreement that half is better than zero …


(this is equally true for the arabic material that was translated by 
volunteers, or for the portuguese ipv6 material that nic.br offered, 
which used to be on the afrinic site, before the site was re-skinned.  i 
am sure you can put a simple “disclaimer” about the publications, to 
show that you haven’t QA’d them, eh?).



Our certification initiatives  is about a standardised 
test/examination -
which is still one of the best ways to reinforce learning. We've 
gotten
lots of requests from our delegates for a "Certificate of Attendance" 
(we
currently don't) but when we launch our certification platform, we'll 
be

able to give people who need that something with global recognition.


i’ve said my piece on this, and, to be clear, i wasn’t referring 
specifically to your certification plans (which i know nothing about), 
but to those unscrupulous ones that see this as an revenue source.  
perhaps you’ll be a welcome change.


—n.

___
AfrIPv6-Discuss mailing list
AfrIPv6-Discuss@afrinic.net
https://lists.afrinic.net/mailman/listinfo/afripv6-discuss