LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Networking
User Name
Password
Linux - Networking This forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.

Notices


Reply
  Search this Thread
Old 03-17-2006, 09:44 AM   #16
Berkut83
Member
 
Registered: Jan 2006
Distribution: red hat enterprise 3.0
Posts: 47

Original Poster
Rep: Reputation: 15

Marozsas listen to me

try to follow this rule with your mind and you will find the solution

now you are having MY SAME DOUBT which i had at the start of this post

it' s incredible but now i have solve the mistery and now you are having my same doubt for which some days ago i have started this post


follow this rule in your mind:

READ THE RULE:
********************************
when a host ping another host, to verify if it can reach the destination host it check its personal ip, then check its personal subnet mask and defines the ranges of ip addresses which it can ping. After decided what range of ip it can ping he control the ip address of the destination machine, IGNORING, and i repeat, IGNORING what is the subnet mask of the DESTINATION MACHINE. It simply checks the ip of the other machine and ask itself: is the other machine ip in my range, yes or no??? if yes it can ping, if not it cannot ping, IT DOESN'T MATTER what is the subnet mask of THE DESTINATION MACHINE.

And again this happens also in the other machine. Other machine when receive a ping packet and has to sent it back ask itself the same question. Is the other machine ip in my range (IGNORING AGAIN OTHER MACHINE SUBNET MASKS)???
If other machine ip addess, IGNORING SUBNET MASK, is in its range, then the 2 way ping connection can be estabilished
********************************


NO LET'S TRY TO APPLY THE RULE TO YOUR TWO EXAMPLES WRITTEN IN YOUR LAST REPLY

**************************************

EXAMPLE 1:

A 10.124.8.1/255.255.252.0 (range 10.124.8.0 to 10.124.11.255)
B 10.124.9.1/255.255.255.0 (range 10.124.9.0 to 10.124.9.255)

Host A ask itself, is the ip address of host B in my range?? YES!
Yes because the maximum value is 10.124.11.255 and so 10.124.9.1 is in the range.
Now host b ask itself the same question, is host A in my range? NO!!
No because 10.124.8.1 is not between the range 10.124.9.0 to 10.124.9.255

RESULT: As you have seen with your eyes they cannot ping each other

EXAMPLE 2:

A 10.124.9.2/255.255.252.0 (range 10.124.8.0 to 10.124.11.255)
B 10.124.9.1/255.255.255.0 (range 10.124.9.0 to 10.124.9.255)


Host A ask itself, is the ip address of host B in my range?? YES!
Yes because the maximum value is 10.124.11.255 and so 10.124.9.1 is in the range.
Now host B ask itself the same question, is host A in my range? YES AGAIN!! Yes because 10.124.9.2 is in the range of host B which is from 10.124.9.0 to 10.124.9.255

RESULT: they can successfully ping each other!!


This is the rule to keep in mind, for hosts it doesn't really matter what is the destination host subnet mask, they simply control:

1)their personal subnet mask
2)their personal address
3)the range of the subnet where they are
3)the destination host ip address

and then decide.


Keep in mind this and you will be on the right path

I know that it is a strange situation but it can be possible, i have discovered this in one day, very illogical but possible, just follow the rule

Last edited by Berkut83; 03-17-2006 at 09:53 AM.
 
Old 03-17-2006, 10:17 AM   #17
Darin
Senior Member
 
Registered: Jan 2003
Location: Portland, OR USA
Distribution: Slackware, SLAX, Gentoo, RH/Fedora
Posts: 1,024

Rep: Reputation: 45
As confusing as it may sound, the question is what determines, "what is on the same network" and the answer is the netmask of the host asking that question. If you look back at my previous post, you will see where I show HostA checking HostB's address vs it's subnet mask.

To expand further, I wouldn't suggest putting into production a network setup like this but simple direct communication will work. A ping request sends a direct ICMP echo request and after determining that (it thinks) the other host is on the same network, it will do an ARP request for the MAC of the other host and send the packet on the local LAN. No router required here and FYI every system has routes to the networks it has addresses on it's route table. More complex communication would of course break since the two systems have different broadcast addresses.
 
Old 03-17-2006, 10:22 AM   #18
marozsas
Senior Member
 
Registered: Dec 2005
Location: Campinas/SP - Brazil
Distribution: SuSE, RHEL, Fedora, Ubuntu
Posts: 1,499
Blog Entries: 2

Rep: Reputation: 68
Quote:
it' s incredible but now i have solve the mistery and now you are having my same doubt for which some days ago i have started this post
(lol) It is a kind of mind virus I guess

The rest of your post make sense too.
I was resistant at begin, because I learned that way as a sort of 11th Commandment of God, you know...

Thanks for your time.

see'ya,
 
Old 03-17-2006, 10:28 AM   #19
marozsas
Senior Member
 
Registered: Dec 2005
Location: Campinas/SP - Brazil
Distribution: SuSE, RHEL, Fedora, Ubuntu
Posts: 1,499
Blog Entries: 2

Rep: Reputation: 68
Hi Darin,
Quote:
"what is on the same network" and the answer is the netmask of the host asking that question.
This is a very concise statement. Is pretty much the same Berkut83 said in his post in a more compact form. I was taking in account the netmask of both machines, what leads me to that state of mental confusion.

Thanks for time too, Darin !

see'ya,
 
Old 03-17-2006, 03:17 PM   #20
Berkut83
Member
 
Registered: Jan 2006
Distribution: red hat enterprise 3.0
Posts: 47

Original Poster
Rep: Reputation: 15
Thanks to all of you too

Finally we all agree with the same


Thanks also to Darin to have written the rule in a short manner


Bye all and thanks again

For another time, this forum has showed me again how fantastic and helpful is this community

Last edited by Berkut83; 03-17-2006 at 03:21 PM.
 
  


Reply



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Can't ping localhost (/etc/hosts and DNS are OK) Mr. Gone Linux - Networking 9 10-16-2004 03:05 PM
dhcp client can't ping gateway but can ping other local hosts dirty_forks Linux - Networking 7 10-08-2004 10:54 AM
Quake3 Server, always 999 ping, can't figure it out stormblast Linux - Games 0 08-15-2004 01:10 PM
Cannot ping internet hosts nikhiljosh Linux - General 3 12-10-2003 09:43 AM
RH 7.2 - Can't ping other hosts spato Linux - Networking 8 05-04-2002 05:19 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Networking

All times are GMT -5. The time now is 10:35 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration