1. Forum
  2. FidoNet
  3. MYSTIC

  • Routing Settings for Fido

    From Mike Dippel@1:135/393 to All on Sun Feb 27 10:49:24 2022
    I believe I saw in a video from Avon that the routing info should read:
    1* 2* 3* 4*

    I tried to send a netmail to someone other than my hub. The netmail did not go direct to the address, but went to the hub.

    The hub asked me to change the setting to:
    1:* 2:* 3:* 4:*
    and it still didn't go through.

    I'm running vA47 Is this a known problem with this version, or is there a better setting for Routing that works?

    Mike Dippel

    --- Mystic BBS v1.12 A47 2021/12/25 (Windows/64)
    * Origin: Mystic Hobbies BBS (1:135/393)
  • From Jay Harris@1:229/664 to Mike Dippel on Sun Feb 27 11:51:10 2022
    On 27 Feb 2022, Mike Dippel said the following...

    I tried to send a netmail to someone other than my hub. The netmail did not go direct to the address, but went to the hub.

    Try running:

    mutil poll route

    And it should give you some guidance. Mine looks like this:

    $ ./mis poll route

    Netmail Route (Top-Down Priority)

    Route 21:3/110.2 to 21:3/110.2
    Route 21:1/10 to 21:1/10
    Route 77:1/156.10 to 77:1/156.10
    Route 80:774/114.10 to 80:774/114.10
    Route 3:770/* to 3:770/1
    Route 2:221/* to 2:221/6
    Route 2:280/* to 2:280/5555
    Route 2:250/1 to 2:250/1
    Route 954:* to 954:895/1
    Route 25:* to 25:25/0
    Route 618:* to 618:500/1
    Route 80:* to 80:774/1
    Route 1337:* to 1337:3/100
    Route 77:* to 77:3/1
    Route 42:* to 42:1/1
    Route 21:* to 21:3/100
    Route 1:* 2:* 3:* 4:* to 1:229/426


    You'll want to make sure that any specific nodes you have setup appear above a wildcard entry. You can copy a node entry in echomail nodes and move it above and entry with a wildcard it in Echomail Nodes.

    Also make sure you enter their node number in the "Route Info" field. e.g:

    Node ID 18 (21:3/110.2@fsxnet)

    Active Yes
    Description Test Node
    SysOp Name Jay Harris
    Address 21:3/110.2
    Domain fsxnet
    Session Type Directory
    Archive Type ZIP
    Export Type Normal
    Route Info 21:3/110.2


    Jay

    ... If at first you don't succeed, destroy all evidence that you tried.

    --- Mystic BBS v1.12 A48 2022/02/15 (Raspberry Pi/32)
    * Origin: Northern Realms (1:229/664)
  • From Björn Wiberg@2:201/137 to Mike Dippel on Sun Feb 27 18:23:53 2022
    Hello Mike!

    On 27 Feb 2022, Mike Dippel said the following...
    I tried to send a netmail to someone other than my hub. The netmail did not go direct to the address, but went to the hub.

    I think that should be so -- only crashmail is sent directly to the recipient's system (for points, via their boss node). However, I don't think there is any option to flag a netmail as "crash" from within the message editor parts of Mystic?

    However, if you have defined an echomail node for that specific recipient in your Mystic setup -- which is a rather tedious "work-around" as netmails often are "one-off" messages -- and flagged (Export Type) that echomail node as Crash (send directly and as soon as possible) or Direct (do not send via anyone else; requires you or the recipient system to initiate a poll, though, to actually deliver it), any outgoing mail for that node will be flagged accordingly in the outbound folders and handled as desired.

    I believe you will also need to make an explicit exception to the routing of the zone that the recipient's node is in, in the Routing Info of your "normal" uplink (hub) for that zone, or it will follow the routing rules and ignore the fact that you have defined a specific echomail node for the recipient...

    There is a short example of this here:

    http://wiki.mysticbbs.com/doku.php?id=config_echomail_nodes#export_type

    ...however that one shows how an entire net (1:123/*) and not just a specific node (e.g. 1:123/456) is being forced to go to a certain uplink. In your case you would want to modify the Routing Info to use the specific node number of the recipient instead of an entire net.

    Hope this helps!

    Best regards
    Bj”rn

    --- Mystic BBS v1.12 A48 2022/02/15 (Linux/64)
    * Origin: Star Collision BBS, Uppsala, Sweden (2:201/137)
  • From g00r00@1:129/215 to Mike Dippel on Mon Feb 28 10:54:13 2022
    I believe I saw in a video from Avon that the routing info should read:
    1* 2* 3* 4*

    Avon's videos are a bit outdated in terms of routing, but in general the same system exists today. You shouldn't need to do anything in your routing for Netmails to be routed through the network.

    I tried to send a netmail to someone other than my hub. The netmail did not go direct to the address, but went to the hub.

    The mail will not go direct to the node if they are not configured to go direct. It will route through the network and get sent to the receiver's node.

    The hub asked me to change the setting to:
    1:* 2:* 3:* 4:* and it still didn't go through.

    What this is doing is saying that you want all netmail addressed to zones 1,2,3,4 (IE all of FidoNet) to be sent to this node. It sounds like you don't want that at all.

    ... When all else fails, read the instructions

    --- Mystic BBS v1.12 A48 2022/02/17 (Windows/32)
    * Origin: Sector 7 * Mystic WHQ (1:129/215)