snmpnetstat, from net-mgmt/net-snmp, behaves differently on sparc than x86

Tillman Hodgson tillman at
Mon Jan 24 18:34:40 PST 2005


(I pulled your email address from the port Makefile, I hope you don't
 mind the direct email. I also cc'd freebsd-sparc@ because it seemed
 likely to be a sparc64 related issue).

I've set up net-snmp on both a i386 -current machine and a sparc64
-current machine. Both ports where compiled from ports today, both after
a fresh cvsup.

[root at thoth]# uname -a
FreeBSD 6.0-CURRENT FreeBSD 6.0-CURRENT #1: Wed Jan 12 19:30:40 CST 2005 toor at  i386

[root at caliban]# uname -a
FreeBSD 6.0-CURRENT FreeBSD 6.0-CURRENT #0: Thu Jan 13 21:49:32 CST 2005 toor at  sparc64

snmpnetstat seems to behave differently on the two hosts. For example:

[root at thoth]# snmpnetstat -v 2c -c rig -r -n thoth | grep tl0 | head -3
10.1.4/24              UG      tl0
10.42/16               UG      tl0
192.168                UG      tl0

[root at thoth]# snmpnetstat -v 2c -c rig -r -n caliban | grep hme | head -3
default                      UG      hme0
default                      U       hme0
default                      U       hme0

Basically all networks and gateway IPs appear as from the
sparc64 host. I've snipped the output because my routing tables are
close to 50 lines long each :-)

I demonstrated this from the i386 host "thoth" because it's the host that
I'll be using to monitor snmpnetstat from but the same problem manifests
if I do it from the sparc64 host "caliban". That is to say, it sees the
"real" IPs and networks from thoth but when I snmpnetstat caliban from
caliban itself it also sees for all routes.

Is this a known problem? If not, can I be of assistance in
trouble-shooting it?

Thanks for your time,

- Tillman

"Learning isn't a means to an end; it is an end in itself."
    -- Robert Heinlein

More information about the freebsd-sparc64 mailing list