George Metz wrote:
>
> On Fri, 31 Aug 2001, David Douthitt wrote:
> > ipmask is designed in particular to be used from scripts; for example:
> >
> > # ./ipmask -c 172.16.3.40
> > 172.16.0.0/16
>
> How are you determining this?
This is using standard class specifications (Class A, Class B, Class
C)...
It doesn't handle Class D or Class E addresses (or shouldn't).
> If along classful lines, then you should be
> listing this as is, though why you'd do that I'm not sure. (Or rather, I
> can think of a ton of good reasons, but I'm not sure if they apply in this
> case.)
I'm not sure what you mean. This specific example could be used, for
example, to permit someone to specify that their system's address was
172.16.3.40, and not have to specify what their network mask was.
> If along RFC 1918 lines, however, this should return 172.16.0.0/12, NOT
> 172.16.0.0/16. Just curious as to how you're doing it.
RFC 1918 specifies private address ranges; perhaps this would be a good
modifier option? Like so:
# ./ipmask -c 172.16.3.40
172.16.0.0/16
# ./ipmask -Pc 172.16.3.40
172.16.0.0/12
# ./ipmask -Pc 206.101.224.57
ipmask: not a private address range!
#
Eh?
_______________________________________________
Leaf-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-devel
