TROUBLESHOOTING IPV4 & IPV6 STATIC

ROUTES
Submitted by
BHARGAV CH (17351-EC-006)
SATYANARAYANA G (17351-EC-042)
SAI DEEPAK D (17351-EC-039)
PRAVEEEN M (17351-EC-034)

Under the Esteemed Guidance of

Mr. T. Vijaya Kanth, M.Tech., MISTE Mr. T. Narendra Kumar, M.Tech.,
Assistant professor in ECE department Assistant professor in ECE department

DIPLOMA IN ELECTRONICS AND COMMUNICATION ENGINEERING

ACADEMIC YEAR:2019-2020
 CONTENTS
• Introduction to the project
• Topology Diagram
• Address Table
• Part-a Snap
• Part- b Snap
• Result Snaps
• Final Code
• Conclusion
 ABSTRACT
Static routes are manually configured and define an explicit path
between two networking devices.configuring an ipv6 static route
is very similar to ipv4 except that the command is now ipv6
route.ipv6 enabled on atleast one interface
Ipv6 also has a default static route similar to the ipv4 quad zero
(0.0.0.0) static default route.instead,the ipv6 command user
the ::/0 notation to specify all networks.for example,a default
static route as specified by the "::/0" entry is configured on
router R2 to reach all other networks connected to R1
 INTRODUCTION
Static Routes
Networking devices forward packets using route information that is
either manually configured or dynamically learned using a routing
protocol. Static routes are manually configured and define an
explicit path between two networking devices. Unlike a dynamic
routing protocol, static routes are not automatically updated and
must be manually reconfigured if the network topology changes.
The benefits of using static routes include security and resource
efficiency. Static routes use less bandwidth than dynamic routing
protocols and no CPU cycles are used to calculate and communicate
routes. The main disadvantage to using static routes is the lack of
automatic reconfiguration if the network topology changes.
TOPOLOGY DIAGRAM
 ADDRESSING TABLE

Device Interface IP Address Default Gateway

192.168.0.1/25
2001:DB8:ACAD::1/64
HQ G0/1 FE80::1 link-local N/A

10.1.1.2/30
S0/0/0 (DCE) 2001:DB8:ACAD:20::2/64 N/A

192.168.0.253/30
S0/0/1 2001:DB8:ACAD:2::1/64 N/A

172.16.3.1/24
2001:DB8:ACAD:30::1/64
ISP G0/0 FE80::1 link-local N/A

10.1.1.1/30
S0/0/0 2001:DB8:ACAD:20::1/64 N/A
 192.168.1.1/24
2001:DB8:ACAD:1::1/64
BRANCH G0/1 FE80::1 link-local N/A
192.168.0.254/30
S0/0/0 (DCE) 2001:DB8:ACAD:2::2/64 N/A
192.168.2.1/24
2001:DB8:ACAD:2::1/64
SUB BRANCH G0/0 FE80::1 link-local N/A
S1 VLAN 1 N/A N/A
S3 VLAN 1 N/A N/A
192.168.0.3/25 192.168.0.1
PC-A NIC 2001:DB8:ACAD::3/64 FE80::1
192.168.0.2/25 192.168.0.1
PC-B NIC 2001:DB8:ACAD::2/64 FE80::1
192.168.0.4/25 192.168.0.1
LP-1 NIC 2001:DB8:ACAD::1/64 FE80::1
172.16.3.3/24 172.16.3.1
Web Server NIC 2001:DB8:ACAD:30::3/64 FE80::1
192.168.2.3/24 192.168.2.1
PC-C NIC 2001:DB8:ACAD:2::3/64 FE80::1
SNAP
SNAP
SNAP
IN PROGRESS
RECEIVED DESTINATION
COMMAND PROMPT
 FINAL CODE
HQ
Ip classless
ip route 172.16.3.0 255.255.255.0 10.1.1.1
ip route 192.168.1.0 255.255.255.0 192.16.0.254
ip route 192.168.1.0 255.255.255.0 10.1.1.1
!
ip flow-export version 9
!
ipv6 route 2001:DB8:ACAD:30::/64 2001:FB8:ACAD::20
ipv6 route 2001:DB8:ACAD:30::/64 2001:DB8:ACAD::20:2
ipv6 route 2001:DB8:ACAD:1::/64 2001:DB8:ACAD:2::2
ISP
ip classless
ip route 192.168.1.0 255.255.255.0 10.1.1.2
ip route 192.168.0.0 255.255.255.0 10.1.1.2
!
ip flow-export version 9
!
ipv6 route 2001:DB8:ACAD::/62 2001:DB8:ACAD:20::2
BRANCH
ip classless
!
!
Ip route 0.0.0.0 0.0.0.0
 CONCLUSION
Hence Networking devices forward packets using route
information that is either manually configured or dynamically
learned using a routing protocol.
THANK YOU