• Routing issue

    From Flavio Bessa@usenet@vk3heg.net to alt.bbs.mystic on Thu Oct 23 07:00:01 2025
    From Newsgroup: alt.bbs.mystic

    Hello folks,

    I am using Mystic as a Hub for region 80.

    My routing table is as per below:

    Netmail Route (Top-Down Priority)

    Route 1:* 2:* 3:* 4:* !4:801/* to 4:902/26
    Route 3:770/1 to 3:770/1
    Route 4:801/197 to 4:801/197
    Route 4:801/200 to 4:801/200
    Route 4:801/201 to 4:801/201
    Route 4:801/161 to 4:801/161
    Route 4:801/189 to 4:801/189
    Route 4:801/188 to 4:801/188
    Route 4:801/194 to 4:801/194
    Route 4:801/10 to 4:801/10
    Route 4:801/202 to 4:801/202
    Route 4:900/108 to 4:900/108
    Route 4:801/203 to 4:801/203

    So, apart from the locally connected nodes, everything should be routed to 4:902/26, right?

    However, I have received a netmail from Z3 as such:

    + Oct 22 12:30:11 Importing 0d619a84.pkt (4:900/108 to 4:80/1)
    + Oct 22 12:30:11 Route (Paul Hayton@3:770/100 to JAS@4:900/733) via 4:900/108

    And 4:900/108 should not receive any netmail from me.. this netmail towards 4:900/733 should have been routed over 4:902/26... Any specific change I should do on my routing table?

    .... There is an exception to every rule, except this one.

    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From Nick Boel@usenet@vk3heg.net to alt.bbs.mystic on Thu Oct 23 11:30:01 2025
    From Newsgroup: alt.bbs.mystic

    Hey Flavio!

    On Wed, 22 Oct 2025 12:47:46 -0300, you wrote:

    My routing table is as per below:

    Netmail Route (Top-Down Priority)

    Route 1:* 2:* 3:* 4:* !4:801/* to 4:902/26
    Route 3:770/1 to 3:770/1
    Route 4:801/197 to 4:801/197
    Route 4:801/200 to 4:801/200
    Route 4:801/201 to 4:801/201
    Route 4:801/161 to 4:801/161
    Route 4:801/189 to 4:801/189
    Route 4:801/188 to 4:801/188
    Route 4:801/194 to 4:801/194
    Route 4:801/10 to 4:801/10
    Route 4:801/202 to 4:801/202
    Route 4:900/108 to 4:900/108
    Route 4:801/203 to 4:801/203

    So, apart from the locally connected nodes, everything should be routed
    to 4:902/26, right?

    Yes. However, you may not need any of the others, as these are not really "routes", these are direct connections. I think with Mystic you can probably blank out the route line for each of the 'direct' links.

    Or if you'd rather change them to 'route' statements, then for example, route 3:770/1.* to 3:770.1

    However, I have received a netmail from Z3 as such:

    + Oct 22 12:30:11 Importing 0d619a84.pkt (4:900/108 to 4:80/1)
    + Oct 22 12:30:11 Route (Paul Hayton@3:770/100 to JAS@4:900/733) via 4:900/108

    And 4:900/108 should not receive any netmail from me.. this netmail
    towards 4:900/733 should have been routed over 4:902/26... Any specific change I should do on my routing table?

    I'm unsure why it did that, and if all you have is what you wrote above, it definitely shouldn't. but try either of the above and see if it happens again afterwards.

    Regards,
    Nick

    .... Sarcasm: because beating people up is illegal.
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From Flavio Bessa@usenet@vk3heg.net to alt.bbs.mystic on Fri Oct 24 06:30:01 2025
    From Newsgroup: alt.bbs.mystic

    On 22 Oct 2025, Nick Boel said the following...

    Yes. However, you may not need any of the others, as these are not really "routes", these are direct connections. I think with Mystic you can probably blank out the route line for each of the 'direct' links.

    Yeah, I tried that but it did not work out, so I added a route to 4:900/733 towards 4:902/26. Paul's system was resending the netmail frequently, and now from the logs I could see that it was properly routed towards my ZC.

    Anyway I am still puzzled with the previous routing decision :)

    .... Do vegetarians eat animal crackers?

    --- Synchronet 3.21a-Linux NewsLink 1.2