ICT Smart Solution

Energy solutions, Smart Choice within Reach. By NIYONGABO Olivier

Follow Us

NIYONGABO Olivier.

We Connect You

To All IT Services, Find it in ICT Smart Solution.

Our Services

In The Truth We Are Able To Give You This Services Above.

Our Address

Call Us On That Contact Above.

How to Use XAMPP

0 comments


How to Use XAMPP to Set Up a Local WordPress Site (In 3 Steps)
Last Updated on: June 18th, 2018
Setting up a locally-hosted environment is a crucial step in any WordPress development project. Doing this enables you to safely test your site’s features and functionality, on a site that’s completely private.
In this article, we’ll explore how to use XAMPP to set up a local web server for developing and testing your WordPress site. This involves three steps:
  1. Install XAMPP.
  2. Run XAMPP and configure your environment.
  3. Download and run WordPress.
We’ll also discuss some best practices for experimenting with code and testing WordPress using XAMPP. Finally, we’ll cover how to use XAMPP with a WordPress multisite installation. Let’s dive in!
Why You Might Need a Local WordPress Site
A locally-hosted WordPress site is one that is only accessible by people on your network (that is, there are no live components). As such, this type of site can serve as a safe environment, in which new features and troubleshooting methods can be tested.
Local websites are perfect for performing the following types of tasks:
  • Creating new themes and plugins: When using a local site, you don’t need to worry about any of the issues you might encounter when developing on a live WordPress site.
  • Website staging: You can create a copy of a live website, which can then be used for testing purposes.
  • Site debugging and troubleshooting: Working under the hood of your live site in order to resolve bugs or other issues may lead to bigger problems (and, potentially, costly downtime). By creating a local WordPress site, you can try out various solutions, and easily restore previous versions of your site should you make any mistakes.     
For these reasons, creating a locally-hosted WordPress site is highly recommended for just about any development project. First, however, you’ll need a tool that will make the process of setting up a locally-hosted site quick and easy.
An Introduction to XAMPP
A few crucial ingredients are needed if you want to install WordPress locally. These consist of web server software (such as Apache), programming languages like Perl and PHP, and the database management software – MySQL. Installing each of these elements separately, however, is time-consuming and difficult.
XAMPP (an acronym for cross (x)-platform, Apache, MySQL, PHP, and Perl) enables you to install all these elements quickly and easily. You can then use XAMPP to set up the environment required to run WordPress on a local machine. There, you can test plugins, experiment with themes and coding, and carry out other development activities safely.
XAMPP is free and open-source software, backed-up by a sizable support community. It’s also extremely lightweight, and all the elements required to set up a local web server are contained within a single extractable file. What’s more, learning how to use XAMPP is relatively straightforward, as we’ll discuss in the following XAMPP tutorial.
How to Use XAMPP to Set Up a Local WordPress Site (In 3 Steps)
In the following steps, we’ll walk you through how to use XAMPP and install WordPress on it. For this tutorial, we will be covering the steps for the Mac version of the software. However, XAMPP can also be set up and run relatively easily on both Windows and Linux devices, using a similar process.
Step 1: Install XAMPP
First of all, you’ll need to go to the Apache Friends website, and select the relevant download link on the homepage:
XAMPP Mac Download button
Next, drag XAMPP into your Applications folder:
XAMPP drag to Applications Folder
Once the initial loading sequence is completed, XAMPP will be installed on your system. This part of the setup process doesn’t require much on your end.
It should be mentioned that if you are running XAMPP on Windows, and another program on your machine is using ports 80 or 443, you may encounter a port error. For example, the World Wide Web Publishing Service program commonly uses port 80 and may cause a conflict with XAMPP.
To resolve this, you’ll need to stop that service from running by doing the following things:
  1. Navigate to the Windows Start menu, and type in services.msc.
  2. In the Services window, locate World Wide Web Publishing Service.
  3. Right click on it, and select the Stop button.
  4. Restart XAMPP. The port error will be resolved if World Wide Web Publishing Service was the culprit.
If this doesn’t resolve the issue, it may be caused by your Windows firewall. To forcibly unlock your ports, you will need to set up a new firewall rule:
  1. Open up Windows Firewall and navigate to Advanced Settings.
  2. Go to Inbound > New Rule.
  3. Go to Port > TCP. You’ll have to type 80,443 in the field labelled Specific Ports, then click on Next.
  4. Select Allow the Connection, then click on Next again.
  5. Make sure all listed options are checked and continue to the next page.
  6. In the Name field, type in a memorable name (such as host1) and select Finish.
  7. You’ll now need to repeat steps 1 to 6, changing the name again (i.e. to host2) to clear the port.
  8. Restart your computer. Ports 80 and 443 should now be unblocked and open locally.
Once XAMPP is installed, you’ll be all set to start running XAMPP.
Step 2: Run XAMPP and Configure Your Environment
Now, open up the XAMPP application and hit the Start button. You should see a green light in the upper right-hand corner of the display:
XAMPP Start Button Screenshot
Next, navigate to the Services tab. You will need to ensure that the status of both the Apache and MySQL stack services are running (i.e. that they have a green light). This will ensure that your database management and server software elements are in place for your local environment. For now, you can ignore ProFTPD (which is a configurable File Transfer Protocol server).
If MySQL or Apache are not running (if they display a red light), simply select them and hitStart:
XAMPP Services Menu
Then, switch over to the Network tab. Here, you can define the port forwarding rules between your host machine and your stack. Select the localhost option you wish to work on, and then hit the Enable button. In this example, we will be using localhost:8080:
XAMPP Network Tab Screenshot
You will now be able to access your localhost, and start using XAMPP as a server environment. To do this, open up your preferred web browser, and type in your localhost name (which in our case would be localhost:8080). This will bring up the XAMPP dashboard. Once there, select the phpMyAdmin button in the top right-hand corner of the page:
XAMPP Dashboard phpMyAdmin Button
You’ll then need to create a database for your WordPress installation. To do this, select theDatabase tab, type in a name for your database (in our case, we’ll simply go with WordPress), ensure the next drop-down menu is set to Collation, and then hit Create:
phpMyAdmin Database Tab
After that, you’ll be ready to learn how to install WordPress on XAMPP.
Step 3: Download and Run WordPress
At this point, you’ll need to go to WordPress.org and download the latest version of WordPress:
WordPress.org Download WordPress pageOpen up the WordPress folder on your machine, and locate the wp-sample-config.php file:
The wp-config-sample.php file
Open this file in your preferred text editor (such as TextEdit). You’ll need to locate this line of text:
  • define('DB_NAME', 'database_name_here');
Replace database_name_here with whatever you named your database in the last step. Then, look for these two lines:
  • define('DB_USER', 'username_here');
  • define('DB_PASSWORD', 'password_here');
You’ll need to replace username_here with root, and delete password_here entirely. The resulting text should look like this:
wp-sample-config file
Once you’ve done that, save the file as wp-config.php. You’ll need to ensure that it is placed in the htdocs subfolder within the XAMPP folder. You’ll also need to paste your WordPress install folder into htdocs as well.
Finally, navigate to http://localhost/wp/ in your browser. Once there, follow the standard WordPress installation procedure. When that’s all done, you’ll have a locally-hosted WordPress site ready to go!
How to Set Up WordPress Multisite on XAMPP
Now that you know how to use XAMPP for a single WordPress installation, you may want to use it to create a multisite network. This enables you to create a network of websites that are all managed from a single WordPress installation. There are a lot of applications for a multisite installation. For instance, it presents a useful way to test how your newly-developed themes and/or plugins will function on a variety of sites.
To get started, you’ll need to open up your wp-config.php file in a text editor again. You’ll then need to add the following lines of code at the bottom, right above the line * That’s all, stop editing! Happy blogging. *:
  • define('WP_DEBUG', false);
  • define('WP_ALLOW_MULTISITE', true);
After you’ve ensured that Apache and MySQL are still running on XAMPP, log in to your localhost site. Then, navigate to Tools > Network Setup:
WordPress Tools Network Setup Option
Once you’ve entered a network title, select Install. You will be prompted to edit your wp-config.php and .htaccess files.
Open up your wp-config.php file once more. You’ll need to add the following code beneath the lines you added previously:
  • define('MULTISITE', true);
  • define('SUBDOMAIN_INSTALL', false);
  • define('DOMAIN_CURRENT_SITE', 'localhost');
  • define('PATH_CURRENT_SITE', '/');
  • define('SITE_ID_CURRENT_SITE', 1);
  • define('BLOG_ID_CURRENT_SITE', 1);
Next, you’ll need to open up (or create) your .htaccess file in the same directory as your wp-config.php file. Then, replace all the existing lines in that file with the following snippet:
  • # BEGIN WordPress
  • RewriteEngine On
  • RewriteBase /
  • RewriteRule ^index\.php$ - [L]
  •  
  • # add a trailing slash to /wp-admin
  • RewriteRule ^([_0-9a-zA-Z-]+/)?wp-admin$ $1wp-admin/ [R=301,L]
  •  
  • RewriteCond %{REQUEST_FILENAME} -f [OR]
  • RewriteCond %{REQUEST_FILENAME} -d
  • RewriteRule ^ - [L]
  • RewriteRule ^([_0-9a-zA-Z-]+/)?(wp-(content|admin|includes).*) $2 [L]
  • RewriteRule ^([_0-9a-zA-Z-]+/)?(.*\.php)$ $2 [L]
  • RewriteRule . index.php [L]
  •  
  • # END WordPress
Save the file and close it. Now, you should be able to access individual sites in your dashboard when you log in to your local WordPress installation.
What to Do With Your Local WordPress Installation
Once you know how to use XAMPP and have a local WordPress site to experiment on, what you do next will largely depend on the kind of development project you’re embarking on. To get you started, WordPress.org offers a great beginner’s guide on how to test drive WordPress.
If you’re interested in theme development, you may want to see our guide on how to develop a WordPress theme, or check out such sites as Theme Shaper. Using your local environment, you can safely edit your files to experiment with new themes and their associated functionality.
If you want to learn how to use XAMPP and WordPress together to test your coding knowledge and gain more PHP experience, there are a number of helpful guides for that as well. BitDegree and Code Academy both offer an excellent variety of tutorials that cover PHP and HTML fundamentals, plus much more.
While using your local WordPress installation for development, you’ll also want to have resources at hand for troubleshooting and honing your skills. Stack Exchange is a thriving online forum where you can pose questions to the WordPress development community, as well as gain invaluable insights. Finally, you’ll probably want to become a regular on theWordPress.org support forum.
Conclusion
As we have seen, XAMPP is a powerful and versatile solution for setting up a local web server. It presents a perfect way to create an environment for basic WordPress coding, experimenting with multisite settings, tweaking themes, and much more. Though it is not the only tool that you can use. A great alternative is setting up WordPress using Docker.
Do you have any questions about how to use XAMPP or your new local WordPress site? Let us know in the comments section below!


How To Post On Instagram Computer From 2018 By NIYO-Olivier

0 comments

You can post on Instagram by using you computer with out any software some they thing is impossible try it you self it possible!!!   

How To Subnet IPv6

0 comments


How To Subnet IPv6

IPv6 is going to replace IPv4. The simple reason is that IPv4 address space is running out. The world has reached the point where there are not enough 32 bit addresses to link every device which wants to connect to the Internet. IPv6 uses 128 bits. Much larger. Much much larger. IPv6 allows almost 8*1028 times as many addresses as IPv4. Basically, a number too large for the human mind to grasp.
Because of the enormity of IPv6 address space, subnetting will change. Currently we use CIDR and VLSM and NAT and other tools to conserve as much IPv4 space as possible. With IPv6 this is no longer a concern. The smallest subnet that is recommended for use in IPv6 is a /64! This means that even if you have 200 devices on a single /64, you still have 264-200 of unused space.
Because of the scale of IPv6, one no longer really worries about how many hosts are on a subnet. Rather the concern is how many subnets fit within a certain network. If you have a /48, how many /64s can you place inside this /48? These are the questions that IPv6 subnetting asks. Try IPv6 Subnetting.
IPv6 is written in hexadecimal which uses the digits 0-9 and a-f. A hexadecimal digit represents 4 bits, or 16 decimal units. Each IPv6 address is represented by eight groups of four hexadecimal digits. These groups are separated by colons. An example may be: 2001:0db8:2231:aaec:0000:0000:4a4a:2100. Try practicing binary.
Even though these addresses are written in hexadecimal units, they are still large and cumbersome. There are a couple of ways to shorten them. One or more leading zeros from each group can be dropped. A consecutive set of groups with only zeros can be replaced with ::. The above address can be written as: 2001:db8:2231:aaec::4a4a:2100.
Note that the :: should only be used on more than one section of zeros, and can only be used once per address. 2001::ab32:: is not a valid address because we do not know how many sets of zeros are in each :: group. The address could be 2001:0000:0000:ab32:0000:0000:0000:0000 or it could be 2001:0000:0000:0000:0000:ab32:0000:0000.
Though the representation of the numbers is different, the computer still uses binary to do the actual subnetting. The binary math is the same, it is just using larger numbers. There is still a network portion and a host portion of every address.
IPv6 does not use network addresses or broadcast addresses. An address where the host bits are all 0s or all 1s is still valid!
We also do not use subnet masks for IPv6. Everything is written in slash notation. In IPv6 the first 48 bits are used for networking and routing. The next 16 and used to define subnets. The last 64 and used to identify a host.
With IPv6 is that every device can create a unique link local address based on the MAC address of the device. What one does is inset 0xFFEE into the middle of the MAC address. This changes the MAC address to 64-bits from 48-bits. The other thing that needs to happen is to flip the 7th bit. A link local unicast address is fe80::/10

The Quick and Easy
The number of subnetting bits is the new prefix length minus the original prefix length. So there are 4 subnetting bits when a /48 is broken into /52s (52-48=4).
The number of subnets possible with x subnetting bits is 2x. So if we have 4 subnetting bits, then we can create 24=16 new subnets.
::1/128 is the loopback address.
::FFFF:0:0/96 are the IPv4-mapped addresses.
fe80::/10 are the link-local unicast.
2001:db8::/32 are the documentation addresses.
ff00::/8 are multicast addresses

Our subnetting cheatsheet includes IPv6.

Correct IPv6 Notation
IPv6 addresses should be written a certain way. This will make interpreting the addresses faster and easier, both for humans and for computer programs.
Leading zeros must be removed. 2001:0db8::0001 must be written as 2001:db8::1.
"::" must be used to represent the largest number of 16-bit sets of zero as possible.
If there are multiple places where "::" can be used, and the numbers of zeros are the same, use "::" on the leftmost set of zeros
"::" cannot be used to shorten a single 16-bit set of zeros.
Letters in an IPv6 address should be written in lowercase.
To represent port numbers, wrap an IPv6 address in square brackets then followed by a colon and the port number as [2001:db8::1]:80
For more information see RFC5952.


OSPF

0 comments

OSPF (Open Shortest Path First)  

OSPF (Open Shortest Path First) is a link state routing protocol. Because it is an open standard, it is implemented by a variety of network vendors. OSPF will run on most routers that don’t necessarily have to be Cisco routers (unlike EIGRP which can be run only on Cisco routers).   OSPF is a classless routing protocol that supports VLSM and CIDR, manual route summarization, incremental updates, equal cost load balancing and many other useful features. OSPF uses only one parameter as the metric, namely interface cost. The administrative distance of OSPF routes is, by default, 110. OSPF uses multicast addresses 224.0.0.5 and 224.0.0.6 for routing updates.   Routers running OSPF have to establish neighbor relationships before exchanging routes. Because OSPF is a link state routing protocol, neighbors doesn’t exchange routing tables. Instead, they exchange information about network toplogy. Each OSFP router then runs SFP algorithm to calculate the best routes and adds those to the routing table. Because each router knows the entire topology of a network, a chance for a routing loop to occur is minimal.   Each OSPF router stores routing and topology information in three tables: •    Neighbor table – stores information about OSPF neighbors  •    Topology table – stores the topology structure of a network •    Routing table –  stores the best routes
OSPF neighbors
OSPF routers need to establish a neighbor relationship before exchanging routing updates. OSPF neighbors are dynamically discovered by sending Hello packets out each OSPF-enabled interface on a router. Hello packets are sent to the multicast IP address of 224.0.0.5.   The process is explained in the following figure: 
 
  Routers R1 and R2 are directly connected. After OSFP is enabled both routers send Hellos to each other to establish a neighbor relationship. You can verify that the neighbor relationship has indeed been established by typing the show ip ospf neighbors command. 
   In the example above, you can see that the router-id of R2 is  2.2.2.2. Each OSPF router is assigned a router ID. A router ID is determined by using one of the following:   1.    Using the router-id command under the OSPF process 2.    Using the highest IP address of the router’s loopback interfaces 3.    Using the highest IP address of the router’s physical interfaces   The following fields in the Hello packets must be the same on both routers in order for routers to become neighbors:
 subnet  area id  hello and dead interval timers  authentication  area stub flag  MTU

By default, OSPF sends hello packets every 10 second on an Ethernet network (Hello interval). A dead timer is four times the value of the hello interval, so if a routers on an Ethernet network doesn’t receive at least one Hello packet from an OSFP neighbor for 40 seconds, the routers declares that neighbor „down“.
OSPF neighbor states
Before establishing a neighbor relationship, OSPF routers need to go through several state changes. These states are explained below.   1. Init state – a router has received a Hello message from the other OSFP router 2. 2-way state – the neighbor has received the Hello message and replied with a Hello message of his own 3. Exstart state – beginning of the LSDB exchange between both routers. Routers are starting to exchange link state information. 4. Exchange state – DBD (Database Descriptor) packets are exchanged. DBDs contain LSAs headers. Routers will use this information to see what LSAs need to be exchanged. 5. Loading state – one neighbor sends LSRs (Link State Requests) for every network it doesn’t know about. The other neighbor replies with the LSUs (Link State Updates) which contain information about requested networks. After all the requested information have been received, other neighbor goes through the same process 6. Full state – both routers have the synchronized database and are fully adjacent with each other.
OSPF areas
OSPF uses the concept of areas. An area is a logical grouping of contiguous networks and routers. All routers in the same area have the same topology table, but they don’t know about routers in the other areas. The main benefits of creating areas is that the size of the topology and the routing table on a router is reduced, less time is required to run the SFP algorithm and routing updates are also reduced.   

Each area in the OSPF network has to connect to the backbone area (area 0). All router inside an area must have the same area ID to become OSPF neighbors. A router that has interfaces in more than one area (area 0 and area 1, for example) is called Area Border Router (ABR). A router that connects an OSPF network to other routing domains (EIGRP network, for example) is called Autonomous System Border Routers (ASBR).   NOTE – in OSPF, manual route summarization is possible only on ABRs and ASBRs.   To better understand the concept of areas, consider the following example.
 All routers are running OSPF. Routers R1 and R2 are inside the backbone area (area 0). Router R3 is an ABR, because it has interfaces in two areas, namely area 0 and area 1. Router R4 and R5 are inside area 1. Router R6 is an ASBR, because it connects OSFP network to another routing domain (an EIGRP domain in this case). If the R1’s directly connected subnet fails, router R1 sends the routing update only to R2 and R3, because all routing updates all localized inside the area.

 NOTE – the role of an ABR is to advertise address summaries to neighboring areas. The role of an ASBR is to connect an OSPF routing domain to another external network (e.g. Internet, EIGRP network…).
LSA, LSU and LSR
The LSAs (Link-State Advertisements) are used by OSPF routers to exchange topology information. Each LSA contains  routing and toplogy information to describe a part of an OSPF network. When two neighbors decide to exchange routes, they send each other a list of all LSAa in their respective topology database. Each router then checks its topology database and  sends a Link State Request (LSR) message requesting all LSAs not found in its topology table. Other router responds with the Link State Update (LSU) that contains all LSAs requested by the other neighbor.   The concept is explained in the following example:
    After configuring OSPF on both routers, routers exchange LSAs to describe their respective topology database. Router R1 sends an LSA header for its directly connected network 10.0.1.0/24. Router R2 check its topology database and determines that it doesn’t have information about that network. Router R2 then sends Link State Request message requesting further information about that network. Router R1 responds with Link State Update which contains information about subnet 10.0.1.0/24 (next hop address, cost…). 

Open Shortest Path First (OSPF) Protocol Configuration
Router(config)# router ospf process_ID Router(config-router)# network network_id wildcard_mask area area_#
Note:
Process id: A value in the range 1–65,535 identifies the OSPF Process ID. OSPF Process ID is a unique number on this router that groups a series of OSPF configuration commands under a specific running process.
Wildcard Mask: The wildcard mask (wildcard_mask) given above is the inverse mask of the subnet mask. A 0 octet in the wildcard mask indicates that the corresponding octet in the network must match exactly. On the other hand, a 255 indicates that you don’t care what the corresponding octet is in the network number. A network and wildcard mask combination of 192.168.10.0 0.0.0.0 would match 192.168.10.0 only, and nothing else.
Area Number: The area_# given above is the Area Number. Area Number can always be zero (0) for small networks, but for larger networks, the Area Number need to be properly planned as all routing updates must traverse Area 0. 
Open Shortest Path First (OSPF) Protocol - Lab Practice
The following diagram shows our lab setup. We have three routers, three switches and three hosts connected as below. The host names, IP addresses and the interfaces of the routers are shown in diagram. The IP addresses of the hosts are also shown in the diagram.
 
Hostname and IP address configuration in Router01
Connect to Router01 console and use the following IOS commands to configure host name as Router01.
Router>enable Router#configure terminal Enter configuration commands, one per line.  End with CNTL/Z. Router(config)#hostname Router01 Router01(config)#
Use the following IOS commands to open the fast ethernet interface Fa0/0 configuration mode on Router01 and configure IP address as 172.16.0.1/16.
Router01>enable Router01#configure terminal Enter configuration commands, one per line.  End with CNTL/Z. Router01(config)#interface fa0/0 Router01(config-if)#ip address 172.16.0.1 255.255.0.0 Router01(config-if)#no shutdown
Use the following IOS commands to open the serial interface S0/0 configuration mode on Router01 and configure IP address as 172.17.0.1/16. You have to set a clock rate also using the "clock rate" command on S0/0 interface, since this is the DCE side.
                 

Router01>enable Router01#configure terminal Enter configuration commands, one per line.  End with CNTL/Z. Router01(config)#interface s0/0 Router01(config-if)#clock rate 64000 Router01(config-if)#ip address 172.17.0.1 255.255.0.0 Router01(config-if)#no shutdown
Do remember to run the "copy running-config startup-config" command from enable mode, if you want to save the changes you have made in the router.
Hostname and IP address configuration in Router02
Connect to Router02 console and use the following IOS commands to configure host name as Router02.
Router>enable Router#configure terminal Enter configuration commands, one per line.  End with CNTL/Z. Router(config)#hostname Router02 Router02(config)#
Use the following IOS commands to open the fast ethernet interface Fa0/0 configuration mode on Router02 and configure IP address as 172.18.0.1/16.
                   Router02>enable  Router02#configure terminal Enter configuration commands, one per line.  End with CNTL/Z. Router02(config)#interface fa0/0 Router02(config-if)#ip address 172.18.0.1 255.255.0.0 Router02(config-if)#no shutdown
Use the following IOS commands to open the serial interface S0/0 configuration mode on Router02 and configure IP address as 172.17.0.2/16.
Router02>enable Router02#configure terminal Enter configuration commands, one per line.  End with CNTL/Z. Router02(config)#interface s0/0 Router02(config-if)#ip address 172.17.0.2 255.255.0.0 Router02(config-if)#no shutdown
Use the following IOS commands to open the serial interface S0/1 configuration mode on Router02 and configure IP address as 172.19.0.1/16. You have to set a clock rate also using the "clock rate" command on S0/1 interface, since this is the DCE side.

Router02>enable Router02#configure terminal Enter configuration commands, one per line.  End with CNTL/Z. Router02(config)#interface s0/1 Router02(config-if)#clock rate 64000 Router02(config-if)#ip address 172.19.0.1 255.255.0.0 Router02(config-if)#no shutdown
Do remember to run the "copy running-config startup-config" command from enable mode, if you want to save the changes you have made in the router.
Hostname and IP address configuration in Router03
Connect to Router03 console and use the following IOS commands to configure host name as Router03.
Router>enable Router#configure terminal Enter configuration commands, one per line.  End with CNTL/Z. Router(config)#hostname Router03 Router03(config)#
Use the following IOS commands to open the fast ethernet interface Fa0/0 configuration mode on Router03 and configure IP address as 172.20.0.1/16.
Router03>enable Router03#configure terminal Enter configuration commands, one per line.  End with CNTL/Z. Router03(config)#interface fa0/0 Router03(config-if)#ip address 172.20.0.1 255.255.0.0 Router03(config-if)#no shutdown
Use the following IOS commands to open the serial interface S0/1 configuration mode on Router03 and configure IP address as 172.19.0.2/16.
Router03>enable Router03#configure terminal Enter configuration commands, one per line.  End with CNTL/Z. Router03(config)#interface s0/1 Router03(config-if)#ip address 172.19.0.2 255.255.0.0 Router03(config-if)#no shutdown
Do remember to run the "copy running-config startup-config" command from enable mode, if you want to save the changes you have made in the router.

Open Shortest Path First (OSPF) Protocol configuration in Router01
Connect to Router01 console and use the following IOS commands to configure Open Shortest Path First (OSPF) Protocol in Router01. Please refer the beginning of this lesson to view the Open Shortest Path First (OSPF) Protocol configuration IOS commands.
Using the IOS "network" command, as shown below, we specify only the directly connected networks of this router.
Router01>enable Router01#configure terminal Enter configuration commands, one per line.  End with CNTL/Z. Router01(config)#router ospf 1 Router01(config-router)#network 172.16.0.0 0.0.255.255 area 0 Router01(config-router)#network 172.17.0.0 0.0.255.255 area 0 Router01(config-router)#exit Router01(config)#exit Router01#
Do remember to run the "copy running-config startup-config" command from enable mode, if you want to save the changes you have made in the router.
Open Shortest Path First (OSPF) Protocol configuration in Router02
Connect to Router02 console and use the following IOS commands to configure Open Shortest Path First (OSPF) Protocol in Router02. Please refer the beginning of this lesson to view the Open Shortest Path First (OSPF) Protocol configuration IOS commands.
Using the IOS "network" command, as shown below, we specify only the directly connected networks of this router.
Router02> Router02>enable Router02#configure terminal Enter configuration commands, one per line.  End with CNTL/Z. Router02(config)#router ospf 1 Router02(config-router)#network 172.17.0.0 0.0.255.255 area 0 Router02(config-router)#network 172.18.0.0 0.0.255.255 area 0 Router02(config-router)#network 172.19.0.0 0.0.255.255 area 0 Router02(config-router)#exit Router02(config)#exit
Do remember to run the "copy running-config startup-config" command from enable mode, if you want to save the changes you have made in the router.

Open Shortest Path First (OSPF) Protocol configuration in Router03
Connect to Router03 console and use the following IOS commands to configure Open Shortest Path First (OSPF) Protocol in Router03. Please refer the beginning of this lesson to view the Open Shortest Path First (OSPF) Protocol configuration IOS commands.
Using the IOS "network" command, as shown below, we specify only the directly connected networks of this router.
                   Router03>enable Router03#configure terminal Enter configuration commands, one per line.  End with CNTL/Z. Router03(config)#router ospf 1 Router03(config-router)#network 172.19.0.0 0.0.255.255 area 0 Router03(config-router)#network 172.20.0.0 0.0.255.255 area 0 Router03(config-router)#exit Router03(config)#exit Router03#
Do remember to run the "copy running-config startup-config" command from enable mode, if you want to save the changes you have made in the router.
How to view the routing table in Router01
After the initial configuration and Open Shortest Path First (OSPF) Protocol configuration in all routers, we can use the "show ip route" to view the routing table in Router01, 


NIYONGABO Olivier
niyolivier90@gmail.com

https://www.youtube.com/watch?v=M43Sh0UiBxg&t=27s

Energy Solution, Smart Choice Within Reach

 
ICT Smart Solution © 2017-2019 | Designed by NIYONGABO Olivier