LMS 3.1: Packet Capture utility issue

Answered Question
Oct 27th, 2009

I received the following error after "Create" through either the Device Center or directly at http://ciscoworks:1741/cwhp/PacketCapture.do.

"WinPcap Problem

There are no available interfaces from which to capture the data.

Note: This tool only works with Ethernet interfaces."

I had used the tool successfully before, though I don't recall whether that's before or after migrating from LMS 2.6 on Sol 8 to LMS 3.1 on Sol 10 with IPMP. Is WinPcap used even on Solaris?

Correct Answer by Joe Clarke about 7 years 4 months ago

See attached.

Correct Answer by Joe Clarke about 7 years 4 months ago

No. jet is not setuid root. Do a chown root /opt/CSCOpx/objects/jet/bin/jet, then try it.

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (3 ratings)
Joe Clarke Tue, 10/27/2009 - 07:24

No. JET can operate directly on kernel APIs. The key is that /opt/CSCOpx/objects/jet/bin/jet must be setuid root. That said, I never did any testing on IPMP. There may be an incompatibility with the old ethereal binary I am using and IPMP. If jet is setuid root, running /opt/CSCOpx/objects/jet/bin/jet -D will indicate if it finds any interfaces.

Note: JET will not work in a non-global zone by default. In order to allow packet capturing in a non-global zone, see this blog:


yjdabear Tue, 10/27/2009 - 07:28

No Solaris zone on the LMS server here. IPMP may be the culprit then?

ls -al /opt/CSCOpx/objects/jet/bin/jet

-rwsr-x--- 1 casuser casusers 4728044 Jun 15 2008 /opt/CSCOpx/objects/jet/bin/jet

/opt/CSCOpx/objects/jet/bin/jet -D

tethereal: There are no interfaces on which a capture can be done

Correct Answer
Joe Clarke Tue, 10/27/2009 - 07:31

No. jet is not setuid root. Do a chown root /opt/CSCOpx/objects/jet/bin/jet, then try it.

yjdabear Tue, 10/27/2009 - 07:42

Will do.

Should the jet binary be installed as setuid root by default? If not, how did it manage to function before, with or without IPMP in the picture?

Joe Clarke Tue, 10/27/2009 - 07:45

Yes, and it is. Someone must have changed it. Note: there are a few setuid binaries installed by LMS. If someone did a wholesale chown, things will certainly break.

yjdabear Tue, 10/27/2009 - 07:56

Arghh, that rings a bell: I had done a mass "find . -group 9999992 -print | xargs chown -h casuser:casusers" because Sol 10 didn't update file ownership after casuser:casusers' uid/gid numbers got changed manually.

Could you post a list of what other specific binaries might have gotten the wrong UID/GID due to the above? Thanks!

Joe Clarke Tue, 10/27/2009 - 08:12

The following are on my Solaris 10 server:


























































yjdabear Tue, 10/27/2009 - 08:24

To be sure, their UID should be root. But what about the GID? casusers or sys, or something else? Thanks for your patience.


This Discussion