• areafix & filefix config in fidoconf 1.9.x

    From Benny Pedersen@2:230/0 to All on Wed Jun 13 08:04:08 2018
    Hello All!

    how to configure it, it was simple in fidoconf 1.4.x

    but 1.9.x is more complicated without any good docs

    still have cvs, if that matter for config options


    Regards Benny

    ... there can only be one way of life, and it works :)

    --- Msged/LNX 6.1.2 (Linux/4.17.0-gentoo (x86_64))
    * Origin: I will always keep a PC running CPM 3.0 (2:230/0)
  • From Richard Menedetter@2:310/31 to Benny Pedersen on Wed Jun 13 10:15:02 2018
    Hi Benny!

    13 Jun 2018 08:04, from Benny Pedersen -> All:

    how to configure it, it was simple in fidoconf 1.4.x
    but 1.9.x is more complicated without any good docs

    I somehow figured it out when I transitioned from 1.4 to 1.9.

    My robots file looks like this:

    ==== Begin "robots" ==== ##################################################################
    # Robots configuration

    # Process areafix requests on the fly. Boolean.
    AreaFixFromPkt Yes

    # Specifies area used for areafix and filefix scanning.
    # Replies from robots will also be stored here.
    # RobotsArea must be NetmailArea for security purposes!
    RobotsArea netmail

    # robot default|areafix|filefix'
    # 'robot' statement begins robot description.
    # 'default' allows you to set common parameters.

    robot default
    # Maximum size for robot's messages in kb.
    # If statement is not defined, messages will be not splitted.
    # msgSize 10
    # Delete requests from links to areafix. Boolean.
    # killRequests
    # This statement lists attributes to be set on robot's reports.
    # kill reports
    # reportsAttr loc pvt k/s npd
    # kill reports and send directly
    reportsAttr loc pvt k/s npd dir
    # do not kill reports
    # reportsAttr loc pvt npd # do not kill reports

    # This statement enables/disables including linked areas list into all
    # robot replies.
    #QueryReports off

    # This string added after splitted robot.s messages.
    #SplitStr > Message splitted. To be continued...

    # Create file-flag after autocreating area.
    AutocreateFlag /home/fido/flags/autocreate.flag

    # This token defines a file which will be used when autocreating echoarea. #newAreaRefuseFile /etc/ftn/areas/dontcrte.lst

    # This statement specifies time to wait (in days) for area requested from
    # uplink. If there is no traffic in this area, <program> qupd unsubscribes
    # area from this uplink and subscribes to it at next uplink. If next uplink
    # for this echoarea not avaiable, <program> qupd removes echoarea from queue. #ForwardRequestTimeout 7

    # This statement specifies time to wait (in days) before unsubscribing
    # echoarea from uplink after the time last downlink unsubscribed. #IdlePassthruTimeout 3

    # This statement specified time wait (days) for delete from config echoarea
    # after unsubscribe it from uplink (last link).
    #KilledRequestTimeout 4

    # Enables or disables area pause algorythm.
    #AutoAreaPause

    robot Areafix
    # This statement defines help file which is sent to a link
    # on '%help' command.
    helpFile /home/fido/areafix.hlp
    # Origin for mail from this robot
    robotOrigin "Husky HPT"
    # FromName for mail from this robot
    fromName "Areafix"
    # This statement specifies the queue file containing your
    # delayed forward-requests.
    queueFile /home/fido/flags/afix_queue
    # SortEchoList none|name|group|group,name

    robot Filefix
    helpFile /home/fido/filefix.hlp
    robotOrigin "Husky Htick"
    fromName "Filefix"
    ==== End "robots" ====

    CU, Ricsi

    --- GoldED+/LNX
    * Origin: The best prophet of the future is the past. (2:310/31)
  • From Benny Pedersen@2:230/0 to Richard Menedetter on Wed Jun 13 19:22:26 2018
    Hello Richard!

    13 Jun 2018 10:15, Richard Menedetter wrote to Benny Pedersen:

    My robots file looks like this:

    thanks that helped me very well, tparser output looks right now

    just still miss forwardrequestfile pr uplink or group config ?

    is every node just a group, and the group defination holds config for forward files ?


    Regards Benny

    ... there can only be one way of life, and it works :)

    --- Msged/LNX 6.1.2 (Linux/4.17.1-gentoo (x86_64))
    * Origin: I will always keep a PC running CPM 3.0 (2:230/0)
  • From Richard Menedetter@2:310/31 to Benny Pedersen on Mon Jun 18 21:38:40 2018
    Hi Benny!

    13 Jun 2018 19:22, from Benny Pedersen -> Richard Menedetter:

    just still miss forwardrequestfile pr uplink or group config ?
    is every node just a group, and the group defination holds config for forward files ?

    I have this set:
    ForwardRequests on

    The groups are for me the networks.
    Eg I have configured Group A to be fidonet, and b,c,d etc. the othernets.
    Then I have access levels for point, node, admin echos that restrict access to certain echos.

    Link description looks like this:

    Link Name
    Aka <aka>
    ourAka <myaka>
    Password pass
    pktpwd
    LinkGrp A
    AreaFixAutoCreate on
    AreaFixAutoCreateDefaults -b Jam -a <myaka>
    FileFixAutoCreate on
    forwardRequests on
    Packer zip

    CU, Ricsi

    --- GoldED+/LNX
    * Origin: The Multitasker = Two PCs and a chair with wheels. (2:310/31)
  • From Benny Pedersen@2:230/0 to Richard Menedetter on Tue Jun 19 02:59:42 2018
    Hello Richard!

    18 Jun 2018 21:38, Richard Menedetter wrote to Benny Pedersen:


    just still miss forwardrequestfile pr uplink or group config ?
    is every node just a group, and the group defination holds config for
    forward files ?

    I have this set:
    ForwardRequests on

    The groups are for me the networks.

    good

    Eg I have configured Group A to be fidonet, and b,c,d etc. the
    othernets.

    groupnames can be more then a single char

    Then I have access levels for point, node, admin echos that restrict access to certain echos.

    okay

    Link description looks like this:

    Link Name
    Aka <aka>
    ourAka <myaka>
    Password pass
    pktpwd
    LinkGrp A
    AreaFixAutoCreate on
    AreaFixAutoCreateDefaults -b Jam -a <myaka>
    FileFixAutoCreate on
    forwardRequests on
    Packer zip

    still missing how to add a unknown list of other echomail and fileareas so husky know this link have more area then in husky config file

    i had this working in fidoconf 1.4, but cant find howto with 1.9


    Regards Benny

    ... there can only be one way of life, and it works :)

    --- Msged/LNX 6.1.2 (Linux/4.17.2-gentoo (x86_64))
    * Origin: I will always keep a PC running CPM 3.0 (2:230/0)
  • From Michael Dukelsky@2:5020/1042 to Benny Pedersen on Tue Jun 19 11:06:24 2018
    Hello Benny,

    Tuesday June 19 2018, Benny Pedersen wrote to Richard Menedetter:

    still missing how to add a unknown list of other echomail and
    fileareas so husky know this link have more area then in husky config
    file
    i had this working in fidoconf 1.4, but cant find howto with 1.9

    This is what I have for one of my links:

    # Allow forwarding requests to the link
    ForwardRequests on

    # Automatically create an area on receiving a message from the area AreafixAutoCreate on

    # The file where new areas are created
    AreafixAutoCreateFile [VHPTDIR]/config/commonAreas.cfg

    # Masks of the areas, requests to which are prohibited to forward
    # to the link
    AreafixFwdDenyMask SPB.*,n5030*,BEL.*,brest.*,n45*

    # The file list of the areas, requests to which are prohibited
    # to forward to the link
    AreafixFwdDenyFile [HUSKYDIR]/denyZ1.lst

    # The file list of the areas available at the link
    AreafixFwdFile [VHPTDIR]/daily/ECH12000.LST

    Michael

    ... node (at) f1042 (dot) ru
    --- GoldED+/LNX 1.1.5-b20170303
    * Origin: Moscow, Russia (2:5020/1042)
  • From Benny Pedersen@2:230/0 to Michael Dukelsky on Wed Jun 20 22:19:30 2018
    Hello Michael!

    19 Jun 2018 11:06, Michael Dukelsky wrote to Benny Pedersen:


    # Allow forwarding requests to the link
    ForwardRequests on

    +1

    # Automatically create an area on receiving a message from the area AreafixAutoCreate on

    +1

    # The file where new areas are created
    AreafixAutoCreateFile [VHPTDIR]/config/commonAreas.cfg

    i got a warning not included with that one, how to create this file then ?

    # Masks of the areas, requests to which are prohibited to forward
    # to the link
    AreafixFwdDenyMask SPB.*,n5030*,BEL.*,brest.*,n45*

    +1

    # The file list of the areas, requests to which are prohibited
    # to forward to the link
    AreafixFwdDenyFile [HUSKYDIR]/denyZ1.lst

    +1

    # The file list of the areas available at the link
    AreafixFwdFile [VHPTDIR]/daily/ECH12000.LST

    this was it for me for echomail, what is it for filearea ?


    Regards Benny

    ... there can only be one way of life, and it works :)

    --- Msged/LNX 6.1.2 (Linux/4.17.2-gentoo (x86_64))
    * Origin: I will always keep a PC running CPM 3.0 (2:230/0)
  • From Michael Dukelsky@2:5020/1042 to Benny Pedersen on Thu Jun 21 10:18:34 2018
    Hello Benny,

    Wednesday June 20 2018, Benny Pedersen wrote to Michael Dukelsky:

    # Allow forwarding requests to the link
    ForwardRequests on

    +1

    # Automatically create an area on receiving a message from the
    area AreafixAutoCreate on

    +1

    # The file where new areas are created
    AreafixAutoCreateFile [VHPTDIR]/config/commonAreas.cfg

    i got a warning not included with that one, how to create this file
    then ?

    You do not have to create it, you already have it, but with a different name. It is the file containing echo areas. When a new area is created it is appended
    to the file.

    # Masks of the areas, requests to which are prohibited to forward
    # to the link
    AreafixFwdDenyMask SPB.*,n5030*,BEL.*,brest.*,n45*

    +1

    # The file list of the areas, requests to which are prohibited
    # to forward to the link
    AreafixFwdDenyFile [HUSKYDIR]/denyZ1.lst

    +1

    # The file list of the areas available at the link
    AreafixFwdFile [VHPTDIR]/daily/ECH12000.LST

    this was it for me for echomail, what is it for filearea ?

    You just substitute 'Areafix' with 'Filefix' in the keywords above, for example
    FilefixFwdFile. You may find it in the documentation, specifically in the file fidoconfig.html, "3.4 Link definition keywords (Link section)". All such keywords, containing a robot name at their beginning are listed with an asterisk instead of the robot name. For example, "*AutoCreate" means AreafixAutoCreate or FilefixAutoCreate. And it is explicitly written in a note at the beginning of the section 3.4:

    Note: '*' mark in keywords here means that it should be either substituted with
    robot's name to which appropriate setting is applied or omitted to apply to all
    robots.

    You may find documentaion here: http://download.huskyproject.org/docs/husky-all-1.9-docs-20170406.zip

    Michael

    ... node (at) f1042 (dot) ru
    --- GoldED+/LNX 1.1.5-b20170303
    * Origin: Moscow, Russia (2:5020/1042)
  • From Richard Menedetter@2:310/31 to Benny Pedersen on Sun Jun 24 14:11:20 2018
    Hi Benny!

    19 Jun 2018 02:59, from Benny Pedersen -> Richard Menedetter:

    still missing how to add a unknown list of other echomail and
    fileareas so husky know this link have more area then in husky config
    file

    For Echomail
    FwdFile /home/fido/areas.txt

    I am not sure for fileareas, as I do not use that feature.

    CU, Ricsi

    --- GoldED+/LNX
    * Origin: I AM standing. (2:310/31)