From owner-freebsd-current  Tue Jun 30 10:48:29 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id KAA00886
          for freebsd-current-outgoing; Tue, 30 Jun 1998 10:48:29 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from biggusdiskus.flyingfox.com (biggusdiskus.flyingfox.com [205.162.1.28])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA00873
          for <freebsd-current@FreeBSD.ORG>; Tue, 30 Jun 1998 10:48:23 -0700 (PDT)
          (envelope-from jas@flyingfox.com)
Received: (from jas@localhost)
	by biggusdiskus.flyingfox.com (8.8.5/8.8.5) id KAA14567;
	Tue, 30 Jun 1998 10:49:45 -0700 (PDT)
Date: Tue, 30 Jun 1998 10:49:45 -0700 (PDT)
From: Jim Shankland <jas@flyingfox.com>
Message-Id: <199806301749.KAA14567@biggusdiskus.flyingfox.com>
To: wollman@khavrinen.lcs.mit.edu
Subject: Re: Retrieving routing table via sysctl
Cc: freebsd-current@FreeBSD.ORG
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Garrett Wollman <wollman@khavrinen.lcs.mit.edu> writes:

> <<On Tue, 30 Jun 1998 06:27:57 -0700 (PDT), Jim Shankland <jas@flyingfox.com> said:
> 
> > struct rt_msghdr tell you which sockaddr's are present.  Beware:  the
> > sockaddr for a netmask is only 8 bytes long.  
> 
> That's because it really isn't a sockaddr at all -- it's just a byte
> count followed by a bit mask.  The only reason you don't see three-byte
> masks for IP /8 routes is the alignment padding.

OK, I'll buy that.  I guess I got fooled by net/route.c consistently
declaring these things as 'struct sockaddr' :-).

Jim Shankland
Flying Fox Computer Systems, Inc.

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message