- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: HP-UX 11i error: tcpdump: recv_ack: promisc_ph...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-30-2004 03:22 AM
11-30-2004 03:22 AM
I have an HP-UX 11i PA-RISC box with the latest patch bundles (GOLDBASE/GOLDAPPS from June 2004 IIRC) installed and I'm trying to use ethereal 0.10.5 (installed from HP Internet Express) to sniff some traffic. I also have libpcap from HPIE, and I've also installed tcpdump and libpcap from the "the Software Porting And Archive Centre for HP-UX" at http://hpux.cs.utah.edu/. Neither of them works, both tcpdump and ethereal failing with this strange message:
tcpdump: recv_ack: promisc_phys: UNIX error - Device busy
(for ethereal, replace 'tcpdump' with ethereal, and the error message appears after starting a capture)
I've looked in the Ethereal docs and there are some instructions on setting promiscuous mode on HP-UX 11i. However, running "echo 'lanc_outbound_promisc_flag/W 1' | adb -w /stand/vmunix /dev/mem" as they advise yields "symbol not found".
Any ideas? Any more info I should provide?
Output of lanscan:
Hardware Station Crd Hdw Net-Interface NM MAC HP-DLPI DLPI
Path Address In# State NamePPA ID Type Support Mjr#
8/0/20/0 0x001083352BBA 0 UP lan0 snap0 1 ETHER Yes 119
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-30-2004 03:33 AM
11-30-2004 03:33 AM
Re: HP-UX 11i error: tcpdump: recv_ack: promisc_phys: UNIX error - Device busy
test the lan card with mstm cstm or xstm
landadmin -x 0
I suspect hardware or configuration problems.
SEP
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-30-2004 03:58 AM
11-30-2004 03:58 AM
Re: HP-UX 11i error: tcpdump: recv_ack: promisc_phys: UNIX error - Device busy
Hello and thanks for replying,
here's the output of the ioscan and lanadmin commands.
[root@hpux /root]# ioscan -fnC lan
Class I H/W Path Driver S/W State H/W Type Description
=====================================================================
lan 0 8/0/20/0 btlan CLAIMED INTERFACE HP PCI 10/100Base-TX Core
/dev/diag/lan0 /dev/ether0 /dev/lan0
[root@hpux /root]# lanadmin -x 0
Current Config = 100 Full-Duplex AUTONEG
About the mstm/cstm part, I suppose I have a bit of RTFM-ing to do.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-30-2004 04:49 AM
11-30-2004 04:49 AM
SolutionI think only one "unbound" promiscuous application is allowed in HP-UX 11i. ( I assume you did not run tcpdump and ethereal in the same time. Did you? )
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-30-2004 05:01 AM
11-30-2004 05:01 AM
Re: HP-UX 11i error: tcpdump: recv_ack: promisc_phys: UNIX error - Device busy
As far as I know, I don't have any other app that has put lan0 in promiscuous mode. nettl doesn't seem to be started:
[root@hpux /root]# nettl -sp
nettl : The tracing and logging facility has not yet been started
To start the facility, execute the following command:
...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-30-2004 05:05 AM
11-30-2004 05:05 AM
Re: HP-UX 11i error: tcpdump: recv_ack: promisc_phys: UNIX error - Device busy
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-01-2004 05:40 AM
12-01-2004 05:40 AM
Re: HP-UX 11i error: tcpdump: recv_ack: promisc_phys: UNIX error - Device busy
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-01-2004 08:45 PM
12-01-2004 08:45 PM
Re: HP-UX 11i error: tcpdump: recv_ack: promisc_phys: UNIX error - Device busy
actually the README.hpux in the ethereal source mentions that HP-UX 11i doesn't need any patches in order to use promiscuous mode (the file quotes some messages from google groups, your name comes up in a few). However, it's not clear from those messages if 11i needs the 'adb -w /stand/vmunix ...' hack or not - it's mentioned as necessary for 10.20, but not as being necessary *only* on that version.
It's likely that the person maintaining the README is not an HP-UX expert, so he/she just resorted to quoting external information.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-02-2004 04:52 AM
12-02-2004 04:52 AM