--Dxnq1zWXvFF0Q93v
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Mon, Jan 23, 2006 at 01:18:23PM -0500, matthew sporleder wrote:
> I didn't realize this was legal in the ip addressing standard,
> however, if nothing else, it's a problem with 'netstat' 's inability
> to represent the number, which is a netbsd problem:
>=20
> # netstat -rnf inet
> 0.0.5&0xa050501    255.255.0.255      UGS         0       23      -  tlp0

But it represents it fine... 0.0.5.0 with a mask (anded with)=20
0xa050501. I don't see any problem there.

> and (to a lesser extent) 'route' 's reporting of a negative mask:
> (I don't know a better way to report this, maybe /-8 would be better.=20
> Maybe slash notation just doesn't work for non-contiguous masks)

That's correct. Slash notation doesn't work for non-contiguous masks.
Maybe "route show" shouldn't try that.=20

	-is

--Dxnq1zWXvFF0Q93v
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: 2.6.i

iQEVAgUBQ9iSHjCn4om+4LhpAQFeWAf9FDa7qPrpwbNGp6GP3PyLztr3jJJ536Wi
OYnNa8thH49FPlahfckmGbjLQ57evP0w461YcH/KjffYI3TY/mODxSSCDzFrzS5U
IwzcQkufgs6HagVjQdN9Ez8qJ9ZqZ2ZdOzWDyTF8EgDMpEQgCSXjA7CojanNxTtG
bqVrFpaRHZ+pr/zqNC6CvVMLG8Lmnb+7XiSRIKgyojNPbKnTpqqVz8v11Bm/RRSB
am+ymchbJEz9tLa0jlBtsarultWVJVgderYbC/GyDsgqFMPnWEfwokS/UkqrGPSG
r0/rX0TbrqEjjJTeBA9VJ0RI9bdBmRe++S6iPn5fyb2+HqvFXgkBrQ==
=KvdA
-----END PGP SIGNATURE-----

--Dxnq1zWXvFF0Q93v--