Another increasingly common way to represent a network's address space is for instance 129.168.1.80/29 This says the network address space begins at 192.168.1.80 and to use 29 bits as the network portion of the address, thus leaving 3 bits for the "host" portion even though, as mentioned earlier, you lose the lowest and highest "host" addresses for the network and broadcast address respectively. I like the $neworknum/xx notation because I don't have to convert 248 to binary and look at where the 1's stop. The stuff I have been reading keeps talking about getting out of the habit of thinking in class a,b,c addresses. Not sure why other than the usable address space in IP V4 was chunked up in too big a chunks and is fast being used up, but that is indeed another story. Bret "Michael J. McGillick" wrote: > > Afternoon: > > I'm trying to understand how netmasks work. We want to set up a small > pool of IP Addresses, and the only thing we can do is specify the network > and the netmask. They want the pool to start at 192.168.1.85, and have 5 > usuable IP Addresses. What do I specify for the netmask, and more > importantly, why? I understand about setting up a network range, when the > network is specified at 0, but this 80 is throwing off my thinking. > > Anyone help? > > - Mike > > -- > To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe" > as the Subject.
begin:vcard n:Hughes;Bret tel;fax:918.587.0131 tel;work:918.587.0131 x-mozilla-html:FALSE url:www.elevating.com org:Elevating Communications Inc adr:;;PO Box 1323;Tulsa;OK;74101-1323;USA version:2.1 email;internet:[EMAIL PROTECTED] title:Chief Solutionist/President x-mozilla-cpt:;19888 fn:Bret Hughes end:vcard
