PROXY_KEY not from specified reply proxy

[Gene A.]

Hello,

I have several response proxies configured in my uftp environment. I am running the following command on the client:

/usr/sbin/uftpd -d -x 3 -L /var/log/uftpd.log -D /download/multicast -T /download/multicast/incoming -P /var/run/uftpd.pid -M 239.172.1.1 -U 09773 -R 10.230.34.16

However, the client is logging over and over again that it has received PROXY_KEY from the OTHER proxies in my environment other than the one specified.
Client log entries:
2018/02/22 07:22:00.146130: Received PROXY_KEY from 10.230.34.16
2018/02/22 07:22:00.383968: Received PROXY_KEY from 10.230.34.18
2018/02/22 07:22:00.384027: PROXY_KEY not from specified reply proxy
2018/02/22 07:22:00.417570: Received PROXY_KEY from 10.230.34.18
2018/02/22 07:22:00.417610: PROXY_KEY not from specified reply proxy
2018/02/22 07:22:00.493320: Received PROXY_KEY from 10.230.34.17
2018/02/22 07:22:00.493364: PROXY_KEY not from specified reply proxy

The above messaging is constant. Why doesn't the client stop reaching out when the PROXY_KEY is received from the SPECIFIED proxy?

response proxy command:
/usr/sbin/uftpproxyd -d -x 3 -L /var/log/uftpproxyd.log -r -M 239.172.1.1 -U 0x00003416 -t 16

[Dennis Bush]

The clients aren't reaching out to the other response proxies.

Anytime a client sends a KEY_REQUEST to a response proxy, that proxy will multicast the PROXY_KEY to the public address. This means that all clients will get a copy of the PROXY_KEY message, and those that don't need it will ignore the message.

The proxy will limit the sending of PROXY_KEY messages to once every 5 seconds to prevent flooding the network.