SlideShare uma empresa Scribd logo
1 de 32
Baixar para ler offline
31
Get more from your IPv4 resources
Presented By:
Shuvodip Roy
Senior Systems
Engineer
Amber IT Limited
sdroy@live.com
Preface
As IPv4 exhausted, RIR’s (Regional Internet Registry) are not getting IPv4 to
be allocated or the block size now become very limited. Alternative and
the next version IPv6 is rolled out. But, demand of IPv4 is still growing.
One of the big reason is globally still the maximum number of sites yet
only available via IPv4.
In the context of Bangladesh, we still need to connect a large numbers of
subscribers with Internet. Sufficient IPv4 addresses are not available. In
this circumstance, we can use RFC3021 Using 31-Bit Prefixes on IPv4
Point-to-Point Links in large scale.
In a ISP or else, 80% or more are actually “Single Home Point-to-Point
Links”. Using the RFC3021, we will be able to connect double numbers of
links than current times using existing IPv4 resources.
This presentation is all about that.
Presented By: Shuvodip Roy in bdNOG 13
ONLINE
2
Disclaimer
* Disclaimer: Although RFC3021 released in December, 2000. Still many
vendors or devices not support it. In this presentation, will try to cover up
the configuration of those which is commonly use in Bangladesh.
The configuration will differ vendor to vendor as well as device to device.
Presented By: Shuvodip Roy in bdNOG 13
ONLINE
3
Exhaustion
All 5 RIR's have either limited supplies or have run out of available IPv4
addresses. ARIN and the RIPE NCC ran out of their available supply in 2015
and 2019 respectively. In APNIC, LACNIC and AFRINIC rationing supplies
according to the community policies.
APNIC’s IPv4 pool to run out by creating policies to limit the amount of
address space delegated to APNIC Members from APNIC’s final /8.
Implemented the final /8 policy, which stipulated that APNIC account
holders new or existing were able to receive up to a /23 from the final /8
pool.
Checkout of the report of IPv4 availability:
https://labs.apnic.net/ipv4/report.html
Presented By: Shuvodip Roy in bdNOG 13
ONLINE
4
Request for Comments: 3021
In December, 2000 the documentation open. The main motivation was to
relief the problem slightly of lack of IPv4 addresses. On that time IPv6 was not
in production. Still IPv6 required many more years for transition fully.
Key Points:
• Consideration of 31-Bit Prefixes on IPv4 Links.
• Networks with 31-bit prefixes have no impact on current routing protocols.
The communication between peers is done using multicast, limited
broadcast or unicast addresses (all on the local network), none of which are
affected with the use of 31-bit subnet masks.
• The use of 31-bit subnet masks within the core of the Internet will reduce
the number of physical links against which a DoS attack relying on packet
replication through the use of directed broadcasts can be launched
[RFC2644, SMURF]
More information available in: https://datatracker.ietf.org/doc/html/rfc3021
Presented By: Shuvodip Roy in bdNOG 13
ONLINE
5
31-Bit Prefixes
Network: 192.0.2.0/31
Address: 192.0.2.0 11000000.00000000.00000010.0000000 0
Netmask: 255.255.255.254 = 31 11111111.11111111.11111111.1111111 0
Wildcard: 0.0.0.1 00000000.00000000.00000000.0000000 1
Broadcast: 192.0.2.1 11000000.00000000.00000010.0000000 1
HostMin: 192.0.2.1 11000000.00000000.00000010.0000000 1
HostMax: 192.0.2.0 11000000.00000000.00000010.0000000 0
Presented By: Shuvodip Roy in bdNOG 13
ONLINE
6
Traditional Point to Point Link
IP Block of 30 Bit Prefix: 192.0.2.0/30
Network Address: 192.0.2.0
Provider Edge Address: 192.0.2.1
Client Edge Address: 192.0.2.2
Broadcast Address: 192.0.2.3
Presented By: Shuvodip Roy in bdNOG 13
ONLINE
7
Provider Edge
IP: 192.0.2.1
Client Edge
IP: 192.0.2.2
Point to Point Link with 31-Bit
Using the same 192.0.2.0/30 rather than traditional Point to Point link in
31-Bit we can create 2 Point to Point link by same resource.
Presented By: Shuvodip Roy in bdNOG 13
ONLINE
8
Provider Edge
IP: 192.0.2.0
Client Edge
IP: 192.0.2.1
Provider Edge
IP: 192.0.2.2
Provider Edge
IP: 192.0.2.3
Client 1 Point to Point Link
Client 2 Point to Point Link
Client 1
/31 Bit Prefix:
192.0.2.0/31
Network Address:
192.0.2.0
Provider Edge Address:
192.0.2.1
Client Edge Address:
192.0.2.2
Broadcast Address:
192.0.2.1
Client 2
/31 Bit Prefix:
192.0.2.2/31
Network Address:
192.0.2.2
Provider Edge Address:
192.0.2.2
Client Edge Address:
192.0.2.3
Broadcast Address:
192.0.2.3
Where 31-Bit can be use?
In a ISP:
• Point to Point Infrastructure Link (i.e.: Backbone) with Public IP.
• Point to Point connected link with “Single Home” dedicated corporate
customers.
• It is also applicable for those customers who have multiple or single link
and the Public IP block routed via any Routing Protocol. Etc.
In a Organization:
• Point to Point Internal Backbone with Public IP.
• In Host (i.e.: Servers, Workstation) running with 30-Bit Prefix. Etc.
Presented By: Shuvodip Roy in bdNOG 13
ONLINE
9
Challenges!!!
A number of vendors or Operating System still now not support the
RFC3021. As a fact, a significant challenges is there to implement.
* In the context of Bangladesh, CISCO IOS support this since release
12.2(2)T, Juniper supports it also.
* Mostly used MikroTik, does not support it but with improvisation
without any side effects it possible to configure with 31-Bit.
* Windows is same as Mikrotik.
* Home based Router TP-Link new version supports 31-Bit but for older
versions need improvisation. But, that improvisation have relative side
effects also. Which will be discussed later to be concerned to use.
* Others all depends on Vendors and it’s Firmware or OS.
Presented By: Shuvodip Roy in bdNOG 13
ONLINE
10
Point to Point with 31-Bit in
CISCO
For R1:
R1(config-if)#ip address 192.0.2.0 255.255.255.254
For R2:
R2(config-if)#ip address 192.0.2.1 255.255.255.254
Presented By: Shuvodip Roy in bdNOG 13
ONLINE
11
Host Name “R1”
IP: 192.0.2.0/31
Host Name “R2”
IP: 192.0.2.1/31
Point to Point with 31-Bit in
CISCO (continue)
After configure IP in both Router if we check Route Table and Reachability
via ping, we will get following.
As CISCO supported RFC3021 31-Bit Prefixes will operate smoothly.
Presented By: Shuvodip Roy in bdNOG 13
ONLINE
12
R1 R2
Point to Point with 31-Bit in
Juniper
For R1:
[edit interfaces fxp0 unit 0]
root@R1# set family inet address 192.0.2.0/31
For R2:
[edit interfaces fxp0 unit 0]
root@R2# set family inet address 192.0.2.1/31
Presented By: Shuvodip Roy in bdNOG 13
ONLINE
13
Host Name “R1”
IP: 192.0.2.0/31
Host Name “R2”
IP: 192.0.2.1/31
Point to Point with 31-Bit in
Juniper (continue)
After configure IP in both Router if we check Route Table and Reachability via
ping, we will get following.
Juniper also supported RFC3021 31-Bit.
Presented By: Shuvodip Roy in bdNOG 13
ONLINE
14
R1 R2
Point to Point with 31-Bit in
MikroTik
For R1:
[admin@R1] > ip address add address=192.0.2.0 network=192.0.2.1
interface=ether1
For R2:
[admin@R2] > ip address add address=192.0.2.1 network=192.0.2.0
interface=ether1
Note: Mikrotik does not support the RFC3021. In MikroTik need to declare IP
as 32-Bit and also need to add “network” manually.
Presented By: Shuvodip Roy in bdNOG 13
ONLINE
15
Identity “R1”
IP: 192.0.2.0/31
Identity “R2”
IP: 192.0.2.1/31
Point to Point with 31-Bit in
Mikrotik (continue)
After configure IP in both Router if we check Route Table and Reachability
via ping, we will get following.
Now in Mikrotik we have the Reachability.
Presented By: Shuvodip Roy in bdNOG 13
ONLINE
16
R1 R2
Issues with MikroTik
We already ensure the Reachability in Point To Point link in Mikrotik by
using improvisation using 31-Bit as 32-Bit.
So, far in this method we can use 31-Bit Prefixes in Mikrotik. But, it creates
a issue also.
• Connected Route not Redistribute:
Suppose, Router R1 is a POP of a ISP and R2 is Client Edge. ISP POP is
connected over Dynamic Routing Protocol where Connected Route
Redistributed over Dynamic Routing Protocol.
As we manually set the IP as 32-Bit and also the network in R1. So that the
original network=192.0.2.0 changed for R1 IP. Which is manually set to
network=192.0.2.1. In that case, it will not Redistribute over Dynamic
Routing Protocol.
Presented By: Shuvodip Roy in bdNOG 13
ONLINE
17
Solution of the Issues with
MikroTik
There are 2 possible solution of this currently.
• Advertise the 31-Bit Prefix: Solution 1, will be the advertising 31-Bit
Prefix 192.0.2.0/31 via Dynamic Routing Protocol in POP/R1 side.
• Set the HostMin IP in POP/R1 as 31-Bit: Solution 2, is in POP/R1 declare
IP as 192.0.2.1/31 where automatically network will be 192.0.2.0. In
Client/R2 set the IP manually as 192.0.2.0 as well as network 192.0.2.1.
Thus Point to Point will be reachable also the connected route in
POP/R1 will be Redistribute also.
Presented By: Shuvodip Roy in bdNOG 13
ONLINE
18
Solution of the Issues with
MikroTik
There are 2 Possible solution of this currently.
• Advertise the 31-Bit Prefix: Solution 1, will be the advertising 31-Bit
Prefix 192.0.2.0/31 via Dynamic Routing Protocol in POP/R1 side.
• Set the HostMin IP in POP/R1 as 31-Bit: Solution 2, is in POP/R1 declare
IP as 192.0.2.1/31 where automatically network will be 192.0.2.0. In
Client/R2 set the IP manually as 192.0.2.0 as well as network 192.0.2.1.
Thus Point to Point will be reachable also the connected route in
POP/R1 will be Redistribute also.
Presented By: Shuvodip Roy in bdNOG 13
ONLINE
19
31-Bit in TP-Link
TP-Link Routers are mostly used in Home, SOHO link. New firmware and
models TP-Link supports RFC3021 and configuration is nothing new.
Presented By: Shuvodip Roy in bdNOG 13
ONLINE
20
31-Bit IP configuration in TP-Link
Issues with TP-Link old
versions
Older version TP-Link does not support RFC3021. In that case, through
improvisation setup could be possible as figured.
Presented By: Shuvodip Roy in bdNOG 13
ONLINE
21
TP-Link 31-Bit configured with improvisation in old version
Issues with TP-Link old
versions (continue)
In the early slide we configured 31-Bit in a old version/model of TP-Link
which does not support the RFC3021.
In that case, Prefix was 118.179.84.12/31 but as TP-Link does not support
it Subnet Mask: 255.255.255.254 or 255.255.255.255 will not be
applicable. It will provide following error
“The IP Address does not match the Subnet Mask: Invalid host number”
Presented By: Shuvodip Roy in bdNOG 13
ONLINE
22
Solution of the Issues with
TP-Link old versions
In 118.179.84.12/31, we need to find a sweet able Subnet Mask where IP:
118.179.84.12 & IP: 118.179.84.13 will not be the Network Address or the
Broadcast Address.
So, in nearest Subnet Mask 255.255.255.248 or /29 IP: 118.179.84.12 &
IP: 118.179.84.13 is not the Network Address or the Broadcast Address.
Then Router will accept the IP configuration and 31-Bit will be useable.
The nearest Subnet Mask will vary with IP.
Caution: There also a side effect brings with this improvisation. As TP-
Link get 118.179.84.8/29 as connected Route due to Subnet Mask:
255.255.255.248. So, from this TP-Link except 118.179.84.12 & IP:
118.179.84.13 all IP will be unreachable in 118.179.84.8/29. If the link
required reachability in this range then this improvisation will be
difficult.
Presented By: Shuvodip Roy in bdNOG 13
ONLINE
23
Others Home Routers
Others Home Router such as Netgear, Asus, Tenda, D-Link etc. are
moreover same as TP-Link.
The new version in some vendors supports RFC3021 but others are not.
Improvisation works but there are side effects of that which already
described.
Presented By: Shuvodip Roy in bdNOG 13
ONLINE
24
31-Bit in Windows
Windows also not support RFC3021. If we set the Subnet Mask
255.255.255.254 it provides following Warning.
Presented By: Shuvodip Roy in bdNOG 13
ONLINE
25
31-Bit in Windows (continue)
But as improvisation we may use the IP as 32-Bit Prefix, that means
Subnet Mask is 255.255.255.255
Presented By: Shuvodip Roy in bdNOG 13
ONLINE
26
31-Bit in Windows
31-Bit in Windows (continue)
Although it will also provide following Warning. But, saving this
configuration by pressing “Yes” will work for 31-Bit Prefix improvisation in
Windows. Thus, smoothly 31-Bit can be useable in Windows.
Presented By: Shuvodip Roy in bdNOG 13
ONLINE
27
31-Bit in Linux
Adding 31-Bit Prefix is Linux have nothing new. It is usual as like others IP
configuration in Linux. Here is a example with Ubuntu 20.10 (Groovy
Gorilla)
Presented By: Shuvodip Roy in bdNOG 13
ONLINE
28
31-Bit Prefix in Linux
Example in Production
In my organization Amber IT Limited, we are deploying 31-Bit Prefixes in
respect of the concerns of all matters which already described. Plenty of
numbers we already deployed in 31-Bit and it’s cost IPv4 resources half
rather than where it traditionally does with 30-Bit Prefix.
Presented By: Shuvodip Roy in bdNOG 13
ONLINE
29
Summary
In Exhaustion, RFC3021 is very helpful in deed. There are no doubts IPv6 is
the longer time solution. But, different expertise already provide
statement that it will require more time to transition fully in to IPv6.
In the mean time, we have none other choice but a option RFC3021.
Which will provide a relief for Exhaustion of IPv4.
The main challenge is primeval Devices and many Vendors still not support
the RFC. As it is a matter of Firmware or OS, we may expect soon Vendors
will rollout updated Firmware or OS which will support RFC3021. Which
will be a great offer for users. It will be also a great relief for Service
Providers.
Presented By: Shuvodip Roy in bdNOG 13
ONLINE
30
Acknowledgement
Special thanks for bdNOG committee members for approve my
presentation.
I would also like to gratefully acknowledge who works and proposed
RFC3021.
• A. Retana
• R. White
• Cisco Systems
• V. Fuller
• GTE Internetworking
• D. McPherson
• Amber Networks
and also to many more.
Presented By: Shuvodip Roy in bdNOG 13
ONLINE
31
Presented By: Shuvodip Roy in bdNOG 13
ONLINE
32

Mais conteúdo relacionado

Mais procurados

DHCP (Dynamic Host Configuration Protocol)
DHCP (Dynamic Host Configuration Protocol)DHCP (Dynamic Host Configuration Protocol)
DHCP (Dynamic Host Configuration Protocol)Faisal Jatt
 
Ftp server configuration on cisco packet tracer
Ftp server configuration on cisco packet tracerFtp server configuration on cisco packet tracer
Ftp server configuration on cisco packet tracerprodhan999
 
Ccna rse chp6 VLAN
Ccna rse chp6 VLANCcna rse chp6 VLAN
Ccna rse chp6 VLANnewbie2019
 
Using BGP To Manage Dual Internet Connections
Using BGP To Manage Dual Internet ConnectionsUsing BGP To Manage Dual Internet Connections
Using BGP To Manage Dual Internet ConnectionsRowell Dionicio
 
ccna summer training ppt ( Cisco certified network analysis) ppt. by Traun k...
ccna summer training ppt ( Cisco certified network analysis) ppt.  by Traun k...ccna summer training ppt ( Cisco certified network analysis) ppt.  by Traun k...
ccna summer training ppt ( Cisco certified network analysis) ppt. by Traun k...Tarun Khaneja
 
Cisco IPv6 Tutorial by Hinwoto
Cisco IPv6 Tutorial by HinwotoCisco IPv6 Tutorial by Hinwoto
Cisco IPv6 Tutorial by HinwotoFebrian ‎
 
Policy Based Routing (PBR) on Mikrotik
Policy Based Routing (PBR) on MikrotikPolicy Based Routing (PBR) on Mikrotik
Policy Based Routing (PBR) on MikrotikGLC Networks
 

Mais procurados (20)

ICMP
ICMPICMP
ICMP
 
Application Layer
Application LayerApplication Layer
Application Layer
 
Bgp protocol
Bgp protocolBgp protocol
Bgp protocol
 
200 301-ccna
200 301-ccna200 301-ccna
200 301-ccna
 
BGP filter with mikrotik
BGP filter with mikrotikBGP filter with mikrotik
BGP filter with mikrotik
 
DHCP (Dynamic Host Configuration Protocol)
DHCP (Dynamic Host Configuration Protocol)DHCP (Dynamic Host Configuration Protocol)
DHCP (Dynamic Host Configuration Protocol)
 
Mobile Transport layer
Mobile Transport layerMobile Transport layer
Mobile Transport layer
 
Ftp server configuration on cisco packet tracer
Ftp server configuration on cisco packet tracerFtp server configuration on cisco packet tracer
Ftp server configuration on cisco packet tracer
 
IP Multicasting
IP MulticastingIP Multicasting
IP Multicasting
 
Ccna rse chp6 VLAN
Ccna rse chp6 VLANCcna rse chp6 VLAN
Ccna rse chp6 VLAN
 
TCP/IP Introduction
TCP/IP IntroductionTCP/IP Introduction
TCP/IP Introduction
 
Using BGP To Manage Dual Internet Connections
Using BGP To Manage Dual Internet ConnectionsUsing BGP To Manage Dual Internet Connections
Using BGP To Manage Dual Internet Connections
 
ccna summer training ppt ( Cisco certified network analysis) ppt. by Traun k...
ccna summer training ppt ( Cisco certified network analysis) ppt.  by Traun k...ccna summer training ppt ( Cisco certified network analysis) ppt.  by Traun k...
ccna summer training ppt ( Cisco certified network analysis) ppt. by Traun k...
 
TCP and UDP
TCP and UDP TCP and UDP
TCP and UDP
 
TCP vs UDP / Sumiet23
TCP vs UDP / Sumiet23TCP vs UDP / Sumiet23
TCP vs UDP / Sumiet23
 
Cisco IPv6 Tutorial by Hinwoto
Cisco IPv6 Tutorial by HinwotoCisco IPv6 Tutorial by Hinwoto
Cisco IPv6 Tutorial by Hinwoto
 
Switch security
Switch securitySwitch security
Switch security
 
Socket programming
Socket programmingSocket programming
Socket programming
 
Policy Based Routing (PBR) on Mikrotik
Policy Based Routing (PBR) on MikrotikPolicy Based Routing (PBR) on Mikrotik
Policy Based Routing (PBR) on Mikrotik
 
Link state protocols.ppt
Link state protocols.pptLink state protocols.ppt
Link state protocols.ppt
 

Semelhante a 31, Get more from your IPv4 resources

MULTIMEDIA COMMUNICATION & NETWORKS
MULTIMEDIA COMMUNICATION & NETWORKSMULTIMEDIA COMMUNICATION & NETWORKS
MULTIMEDIA COMMUNICATION & NETWORKSKathirvel Ayyaswamy
 
Www ccnav5 net_ccna_3_v5_0_scaling_networks_final_exam_2013
Www ccnav5 net_ccna_3_v5_0_scaling_networks_final_exam_2013Www ccnav5 net_ccna_3_v5_0_scaling_networks_final_exam_2013
Www ccnav5 net_ccna_3_v5_0_scaling_networks_final_exam_2013Đồng Quốc Vương
 
Bgp route reflector
Bgp route reflector Bgp route reflector
Bgp route reflector Deepak Kumar
 
Www ccnav5 net_ccna_1_chapter_8_v5_0_exam_answers_2014
Www ccnav5 net_ccna_1_chapter_8_v5_0_exam_answers_2014Www ccnav5 net_ccna_1_chapter_8_v5_0_exam_answers_2014
Www ccnav5 net_ccna_1_chapter_8_v5_0_exam_answers_2014Đồng Quốc Vương
 
Running BGP with Mikrotik
Running BGP with MikrotikRunning BGP with Mikrotik
Running BGP with MikrotikGLC Networks
 
Device replacement in eip with lldp
Device replacement in eip with lldpDevice replacement in eip with lldp
Device replacement in eip with lldpromangl
 
Mikro tik vpn configuration with site converted
Mikro tik vpn configuration with site convertedMikro tik vpn configuration with site converted
Mikro tik vpn configuration with site convertedUttam Ds
 
Cisco discovery d homesb module 5 - v.4 in english.
Cisco discovery   d homesb module 5 - v.4 in english.Cisco discovery   d homesb module 5 - v.4 in english.
Cisco discovery d homesb module 5 - v.4 in english.igede tirtanata
 
Ccna 1 final exam answer v5
Ccna 1 final exam answer v5Ccna 1 final exam answer v5
Ccna 1 final exam answer v5friv4schoolgames
 
I pv6 tutorial
I pv6 tutorialI pv6 tutorial
I pv6 tutorialFred Bovy
 
Abitcool - A vast array of small-scale service providers with gigabit access,...
Abitcool - A vast array of small-scale service providers with gigabit access,...Abitcool - A vast array of small-scale service providers with gigabit access,...
Abitcool - A vast array of small-scale service providers with gigabit access,...APNIC
 
IP Concept in LTE
IP Concept in LTEIP Concept in LTE
IP Concept in LTESofian .
 
Www ccnav5 net_ccna_1_chapter_3_v5_0_exam_answers_2014
Www ccnav5 net_ccna_1_chapter_3_v5_0_exam_answers_2014Www ccnav5 net_ccna_1_chapter_3_v5_0_exam_answers_2014
Www ccnav5 net_ccna_1_chapter_3_v5_0_exam_answers_2014Đồng Quốc Vương
 

Semelhante a 31, Get more from your IPv4 resources (20)

IPAddressing .pptx
IPAddressing .pptxIPAddressing .pptx
IPAddressing .pptx
 
MULTIMEDIA COMMUNICATION & NETWORKS
MULTIMEDIA COMMUNICATION & NETWORKSMULTIMEDIA COMMUNICATION & NETWORKS
MULTIMEDIA COMMUNICATION & NETWORKS
 
2017 01-31-cgns
2017 01-31-cgns2017 01-31-cgns
2017 01-31-cgns
 
Www ccnav5 net_ccna_3_v5_0_scaling_networks_final_exam_2013
Www ccnav5 net_ccna_3_v5_0_scaling_networks_final_exam_2013Www ccnav5 net_ccna_3_v5_0_scaling_networks_final_exam_2013
Www ccnav5 net_ccna_3_v5_0_scaling_networks_final_exam_2013
 
Bgp route reflector
Bgp route reflector Bgp route reflector
Bgp route reflector
 
Bots.pdf
Bots.pdfBots.pdf
Bots.pdf
 
Www ccnav5 net_ccna_1_chapter_8_v5_0_exam_answers_2014
Www ccnav5 net_ccna_1_chapter_8_v5_0_exam_answers_2014Www ccnav5 net_ccna_1_chapter_8_v5_0_exam_answers_2014
Www ccnav5 net_ccna_1_chapter_8_v5_0_exam_answers_2014
 
Running BGP with Mikrotik
Running BGP with MikrotikRunning BGP with Mikrotik
Running BGP with Mikrotik
 
Computer Network
Computer Network Computer Network
Computer Network
 
Device replacement in eip with lldp
Device replacement in eip with lldpDevice replacement in eip with lldp
Device replacement in eip with lldp
 
Mikro tik vpn configuration with site converted
Mikro tik vpn configuration with site convertedMikro tik vpn configuration with site converted
Mikro tik vpn configuration with site converted
 
Cisco discovery d homesb module 5 - v.4 in english.
Cisco discovery   d homesb module 5 - v.4 in english.Cisco discovery   d homesb module 5 - v.4 in english.
Cisco discovery d homesb module 5 - v.4 in english.
 
Ccna 1 final exam answer v5
Ccna 1 final exam answer v5Ccna 1 final exam answer v5
Ccna 1 final exam answer v5
 
I pv6 tutorial
I pv6 tutorialI pv6 tutorial
I pv6 tutorial
 
Abitcool - A vast array of small-scale service providers with gigabit access,...
Abitcool - A vast array of small-scale service providers with gigabit access,...Abitcool - A vast array of small-scale service providers with gigabit access,...
Abitcool - A vast array of small-scale service providers with gigabit access,...
 
IP Addressing.ppt
IP Addressing.pptIP Addressing.ppt
IP Addressing.ppt
 
ccna 4 final 2012
ccna 4 final 2012ccna 4 final 2012
ccna 4 final 2012
 
IP Concept in LTE
IP Concept in LTEIP Concept in LTE
IP Concept in LTE
 
Mod6
Mod6Mod6
Mod6
 
Www ccnav5 net_ccna_1_chapter_3_v5_0_exam_answers_2014
Www ccnav5 net_ccna_1_chapter_3_v5_0_exam_answers_2014Www ccnav5 net_ccna_1_chapter_3_v5_0_exam_answers_2014
Www ccnav5 net_ccna_1_chapter_3_v5_0_exam_answers_2014
 

Mais de Bangladesh Network Operators Group

Accelerating Hyper-Converged Enterprise Virtualization using Proxmox and Ceph
Accelerating Hyper-Converged Enterprise Virtualization using Proxmox and CephAccelerating Hyper-Converged Enterprise Virtualization using Proxmox and Ceph
Accelerating Hyper-Converged Enterprise Virtualization using Proxmox and CephBangladesh Network Operators Group
 
Contents Localization Initiatives to get better User Experience
Contents Localization Initiatives to get better User ExperienceContents Localization Initiatives to get better User Experience
Contents Localization Initiatives to get better User ExperienceBangladesh Network Operators Group
 
Re-define network visibility for capacity planning & forecasting with Grafana
Re-define network visibility for capacity planning & forecasting with GrafanaRe-define network visibility for capacity planning & forecasting with Grafana
Re-define network visibility for capacity planning & forecasting with GrafanaBangladesh Network Operators Group
 

Mais de Bangladesh Network Operators Group (20)

Accelerating Hyper-Converged Enterprise Virtualization using Proxmox and Ceph
Accelerating Hyper-Converged Enterprise Virtualization using Proxmox and CephAccelerating Hyper-Converged Enterprise Virtualization using Proxmox and Ceph
Accelerating Hyper-Converged Enterprise Virtualization using Proxmox and Ceph
 
Recent IRR changes by Yoshinobu Matsuzaki, IIJ
Recent IRR changes by Yoshinobu Matsuzaki, IIJRecent IRR changes by Yoshinobu Matsuzaki, IIJ
Recent IRR changes by Yoshinobu Matsuzaki, IIJ
 
Fact Sheets : Network Status in Bangladesh
Fact Sheets : Network Status in BangladeshFact Sheets : Network Status in Bangladesh
Fact Sheets : Network Status in Bangladesh
 
AI Driven Wi-Fi for the Bottom of the Pyramid
AI Driven Wi-Fi for the Bottom of the PyramidAI Driven Wi-Fi for the Bottom of the Pyramid
AI Driven Wi-Fi for the Bottom of the Pyramid
 
IPv6 Security Overview by QS Tahmeed, APNIC RCT
IPv6 Security Overview by QS Tahmeed, APNIC RCTIPv6 Security Overview by QS Tahmeed, APNIC RCT
IPv6 Security Overview by QS Tahmeed, APNIC RCT
 
Network eWaste : Community role to manage end of life Product
Network eWaste : Community role to manage end of life ProductNetwork eWaste : Community role to manage end of life Product
Network eWaste : Community role to manage end of life Product
 
A plenarily integrated SIEM solution and it’s Deployment
A plenarily integrated SIEM solution and it’s DeploymentA plenarily integrated SIEM solution and it’s Deployment
A plenarily integrated SIEM solution and it’s Deployment
 
IPv6 Deployment in South Asia 2022
IPv6 Deployment in South Asia  2022IPv6 Deployment in South Asia  2022
IPv6 Deployment in South Asia 2022
 
Introduction to Software Defined Networking (SDN)
Introduction to Software Defined Networking (SDN)Introduction to Software Defined Networking (SDN)
Introduction to Software Defined Networking (SDN)
 
RPKI Deployment Status in Bangladesh
RPKI Deployment Status in BangladeshRPKI Deployment Status in Bangladesh
RPKI Deployment Status in Bangladesh
 
An Overview about open UDP Services
An Overview about open UDP ServicesAn Overview about open UDP Services
An Overview about open UDP Services
 
12 Years in DNS Security As a Defender
12 Years in DNS Security As a Defender12 Years in DNS Security As a Defender
12 Years in DNS Security As a Defender
 
Contents Localization Initiatives to get better User Experience
Contents Localization Initiatives to get better User ExperienceContents Localization Initiatives to get better User Experience
Contents Localization Initiatives to get better User Experience
 
BdNOG-20220625-MT-v6.0.pptx
BdNOG-20220625-MT-v6.0.pptxBdNOG-20220625-MT-v6.0.pptx
BdNOG-20220625-MT-v6.0.pptx
 
Route Leak Prevension with BGP Community
Route Leak Prevension with BGP CommunityRoute Leak Prevension with BGP Community
Route Leak Prevension with BGP Community
 
Tale of a New Bangladeshi NIX
Tale of a New Bangladeshi NIXTale of a New Bangladeshi NIX
Tale of a New Bangladeshi NIX
 
MANRS for Network Operators
MANRS for Network OperatorsMANRS for Network Operators
MANRS for Network Operators
 
Re-define network visibility for capacity planning & forecasting with Grafana
Re-define network visibility for capacity planning & forecasting with GrafanaRe-define network visibility for capacity planning & forecasting with Grafana
Re-define network visibility for capacity planning & forecasting with Grafana
 
RPKI ROA updates
RPKI ROA updatesRPKI ROA updates
RPKI ROA updates
 
Blockchain Demystified
Blockchain DemystifiedBlockchain Demystified
Blockchain Demystified
 

Último

Vision Forward: Tracing Image Search SEO From Its Roots To AI-Enhanced Horizons
Vision Forward: Tracing Image Search SEO From Its Roots To AI-Enhanced HorizonsVision Forward: Tracing Image Search SEO From Its Roots To AI-Enhanced Horizons
Vision Forward: Tracing Image Search SEO From Its Roots To AI-Enhanced HorizonsRoxana Stingu
 
Presentation2.pptx - JoyPress Wordpress
Presentation2.pptx -  JoyPress WordpressPresentation2.pptx -  JoyPress Wordpress
Presentation2.pptx - JoyPress Wordpressssuser166378
 
Check out the Free Landing Page Hosting in 2024
Check out the Free Landing Page Hosting in 2024Check out the Free Landing Page Hosting in 2024
Check out the Free Landing Page Hosting in 2024Shubham Pant
 
Computer 10 Lesson 8: Building a Website
Computer 10 Lesson 8: Building a WebsiteComputer 10 Lesson 8: Building a Website
Computer 10 Lesson 8: Building a WebsiteMavein
 
LESSON 5 GROUP 10 ST. THOMAS AQUINAS.pdf
LESSON 5 GROUP 10 ST. THOMAS AQUINAS.pdfLESSON 5 GROUP 10 ST. THOMAS AQUINAS.pdf
LESSON 5 GROUP 10 ST. THOMAS AQUINAS.pdfmchristianalwyn
 
Bio Medical Waste Management Guideliness 2023 ppt.pptx
Bio Medical Waste Management Guideliness 2023 ppt.pptxBio Medical Waste Management Guideliness 2023 ppt.pptx
Bio Medical Waste Management Guideliness 2023 ppt.pptxnaveenithkrishnan
 
Zero-day Vulnerabilities
Zero-day VulnerabilitiesZero-day Vulnerabilities
Zero-day Vulnerabilitiesalihassaah1994
 
Introduction to ICANN and Fellowship program by Shreedeep Rayamajhi.pdf
Introduction to ICANN and Fellowship program  by Shreedeep Rayamajhi.pdfIntroduction to ICANN and Fellowship program  by Shreedeep Rayamajhi.pdf
Introduction to ICANN and Fellowship program by Shreedeep Rayamajhi.pdfShreedeep Rayamajhi
 
Benefits of doing Internet peering and running an Internet Exchange (IX) pres...
Benefits of doing Internet peering and running an Internet Exchange (IX) pres...Benefits of doing Internet peering and running an Internet Exchange (IX) pres...
Benefits of doing Internet peering and running an Internet Exchange (IX) pres...APNIC
 
WordPress by the numbers - Jan Loeffler, CTO WebPros, CloudFest 2024
WordPress by the numbers - Jan Loeffler, CTO WebPros, CloudFest 2024WordPress by the numbers - Jan Loeffler, CTO WebPros, CloudFest 2024
WordPress by the numbers - Jan Loeffler, CTO WebPros, CloudFest 2024Jan Löffler
 
TYPES AND DEFINITION OF ONLINE CRIMES AND HAZARDS
TYPES AND DEFINITION OF ONLINE CRIMES AND HAZARDSTYPES AND DEFINITION OF ONLINE CRIMES AND HAZARDS
TYPES AND DEFINITION OF ONLINE CRIMES AND HAZARDSedrianrheine
 
LESSON 10/ GROUP 10/ ST. THOMAS AQUINASS
LESSON 10/ GROUP 10/ ST. THOMAS AQUINASSLESSON 10/ GROUP 10/ ST. THOMAS AQUINASS
LESSON 10/ GROUP 10/ ST. THOMAS AQUINASSlesteraporado16
 

Último (12)

Vision Forward: Tracing Image Search SEO From Its Roots To AI-Enhanced Horizons
Vision Forward: Tracing Image Search SEO From Its Roots To AI-Enhanced HorizonsVision Forward: Tracing Image Search SEO From Its Roots To AI-Enhanced Horizons
Vision Forward: Tracing Image Search SEO From Its Roots To AI-Enhanced Horizons
 
Presentation2.pptx - JoyPress Wordpress
Presentation2.pptx -  JoyPress WordpressPresentation2.pptx -  JoyPress Wordpress
Presentation2.pptx - JoyPress Wordpress
 
Check out the Free Landing Page Hosting in 2024
Check out the Free Landing Page Hosting in 2024Check out the Free Landing Page Hosting in 2024
Check out the Free Landing Page Hosting in 2024
 
Computer 10 Lesson 8: Building a Website
Computer 10 Lesson 8: Building a WebsiteComputer 10 Lesson 8: Building a Website
Computer 10 Lesson 8: Building a Website
 
LESSON 5 GROUP 10 ST. THOMAS AQUINAS.pdf
LESSON 5 GROUP 10 ST. THOMAS AQUINAS.pdfLESSON 5 GROUP 10 ST. THOMAS AQUINAS.pdf
LESSON 5 GROUP 10 ST. THOMAS AQUINAS.pdf
 
Bio Medical Waste Management Guideliness 2023 ppt.pptx
Bio Medical Waste Management Guideliness 2023 ppt.pptxBio Medical Waste Management Guideliness 2023 ppt.pptx
Bio Medical Waste Management Guideliness 2023 ppt.pptx
 
Zero-day Vulnerabilities
Zero-day VulnerabilitiesZero-day Vulnerabilities
Zero-day Vulnerabilities
 
Introduction to ICANN and Fellowship program by Shreedeep Rayamajhi.pdf
Introduction to ICANN and Fellowship program  by Shreedeep Rayamajhi.pdfIntroduction to ICANN and Fellowship program  by Shreedeep Rayamajhi.pdf
Introduction to ICANN and Fellowship program by Shreedeep Rayamajhi.pdf
 
Benefits of doing Internet peering and running an Internet Exchange (IX) pres...
Benefits of doing Internet peering and running an Internet Exchange (IX) pres...Benefits of doing Internet peering and running an Internet Exchange (IX) pres...
Benefits of doing Internet peering and running an Internet Exchange (IX) pres...
 
WordPress by the numbers - Jan Loeffler, CTO WebPros, CloudFest 2024
WordPress by the numbers - Jan Loeffler, CTO WebPros, CloudFest 2024WordPress by the numbers - Jan Loeffler, CTO WebPros, CloudFest 2024
WordPress by the numbers - Jan Loeffler, CTO WebPros, CloudFest 2024
 
TYPES AND DEFINITION OF ONLINE CRIMES AND HAZARDS
TYPES AND DEFINITION OF ONLINE CRIMES AND HAZARDSTYPES AND DEFINITION OF ONLINE CRIMES AND HAZARDS
TYPES AND DEFINITION OF ONLINE CRIMES AND HAZARDS
 
LESSON 10/ GROUP 10/ ST. THOMAS AQUINASS
LESSON 10/ GROUP 10/ ST. THOMAS AQUINASSLESSON 10/ GROUP 10/ ST. THOMAS AQUINASS
LESSON 10/ GROUP 10/ ST. THOMAS AQUINASS
 

31, Get more from your IPv4 resources

  • 1. 31 Get more from your IPv4 resources Presented By: Shuvodip Roy Senior Systems Engineer Amber IT Limited sdroy@live.com
  • 2. Preface As IPv4 exhausted, RIR’s (Regional Internet Registry) are not getting IPv4 to be allocated or the block size now become very limited. Alternative and the next version IPv6 is rolled out. But, demand of IPv4 is still growing. One of the big reason is globally still the maximum number of sites yet only available via IPv4. In the context of Bangladesh, we still need to connect a large numbers of subscribers with Internet. Sufficient IPv4 addresses are not available. In this circumstance, we can use RFC3021 Using 31-Bit Prefixes on IPv4 Point-to-Point Links in large scale. In a ISP or else, 80% or more are actually “Single Home Point-to-Point Links”. Using the RFC3021, we will be able to connect double numbers of links than current times using existing IPv4 resources. This presentation is all about that. Presented By: Shuvodip Roy in bdNOG 13 ONLINE 2
  • 3. Disclaimer * Disclaimer: Although RFC3021 released in December, 2000. Still many vendors or devices not support it. In this presentation, will try to cover up the configuration of those which is commonly use in Bangladesh. The configuration will differ vendor to vendor as well as device to device. Presented By: Shuvodip Roy in bdNOG 13 ONLINE 3
  • 4. Exhaustion All 5 RIR's have either limited supplies or have run out of available IPv4 addresses. ARIN and the RIPE NCC ran out of their available supply in 2015 and 2019 respectively. In APNIC, LACNIC and AFRINIC rationing supplies according to the community policies. APNIC’s IPv4 pool to run out by creating policies to limit the amount of address space delegated to APNIC Members from APNIC’s final /8. Implemented the final /8 policy, which stipulated that APNIC account holders new or existing were able to receive up to a /23 from the final /8 pool. Checkout of the report of IPv4 availability: https://labs.apnic.net/ipv4/report.html Presented By: Shuvodip Roy in bdNOG 13 ONLINE 4
  • 5. Request for Comments: 3021 In December, 2000 the documentation open. The main motivation was to relief the problem slightly of lack of IPv4 addresses. On that time IPv6 was not in production. Still IPv6 required many more years for transition fully. Key Points: • Consideration of 31-Bit Prefixes on IPv4 Links. • Networks with 31-bit prefixes have no impact on current routing protocols. The communication between peers is done using multicast, limited broadcast or unicast addresses (all on the local network), none of which are affected with the use of 31-bit subnet masks. • The use of 31-bit subnet masks within the core of the Internet will reduce the number of physical links against which a DoS attack relying on packet replication through the use of directed broadcasts can be launched [RFC2644, SMURF] More information available in: https://datatracker.ietf.org/doc/html/rfc3021 Presented By: Shuvodip Roy in bdNOG 13 ONLINE 5
  • 6. 31-Bit Prefixes Network: 192.0.2.0/31 Address: 192.0.2.0 11000000.00000000.00000010.0000000 0 Netmask: 255.255.255.254 = 31 11111111.11111111.11111111.1111111 0 Wildcard: 0.0.0.1 00000000.00000000.00000000.0000000 1 Broadcast: 192.0.2.1 11000000.00000000.00000010.0000000 1 HostMin: 192.0.2.1 11000000.00000000.00000010.0000000 1 HostMax: 192.0.2.0 11000000.00000000.00000010.0000000 0 Presented By: Shuvodip Roy in bdNOG 13 ONLINE 6
  • 7. Traditional Point to Point Link IP Block of 30 Bit Prefix: 192.0.2.0/30 Network Address: 192.0.2.0 Provider Edge Address: 192.0.2.1 Client Edge Address: 192.0.2.2 Broadcast Address: 192.0.2.3 Presented By: Shuvodip Roy in bdNOG 13 ONLINE 7 Provider Edge IP: 192.0.2.1 Client Edge IP: 192.0.2.2
  • 8. Point to Point Link with 31-Bit Using the same 192.0.2.0/30 rather than traditional Point to Point link in 31-Bit we can create 2 Point to Point link by same resource. Presented By: Shuvodip Roy in bdNOG 13 ONLINE 8 Provider Edge IP: 192.0.2.0 Client Edge IP: 192.0.2.1 Provider Edge IP: 192.0.2.2 Provider Edge IP: 192.0.2.3 Client 1 Point to Point Link Client 2 Point to Point Link Client 1 /31 Bit Prefix: 192.0.2.0/31 Network Address: 192.0.2.0 Provider Edge Address: 192.0.2.1 Client Edge Address: 192.0.2.2 Broadcast Address: 192.0.2.1 Client 2 /31 Bit Prefix: 192.0.2.2/31 Network Address: 192.0.2.2 Provider Edge Address: 192.0.2.2 Client Edge Address: 192.0.2.3 Broadcast Address: 192.0.2.3
  • 9. Where 31-Bit can be use? In a ISP: • Point to Point Infrastructure Link (i.e.: Backbone) with Public IP. • Point to Point connected link with “Single Home” dedicated corporate customers. • It is also applicable for those customers who have multiple or single link and the Public IP block routed via any Routing Protocol. Etc. In a Organization: • Point to Point Internal Backbone with Public IP. • In Host (i.e.: Servers, Workstation) running with 30-Bit Prefix. Etc. Presented By: Shuvodip Roy in bdNOG 13 ONLINE 9
  • 10. Challenges!!! A number of vendors or Operating System still now not support the RFC3021. As a fact, a significant challenges is there to implement. * In the context of Bangladesh, CISCO IOS support this since release 12.2(2)T, Juniper supports it also. * Mostly used MikroTik, does not support it but with improvisation without any side effects it possible to configure with 31-Bit. * Windows is same as Mikrotik. * Home based Router TP-Link new version supports 31-Bit but for older versions need improvisation. But, that improvisation have relative side effects also. Which will be discussed later to be concerned to use. * Others all depends on Vendors and it’s Firmware or OS. Presented By: Shuvodip Roy in bdNOG 13 ONLINE 10
  • 11. Point to Point with 31-Bit in CISCO For R1: R1(config-if)#ip address 192.0.2.0 255.255.255.254 For R2: R2(config-if)#ip address 192.0.2.1 255.255.255.254 Presented By: Shuvodip Roy in bdNOG 13 ONLINE 11 Host Name “R1” IP: 192.0.2.0/31 Host Name “R2” IP: 192.0.2.1/31
  • 12. Point to Point with 31-Bit in CISCO (continue) After configure IP in both Router if we check Route Table and Reachability via ping, we will get following. As CISCO supported RFC3021 31-Bit Prefixes will operate smoothly. Presented By: Shuvodip Roy in bdNOG 13 ONLINE 12 R1 R2
  • 13. Point to Point with 31-Bit in Juniper For R1: [edit interfaces fxp0 unit 0] root@R1# set family inet address 192.0.2.0/31 For R2: [edit interfaces fxp0 unit 0] root@R2# set family inet address 192.0.2.1/31 Presented By: Shuvodip Roy in bdNOG 13 ONLINE 13 Host Name “R1” IP: 192.0.2.0/31 Host Name “R2” IP: 192.0.2.1/31
  • 14. Point to Point with 31-Bit in Juniper (continue) After configure IP in both Router if we check Route Table and Reachability via ping, we will get following. Juniper also supported RFC3021 31-Bit. Presented By: Shuvodip Roy in bdNOG 13 ONLINE 14 R1 R2
  • 15. Point to Point with 31-Bit in MikroTik For R1: [admin@R1] > ip address add address=192.0.2.0 network=192.0.2.1 interface=ether1 For R2: [admin@R2] > ip address add address=192.0.2.1 network=192.0.2.0 interface=ether1 Note: Mikrotik does not support the RFC3021. In MikroTik need to declare IP as 32-Bit and also need to add “network” manually. Presented By: Shuvodip Roy in bdNOG 13 ONLINE 15 Identity “R1” IP: 192.0.2.0/31 Identity “R2” IP: 192.0.2.1/31
  • 16. Point to Point with 31-Bit in Mikrotik (continue) After configure IP in both Router if we check Route Table and Reachability via ping, we will get following. Now in Mikrotik we have the Reachability. Presented By: Shuvodip Roy in bdNOG 13 ONLINE 16 R1 R2
  • 17. Issues with MikroTik We already ensure the Reachability in Point To Point link in Mikrotik by using improvisation using 31-Bit as 32-Bit. So, far in this method we can use 31-Bit Prefixes in Mikrotik. But, it creates a issue also. • Connected Route not Redistribute: Suppose, Router R1 is a POP of a ISP and R2 is Client Edge. ISP POP is connected over Dynamic Routing Protocol where Connected Route Redistributed over Dynamic Routing Protocol. As we manually set the IP as 32-Bit and also the network in R1. So that the original network=192.0.2.0 changed for R1 IP. Which is manually set to network=192.0.2.1. In that case, it will not Redistribute over Dynamic Routing Protocol. Presented By: Shuvodip Roy in bdNOG 13 ONLINE 17
  • 18. Solution of the Issues with MikroTik There are 2 possible solution of this currently. • Advertise the 31-Bit Prefix: Solution 1, will be the advertising 31-Bit Prefix 192.0.2.0/31 via Dynamic Routing Protocol in POP/R1 side. • Set the HostMin IP in POP/R1 as 31-Bit: Solution 2, is in POP/R1 declare IP as 192.0.2.1/31 where automatically network will be 192.0.2.0. In Client/R2 set the IP manually as 192.0.2.0 as well as network 192.0.2.1. Thus Point to Point will be reachable also the connected route in POP/R1 will be Redistribute also. Presented By: Shuvodip Roy in bdNOG 13 ONLINE 18
  • 19. Solution of the Issues with MikroTik There are 2 Possible solution of this currently. • Advertise the 31-Bit Prefix: Solution 1, will be the advertising 31-Bit Prefix 192.0.2.0/31 via Dynamic Routing Protocol in POP/R1 side. • Set the HostMin IP in POP/R1 as 31-Bit: Solution 2, is in POP/R1 declare IP as 192.0.2.1/31 where automatically network will be 192.0.2.0. In Client/R2 set the IP manually as 192.0.2.0 as well as network 192.0.2.1. Thus Point to Point will be reachable also the connected route in POP/R1 will be Redistribute also. Presented By: Shuvodip Roy in bdNOG 13 ONLINE 19
  • 20. 31-Bit in TP-Link TP-Link Routers are mostly used in Home, SOHO link. New firmware and models TP-Link supports RFC3021 and configuration is nothing new. Presented By: Shuvodip Roy in bdNOG 13 ONLINE 20 31-Bit IP configuration in TP-Link
  • 21. Issues with TP-Link old versions Older version TP-Link does not support RFC3021. In that case, through improvisation setup could be possible as figured. Presented By: Shuvodip Roy in bdNOG 13 ONLINE 21 TP-Link 31-Bit configured with improvisation in old version
  • 22. Issues with TP-Link old versions (continue) In the early slide we configured 31-Bit in a old version/model of TP-Link which does not support the RFC3021. In that case, Prefix was 118.179.84.12/31 but as TP-Link does not support it Subnet Mask: 255.255.255.254 or 255.255.255.255 will not be applicable. It will provide following error “The IP Address does not match the Subnet Mask: Invalid host number” Presented By: Shuvodip Roy in bdNOG 13 ONLINE 22
  • 23. Solution of the Issues with TP-Link old versions In 118.179.84.12/31, we need to find a sweet able Subnet Mask where IP: 118.179.84.12 & IP: 118.179.84.13 will not be the Network Address or the Broadcast Address. So, in nearest Subnet Mask 255.255.255.248 or /29 IP: 118.179.84.12 & IP: 118.179.84.13 is not the Network Address or the Broadcast Address. Then Router will accept the IP configuration and 31-Bit will be useable. The nearest Subnet Mask will vary with IP. Caution: There also a side effect brings with this improvisation. As TP- Link get 118.179.84.8/29 as connected Route due to Subnet Mask: 255.255.255.248. So, from this TP-Link except 118.179.84.12 & IP: 118.179.84.13 all IP will be unreachable in 118.179.84.8/29. If the link required reachability in this range then this improvisation will be difficult. Presented By: Shuvodip Roy in bdNOG 13 ONLINE 23
  • 24. Others Home Routers Others Home Router such as Netgear, Asus, Tenda, D-Link etc. are moreover same as TP-Link. The new version in some vendors supports RFC3021 but others are not. Improvisation works but there are side effects of that which already described. Presented By: Shuvodip Roy in bdNOG 13 ONLINE 24
  • 25. 31-Bit in Windows Windows also not support RFC3021. If we set the Subnet Mask 255.255.255.254 it provides following Warning. Presented By: Shuvodip Roy in bdNOG 13 ONLINE 25
  • 26. 31-Bit in Windows (continue) But as improvisation we may use the IP as 32-Bit Prefix, that means Subnet Mask is 255.255.255.255 Presented By: Shuvodip Roy in bdNOG 13 ONLINE 26 31-Bit in Windows
  • 27. 31-Bit in Windows (continue) Although it will also provide following Warning. But, saving this configuration by pressing “Yes” will work for 31-Bit Prefix improvisation in Windows. Thus, smoothly 31-Bit can be useable in Windows. Presented By: Shuvodip Roy in bdNOG 13 ONLINE 27
  • 28. 31-Bit in Linux Adding 31-Bit Prefix is Linux have nothing new. It is usual as like others IP configuration in Linux. Here is a example with Ubuntu 20.10 (Groovy Gorilla) Presented By: Shuvodip Roy in bdNOG 13 ONLINE 28 31-Bit Prefix in Linux
  • 29. Example in Production In my organization Amber IT Limited, we are deploying 31-Bit Prefixes in respect of the concerns of all matters which already described. Plenty of numbers we already deployed in 31-Bit and it’s cost IPv4 resources half rather than where it traditionally does with 30-Bit Prefix. Presented By: Shuvodip Roy in bdNOG 13 ONLINE 29
  • 30. Summary In Exhaustion, RFC3021 is very helpful in deed. There are no doubts IPv6 is the longer time solution. But, different expertise already provide statement that it will require more time to transition fully in to IPv6. In the mean time, we have none other choice but a option RFC3021. Which will provide a relief for Exhaustion of IPv4. The main challenge is primeval Devices and many Vendors still not support the RFC. As it is a matter of Firmware or OS, we may expect soon Vendors will rollout updated Firmware or OS which will support RFC3021. Which will be a great offer for users. It will be also a great relief for Service Providers. Presented By: Shuvodip Roy in bdNOG 13 ONLINE 30
  • 31. Acknowledgement Special thanks for bdNOG committee members for approve my presentation. I would also like to gratefully acknowledge who works and proposed RFC3021. • A. Retana • R. White • Cisco Systems • V. Fuller • GTE Internetworking • D. McPherson • Amber Networks and also to many more. Presented By: Shuvodip Roy in bdNOG 13 ONLINE 31
  • 32. Presented By: Shuvodip Roy in bdNOG 13 ONLINE 32