BeCode Network Module - One Simple Network

• 3 PCs
• 1 switch
• 1 router
• 1 DNS

• 1 external router
• 1 web server

The 3 PCs are linked to the switch's first 3 ports (FastEthernet 0/1 0/2 0/3) through their FastEthernet0 port. I've attributed the ips/subnets masks to the PCs' interfaces as instructed and made sure the interfaces were up on both them and the switch.

The local router's GigabitEthernet 0/0/0 port is linked to the switch's GigabitEthernet 0/1 port.

The router's interface is configured with the following ip/subnet mask : 192.168.1.1 /255.255.255.0.

Again I made sure the ports are ON.

The router's ip can now be set as the default gateway for the 3 PCs.

With this, pings between the local router and the PCs are possible.

The external router's GigabitEthernet 0/0/0 port is linked to the webserver's FastEthernet0 port.

The router's interface is configured with the following ip/subnet mask : 192.140.1.1 / 255.255.255.0.

The server's interface is configured with the following ip/subnet mask : 192.140.1.10 / 255.255.255.0 and it's default gateway is 192.140.1.1.

Again I made sure the ports are ON.

The external router can now ping the webserver.

The routers are linked together through their GigabitEthernet 0/0/1 port.

The local router's interface is configured with the following ip/subnet mask : 192.168.2.1 / 255.255.255.0.

The external router's interface is configured with the following ip/subnet mask : 192.168.2.2 / 255.255.255.0.

Again I made sure the ports are ON.

The routers can now ping each other. But a this point the PCs can't communicate with the webserver or even the external router so adding static routes is necessary.

First on the local router with a route to reach network 192.140.1.0 with the mask 255.255.255.0 through next hop which is 192.168.2.2.

Then on the external router with a route to reach network 192.168.1.0 with the mask 255.255.255.0 through next hop which is 192.168.2.1.

The PCs can now reach the webserver on another network. If we use a browser on a PC and try to reach 192.140.1.10, the default cisco packet tracer webpage will be displayed.

But users mostly use domain names. Let's say the domain name of this site is www.helloworld.com. If we try to reach it we get a "Host Name Unresolved" error. It's because our network doesn't know which ip is behind this domain name. So we're gonna add a local DNS server to help us.

The DNS server will be linked through its FastEthernet0 port to the switch's FastEthernet 0/20 port.

It is configured with the following ip/subnet mask : 192.168.1.254 / 255.255.255.0. It's default gateway is 192.168.1.1.

Again I made sure the ports are ON.

The DNS server can now be reached by other end devices.

I've enabled the DNS service on the DNS server and I've added an entry with the name www.helloworld.com which has the address 192.140.1.10.

Then I've configured all the end devices with 192.168.1.254 as the DNS server address.

That's it ! www.helloworld.com can now be reached through the browser of the PCs.