FreeBSD Port: whatmask-1.1 *UPDATED* to whatmask-1.2
Daniel Rudy
dcrudy at pacbell.net
Fri Nov 28 20:09:28 PST 2003
FreeBSD port whatmask-1.1 has been updated to whatmask-1.2. The auto
fetch is broken though. I'm not sure WHY it won't work, but it does
compile and execute correctly under FreeBSD 4.9-RELEASE once you get the
file whatmask-1.2.tar.gz in the distfiles directory. Below are the
files for the port:
Makefile:
# ex:ts=8
# New ports collection makefile for: whatmask
# Date created: May 20, 2001
# Whom: ijliao
#
# $FreeBSD: ports/net/whatmask/Makefile,v 1.5 2003/02/20 18:51:12 knu Exp $
#
PORTNAME= whatmask
PORTVERSION= 1.2
CATEGORIES= net
MASTER_SITES= http://moog.laffeycomputer.com:8080/
MAINTAINER= ports at FreeBSD.org
COMMENT= Easily convert between four common subnet mask notations
GNU_CONFIGURE= yes
.include <bsd.port.mk>
distinfo:
MD5 (whatmask-1.2.tar.gz) = 26aeff74dbba70262ccd426e681dcf4a
pkg-descr:
Notations supported:
---------------------------------------------
TCP/IP SUBNET MASK EQUIVALENTS
---------------------------------------------
CIDR = .....................: /26
Netmask = ..................: 255.255.255.192
Netmask (hex) = ............: 0xffffffc0
Wildcard Bits = ............: 0.0.0.63
Usable IP Addresses = ......: 62
The above notations are all identical. CIDR notation commonly has a "/" in
front of the number (representing the number of bits). Whatmask can accept
these notations with or without a slash. This notation is used more and more
recently. A lot of popular routers and software supprt this notation.
Netmask notation is pretty much the standard old-school way of doing it.
It is
supported by most systems (Un*x, Win, Mac, etc.).
Netmask (hex) was recently added to support conversions between dotted quad
hex notation.
Wilcard bits are similar to the netmask, but they are the logical not of the
netmask. This notation is used by a number of popular routers.
WWW: http://www.laffeycomputer.com/whatmask.html
pkg-plist:
bin/whatmask
There was a comment file in the work directory, but since I built the
port, the file seems to have been clobbered.
--
Daniel Rudy
More information about the freebsd-ports
mailing list