Forums before death by AOL, social media and spammers... "We can't have nice things"
|    comp.protocols.tcp-ip    |    TCP and IP network protocols.    |    14,669 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 13,821 of 14,669    |
|    KR to Bluz    |
|    Re: why does the block eth0=10.0.0.0/8 n    |
|    18 Oct 11 15:39:28    |
      b7e693fb       From: kristian.rasmussen@broadpark.no.spam.com              On 18.10.2011 14:47, Bluz wrote:       >       > You are absolutely correct indeed, the bigger problem being that all the       other machines on the 10.0.0.0/8 subnet trying to reach machines on the       10.0.0.0/9 subnet will fail, and that is precisely what I am trying to       understand. Is this because of the        way TCP/IP subnetting is designed ? But you seem to say that is technically       possible ?              The reason why nodes on the 10.0.0.0/8 net can't reach 10.127.255.253/9,       is that you've told them that they belong to the same network as the       address they're trying to reach. Hence they won't try to reach the       address through a router, but rather by broadcasting an arp request.              Your network is incorrectly designed, as you have the same network on       both sides of a router. As you yourself pointed out, 10.0.0.0/9 is a       subnet of 10.0.0.0/8. Your setup cannot possibly work (and shouldn't).              --- SoupGate-Win32 v1.05        * Origin: you cannot sedate... all the things you hate (1:229/2)    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca