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

kommunikation problem RMS relay <-> rmsgw

Expand Messages
  • Michael Przybilla
    Hi Group We have some little problems with RMS Relay here, working together with the LinuxRMSgw software. If one connects to the LinuxRMSgw (which is DB0FHW-9
    Message 1 of 3 , Jul 1, 2008
      Hi Group

      We have some little problems with RMS Relay here, working together
      with the LinuxRMSgw software.
      If one connects to the LinuxRMSgw (which is DB0FHW-9 in packet radio
      and IGATE) it connects to pactor.afu-ag.de:8772 which is the RMS Relay.
      RMS Relay then shows pending, but then the connection times out.
      Unfortunately there is nothing in the logs...

      In the ethernet sniff, you can see the LinuxRMSgw (141.41.64.81)
      connect to RMS Relay (141.41.64.82), RMS Relay requesting the
      Callsign, RMS Gw sending it.... And then timeout!

      Can you insert a debug log feature in rmsgw to track this down?
      I reported this to the WDT as well, to check RMS Relay.

      Greetings
      Micha
      DD2MIC

      -----Ursprüngliche Nachricht-----
      Von: admin-bounces@... [mailto:admin-bounces@...] Im
      Auftrag von Christof Vogeler DD7AN
      -----BEGIN PGP SIGNED MESSAGE-----
      Hash: SHA1


      micha,
      ich habe mal im netzwerk gesnifft. das problem liegt wohl in der
      kommunikation zwischen relay und rmsgw.

      der connect verläuft einwandfrei, danach erwart der relay das call
      der connectenden station und es steht erstmal <pending> im relay fenster.

      der rmsgw sendet dies auch zum relay, was aber dort nicht ankommt oder
      so ähnlich... danach kommt dann eben ein timeout, da der relay
      vom rmsgw "scheinbar" nichts hört.

      nur wo liegt nun das problem?! ich vermute mal das relay programm
      version 1.0.0.0 hat ein bug.



      T 2008/06/30 23:47:17.527709 141.41.64.81:56483 -> 141.41.64.82:8772 [S]
      #
      T 2008/06/30 23:47:17.527895 141.41.64.82:8772 -> 141.41.64.81:56483 [AS]
      #
      T 2008/06/30 23:47:17.527919 141.41.64.81:56483 -> 141.41.64.82:8772 [A]
      #
      T 2008/06/30 23:47:18.275593 141.41.64.82:8772 -> 141.41.64.81:56483 [AP]
      .Callsign :.
      #
      T 2008/06/30 23:47:18.275890 141.41.64.81:56483 -> 141.41.64.82:8772 [A]
      #
      T 2008/06/30 23:47:18.276012 141.41.64.81:56483 -> 141.41.64.82:8772 [AP]
      .DF0WFB.
      #
      T 2008/06/30 23:47:18.435703 141.41.64.82:8772 -> 141.41.64.81:56483 [A]
      #
      T 2008/06/30 23:48:18.253587 141.41.64.82:8772 -> 141.41.64.81:56483 [AP]
      Login timeout....
      #



      - --


      MfG
      Christof Vogeler (DD7AN)
      www.afu-ag.de
    • Hans-Juergen Barthen
      Michael, from your short description it looks like RMS Relay still requires the old login procedure. In the past the telpac software sent call, password and
      Message 2 of 3 , Jul 1, 2008
        Michael,
        from your short description it looks like RMS Relay still requires the old login procedure.
        In the past the telpac software sent call, password and telpac-node-call just in 1 string delimited by linefeeds as soon as the host came up with the login-prompt.
        It did not wait for any new prompt.
         
        With RMS Gateway we had to change that.
        We now need to send some more parameters like for example the channelnumber.
        rmsgw sends the callsign only and then waits for the next prompt from the host requesting the password.
        If that will not come from the RMS relay the connection will stock.
         
        This logon-dialog was 1 of the changes implemented with the new rmsgw.
        I don't know if this is something that still needs to be changed on the relay-software or if it is necessary to use a special login procedure for relays in rmsgw.
         
        If my understanding of your email as described above is correct, I will ask the developement team how to proceed.
        Please just let me know if I understood it correct.
         
         
        Thanks!
         
        Hans, DL5DI


        Von: LinuxRMS@yahoogroups.com [mailto:LinuxRMS@yahoogroups.com] Im Auftrag von Michael Przybilla
        Gesendet: Dienstag, 1. Juli 2008 09:56
        An: LinuxRMS@yahoogroups.com
        Betreff: [LinuxRMS] kommunikation problem RMS relay <-> rmsgw

        Hi Group

        We have some little problems with RMS Relay here, working together
        with the LinuxRMSgw software.
        If one connects to the LinuxRMSgw (which is DB0FHW-9 in packet radio
        and IGATE) it connects to pactor.afu-ag. de:8772 which is the RMS Relay.
        RMS Relay then shows pending, but then the connection times out.
        Unfortunately there is nothing in the logs...

        In the ethernet sniff, you can see the LinuxRMSgw (141.41.64.81)
        connect to RMS Relay (141.41.64.82) , RMS Relay requesting the
        Callsign, RMS Gw sending it.... And then timeout!

        Can you insert a debug log feature in rmsgw to track this down?
        I reported this to the WDT as well, to check RMS Relay.

        Greetings
        Micha
        DD2MIC

        -----Ursprüngliche Nachricht--- --
        Von: admin-bounces@ afu-ag.de [mailto:admin-bounces@ afu-ag.de] Im
        Auftrag von Christof Vogeler DD7AN
        -----BEGIN PGP SIGNED MESSAGE-----
        Hash: SHA1

        micha,
        ich habe mal im netzwerk gesnifft. das problem liegt wohl in der
        kommunikation zwischen relay und rmsgw.

        der connect verläuft einwandfrei, danach erwart der relay das call
        der connectenden station und es steht erstmal <pending> im relay fenster.

        der rmsgw sendet dies auch zum relay, was aber dort nicht ankommt oder
        so ähnlich... danach kommt dann eben ein timeout, da der relay
        vom rmsgw "scheinbar" nichts hört.

        nur wo liegt nun das problem?! ich vermute mal das relay programm
        version 1.0.0.0 hat ein bug.

        T 2008/06/30 23:47:17.527709 141.41.64.81: 56483 -> 141.41.64.82: 8772 [S]
        #
        T 2008/06/30 23:47:17.527895 141.41.64.82: 8772 -> 141.41.64.81: 56483 [AS]
        #
        T 2008/06/30 23:47:17.527919 141.41.64.81: 56483 -> 141.41.64.82: 8772 [A]
        #
        T 2008/06/30 23:47:18.275593 141.41.64.82: 8772 -> 141.41.64.81: 56483 [AP]
        .Callsign :.
        #
        T 2008/06/30 23:47:18.275890 141.41.64.81: 56483 -> 141.41.64.82: 8772 [A]
        #
        T 2008/06/30 23:47:18.276012 141.41.64.81: 56483 -> 141.41.64.82: 8772 [AP]
        .DF0WFB.
        #
        T 2008/06/30 23:47:18.435703 141.41.64.82: 8772 -> 141.41.64.81: 56483 [A]
        #
        T 2008/06/30 23:48:18.253587 141.41.64.82: 8772 -> 141.41.64.81: 56483 [AP]
        Login timeout....
        #

        - --

        MfG
        Christof Vogeler (DD7AN)
        www.afu-ag.de

      • Michael Przybilla
        Hi Hans Yes, please, can you clarify this with the WDT. From my point of view, it does not make sense, to have two different login procedures. Greetings Micha
        Message 3 of 3 , Jul 1, 2008
          Hi Hans

          Yes, please, can you clarify this with the WDT.
          From my point of view, it does not make sense, to have two different
          login procedures.

          Greetings
          Micha
          DD2MIC

          --- In LinuxRMS@yahoogroups.com, "Hans-Juergen Barthen" <dl5di@...> wrote:
          >
          > Michael,
          > from your short description it looks like RMS Relay still requires
          the old
          > login procedure.
          > In the past the telpac software sent call, password and telpac-node-call
          > just in 1 string delimited by linefeeds as soon as the host came up
          with the
          > login-prompt.
          > It did not wait for any new prompt.
          >
          > With RMS Gateway we had to change that.
          > We now need to send some more parameters like for example the
          channelnumber.
          > rmsgw sends the callsign only and then waits for the next prompt
          from the
          > host requesting the password.
          > If that will not come from the RMS relay the connection will stock.
          >
          > This logon-dialog was 1 of the changes implemented with the new rmsgw.
          > I don't know if this is something that still needs to be changed on the
          > relay-software or if it is necessary to use a special login
          procedure for
          > relays in rmsgw.
          >
          > If my understanding of your email as described above is correct, I
          will ask
          > the developement team how to proceed.
          > Please just let me know if I understood it correct.
          >
          >
          > Thanks!
          >
          > Hans, DL5DI
          >
        Your message has been successfully submitted and would be delivered to recipients shortly.