Menu

[broadcast] address => bug #529 => fixed with YAT 2.5.0 and above

TCP/IP
2021-11-15
2022-12-27
  • Ivaylo Iltchev

    Ivaylo Iltchev - 2021-11-15

    Hi,
    I have a board that implements RNDIS, Ethernet over USB interface and DHCP,
    DNS servers on this connection. If I try to connect with YAT to the dns
    address provided by the board, for example board.trm, dialog says: Invalid
    input, broadcast is not supported for a TCP/IP Client. Connecting to the
    same board via Ethernet and mDNS address board.local is available. Using
    www.board.trm, board.anyhow have the same result - Invalid input. Address
    board.trm is resolved by ping, Putty and CLI telnet client without problems.

    Regards

    [image: image.png]

     
    • Maettu

      Maettu - 2021-11-18

      Hi Ivaylo,

      I have not received any such report, but I guess way less people use TCP or UDP than serial COM with YAT.

      Could you tell me the IP address the URL relates to? There could be a bug in YAT's handling of special IP addresses.

      Or, if the IP indeed is a broadcast address, you should try with a UDP/IP client terminal. TCP/IP doesn't support broadcast. Maybe PuTTy or other telnet clients implement a mechanism to broadcast via UDP and then open a TCP connection. YAT does not (yet) implement such mechanism, but such of course could be requested here.

      Finally, you could capture and attach a Wireshark trace when doing this with PuTTy or CLI. This could help me understand the mechanism they use. I have googled and asked around whether any of my engineering colleagues know of any RFC that specifies such UDP to TCP discovery, no success so far. So additional information on the behavior would be appreciated.

      Best regards,
      Matthias

       
      • Anonymous

        Anonymous - 2022-04-05

        With the current version of YAT I observed this problem as well. Version 2.1.0 did not suffer from the error.

         
        • Maettu

          Maettu - 2022-04-05

          That's interesting, this now rang a bell! Because for 2.4.1:

          [broadcast] recently selected for UDP/IP remote host is no longer listed for TCP/IP (bug #508).

          Now if you see this, could you try also with 2.4.0? That would ease narrowing down this bug. And of course it will get fixed by 2.4.2.

           
          • Anonymous

            Anonymous - 2022-04-05

            Seems to work as expected with 2.4.0

             
            • Maettu

              Maettu - 2022-04-05

              Thanks! Then should find the buggy change quickly.

              Note that you may get notifcations on bug #529 to see when this got fixed and to get preliminary binaries if you like.

               
  • Maettu

    Maettu - 2022-04-05

    Bug #529 created.

     

    Last edit: Maettu 2022-08-04
    • Anonymous

      Anonymous - 2022-04-05

      Thanks a lot for your fast response!

       
  • Maettu

    Maettu - 2022-08-01

    Bug #529 fixed. Thread subject renamed from "[broadcast] address" to "[broadcast] address => bug #529 => fixed".

     

    Last edit: Maettu 2022-12-26
    • Maettu

      Maettu - 2022-12-26

      YAT 2.5.0 fixing this issue recently got released. Thread subject renamed to "...fixed with YAT 2.5.0 and above".

       

      Last edit: Maettu 2022-12-27

Anonymous
Anonymous

Add attachments
Cancel





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.