[Mispa-management-l] ipv6 interface - MIX router - RE: MTL - NITEL - SKYBAND - route server config - RE: ROUTE OF 102.176.250.0 /24
Dr P Nyirenda
paulos at sdnp.org.mw
Tue Jun 4 17:19:45 CAT 2019
On 4 Jun 2019 at 9:23, Clement Ngoma wrote:
> Dr,
>
> Yes we can now ping as shown below.
>
> run ping 2001:43f8:380::2 rapid count 10
> PING6(56=40+8+8 bytes) 2001:43f8:380::35 --> 2001:43f8:380::2
> !!!!!!!!!!
> --- 2001:43f8:380::2 ping6 statistics ---
> 10 packets transmitted, 10 packets received, 0% packet loss
> round-trip min/avg/max/std-dev = 0.639/0.744/0.955/0.106 ms
Thank you for the confirmation, I can also ping the Skyband IPv6 interface from the route
server as follows;
route-server-01>ping 2001:43F8:380::35
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 2001:43F8:380::35, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/4 ms
route-server-01>
I have noted with concern that Skyband is using IPv6 addresses from what looks like your
upstream Internet service provider such as for your DNS servers:
proxy2.africa-online.net. 2990 IN AAAA 2c0f:fd50:0:20::29be:5dc6
Why do you not just go to AFRINIC and get and use your own IPv6 address block?
If you have IPv4 from AFRINIC then they used to allocate IPv6 blocks for free.
> The good thing is the interface can have multiple IPv6 addresses without a problem, so the
> eui-64 can remain on the interface.
I will leave it out for now unless someone specifically asks for it.
> I should have the IPv6 BGP setting ready before end of the week.
I look forward to this and hope I can ideed get it sooner.
Regards,
Paulos
======================
Dr Paulos B Nyirenda
NIC.MW & .mw ccTLD
http://www.registrar.mw
> Kind regards,
>
> Clement Ngoma
> Skyband Corp.
>
>
>
> From: Dr P Nyirenda <paulos at sdnp.org.mw>
> Sent: Tuesday, June 4, 2019 11:05 AM
> To: Clement Ngoma <clement at skyband.mw>; mispa-management-l at sdnp.org.mw
> Cc: mispa-chair at mix.mw; Maloto Nyirenda <Maloto.Nyirenda at MTL.mw>; Limbika Kanjadza
> <limbika at skyband.mw>
> Subject: ipv6 interface - MIX router - RE: MTL - NITEL - SKYBAND - route server config - RE:
> ROUTE OF 102.176.250.0 /24
>
> On 4 Jun 2019 at 7:06, Clement Ngoma wrote:
>
> > Dr,
> >
> > Yes this IP block 105.234.0.0/16 can be removed from the our prefix-list as it an old setting.
>
> Great, I have taken this out of the prefix-list to show a new config as here attached.
>
> > I have noticed the attached config interface g0/1 has an IP "ipv6
> > address 2001:43F8:380::/64 eui-64" it's not the best way of doing this
> > as we will not be able to know the IP address of the interface.
>
> I am glad to see that this has provoked this response. Under cisco systems this is one way of
> assigning an IP address that is well documented.
>
> I did see that it gives the interface a longer IPv6 address but I decided to give it a go anyway ... in
> this testing pahse.
>
> > My suggestion is "ipv6 address 2001:43F8:380::2/64" so we can ping the interface currently it's
> not pingable.
>
> As you can see here below, you can ping the interface with this address
> 2001:43F8:380:0:7EAD:74FF:FE2C:9841 which is what that command gives to the interface and
> it works just fine, other than it is not intuitively identifiable ... but no IPv6 address can claim to be
> so.
>
> Using "ipv6 address 2001:43F8:380::2/64" as you have suggested also works, is less fun :-) but I
> guess gives a more intuitive address as you can see in the attached config now in place. And as
> you can also see here below you can also ping the interface using this config.
>
> If you prefer the config this way then I will leave it like that even though both formats are usable.
>
> Now, can you ping the interface on the IPv6 address 2001:43F8:380::2/64 ?
>
> Can you suggest config lines to wake up IPv6 BGP peering on the route server ?
>
> Regards,
>
> Paulos
> ======================
> Dr Paulos B Nyirenda
> NIC.MW & .mw ccTLD
> http://www.registrar.mw
>
>
> route-server-01>
> route-server-01>
> route-server-01>ping ipv6 2001:43F8:380:0:7EAD:74FF:FE2C:9841
> Type escape sequence to abort.
> Sending 5, 100-byte ICMP Echos to 2001:43F8:380:0:7EAD:74FF:FE2C:9841, timeout is 2
> seconds:
> !!!!!
> Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/1 ms
> route-server-01>
>
> !
> interface GigabitEthernet0/1
> description Transit
> ip address 196.223.27.2 255.255.255.0
> no ip redirects
> no ip proxy-arp
> duplex auto
> speed auto
> ipv6 address 2001:43F8:380::2/64
> ipv6 nd ra suppress
> no keepalive
> no cdp enable
> no mop enabled
> !
>
> route-server-01>sh ipv6 interface
> GigabitEthernet0/1 is up, line protocol is up
> IPv6 is enabled, link-local address is FE80::7EAD:74FF:FE2C:9841
> No Virtual link-local address(es):
> Description: Transit
> Global unicast address(es):
> 2001:43F8:380::2, subnet is 2001:43F8:380::/64
> Joined group address(es):
> FF02::1
> FF02::2
> FF02::1:FF00:2
> FF02::1:FF2C:9841
> MTU is 1500 bytes
> ICMP error messages limited to one every 100 milliseconds
> ICMP redirects are enabled
> ICMP unreachables are sent
> ND DAD is enabled, number of DAD attempts: 1
> ND reachable time is 30000 milliseconds (using 30000)
> ND advertised reachable time is 0 (unspecified)
> ND advertised retransmit interval is 0 (unspecified)
> ND router advertisements are sent every 200 seconds
> ND router advertisements live for 1800 seconds
> ND advertised default router preference is Medium
> ND RAs are suppressed (periodic)
> Hosts use stateless autoconfig for addresses.
> route-server-01>
>
>
>
> route-server-01#
> route-server-01#ping ipv6 2001:43F8:380::2
> Type escape sequence to abort.
> Sending 5, 100-byte ICMP Echos to 2001:43F8:380::2, timeout is 2 seconds:
> !!!!!
> Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/1 ms
> route-server-01#
>
> > Kind regards,
> >
> > Clement Ngoma
> > Skyband Corp.
> >
> >
> >
> >
> > -----Original Message-----
> > From: Dr P Nyirenda <paulos at sdnp.org.mw>
> > Sent: Friday, May 31, 2019 7:23 PM
> > To: Rajab R. Hussein <Rajab.Hussein at MTL.mw>; mispa-management-l at sdnp.org.mw
> > Cc: mispa-chair at mix.mw; Maloto Nyirenda <Maloto.Nyirenda at MTL.mw>; Clement Ngoma
> <clement at skyband.mw>; Limbika Kanjadza <limbika at skyband.mw>
> > Subject: MTL - NITEL - SKYBAND - route server config - RE: ROUTE OF 102.176.250.0 /24
> >
> >
> > Rajab: MTL : I have updated the route server config as you requested, see attached.
> >
> > T.Jumbe: NITEL: I have removed the MALSWITCH prefix as discussed at the MMC Meeting.
> > This leaves the prefix 41.79.88.0/22 on Simbanet as here attached
> >
> > Clement: SKYBAND: It was observed at the Mispa Management Committee Meeting on 30 May
> 2019 that the prefix 105.234.0.0/16 that appears on the Skyband prefix-list also appears on the
> Airtel prefix-list as shown in the attached config and a recommendation was hence made to
> remove it from Skyband list. Please review the config and the recommendation and give me your
> direction.
> >
> > IPv6: ALL: You will all note on the attached config that I have now assigned an IPv6 address
> > 2001:43F8:380::2/64 on the interface GigabitEthernet0/1 of the route server and you will see the
> IPv6 interface config towards the bottom of the attached file that shows the route server config,
> the BGP routes and the IPv6 interface.
> >
> > It would be great if you can activate IPv6 on your routers and give your interface the IPv6
> address on the 2001:43F8:380::/64 subnet which ends with the last quartet on your IPv4 peering
> interface address. So for example if your IPv4 peering address is 196.223.27.40/24 then your
> IPv6 address is 2001:43F8:380::40/64
> >
> > Once done then please check if you can ping the IPv6 interface on the route server and let me
> know.
> >
> > Regards,
> >
> > Paulos
> > ======================
> > Dr Paulos B Nyirenda
> > NIC.MW & .mw ccTLD
> > http://www.registrar.mw
> >
> >
> >
> > On 31 May 2019 at 13:51, Rajab R. Hussein wrote:
> >
> > > Dear Dr Paulos,
> > >
> > > Find attached how the config should be under MTL lines.
> > >
> > > Regards,
> > >
> > > Rajab
> > >
> > > -----Original Message-----
> > > From: Dr P Nyirenda [mailto:paulos at sdnp.org.mw]
> > > Sent: Friday, May 31, 2019 2:35 PM
> > > To: Rajab R. Hussein
> > > Cc: mispa-chair at mix.mw; Maloto Nyirenda
> > > Subject: Re: ROUTE OF 102.176.250.0 /24
> > >
> > > On 30 May 2019 at 11:31, Rajab R. Hussein wrote:
> > >
> > > >
> > > > Dear Dr. Paulos,
> > > >
> > > > We request to have the ip address below advertised in the route server :
> > > >
> > > > 102.176.250.0 /24
> > >
> > > As we have normally done on the MIX, please send the exact config lines that I should use to
> act on this request for you.
> > >
> > > We do this to have a common understanding of the config as the config evolves.
> > >
> > > To assist with this config, I have here attached the current cisco route server config where
> your lines will fit.
> > >
> > > I will take receipt of the config lines as confirmation from you for this to be done for your MTL
> peering configuration at the MIX.
> > >
> > > Regards,
> > >
> > > PC
> > > ======================================
> > > Dr Paulos B Nyirenda
> > > Malawi SDNP PC: http://www.sdnp.org.mw NIC.MW & .mw ccTLD
> > > http://www.registrar.mw
> > > Chair: MISPA http://www.mispa.org.mw
> > >
> > >
> > > >
> > > >
> > > > Best regards,
> > > >
> > > >
> > > > Rajab
> > > >
> > > >
> > > >
> > > >
> > > > --
> > > > This message has been scanned for viruses and dangerous content by
> > > > MailScanner, and is believed to be clean.
> > >
> > >
> > >
> > >
> > > ---
> > > This email has been checked for viruses by AVG.
> > > https://www.avg.com
> > >
> > > --
> > > This message has been scanned for viruses and dangerous content by
> > > MailScanner, and is believed to be clean.
> > >
> > >
> > > --
> > > This message has been scanned for viruses and dangerous content by
> > > MailScanner, and is believed to be clean.
> > >
> > >
> >
> >
> >
> > --
> > This message has been scanned for viruses and dangerous content by MailScanner, and is
> believed to be clean.
> >
>
>
>
>
> AVG logo
> This email has been checked for viruses by AVG antivirus software.
> www.avg.com
>
>
>
>
> --
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
More information about the Mispa-management-l
mailing list