#99 Revision of RFE 444248: Promiscuous IP

[Thomas Kurowski]

According to the comment on feature 444248, the
implementation of the promiscuous mode for BACnet/IP
has been accomplished upon the release of VTS 3.4.
However, VTS 3.4.4 does still not provide this function.
It is not treated as a high priority task in the case of
manual testing since the tester does not have to rely on
the VTS sniffer by using supplementary protocol
analyzers, but we have to pay more attention to this
feature for the sake of automated testing. Many scripts
require the capturing of messages being sent by the IUT
to other devices than the TD.

EXAMPLE:
Excerpt from ASHRAE 135.1-2003, clause 9.1.2.1 (see
STEP 3):
1. MAKE (a change that triggers the detection of an
alarm event in the IUT)
2. RECEIVE ConfirmedEventNotification-Request,
'Process Identifier' = (the process identifier
configured for this event),

3. RECEIVE
DESTINATION = (at least one device other than
the TD),
SOURCE = IUT,
ConfirmedEventNotification-Request,
'Process Identifier' = (the process identifier
configured for this event),

The AcknowledgeAlarm Service Execution Tests cannot
be performed automatically as long as the promiscuous
mode is not supported by VTS.