Добро пожаловать, Гость. Пожалуйста авторизуйтесь здесь.
FGHIGate на GaNJa NeTWoRK ST@Ti0N - Просмотр сообщения в эхоконференции FTSC_PUBLIC
Введите FGHI ссылку:


Присутствуют сообщения из эхоконференции FTSC_PUBLIC с датами от 13 Sep 13 18:57:24 до 01 Apr 24 01:17:44, всего сообщений: 7124
Ответить на сообщение К списку сообщений Предыдущее сообщение Следующее сообщение
= Сообщение: 5283 из 7124 ====================================== FTSC_PUBLIC =
От   : Michiel van der Vlist            2:280/5555         19 Nov 20 09:34:20
Кому : Jeff Smith                                          19 Nov 20 09:34:20
Тема : Nodelist Thoughts?
FGHI : area://FTSC_PUBLIC?msgid=2:280/5555+5fb62e0e
На   : area://FTSC_PUBLIC?msgid=1:282/1031.0+71a4f347
= Кодировка сообщения определена как: UTF-8 ==================================
==============================================================================
Hello Jeff,

On Saturday October 31 2020 12:38, you wrote to Carol Shenkenberger:

JS> If a non-standard port is in use I use the syntax INA:FQDN/IP:<port>

Different protocols use different ports. A port is associated with one specific protocol and one protocol only. If a protocol uses a port not standard for that protocol that non standard port applies to that protocol only. Therefore a non standard port should be attached to the protocol flag.

The INA flag is not a protocol flag, but a server address flag. It never carries a port number, just an address.

So this:

,26,Stepping_Stone_BBS,Wichita_Kansas,Jon_Justvig,-Unpublished-,300,CM,INA::steppingstone bbs.com:24555,CM,ITN,IBN

  ... is wrong. (apart from the double CM flag) The proper way to list is:

,26,Stepping_Stone_BBS,Wichita_Kansas,Jon_Justvig,-Unpublished-,300,CM,INA:steppingstoneb bs.com,ITN,IBN:24555

The system is connectable via steppingstonebbs.com and supports two protocols: IBN and ITN. ITN via the standard port 23 and IBN via the non stamdard port 24555.


From FTS-5001.006:

====  quote == ====

  There are five classes of Internet Capability flags:


   .1 Internet Protocol Flags
   --------------------------

   Internet Protocol flags use the syntax:

   <flag>[:<server address>][:<port>]

   Where <server address> is:
   * a fully qualified domain name (FQDN), or
   * an IPv6 address encased in square brackets, or
   * an IPv4 address in dotted-quad format

   and <port> is the decimal service port number. A port number
   should only be specified if it is not the default port number
   for that protocol.


        Default
   Flag     port Description
   --------------------------


   IBN    24554  Binkp (FTS-1026 - FTS-1030)
   IFC    60179  RAW ifcico (FTS-1024)
   IFT       21  FTP (RFC-0959); Note there is currently no widely
                 accepted authentication scheme for FTP transfers by
                 Fidonet mailers.
   ITN       23  Telnet connection using FTS-1 or any other protocol
                 designed for classic POTS and modem.
   IVM     3141  Vmodem connection using FTS-1 or any other protocol
                 designed for classic POTS and modem.
   IP      none  Mostly used during the introduction of IP capable
                 systems to the nodelist. Denotes an unspecified
                 protocol. (Deprecated)


   .2 Server Address Flags
   -------------------------

   Server address flags use the syntax:

   <flag>:<server address>

   Where <server address> is the same as for protocol flags.
   These flags are used to specify a server address for Internet
   Protocol Flags that do not specify an address themselves.

   Flag          Description
   -------------------------

   INA           This flag sets a default server address used
                 for any Internet Protocol Flag that does not
                 specify its own.


   .3 Internet Information Flags
   -----------------------------

   Internet Informations Flags use the syntax:

   <flag>

   These flags are used to signal additional information
   regarding the internet connection.

   Flag          Description
   -------------------------

   INO4          Indicates that an otherwise IP capable node is
                 unable to accept incoming connections over IPv4.
                 (FRL-1038)
   ICM           Node accepts mail 24 hours a day using all listed
                 TCP/IP methods, but not all of the other listed
                 methods (such as PSTN/ISDN) and therefore cannot
                 be CM.  See FRL-1017.
                 See also the CM flag under section 5.1



==== end quote ====

Hope this helps.


Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin: http://www.vlist.org (2:280/5555)

К главной странице гейта
Powered by NoSFeRaTU`s FGHIGate
Открытие страницы: 0.045276 секунды