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

How BPQ CMS Access works - was RE: [BPQ32] Obselete gateway

Expand Messages
  • John Wiseman
    Dave, (and everyone using BPQ Telnet to access thr CMS system) This is my understanding of how the WL2K system works - I have copied this message to Lee and
    Message 1 of 5 , Jul 25, 2013
    • 0 Attachment
      Dave, (and everyone using BPQ Telnet to access thr CMS system)
       
       
      This is my understanding of how the WL2K system works - I have copied this message to Lee and Lor of the WL2K team, and would appreciate if they would correct any misunderstandings.
       
       
       
      The WL2K system recognises two types of stations - clients and gateways. Until recently access for both was the same. They now require gateway systems to have a password, AND authorisation from them to be a gateway. Any station can still be a client.
       
      BPQ32 can be either a client or a gateway. When BPQMail (or the sysop on a console) connects, it behaves as a client. When a station connects to a CMS via you, it acts as a gateway.
       
      BPQ32 (from Version 6.0.2.1) supports the new secure signon, BUT ONLY IF CONFIGURED TO DO SO. You must add CMSCALL and CMSPASS to your Telnet config - see http://www.cantab.net/users/john.wiseman/Documents/TelnetServer.htm##cms
       
      The WL2K software reports "*** Obsolete gateway detected - please notify sysop - Disconnecting " if a BPQ System tries to be a gateway without CMSCALL and CMSPASS being configured - IT DOES NOT NECESSARILY mean you are not running the required version.
       
       
      If you define CMSCALL and CMSPASS, the BPQ software will try to do all connects as a gateway, which will fail if the station is not Authorised to be a gateway. So if you only need Client access (ie for BPQMAIL, but not for stations connecting to you), and you don't meet the WL2K requirements to be a Gateway, you are better off omitting the CMSCALL/CMSPASS.
       
      If you want to be a gateway (in practice this means having any WL2KREPORT lines in your config, which enable reporting to the WL2K frequency/mode database), you must include CMSCALL/CMSPASS, and be Authorised by the WL2K team.
       
      73, John
       
       
       
       
       
       
       
       
       
       


      From: BPQ32@yahoogroups.com [mailto:BPQ32@yahoogroups.com] On Behalf Of k9drh@...
      Sent: 24 July 2013 23:07
      To: BPQ32@yahoogroups.com
      Subject: [BPQ32] Obselete gateway

       

      Well as well all have seen from the email this morning they changed the CMS. well when email sent from BPQ32 BBS works fine however if you (I) created a RMS Gateway node from within the program and you connect DRHRMS it complains of outdated gateway. are there two different gateways. from within BBS C RMS and connect DRHRMS should be the same gateway. Poll of RMS for my messages works and log supports

      21:57:14 10 K9IJ Connected to CMS
      21:57:14 10 Callsign :
      21:57:14 10 K9IJ
      21:57:14 10 Password :
      21:57:14 10 CMSTELNET K9DRH-10 145610000 1

      21:57:14 10 *** Obsolete gateway detected - please notify sysop - Disconnecting (75.32.34.91)<cr>
      21:57:25 10 Disconnected. Bytes Sent = 0 Bytes Received 82 Time 11 Seconds
      22:03:27 10 K9DRH Connected to CMS
      22:03:28 10 Callsign :
      22:03:28 10 K9DRH
      22:03:28 10 Password :
      22:03:28 10 CMSTELNET

      22:03:28 10 [WL2K-2.7.8.0-B2FWIHJM$]<cr>
      22:03:29 10 ;PQ: 89911734<cr>
      22:03:29 10 Wien CMS ><cr>
      22:03:29 10 ;FW: K9DRH RMS<cr>
      22:03:29 10 [BPQ-1.4.56.1-B2FIHJM$]<cr>
      22:03:29 10 FF<cr>
      22:03:30 10 FQ<cr>
      22:03:30 10 Disconnected. Bytes Sent = 42 Bytes Received 53 Time 3 Seconds

      Any ideas guys?

      Dave K9DRH

    • PE1RDW
      ... This means that when always pulling WL2K for users trough the BBS you do not need to request a gateway status? that would make setting up a hub for a local
      Message 2 of 5 , Jul 25, 2013
      • 0 Attachment
        Op 25-07-13 10:44, John Wiseman schreef:
        Dave, (and everyone using BPQ Telnet to access thr CMS system)
         
         
        This is my understanding of how the WL2K system works - I have copied this message to Lee and Lor of the WL2K team, and would appreciate if they would correct any misunderstandings.
         
         
         
        The WL2K system recognises two types of stations - clients and gateways. Until recently access for both was the same. They now require gateway systems to have a password, AND authorisation from them to be a gateway. Any station can still be a client.
         
        BPQ32 can be either a client or a gateway. When BPQMail (or the sysop on a console) connects, it behaves as a client. When a station connects to a CMS via you, it acts as a gateway.
         
        BPQ32 (from Version 6.0.2.1) supports the new secure signon, BUT ONLY IF CONFIGURED TO DO SO. You must add CMSCALL and CMSPASS to your Telnet config - see http://www.cantab.net/users/john.wiseman/Documents/TelnetServer.htm##cms
         
        The WL2K software reports "*** Obsolete gateway detected - please notify sysop - Disconnecting " if a BPQ System tries to be a gateway without CMSCALL and CMSPASS being configured - IT DOES NOT NECESSARILY mean you are not running the required version.
         
         
        If you define CMSCALL and CMSPASS, the BPQ software will try to do all connects as a gateway, which will fail if the station is not Authorised to be a gateway. So if you only need Client access (ie for BPQMAIL, but not for stations connecting to you), and you don't meet the WL2K requirements to be a Gateway, you are better off omitting the CMSCALL/CMSPASS.
         
        If you want to be a gateway (in practice this means having any WL2KREPORT lines in your config, which enable reporting to the WL2K frequency/mode database), you must include CMSCALL/CMSPASS, and be Authorised by the WL2K team.
         
        73, John
         

        This means that when always pulling WL2K for users trough the BBS you do not need to request a gateway status? that would make setting up a hub for a local group faster as you would not need to wait for the WDT to aprove your gateway status and run the risk of being rejected for whatever reason.

        73 Andre PE1RDW
      • John Wiseman
        I believe that is correct, yes, 73, John _____ From: BPQ32@yahoogroups.com [mailto:BPQ32@yahoogroups.com] On Behalf Of PE1RDW Sent: 25 July 2013 11:32 To:
        Message 3 of 5 , Jul 25, 2013
        • 0 Attachment
          I believe that is correct, yes,
           
          73, John


          From: BPQ32@yahoogroups.com [mailto:BPQ32@yahoogroups.com] On Behalf Of PE1RDW
          Sent: 25 July 2013 11:32
          To: BPQ32@yahoogroups.com
          Subject: Re: How BPQ CMS Access works - was RE: [BPQ32] Obselete gateway

           
          This means that when always pulling WL2K for users trough the BBS you do not need to request a gateway status? that would make setting up a hub for a local group faster as you would not need to wait for the WDT to aprove your gateway status and run the risk of being rejected for whatever reason.

          73 Andre PE1RDW

        • k9drh@sbcglobal.net
          Thanks John, That is what I thought I understood. I already set CMSCALL & Pass when 6.0.2 came out. Having had that set I thought everything was going to work.
          Message 4 of 5 , Jul 25, 2013
          • 0 Attachment
            Thanks John,
            That is what I thought I understood.
            I already set CMSCALL & Pass when 6.0.2 came out. Having had that set I thought everything was going to work. Since posting the original message everything for my call works whether Sysop or Client through BBS or direct to RMS telnet.
            However I still have one client that connects straight to RMS node that is still getting the error. I will have to work with him to see what he has setup that may be causing the error. Not sure what program he is using either.
            Again thanks for the clarification.
            Dave K9DRH

            --- In BPQ32@yahoogroups.com, "John Wiseman" <john.wiseman@...> wrote:
            >
            > Dave, (and everyone using BPQ Telnet to access thr CMS system)
            >
            >
            > This is my understanding of how the WL2K system works - I have copied this
            > message to Lee and Lor of the WL2K team, and would appreciate if they would
            > correct any misunderstandings.
            >
            >
            >
            > The WL2K system recognises two types of stations - clients and gateways.
            > Until recently access for both was the same. They now require gateway
            > systems to have a password, AND authorisation from them to be a gateway. Any
            > station can still be a client.
            >
            > BPQ32 can be either a client or a gateway. When BPQMail (or the sysop on a
            > console) connects, it behaves as a client. When a station connects to a CMS
            > via you, it acts as a gateway.
            >
            > BPQ32 (from Version 6.0.2.1) supports the new secure signon, BUT ONLY IF
            > CONFIGURED TO DO SO. You must add CMSCALL and CMSPASS to your Telnet config
            > - see
            > <http://www.cantab.net/users/john.wiseman/Documents/TelnetServer.htm##cms>
            > http://www.cantab.net/users/john.wiseman/Documents/TelnetServer.htm##cms
            >
            > The WL2K software reports "*** Obsolete gateway detected - please notify
            > sysop - Disconnecting " if a BPQ System tries to be a gateway without
            > CMSCALL and CMSPASS being configured - IT DOES NOT NECESSARILY mean you are
            > not running the required version.
            >
            >
            > If you define CMSCALL and CMSPASS, the BPQ software will try to do all
            > connects as a gateway, which will fail if the station is not Authorised to
            > be a gateway. So if you only need Client access (ie for BPQMAIL, but not for
            > stations connecting to you), and you don't meet the WL2K requirements to be
            > a Gateway, you are better off omitting the CMSCALL/CMSPASS.
            >
            > If you want to be a gateway (in practice this means having any WL2KREPORT
            > lines in your config, which enable reporting to the WL2K frequency/mode
            > database), you must include CMSCALL/CMSPASS, and be Authorised by the WL2K
            > team.
            >
            > 73, John
            >
            >
            >
            >
            >
            >
            >
            >
            >
            >
            >
            > _____
            >
            > From: BPQ32@yahoogroups.com [mailto:BPQ32@yahoogroups.com] On Behalf Of
            > k9drh@...
            > Sent: 24 July 2013 23:07
            > To: BPQ32@yahoogroups.com
            > Subject: [BPQ32] Obselete gateway
            >
            >
            >
            >
            > Well as well all have seen from the email this morning they changed the CMS.
            > well when email sent from BPQ32 BBS works fine however if you (I) created a
            > RMS Gateway node from within the program and you connect DRHRMS it complains
            > of outdated gateway. are there two different gateways. from within BBS C RMS
            > and connect DRHRMS should be the same gateway. Poll of RMS for my messages
            > works and log supports
            >
            > 21:57:14 10 K9IJ Connected to CMS
            > 21:57:14 10 Callsign :
            > 21:57:14 10 K9IJ
            > 21:57:14 10 Password :
            > 21:57:14 10 CMSTELNET K9DRH-10 145610000 1
            >
            > 21:57:14 10 *** Obsolete gateway detected - please notify sysop -
            > Disconnecting (75.32.34.91)<cr>
            > 21:57:25 10 Disconnected. Bytes Sent = 0 Bytes Received 82 Time 11 Seconds
            > 22:03:27 10 K9DRH Connected to CMS
            > 22:03:28 10 Callsign :
            > 22:03:28 10 K9DRH
            > 22:03:28 10 Password :
            > 22:03:28 10 CMSTELNET
            >
            > 22:03:28 10 [WL2K-2.7.8.0-B2FWIHJM$]<cr>
            > 22:03:29 10 ;PQ: 89911734<cr>
            > 22:03:29 10 Wien CMS ><cr>
            > 22:03:29 10 ;FW: K9DRH RMS<cr>
            > 22:03:29 10 [BPQ-1.4.56.1-B2FIHJM$]<cr>
            > 22:03:29 10 FF<cr>
            > 22:03:30 10 FQ<cr>
            > 22:03:30 10 Disconnected. Bytes Sent = 42 Bytes Received 53 Time 3 Seconds
            >
            > Any ideas guys?
            >
            > Dave K9DRH
            >
          Your message has been successfully submitted and would be delivered to recipients shortly.