On Thursday 21 February 2002 12:23 am, Edward Dekkers wrote: > > Any documentation that states this is a class B network is wrong. It is a > > class C. > > > > Here is the breakdown... > > Class Netmask Network Addresses > > A 255.0.0.0 0.0.0.0 - 127.255.255.255 > > B 255.255.0.0 128.0.0.0 - 191.255.255.255 > > C 255.255.255.0 192.0.0.0 - 223.255.255.255 > > > > These are the defaults. > > This explains a lot. After reading this, I stepped back to my original > reference below which I saved years ago from the internet: > > --- > > Section 3: Private Address Space > > The Internet Assigned Numbers Authority (IANA) has reserved the > following three blocks of the IP address space for private networks: > > 10.0.0.0 - 10.255.255.255 > 172.16.0.0 - 172.31.255.255 > 192.168.0.0 - 192.168.255.255 > > We will refer to the first block as "24-bit block", the second as "20-bit > block", and the third as "16-bit" block". Note that the first block is > nothing but a single class A network number, while the second block is a > set of 16 continuous class B network numbers, and the third block is a set > of 255 > continuous class C network numbers. > --- > > I actually misread it. When it specifies here 192.168.0.0 - > 192.168.255.255, AND that it is a 16 bit block, I thought it was a class B > as I seemed to have 255 * 255 combinations of addresses. But it > specifically says on the last sentence it is actually by default a Class C. > A bit confusing as I though a 16 bit block meant B Class. > > My only excuse is I tried to read and understand it while I was still a > newbie years ago, and it 'stuck' in my head. > > HOWEVER. Do Linux Servers/Win Clients actually KNOW this, or should the > netmask of 255.255.0.0 override this as the other kind repondents have > said? OR is the only way around it to add the route line to the Linux > server (yes, the Linux server acts as gateway to the Win clients)?
The Class system is purely a convention, and is honoured by some config/installation software. E.g. when installing IP on a RH system it will give you the default netmask based on the IP address. However, the IP stack has absolutely no idea of this convention and works purely on the IP ADDR/NETMASK settings, as I decribed in my previous post. As I said, we use the 10. Class 'A' private rage as a number of Class 'B' ranges to help with routing and reduce the WAN broadcast traffic. One question I did think of after sending my last post is, are they on the same wire or is there some form of router between them. Both being on the same hub would constitute being on the same wire, but if there's a switch in between, then it depends on the switch as to what happens, but it *should* still work. If there's a router involved too then this will almost certainly be your problem. > > I guess next time I'll just try it both ways. > > Thanks to all repondents for your time. > > Edward. > > > > > _______________________________________________ > Redhat-list mailing list > [EMAIL PROTECTED] > https://listman.redhat.com/mailman/listinfo/redhat-list -- Gary Stainburn This email does not contain private or confidential material as it may be snooped on by interested government parties for unknown and undisclosed purposes - Regulation of Investigatory Powers Act, 2000 _______________________________________________ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
