Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watnot!watmath!clyde!cbatt!ucbvax!YALE.ARPA!LEICHTER-JERRY
From: LEICHTER-JERRY@YALE.ARPA.UUCP
Newsgroups: mod.computers.vax
Subject: Re:
Message-ID: <8702260214.AA14286@ucbvax.Berkeley.EDU>
Date: Wed, 25-Feb-87 21:14:50 EST
Article-I.D.: ucbvax.8702260214.AA14286
Posted: Wed Feb 25 21:14:50 1987
Date-Received: Sat, 28-Feb-87 00:05:06 EST
Sender: daemon@ucbvax.BERKELEY.EDU
Reply-To: <LEICHTER-JERRY@YALE.ARPA>
Distribution: world
Organization: The ARPA Internet
Lines: 19
Approved: info-vax@sri-kl.arpa


    I have a problem with the Ethernet QIO-Interface. When I init the Ethernet
    Ports in non promiscious mode, all works fine. But for promiscious mode
    the QIO returns a "BAD PARAMETER" I/O-status for NMA$C_PCLI_PRM (hex
    value=B18). Indeed this could not be a bad parameter because it works for
    non promiscious mode. Could it be a problem with the combination of
    other init parameters ?

The "bad parameter" returned in response to the QIO is an indication of what
parameter was being processed when an error was detected.  It's not, in
general, the parameter that's wrong - it's the value specified, in combination
with the state of the channel, device, and process.

My guess about your problem is that your process doesn't have the PHY_IO
privilege enabled; you need that to start a promiscuous-mode channel.  Another
possibility is that some other user has already enabled promiscuous mode -
there can only be one promiscuous mode user at a time.
							-- Jerry
-------