Good point. We'll fix that.

info-multinet@process.com wrote:
>
>Hi,
>
>Process Software MultiNet V5.1 Rev A-X, COMPAQ AlphaServer DS20E 666 MHz,
>OpenVMS AXP V8.3
>
>On this machine we had set up a psuedo-interface "pd0" to do some testing;
>this interface was configured with an IP address in the same subnet as the
>"se0" interface it was tied to.
>
>Later we acquired another system to which we assigned the IP address of the
>"pd0" interface of the first machine, and disabled the "pd0" interface on
>the first machine using $ MU SET/INTERFACE/DOWN PD0.
>
>TCP/IP sessions between the two machines worked fine, but we soon found that
>any attempt to connect to the new machine from anywhere else resulted in
>either a failed connection attempt or was very unreliable (would die after a
>period of time).
>
>Eventually we worked out that the first machine was still responding to ARP
>requests for the IP address of the "pd0" interface, even though that
>interface was down, and this was interfering with connectivity to the second
>machine.
>
>I fixed it using $ MU SET/ARP/DELETE=a.b.c.d which was easy to do (once we
>realised the problem). However, why is it even necessary? Why does
>MultiNet continue to respond to ARP requests for an interface that it isn't
>listening on?
>
>Thanks,
>
> Jeremy Begg
>
> +---------------------------------------------------------+
> | VSM Software Services Pty. Ltd. |
> | http://www.vsm.com.au/ |
> | "OpenVMS Systems Management & Programming" |
> |---------------------------------------------------------|
> | P.O.Box 402, Walkerville, | E-Mail: jeremy@vsm.com.au |
> | South Australia 5081 | Phone: +61 8 8221 5188 |
> |---------------------------| Mobile: 0414 422 947 |
> | A.C.N. 068 409 156 | FAX: +61 8 8221 7199 |
> +---------------------------------------------------------+