crossbow discuss - Apr 2009 - snoop: no datalinks found

How come snoop doesn''t find the vnic0, by default:

root at pine:~# ifconfig -a
lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232
index 1
        inet 127.0.0.1 netmask ff000000 
vnic0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
        inet 10.9.59.56 netmask ffffffe0 broadcast 10.9.59.63
        ether 2:8:20:7f:a9:16 
lo0: flags=2002000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv6,VIRTUAL> mtu 8252
index 1
        inet6 ::1/128 


root at pine:~# snoop
snoop: no datalinks found


root at pine:~# snoop -d vnic0 -o /dev/null
Using device vnic0 (promiscuous mode)
1 ^C
root at pine:~#
-- 
This message posted from opensolaris.org

> How come snoop doesn''t find the vnic0, by default:
 > 
 > root at pine:~# ifconfig -a
 > lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL>
mtu 8232 index 1
 >         inet 127.0.0.1 netmask ff000000 
 > vnic0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500
index 2
 >         inet 10.9.59.56 netmask ffffffe0 broadcast 10.9.59.63
 >         ether 2:8:20:7f:a9:16 
 > lo0: flags=2002000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv6,VIRTUAL>
mtu 8252 index 1
 >         inet6 ::1/128 
 > 
 > 
 > root at pine:~# snoop
 > snoop: no datalinks found

Hmm, this is in an exclusive zone, right?  This looks like a bug: snoop
uses dlpi_walk(), which calls dladm_open()/dladm_walk(), but dladm_open()
fails from inside an exclusive zone since dlmgmtd is only in the global
zone.  I''ll get a bug logged on this.

-- 
meem