Menu

Response proxy: keys exchange between proxy -> clients

banuchka
2015-02-04
2015-02-05
  • banuchka

    banuchka - 2015-02-04

    Hi,

    My setup looks like this:

    1) i've got a "server" in one VLAN, it can access to all clients with ttl > 1 (ex. 10.20.1.2)
    2) i've got a response proxy, running on different than the server VLAN. There are more than one ip address on it, there are 4 VLANs on trunk. All of them looks directly to clients.
    (ex. 10.20.2.2 - for native VLAN, 10.20.3.253, 10.20.4.253 etc for client's VLANs)

    it is running with "uftpproxyd -r -d -x 2 -M 230.4.3.100 -N -20 -k key -B 2097152"

    yes, im using address 230.4.3.100 for pub multicast address
    ive seen in proxy_usage.txt that -M needed only for server proxy, but without that option all clients running with "-R proxy_ip" cant receive files.

    Problems(?) that i have:

    • every 5 sec in client's log i see "Sent KEY_REQ to 10.20.3.253:1044"
    • in the proxy's log i see "Received KEY_REQ from CLIENT_IP", "Sent PROXY_KEY to 230.4.3.100"

    is that looks like something wrong in keys exchange between them? or all of my configuration looks sad?

    Dennis, any chances to hear some comments from you? Thank you.

    ps: to be honest there are a lot questions about some parts of UFTP in my head... It is really nice product we are using for delivery data to thousand hosts, thanks for that.

     
  • Dennis Bush

    Dennis Bush - 2015-02-04

    It looks like the clients aren't getting the PROXY_KEY from the proxy. Does the client have -M 230.4.3.100 specified, and can the proxy reach the clients using that address?

     
  • banuchka

    banuchka - 2015-02-04

    Yes, client have option '-M 230.4.3.100' and this is only one public address that they are listening.

    Im not sure that i know how to check your last question. Is it possible to explain little?

    Thank you for answer.

     
  • Dennis Bush

    Dennis Bush - 2015-02-05

    On the client machine, run a Wireshark trace to see if packets from the proxy sent to 230.4.3.100 are arriving. If not, you may need to set the TTL on the proxy (-t) and/or check your router settings.

     
  • banuchka

    banuchka - 2015-02-05

    yes, it was ttl. uftproxy is using first interface to send response from and ignoring all of my trunk interfaces.

    But for now there are a lot of messages like "2015/02/05 11:37:40.528803: Received PROXY_KEY from PROXY_MAIN_IP" in the client's log file. Maybe 10-20 messages per second. Is that fine?

     

    Last edit: banuchka 2015-02-05
  • banuchka

    banuchka - 2015-02-05

    Sorry, it is looks like as client capture all of requests from proxy, eg it capture all responses on key requests from other clients.

    Thanks for your help.

     
  • banuchka

    banuchka - 2015-02-05

    hope that it is last question about proxy: every time after file transfer it proxy logs i see strings like:

    2015/02/05 11:51:07.592617: [2501D6DA:0]: Sent COMPLETE
    2015/02/05 11:51:07.669917: [2501D6DA:0]: Received COMPLETE from 0x0A144119
    2015/02/05 11:51:07.803481: [2501D6DA:0]: Sent COMPLETE
    2015/02/05 11:51:09.138414: [2501D6DA:0]: Group timed out

    What does "Group timed out" mean?

     
  • Dennis Bush

    Dennis Bush - 2015-02-05

    The "Group timed out" message means that the proxy hasn't received any messages in either direction for some time. This is a normal occurrence at the end of a session, however it can also occur if the server or all clients drop out of the session for some reason.

     
  • banuchka

    banuchka - 2015-02-05

    so it isnt an error, right? if file present on all nodes.

     
  • Dennis Bush

    Dennis Bush - 2015-02-05

    Correct. If the client got confirmation from the server, it was successful.

     

Log in to post a comment.

Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.