How do you simulate 'the internet' in Packet Tracer 5?

I've searched the forums, help files and Google but cant find an answer to this one. I see that you can add a 'cloud' device, but since I've just starting to learn about DLCIs and Frame Relay I'm not sure how to set this virtual device up in PT to simulate the internet, if indeed you can simulate it at all?

Is this one of PT's many weaknesses? Is it possible?

Thanks chaps!

Find more posts tagged with

Comments

Bl8ckr0uter

nelsonnr wrote: »

I've searched the forums, help files and Google but cant find an answer to this one. I see that you can add a 'cloud' device, but since I've just starting to learn about DLCIs and Frame Relay I'm not sure how to set this virtual device up in PT to simulate the internet, if indeed you can simulate it at all?

Is this one of PT's many weaknesses? Is it possible?

Thanks chaps!

IF you are inside of PT look towards the bottom where you can add things from. Look for WAN emulation and click on it. You will see a cloud.

nelsonnr

Thanks knwminus, I managed to get that far. I'm not sure how to setup the cloud device though to emulate the internet.

Do you simply add a 'public' IP address to a serial interface and then send packets to that interface? I suppose that would work hey? Guess I just want to emulate a network outside my private address range to force the packets out the default gateway.

Bl8ckr0uter

nelsonnr wrote: »

Thanks knwminus, I managed to get that far. I'm not sure how to setup the cloud device though to emulate the internet.

Do you simply add a 'public' IP address to a serial interface and then send packets to that interface? I suppose that would work hey? Guess I just want to emulate a network outside my private address range to force the packets out the default gateway.

Not sure about that one. I will take a look later tonight.

ccnacertified2000

There is no such thing as a simulation of the Internet. The Internet consist of a bunch of servers, routers, switches, transport platforms, and many other various devices all connected to one another and shares routes using various routing protocols. Different companies have their own network that they manage called an "autonomous system" from here on referred to as AS. Within this AS, a series of routers, switches, servers, etc are connected together, including but not limited to your own PC. Also within this AS, the network is configured with some form of routing protocol so that every device (hopefully) within the network is able to reach any other computer in the AS.

You are within such an AS, although specifically, your PC are within you ISP's customer network AS. The Internet therefore consists of your PC, your AS, and by applying this rule to others, also consists of other people's PCs like yours, the AS they're in, and such.

So we've established that every computer on the internet is in some AS. We've also established that every computer in every AS is connected to every computer within their AS by way of a routing protocol within their AS.

To connect every computer on the internet to another computer on the internet, we need to route between different AS. So each AS is connected to another Peering site where various AS's have a connection to and share routing information. This routing protocol is called BGP (border gateway protocol). It is the protocol that shares routes between ASes on the internet so that different ASes can reach other ASes. This routing protocol helps establish a route between your computer to any other computer in the internet.

Thats the Internet.

SO PT is a simulation. Looking at the above of what is the Internet, you can see that there are no such thing as simulating the Internet, rather you simulate pieces of the internet. And looking at the list of things needed to simulate all of the pieces, you will see that some pieces are not available in PT.

The Cloud in PT is a simulation of your ISP's layer 1 and layer 2 device. So it simulates the fact that you may use cable or DSL to connect to the internet, and simulates companys' use of frame relay etc. It does not simulate the other end of the connection being the internet. Your cable or dsl modem connects to a router of some sorts at the ISP's end, to simulate this in PT, you would need to have a router connected to the cloud along with the dsl modem and such.
If you want to model the entire internet, that means you would need to create a bunch of routers and connect them to simulate different ASes. If you want, you could cluster these routers so that it looks like a cloud. The idea of the cloud is that it is a bunch of devices.

I'm too tired to type more....so i'll leave it at that.

sandman748

Here's how we did it in class.

Add another router named ISP (or whatever) and connect it to the router in your local network you want the traffic to pass through.

Put the passive interface command on the interface connected to the ISP router in order to suppress your routing updates.

Put a static route 0.0.0.0 0.0.0.0 to the ISP router and redistribute that route to the other routers in your LAN.

From here, all of your routers will forward the data out to the "internet." In order for that data to return you'll need to have NAT set up. If you want your local hosts to ping "websites" you can either use loopbacks on the ISP router or servers attached to it. You'll also need to set up a local DNS server to convert the url's to the ip address of the loopbacks/servers. The cool thing about using servers instead of the loopback is that you can actually go into the browser of your local hosts and browse to those websites. This comes in handy if you want to set up ACL's where you can test connectivity by pinging but still block web traffic.

This may not simulate the actual routing outside of your network but it does simulate what you need to do to get your local network communicating with the WAN. Add in your own DHCP server and you've got a fairly decent lab setup that covers most of the communicating with WAN topics.

nelsonnr

Very very very helpful analysis ccnacertified2000 and thanks so much for typing such a great reply when you were tired. Really appreciate that. It has really helped on re-briefing me about AS's and what the internet is in a physical sense as a cloud. I reckon someone should pay you for that paragraph as an entry into a training book!

sandman - thanks to you too. Thats how I'm beginning to set it up on PT5. I'm needing this for CBT Nuggets video 3 where Jeremy is beginning to implement the static route out to the 'internet'. In his video he does actually have the internet in his lab (he pings 4.2.2.2) and I was wanting to work out how I could replicate it to a certain degree. Your solution sounds ace so will set it up.

mrengineer

sandman748 wrote: »

Here's how we did it in class.

Add another router named ISP (or whatever) and connect it to the router in your local network you want the traffic to pass through.

Put the passive interface command on the interface connected to the ISP router in order to suppress your routing updates.

Put a static route 0.0.0.0 0.0.0.0 to the ISP router and redistribute that route to the other routers in your LAN.

From here, all of your routers will forward the data out to the "internet." In order for that data to return you'll need to have NAT set up. If you want your local hosts to ping "websites" you can either use loopbacks on the ISP router or servers attached to it. You'll also need to set up a local DNS server to convert the url's to the ip address of the loopbacks/servers. The cool thing about using servers instead of the loopback is that you can actually go into the browser of your local hosts and browse to those websites. This comes in handy if you want to set up ACL's where you can test connectivity by pinging but still block web traffic.

This may not simulate the actual routing outside of your network but it does simulate what you need to do to get your local network communicating with the WAN. Add in your own DHCP server and you've got a fairly decent lab setup that covers most of the communicating with WAN topics.

sandman, are you talking about realtime simulation with physical equipments, or using the packet tracer emulator??

billscott92787

Some people even set up a loopback interface on the particular "Gateway" route and then set up a static route to 0.0.0.0 0.0.0.0 ip address of next hop here.

really the WAN cloud is more of like a Frame relay. You could set it up with a router then the cloud then another Route, and set up frame relay between the two. It really depends on how you want to do it.

sotir1984

I am also studying for the CCNA. How i simulated ISP so i can work with the videos was: I connected Jeremy's R1(interface E0/1 with public ip (68.110.171.9)

with a router that i named ISP (interface FE 0/0 ip 68.110.171.97) On R1 i've enabled NAT (using of course 68.110.171.9)

and on the ISP router i have set an ACL that only allows traffic from that adress. Now on the side behind ISP router i have set switch, couple of PC's/server's one of them has IP 4.2.2.2

I am still learning how to set the servers in PT to act as web servers mail servers etc. I think for the CCNA this will be enough.

wrwarwick

If you really wanted to get fancy you can use GNS3 and actually connect it to the Internet. I have played around and created virtual GNS3 networks that can ping 4.2.2.2, 8.8.8.8, google.com, etc.

MrRyte

I thought that there was some type of "WAN cloud" that you could select....

asoft

Don't get carried away with different scenarios. It is very easy to drift when studying for CCENT/CCNA and get into BGP, etc. These topics are covered well in CCNP and CCIE. Stick to exam objectives and learn thoroughly within the scope of the exam unless one has lot of time to experiment. Various certs are developed such that a candidate will learn progressively and achieve Expert level knowledge and skills over a period of time.

djfunz

wrwarwick wrote: »

If you really wanted to get fancy you can use GNS3 and actually connect it to the Internet. I have played around and created virtual GNS3 networks that can ping 4.2.2.2, 8.8.8.8, google.com, etc.

I was a skeptic in the beginning but have come to love GNS3. It takes a few days to iron out all the confusion but I think it's worth it.

I spent a few hours, researched Loopback adapters, and just gave it a IP and default gateway. Enabled network sharing on my Ethernet adapter and connected a router to the Loopback IP address. There is a nice Video on how to do it on Youtube here:

Connecting GNS3 to the internet Part 1 - YouTube

savedlema

ccnacertified2000

You're a great man! I landed here from Google search, and what a great explanation! As the other said, you deserve to be paid for this! (May be you write a book.)

Thank you very much for this.

theodoxa

MrRyte wrote: »

I thought that there was some type of "WAN cloud" that you could select....

Yes, but I've never been able to get it to work correctly. I just add an ISP router. It's much easier than trying to figure out Packet Tracer's convoluted WAN Cloud.

theodoxa

djfunz wrote: »

I was a skeptic in the beginning but have come to love GNS3. It takes a few days to iron out all the confusion but I think it's worth it.

I spent a few hours, researched Loopback adapters, and just gave it a IP and default gateway. Enabled network sharing on my Ethernet adapter and connected a router to the Loopback IP address. There is a nice Video on how to do it on Youtube here:

Connecting GNS3 to the internet Part 1 - YouTube

Connecting GNS to your home network [and thusly the internet] isn't too difficult. I wish Packet Tracer had this ability. Though, I have heard murmurs of people trying to create something for just this purpose.