[VPM] Re: Types of LAN's for compatibility

[Darren Duncan]

Jeremy, please always send these questions to the list, not me directly.

With a typical DHCP server, then your "192.168.1.(1 -254 
possibilities)" is correct.

Regarding the 16.7 million et al, these A|B|C things I referred to 
were actually allocations of the public internet, and there are 
ranges that big there.

I don't know the answers to the other questions.

-- Darren Duncan

At 5:52 PM -0700 6/11/04, Jeremy Aiyadurai wrote:
>hi Darren,
>
>Thankyou for your replies.
>
>my router has a dhcp server. this is not the case with all networks, is it?
>given the broadcast address, (router address), what would be a good 
>perl algorithm for (pinging) detecting
>all machines.
>eg. if router address (default gateway) is 192.168.1.1, then it 
>would be 192.168.1.(1 -254 possibilities).
>that is easy to figure out, for a normal lan,
>but what if the router (default gateway) address is different.
>
>what is a good algorithm, that is optimal for testing for machines, 
>given any default gateway address.
>I know there are 16.7 million possibilities, but no network is going 
>to be that big.
>
>also, what is a subnet mask? should this be used for the algorthim 
>instead of the gateway address? can this be used for figuring what 
>ip's to check?
>
>Regards,
>
>Jeremy A.
>
>>From: Darren Duncan <darren at darrenduncan.net>
>>To: victoria-pm at pm.org
>>Subject: [VPM] Re: Types of LAN's for compatibility
>>Date: Fri, 11 Jun 2004 16:39:59 -0700
>>
>>At 2:50 PM -0700 6/11/04, Jeremy Aiyadurai wrote:
>>>what makes a LAN, a normal LAN?
>>>how many types a LAN's are there, and what would be the ip ranges?
>>>eg. my lan is 192.168.1.* (eg. * = 1 - 254).
>>>The reason i am asking these questions is I dont know too much 
>>>about lan computing, but need
>>>to know, so my client/server app, will be able to work on any type of lan.
>>>Thanks in advance,
>>>Jeremy A.
>>
>>I don't recall all the details, but some person or organization can 
>>be allocated different blocks of IP addresses for their use, with 
>>names like A, B, and C; depending what you have, you can work with 
>>either 256, or 65,536, or 16.7 million different IP addresses. 
>>Checking the status of 256 is easy, checking the much larger 
>>numbers is not usually practical.  That's sort of what I'm getting 
>>at. -- Darren Duncan