IP Address Question (CISCO Packet Tracer)

Sylice

Why cant an ip address of 192.168.1.121 ping an ip address of 192.168.2.204?

Find more posts tagged with

Free for TechExams community: Cybersecurity salary guide

Compare cert salaries and plan your next career move

Button

Comments

mikeybinec

What's the subnet mask? Assuming that the 192.168.1.x and the 192.168.2.x have the same /24 subnet mask, they are in different networks and can't see each other. The members of the 1.x are in the range of 1.1 - 1.254 etc for the 2.x club

Sylice

mikeybinec wrote: »

What's the subnet mask? Assuming that the 192.168.1.x and the 192.168.2.x have the same /24 subnet mask, they are in different networks and can't see each other. The members of the 1.x are in the range of 1.1 - 1.254 etc for the 2.x club

Thats what I figured..

So, devices with an I.P of 192.168.1.0-192.168.1.255 cant communicate with devices with an I.P of 192.168.2.1-192.168.2.255 in vice versa?

And why cant they?

RouteMyPacket

Sylice wrote: »

Thats what I figured..

So, devices with an I.P of 192.168.1.0-192.168.1.255 cant communicate with devices with an I.P of 192.168.2.1-192.168.2.255 in vice versa?

And why cant they?

Where are you in your studies? You should find this answer yourself with little reading.

Why can't someone who speaks German communicate with someone who speaks Japanese? Before that can happen they are going to need something to allow them to understand each other. Same with IP segments.

Sylice

Im not going by any books yet, I am just playing around with it lol. I will be getting a book soon though.

But so far, I have a little network up and running perfectly:

Network.jpg

Binary Freak

Sylice wrote: »

Im not going by any books yet, I am just playing around with it lol. I will be getting a book soon though.

But so far, I have a little network up and running perfectly:

Not bad..

In the meantime you should probably learn the basics from watching some videos before you start fiddling with the CLI.

Jon_Cisco

The device in the middle will allow the two subnets to communicate.

On a very basic level you can think of switches moving traffic in the same subnet and routers moving traffic between subnets.

There is a lot more to it then that but starting out it's not a bad way to think about it. Do yourself a favor. Switch to simulation mode and follow the packets. They describe each step and will tell you why packets fail.

mikeybinec

^^^^ As for the OP's original question, in a basic ARP able network, the 2.X and 1.x can communicate with each other. The router in the middle sees the two network as directly connected

markulous

I would recommend studying for your Network+. It will answer a lot of basic questions.

Justin-

markulous wrote: »

I would recommend studying for your Network+. It will answer a lot of basic questions.

I agree with markulous.

The default gateway is what will allow different networks to communicate with each other. Without it, you won't be able to ping it, unless you're on the same network.

RouteMyPacket

Justin- wrote: »

I agree with markulous.

The default gateway is what will allow different networks to communicate with each other. Without it, you won't be able to ping it, unless you're on the same network.

How does a Default Gateway "allow different networks to communicate with each other"? So if I configure a switch with an IP of 192.168.1.254/24 and my PC is 192.168.1.1/24 and the DG set to .254 I should then be able to communicate with another IP segment, say 192.168.2.0/24? Hmm, can you explain how that would work?

broli720

RouteMyPacket wrote: »

How does a Default Gateway "allow different networks to communicate with each other"? So if I configure a switch with an IP of 192.168.1.254/24 and my PC is 192.168.1.1/24 and the DG set to .254 I should then be able to communicate with another IP segment, say 192.168.2.0/24? Hmm, can you explain how that would work?

He probably meant to say router