eventually this will meet your requirements (RIP)

Oh man! Ad-blocking software has been detected! :'(

This website is run by the community, for the community... and it needs advertisements in order to keep running. Blocking our ads means your killing our stats!
Please disable your ad-block, or become a premium member to hide all advertisements and this notice.

hm ok , if the subnet mask became 255.255.0.0 i mean /16 , what would be the result?

 

Oh man! Ad-blocking software has been detected! :'(

This website is run by the community, for the community... and it needs advertisements in order to keep running. Blocking our ads means your killing our stats!
Please disable your ad-block, or become a premium member to hide all advertisements and this notice.

This is EXACTLY what I mean. Are you going to ask about EVERY EXAMPLE YOU FIND, or are you going to learn the BASICS properly. Your questions have been answered but you still dont understand because you dont know HOW the answers were found.

As for keeping saying the same thing over and over again, you are asking the same question but with different examples, OVER, AND OVER AGAIN!!

 

kobem,

In your own words, explain the encapsulation and decapsulation process with reference to the OSI Layer Model. THAT is at least one of the "basics" that people have been referring to.

 

What do you think would happen, and why?

 

What do you think the result would be, and why?

 

forget those and examine this

due to same example

while subnet mask is /24

ankara will advertise 172.16.0.0(i looked at the book this is written so) to izmir
and izmir does same too

in my opinion : ankara always knows 172.16.0.0 also receives it from izmir
and this will occur a problem

according to you : in ankara >> network 172.16.0.0 , in izmir >> network 172.16.0.0 NO PROB


..............

again while subnet mask is /24
but between ankara and router , think there is a 10.2.1.0/24 network

in my opinion if it is so , this won't make a problem too cos

in ankara >> network 172.16.0.0 , network 10.0.0.0(advertised routes)
in izmir >> network 10.0.0.0 , network 172.16.0.0(advertised routes)


SO NO PROBLEM YOU SEE , BUT BOOKS DO NOT SAY SAME WHY NOT?

 

I don't know what else to say - I keep saying it, and you ignore it. If you provide a /24 mask on all interfaces, then that is what is used to create the route map, not a /16 mask. If the network is contiguous it will work and if it is not, it won't.

 

Try reading my post #19 again, I said nothing of the kind.

 

Because 10.0.0.0 introduced between the two 172.16.x.x networks makes them not contiguous. And RIP can not deal with non-contiguous networks.


Kobem, this is my last post on this subject.

 

hey mac , i already know that RIP is contiguous and because of being contiguous , it doesn't
advertise if between there is a part of a different major network


i know all these but this is a rule!

the main thing i am trying to say ,searching the reason of that not to be dependent on rules just..