Tillbaka till svenska Fidonet
English   Information   Debug  
ENET.SYSOP   33773
ENET.TALKS   0/32
ENGLISH_TUTOR   0/2000
EVOLUTION   0/1335
FDECHO   0/217
FDN_ANNOUNCE   0/7068
FIDONEWS   23439
FIDONEWS_OLD1   0/49742
FIDONEWS_OLD2   0/35949
FIDONEWS_OLD3   0/30874
FIDONEWS_OLD4   0/37224
FIDO_SYSOP   12841
FIDO_UTIL   0/180
FILEFIND   0/209
FILEGATE   0/212
FILM   0/18
FNEWS_PUBLISH   4155
FN_SYSOP   41520
FN_SYSOP_OLD1   71952
FTP_FIDO   0/2
FTSC_PUBLIC   0/13557
FUNNY   0/4886
GENEALOGY.EUR   0/71
GET_INFO   105
GOLDED   0/408
HAM   0/16041
HOLYSMOKE   0/6791
HOT_SITES   0/1
HTMLEDIT   0/71
HUB203   466
HUB_100   264
HUB_400   39
HUMOR   0/29
IC   0/2851
INTERNET   0/424
INTERUSER   0/3
IP_CONNECT   719
JAMNNTPD   0/233
JAMTLAND   0/47
KATTY_KORNER   0/41
LAN   0/16
LINUX-USER   0/19
LINUXHELP   0/1155
LINUX   0/22002
LINUX_BBS   0/957
mail   18.68
mail_fore_ok   249
MENSA   0/341
MODERATOR   0/102
MONTE   0/992
MOSCOW_OKLAHOMA   0/1245
MUFFIN   0/783
MUSIC   0/321
N203_STAT   894
N203_SYSCHAT   313
NET203   321
NET204   69
NET_DEV   0/10
NORD.ADMIN   0/101
NORD.CHAT   0/2572
NORD.FIDONET   189
NORD.HARDWARE   0/28
NORD.KULTUR   0/114
NORD.PROG   0/32
NORD.SOFTWARE   0/88
NORD.TEKNIK   0/58
NORD   0/453
OCCULT_CHAT   0/93
OS2BBS   0/787
OS2DOSBBS   0/580
OS2HW   0/42
OS2INET   0/37
OS2LAN   0/134
OS2PROG   0/36
OS2REXX   0/113
OS2USER-L   207
OS2   0/4779
OSDEBATE   0/18996
PASCAL   0/490
PERL   0/457
PHP   0/45
POINTS   0/405
POLITICS   0/29554
POL_INC   0/14731
PSION   103
R20_ADMIN   1117
R20_AMATORRADIO   0/2
R20_BEST_OF_FIDONET   13
R20_CHAT   0/893
R20_DEPP   0/3
R20_DEV   399
R20_ECHO2   1379
R20_ECHOPRES   0/35
R20_ESTAT   0/719
R20_FIDONETPROG...
...RAM.MYPOINT
  0/2
R20_FIDONETPROGRAM   0/22
R20_FIDONET   0/248
R20_FILEFIND   0/24
R20_FILEFOUND   0/22
R20_HIFI   0/3
R20_INFO2   2632
R20_INTERNET   0/12940
R20_INTRESSE   0/60
R20_INTR_KOM   0/99
R20_KANDIDAT.CHAT   42
R20_KANDIDAT   28
R20_KOM_DEV   112
R20_KONTROLL   0/13030
R20_KORSET   0/18
R20_LOKALTRAFIK   0/24
R20_MODERATOR   0/1852
R20_NC   76
R20_NET200   245
R20_NETWORK.OTH...
...ERNETS
  0/13
R20_OPERATIVSYS...
...TEM.LINUX
  0/44
R20_PROGRAMVAROR   0/1
R20_REC2NEC   534
R20_SFOSM   0/340
R20_SF   0/108
R20_SPRAK.ENGLISH   0/1
R20_SQUISH   107
R20_TEST   2
R20_WORST_OF_FIDONET   12
RAR   0/9
RA_MULTI   106
RA_UTIL   0/162
REGCON.EUR   0/2055
REGCON   0/13
SCIENCE   0/1206
SF   0/239
SHAREWARE_SUPPORT   0/5146
SHAREWRE   0/14
SIMPSONS   0/169
STATS_OLD1   0/2539.065
STATS_OLD2   0/2530
STATS_OLD3   0/2395.095
STATS_OLD4   0/1692.25
SURVIVOR   0/495
SYSOPS_CORNER   0/3
SYSOP   0/84
TAGLINES   0/112
TEAMOS2   0/4530
TECH   0/2617
TEST.444   0/105
TRAPDOOR   0/19
TREK   0/755
TUB   0/290
UFO   0/40
UNIX   0/1316
USA_EURLINK   0/102
USR_MODEMS   0/1
VATICAN   0/2740
VIETNAM_VETS   0/14
VIRUS   0/378
VIRUS_INFO   0/201
VISUAL_BASIC   0/473
WHITEHOUSE   0/5187
WIN2000   0/101
WIN32   0/30
WIN95   0/4275
WIN95_OLD1   0/70272
WINDOWS   0/1517
WWB_SYSOP   0/419
WWB_TECH   0/810
ZCC-PUBLIC   0/1
ZEC   4

 
4DOS   0/134
ABORTION   0/7
ALASKA_CHAT   0/506
ALLFIX_FILE   0/1313
ALLFIX_FILE_OLD1   0/7997
ALT_DOS   0/152
AMATEUR_RADIO   0/1039
AMIGASALE   0/14
AMIGA   0/331
AMIGA_INT   0/1
AMIGA_PROG   0/20
AMIGA_SYSOP   0/26
ANIME   0/15
ARGUS   0/924
ASCII_ART   0/340
ASIAN_LINK   0/651
ASTRONOMY   0/417
AUDIO   0/92
AUTOMOBILE_RACING   0/105
BABYLON5   0/17862
BAG   135
BATPOWER   0/361
BBBS.ENGLISH   0/382
BBSLAW   0/109
BBS_ADS   0/5290
BBS_INTERNET   0/507
BIBLE   0/3563
BINKD   0/1119
BINKLEY   0/215
BLUEWAVE   0/2173
CABLE_MODEMS   0/25
CBM   0/46
CDRECORD   0/66
CDROM   0/20
CLASSIC_COMPUTER   0/378
COMICS   0/15
CONSPRCY   0/899
COOKING   27601
COOKING_OLD1   0/24719
COOKING_OLD2   0/40862
COOKING_OLD3   0/37489
COOKING_OLD4   0/35496
COOKING_OLD5   9370
C_ECHO   0/189
C_PLUSPLUS   0/31
DIRTY_DOZEN   0/201
DOORGAMES   0/1974
DOS_INTERNET   0/196
duplikat   5999
ECHOLIST   0/18295
EC_SUPPORT   0/318
ELECTRONICS   0/359
ELEKTRONIK.GER   1534
ENET.LINGUISTIC   0/13
ENET.POLITICS   0/4
ENET.SOFT   0/11701
Möte FIDONEWS_OLD4, 37224 texter
 lista första sista föregående nästa
Text 4210, 207 rader
Skriven 2012-09-23 14:59:54 av Nick Kill (1:261/1406)
Ärende: Fidonews Vol 29 no 39 Page: 3
=====================================
    =================================================================
                          A R T I C L E S
    =================================================================



    Not Just For the New/Returning SysOp
    By Janis Kracht, 1:261/38, janis@filegate.net

    This article isn't meant to be a reference in the way that FTS
    documents (Fidonet Technical Standards) are.  This article may
    though encourage you, as a sysop, to read the appropriate FTS
    documents at FTSC.ORG.

    Internet nodelist flags were recently brought up in the Fidonews
    echo by Dale Shipp.  Good idea, Dale.  This is something that
    all sysops in fidonet should be aware of..  And NCs should be
    checking their segments to correct those entries where Internet
    capability flags are used incorrectly.

    A look at Some of the Nodelist Internet Capability Flags:
    ========================================================

    Because we deal with these terms and protocol flags every day,
    it can be easy to fall into the trap of assuming everyone knows
    their meaning, and how to use them.

    An example is the telnet flag, ITN.

    ITN

    Question: Who is that flag for?  Is it for systems who run an
    internet bbs and have telnet capability for USERS to their BBS
    systems?  If so, shouldn't all internet nodes have that flag
    somewhere in their nodelist entry?

    Well, the answer to both questions above is no.  Please read on.

    The ITN flag is meant to describe a Fidonet system that has a
    telnet _Mailer_ protocol enabled.

    In other words, this flag, as well as all of the flags listed in
    table 1, are meant to show Mailer capabilities, not BBS
    capabilities say for end-users or sysops who browse the Fidonet
    nodelist looking for telnet accessible bbs systems.

    An example of a Fidonet mailers that can handle a telnet mailer
    connection is BBBS's mailer daemon, for example.

    For listing bbs capabilities of interest to users one ought to
    have your bbs listed say in a fidonet bbs list where you can
    list the features of your bbs that users might enjoy..  like the
    FidoGazette BBS list, for example, or the bbs-scene BBS list.

    Where to Use It:

    You can use the ITN flag as part of an INA: segment of your
    nodelist entry thus:

    ,INA:somedomain.com,ITN,

    or:

    ,ITN:60177,

    In the example above, one is specifying a port other than the
    standard telnet port after the colon.

    ===

    IBN

    The original BinkP protocol was designed and developed by
    Fidonet sysop, Dima Maloff for his then new BinkD mailer.

    Since then, the BinkP protocol has been adopted by many internet
    mailers such as MBSE, BBBS, Argus and Radius and I'm sure many
    others.

    Some bbs packages which do not have an FTN mailer "built-in",
    but rely upon usage of a separate mailer like BinkD or Argus and
    it's clones, provide hooks in the setup to use your preferred
    mailers' implementation of BinkP (Synchronet is an example
    there).

    Though it sounds a bit simplistic (and I know this is very much
    so) one might consider the binkp protocol to be similar to a
    combination of ftp and telnet, but more secure and probably
    faster than both those protocols.

    Where to Use it:

    Again, you can use it in your INA: segment of your nodelist
    entry:

    ,INA:somedomain.com,IBN:24555,

    or all by itself:

    ,IBN,

    or specify a non-standard port:

    ,IBN:24555,

    ===

    IFT

    The IFT flag may be a bone of contention to some since it's hard
    to sometimes imagine a mailer that uses FTP for Fidonet mail
    transfers..  but they do exist.  Once you set up a password and
    other information, that site would then be accessible to you.

    BBBS allows you to send to a node by his or her nodenumber, via
    ftp.  Once again it must be stressed this is a mailer flag, not
    a 'bbs capability flag', i.e, where a bbs allows nodes to ftp
    files.

    Where to Use It:

    You can list the flag by itself,

    ,IFT,

    or in of course the INA: statement:

    ,INA:somedomain.com,ITN,IBN:24555,IFT:60724,



    ===

    INA:

    This flag, designed by Ross Cassell, R18C, can be used to solve
    problems like multiple domains which might take up additional
    lines in the nodelist, or (and this was the reason it was
    created by Ross) to keep nodelist entry lines to a length
    acceptable to many Operating Systems.  When used properly as
    intended, it can save a good deal of characters on one line of a
    nodelist entry.

    It should be the last protocol flag in an entry in the nodelist

    As Ross put it so well when he first documented the INA: flag:

      "So instead of having this:

       ,IBN:some-address.com,IFT:some_address.com,ITN:some_address.com:60177,
       IFC:some_address.com

       We have 90 characters used to define that which can be
       conveyed like so:

       ,INA:some_address.com,IBN,IFT,ITN:60177,IFC

       inside 43 characters for a savings of 47 characters while
       conveying the SAME EXACT INFORMATION."



    ===

    Next time.. more flags!


    table 1)
    H: INTERNET CAPABILITY FLAGS:

    FLAG   MEANING

    IBN - denotes a system that does BINKP
    IFC - denotes a system that is capable of RAW or IFCICO
    ITN - denote a system that does TELNET
    IVM - denotes a system that is capable of VMODEM
    IFT - denotes a system that allows FTP
    ITX - denotes a system that uses TransX encoding for email
          tunneling
    IUC - denotes a system that uses UUEncode for email tunneling
    IMI - denotes a system which uses MIME encoding for email
          tunneling
    ISE - denotes a system which supports SEAT receipts for anonymous
          mail
    IP  - denotes a system that can receive TCP/IP connects using a
          protocol that is not covered by any other flag.
    IEM - is a deprecated flag, and new implementations must not
          write it in nodelist entries. This was used as a single
          placeholder for the InterNet address of the system if it
          supported several transport methods. Instead of placing
          the system address in the deprecated form specified below
          in each flag, the address would be placed once only in this
          flag. Implementations may need to parse this information
          from nodelists created with older programs.
    INA - Place to list a Fully Qualified Domain Name Or Static IP
          Address, to be followed by applicable protocol flags
          offered.   Usage:  INA:<somedomain.com>|<x.x.x.x>



    FIDONEWS  Vol 29 No 39       Page  3         September 24, 2012


    -----------------------------------------------------------------

--- BBBS/LiI v4.01 Flag
 * Origin: Amachat - Utica NY (1:261/1406)