Loading ...
Sorry, an error occurred while loading the content.

How to Update TBD?

Expand Messages
  • Tim - WD6AWP
    I ve had a strange problem where some echolink users can t head my node. They can connect and transmit but don t hear. I ve been talking to Skip WB6YMH (tbd
    Message 1 of 2 , Jun 10, 2010
    • 0 Attachment
      I've had a strange problem where some echolink users can't head my node. They can connect and transmit but don't hear. I've been talking to Skip WB6YMH (tbd author) and he feels that updating tbd will help with problem. This from the tbd release notes:

        427 ####################################
       428 Changes in version 0.86, 12/8/2007: (limited beta release)
       429
       430 Bug Fixes:
       431 1. Modified code so data is always sent from the appropriate port. Previously
       432    IRLP data (after conversion to EchoLink format) was sent to the EchoLink
       433    ports, but from the IRLP ports.  Normally this is not a problem, but if
       434    a user's firewall is using dynamic rules created by outbound packets then
       435    the these packets would be lost.  Effect is some EchoLink clients can not
       436    hear IRLP stations via integrated IRLP/EchoLink conferences.

       356 ####################################
       357 Changes in version 0.89, 2/9/2008:
       358
       359 Minor enhancements:
       360 1. Added Echolink firewall mitigation code courtesy of Johnathan K1RFD.
       361    This code is invoked by the .connect command to assist with connections to
       362    version 2.0 and above EchoLink nodes located behind unconfigured firewalls.
       363    For more details about the new firewall friendliness of Echolink 2.x see
       364    http://www.echolink.org/firewall-friendly.htm .

      So I either need to know the tool chain used to build tbd so I can have Skip build it, or I need a new binary. Any help out there?

      TIA,
      Tim WD6AWP
    • David Cameron (IRLP)
      You can build it under CentOS 4.8 and it should work on the embedded nodes (as a binary). I use a Slackware 10 build environment for most compiling for IRLP,
      Message 2 of 2 , Jun 14, 2010
      • 0 Attachment
        You can build it under CentOS 4.8 and it should work on the embedded
        nodes (as a binary). I use a Slackware 10 build environment for most
        compiling for IRLP, including the TBD that is currently shipped with
        embedded nodes.

        Be aware that there may be additional changes to the tbd.conf file that
        may make your node not work correctly.

        Dave Cameron

        Tim - WD6AWP wrote:
        >
        >
        > I've had a strange problem where some echolink users can't head my node.
        > They can connect and transmit but don't hear. I've been talking to Skip
        > WB6YMH (tbd author) and he feels that updating tbd will help with
        > problem. This from the tbd release notes:
        >
        > 427 ####################################
        > 428 Changes in version 0.86, 12/8/2007: (limited beta release)
        > 429
        > 430 Bug Fixes:
        > 431 1. Modified code so data is always sent from the appropriate port.
        > Previously
        > 432 IRLP data (after conversion to EchoLink format) was sent to the
        > EchoLink
        > 433 ports, but from the IRLP ports. Normally this is not a problem,
        > but if
        > 434 a user's firewall is using dynamic rules created by outbound
        > packets then
        > 435 the these packets would be lost. Effect is some EchoLink
        > clients can not
        > 436 hear IRLP stations via integrated IRLP/EchoLink conferences.
        >
        > 356 ####################################
        > 357 Changes in version 0.89, 2/9/2008:
        > 358
        > 359 Minor enhancements:
        > 360 1. Added Echolink firewall mitigation code courtesy of Johnathan K1RFD.
        > 361 This code is invoked by the .connect command to assist with
        > connections to
        > 362 version 2.0 and above EchoLink nodes located behind unconfigured
        > firewalls.
        > 363 For more details about the new firewall friendliness of Echolink
        > 2.x see
        > 364 http://www.echolink.org/firewall-friendly.htm .
        >
        > So I either need to know the tool chain used to build tbd so I can have
        > Skip build it, or I need a new binary. Any help out there?
        >
        > TIA,
        > Tim WD6AWP
        >
        >
      Your message has been successfully submitted and would be delivered to recipients shortly.