I knew that was there but didn't bother fixing it.. BTW, it is a bad habit to get into of using 192.168.0.? as your network. The reason is if you have more than one network and you subnet it to 255.255.255.0 your route ends up being 192.168.0.0 which is a class B.. If you develop or VPN to a lot of networks as we do and you so happen to join a 192.168.5.0 network.. Nothing will work because you are class b'd to your own network.
Danny At 10/14/2001 10:18 PM, you wrote: >At 09:33 PM 10/14/2001 -0500, Danny Mallory <[EMAIL PROTECTED]> >wrote: > >>I have to agree. There are many fancier scanners out there. As I >>mentioned the one that I wrote >>is for quick floppy utility to gather information on a new network. If >>you want ours you can get >>it at http://www.cnsonline.com under toolshelp section. >> >>Danny > >Neat Perl script, Danny. The only problem I had was scanning a subnet >with a third octet of 0 (i.e. 192.168.0.0). In my example, the code that >sets the subnet variable (shown below) sets it to 192.168, thus the >discovery searches for 192.168.1, 192.168.2, ..., 192.168.255. > >$subnet = substr($a, 0, index("$a",".0")); > >Other than that little issue, which I worked around easily, I found it to >be a nice tool. > >Thanks for sharing! > >-Jeff > > >-------------------------------------------------------------------------------- >For unsubscription of this list send an email to [EMAIL PROTECTED] with >email >data containing unsubscribe emailadd sambar > -------------------------------------------------------------------------------- For unsubscription of this list send an email to [EMAIL PROTECTED] with email data containing unsubscribe emailadd sambar
