Home Forums Legacy SDKs other Network Sessions with REX TCPIP Driver

This topic contains 3 replies, has 4 voices, and was last updated by  Grant [Tobii] 3 months, 2 weeks ago.

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #618

    Ian Smith
    Participant

    I was hoping to find a port I could connect to directly and get a data stream. Instead I see a control port with multiple sessions on a fake IP 172.28.195.1 (internet black hole address) and 172.68.195.1 (this shouldn’t be used, it is a real IP address on the internet).

    (With Eye Tracking)
    TCP 127.0.0.1:10667 127.0.0.1:10669 TIME_WAIT
    TCP 127.0.0.1:10668 127.0.0.1:10670 TIME_WAIT
    TCP 127.0.0.1:10669 127.0.0.1:10667 TIME_WAIT
    TCP 127.0.0.1:10674 127.0.0.1:10676 TIME_WAIT
    TCP 127.0.0.1:10675 127.0.0.1:10677 TIME_WAIT
    TCP 127.0.0.1:10681 127.0.0.1:10683 TIME_WAIT
    TCP 127.0.0.1:10682 127.0.0.1:10684 TIME_WAIT
    TCP 127.0.0.1:10688 127.0.0.1:10690 TIME_WAIT
    TCP 127.0.0.1:10689 127.0.0.1:10692 TIME_WAIT
    TCP 127.0.0.1:10696 127.0.0.1:10698 TIME_WAIT
    TCP 127.0.0.1:10697 127.0.0.1:10699 TIME_WAIT
    TCP 127.0.0.1:10699 127.0.0.1:10697 TIME_WAIT
    TCP 127.0.0.1:10703 127.0.0.1:10705 TIME_WAIT
    TCP 127.0.0.1:10704 127.0.0.1:10706 TIME_WAIT
    TCP 127.0.0.1:10710 127.0.0.1:10712 TIME_WAIT
    TCP 127.0.0.1:10711 127.0.0.1:10713 TIME_WAIT
    TCP 127.0.0.1:10718 127.0.0.1:10720 TIME_WAIT
    TCP 127.0.0.1:10719 127.0.0.1:10721 TIME_WAIT
    TCP 127.0.0.1:10725 127.0.0.1:10727 TIME_WAIT
    TCP 127.0.0.1:10726 127.0.0.1:10728 TIME_WAIT
    TCP 127.0.0.1:10733 127.0.0.1:10736 TIME_WAIT
    TCP 127.0.0.1:10734 127.0.0.1:10735 TIME_WAIT
    TCP 127.0.0.1:10740 127.0.0.1:10742 ESTABLISHED
    TCP 127.0.0.1:10741 127.0.0.1:10743 ESTABLISHED
    TCP 127.0.0.1:10742 127.0.0.1:10740 ESTABLISHED
    TCP 127.0.0.1:10743 127.0.0.1:10741 ESTABLISHED
    TCP 192.168.1.7:10691 172.28.195.1:4455 SYN_SENT
    TCP 192.168.1.7:10693 172.68.195.1:4455 SYN_SENT
    TCP 192.168.1.7:10700 172.68.195.1:4455 SYN_SENT
    TCP 192.168.1.7:10701 172.28.195.1:4455 SYN_SENT
    TCP 192.168.1.7:10707 172.28.195.1:4455 SYN_SENT
    TCP 192.168.1.7:10708 172.68.195.1:4455 SYN_SENT
    TCP 192.168.1.7:10714 172.28.195.1:4455 SYN_SENT
    TCP 192.168.1.7:10715 172.68.195.1:4455 SYN_SENT
    TCP 192.168.1.7:10722 172.28.195.1:4455 SYN_SENT
    TCP 192.168.1.7:10723 172.68.195.1:4455 SYN_SENT
    TCP 192.168.1.7:10729 172.28.195.1:4455 SYN_SENT
    TCP 192.168.1.7:10730 172.68.195.1:4455 SYN_SENT
    TCP 192.168.1.7:10737 172.68.195.1:4455 SYN_SENT
    TCP 192.168.1.7:10738 172.28.195.1:4455 SYN_SENT
    TCP 192.168.1.7:10744 172.28.195.1:4455 SYN_SENT
    TCP 192.168.1.7:10745 172.68.195.1:4455 SYN_SENT

    (I stopped eye tracking)
    TCP 127.0.0.1:10771 127.0.0.1:10773 TIME_WAIT
    TCP 127.0.0.1:10772 127.0.0.1:10774 TIME_WAIT
    TCP 127.0.0.1:10778 127.0.0.1:10780 TIME_WAIT
    TCP 127.0.0.1:10779 127.0.0.1:10781 TIME_WAIT
    TCP 127.0.0.1:10781 127.0.0.1:10779 TIME_WAIT
    TCP 127.0.0.1:10786 127.0.0.1:10788 TIME_WAIT
    TCP 127.0.0.1:10787 127.0.0.1:10789 TIME_WAIT
    TCP 127.0.0.1:10793 127.0.0.1:10795 TIME_WAIT
    TCP 127.0.0.1:10794 127.0.0.1:10796 TIME_WAIT
    TCP 127.0.0.1:10801 127.0.0.1:10803 TIME_WAIT
    TCP 127.0.0.1:10802 127.0.0.1:10804 TIME_WAIT
    TCP 127.0.0.1:10808 127.0.0.1:10810 TIME_WAIT
    TCP 127.0.0.1:10809 127.0.0.1:10811 TIME_WAIT
    TCP 127.0.0.1:10811 127.0.0.1:10809 TIME_WAIT
    TCP 127.0.0.1:10816 127.0.0.1:10818 TIME_WAIT
    TCP 127.0.0.1:10817 127.0.0.1:10819 TIME_WAIT
    TCP 127.0.0.1:10824 127.0.0.1:10826 TIME_WAIT
    TCP 127.0.0.1:10825 127.0.0.1:10827 TIME_WAIT
    TCP 127.0.0.1:10831 127.0.0.1:10834 TIME_WAIT
    TCP 127.0.0.1:10832 127.0.0.1:10833 TIME_WAIT
    TCP 127.0.0.1:10834 127.0.0.1:10831 TIME_WAIT
    TCP 127.0.0.1:10839 127.0.0.1:10841 TIME_WAIT
    TCP 127.0.0.1:10840 127.0.0.1:10842 TIME_WAIT
    TCP 192.168.1.7:10797 172.28.195.1:4455 SYN_SENT
    TCP 192.168.1.7:10798 172.68.195.1:4455 SYN_SENT
    TCP 192.168.1.7:10805 172.28.195.1:4455 SYN_SENT
    TCP 192.168.1.7:10806 172.68.195.1:4455 SYN_SENT
    TCP 192.168.1.7:10812 172.68.195.1:4455 SYN_SENT
    TCP 192.168.1.7:10813 172.28.195.1:4455 SYN_SENT
    TCP 192.168.1.7:10820 172.28.195.1:4455 SYN_SENT
    TCP 192.168.1.7:10821 172.68.195.1:4455 SYN_SENT
    TCP 192.168.1.7:10828 172.28.195.1:4455 SYN_SENT
    TCP 192.168.1.7:10829 172.68.195.1:4455 SYN_SENT
    TCP 192.168.1.7:10835 172.28.195.1:4455 SYN_SENT
    TCP 192.168.1.7:10836 172.68.195.1:4455 SYN_SENT
    TCP 192.168.1.7:10843 172.28.195.1:4455 SYN_SENT
    TCP 192.168.1.7:10844 172.68.195.1:4455 SYN_SENT

    Is there any way I can connect to the stream? I don’t mind doing struct unpacking or variable length byte arrays. It appears a lot of port hopping occurs with 4455 acting as the control session (in the same way FTP has a dedicated control port, with data sent on another port).

    I have some wireshark dumps as well, I’d like to be able to parse and relay this. In the meantime, I’ll be making a telnet server to relay data.

    #619

    Anders [Tobii]
    Moderator

    Hi Ian,
    the protocol that runs on top of TCP/IP is Tobii proprietary, and the only supported way to access the eye tracker is by using the client libraries included with our SDKs. If that isn’t possible for your application, please let us know what it is you’re trying to achieve and we’ll see if we can help you out.

    #8744

    Indeed
    Participant

    4 years and 4 months have passed since Ian posted this, but tobii is still actively vomiting into users’ networks.
    No, disabling tobii (tray icon > open > off) doesn’t stop this flood.
    Yes, every second, the C:\Program Files (x86)\Tobii\Service\tobii.Service.exe tries hard to reach out to 172.28.195.1:4455 (which, of course, does not exist in most networks).

    Please, developers @ tobii, get your act together and learn to write software so, that it behaves politely in your customers computers AND in the networks those computers are connected to.

    #8753

    Grant [Tobii]
    Moderator

    Hi @user, sorry to hear about your unsatisfactory experience. This network activity is a result of support for earlier eye tracker models which we still try to support even in our latest software versions which requires regularly polling this address in order to discover if such a tracker is available.

    We do however understand that this is not the case for most recent users and accordingly we are currently transitioning to a new architecture where the need for this type of polling can be removed. Our apologies for the inconvenience during this transition period and thanks for your patience.

Viewing 4 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic.