134.83.112.0/8
or
134.83.112.0/255.255.255.0
and you will find manipulating them in Tcl is non trivial - but obviously not
impossible. Hence suggesting some support ...
> If subnet mask was added to the IP discover, then only the devices on
> that network would be polled for ip discover. This would cut down on a
> lot of the bandwidth the current implementation uses. I have found that
> SNMP IP discover routines from other managers (which also don't use
> subnet mask to limit their search) can flood a network and bring it to
> its knees. I expect tkined will have similar results which is why I
> hesitate to use it esp. when I have a subnet with a mask of
> 255.255.255.0 and tkined is searching a network with a mask of 255.0.0.0
> because it is using classful masks. That's a lot of wasteful traffic!!!
>
This I agree with ...
> - Matthew
>
> --
> ---
> ------
> Matthew Levine
> Quality Assurance (Global Alliances)
> Cisco Systems, Santa Cruz http://www.cisco.com/
> mlevine@cisco.com (408) 457 - 5431
-- ----------------------------------------------------------------------------- | Peter Polkinghorne, Computer Centre, Brunel University, Uxbridge, UB8 3PH,| | Peter.Polkinghorne@brunel.ac.uk +44 1895 274000 x2561 UK | -----------------------------------------------------------------------------
-- !! This message is brought to you via the `tkined & scotty' mailing list. !! Please do not reply to this message to unsubscribe. To subscribe or !! unsubscribe, send a mail message to <tkined-request@ibr.cs.tu-bs.de>. !! See http://wwwsnmp.cs.utwente.nl/~schoenw/scotty/ for more information.