Please include the routing trace from the BBS log with any reports of routing not working as expected so I can investigate.
73,
John
toggle quoted message
Show quoted text
On 28/09/2024 16:52, Eric H. Christensen via groups.io wrote:
Routing is also not occurring for messages sent to @NA.
73,
Eric WG3K
FM18rp
Packet: WG3K@WG3K.#SMD.MD.USA.NOAM
E-Mail: wg3k@...
On Friday, September 27th, 2024 at 16:23, Eric H. Christensen via groups.io <wg3k@...> wrote:
WG3K.#SMD.MD.USA.NOAM
73,
Eric WG3K
FM18rp
Packet: WG3K@WG3K.#SMD.MD.USA.NOAM
E-Mail: wg3k@...
Sent from Proton Mail Android
-------- Original Message --------
On 9/27/24 15:49, John G8BPQ john.wiseman@... wrote:
The code doesn't think it should flood or it would say so after the B in
the Routing Trace Type B message.
What is your BBS's HA?
Thanks,
John.
On 27/09/2024 19:06, Eric H. Christensen via groups.io wrote:
Okay, it appears to me that maybe bulletins are being routed as P messages. Here's one that landed on my system earlier today:
240927 10:19:34 |KA1VSC-4 Incoming Connect from KA1VSC
240927 10:19:34 >KA1VSC-4 [BPQ-6.0.24.42-B1FWIHJM$]
240927 10:19:34 >KA1VSC-4
240927 10:19:34 >KA1VSC-4 de WG3K>
240927 10:19:35 <KA1VSC-4 [BPQ-6.0.24.38-B1FIHJM$]
240927 10:19:35 <KA1VSC-4 FA B N3MEL USA WX 49885_N3MEL 7801
240927 10:19:35 <KA1VSC-4 F> D3
240927 10:19:35 >KA1VSC-4 FS +
240927 10:19:40 |KA1VSC-4 Uncompressing Message Comp Len 3872 Msg Len 7801 CRC 7853
240927 10:19:40 ?KA1VSC-4 Msg 8672 Routing Trace To WX Via USA
240927 10:19:40 ?KA1VSC-4 Routing Trace Type B TO WX VIA USA Route On WW NOAM USA (null) (null)
240927 10:19:40 ?KA1VSC-4 Routing Trace HR Matches BBS KA1VSC Depth 3
240927 10:19:40 ?KA1VSC-4 Routing Trace HR Matches BBS N3HYM Depth 3
240927 10:19:40 ?KA1VSC-4 Routing Trace HR Best Match is KA1VSC
240927 10:19:40 >KA1VSC-4 FF
240927 10:19:41 <KA1VSC-4 FQ
240927 10:19:41 |KA1VSC-4 KA1VSC-4 Disconnected
So, it's a type B "bulletin" message but is going through the HR matches for directed bulletins instead of HA for flood bulletins. This message should have been directed to KA1VSC, N3HYM, and KB3KOW but was treated as a P message looking for an HR match. This is something new to version 6.0.24.42 as it wasn't present in the, I think, previous non-beta release (sorry, I don't know what version of the software I was running before).
I don't know if this is related or not but I'm also seeing weird routing with P messages when the "Send P Msgs to more than one BBS" was selected. It was discovered that messages that were bound to my BBS were then being resent out by my system based on HR addresses. I turned that feature off after the upgrade to 6.0.24.42 to keep this from happening.
73,
Eric WG3K
FM18rp
Packet: WG3K@WG3K.#SMD.MD.USA.NOAM
E-Mail: wg3k@...
On Friday, September 27th, 2024 at 10:31, John G8BPQ john.wiseman@... wrote:
Routing rules.
A message addressed to a valid country or continent code eg ALL@USA, ALL@NA will have the @ field expanded to a full HA by adding implied elements at end, eg USA.NA.WW, NA.WW. This has implications for deciding if a bull is in the right area and processing SendPtoMultiple.
First a few terms.
Implied AT means send to the BBS with the AT call. Eg if to g8bpq@gm8bpq it is sent to BBS gm8bpq without needed an entry in AT
WIldcarded means call ending in * which matches any number of characters after the . This is normally used for the NTS TO field, eg. NTS 12 will route any zip code starting 12. Can also be used in AT field, eg just * in the AT field will create a 'Default Route' where any message with no where else to go will be sent.
Directed Bulls are bulls sent to an HA where the message isn't addressed to the BBS's own area. Eg a bull sent to all@... from in the UK or sent to CA.USA from another state. These are routed as a P message until they reach the required area.
Rules for each message type. These run in the order specified.
T (NTS) Messages:
TO Address, wildcarded
AT Address, possibly wildcarded.
P message with SendPtoMultiple set:
First look for matches on HA. If any found sent to those all with the best match level (highest number of elements of HA that match and don't check AT or TO
If no matches on HA, send to any that match AT or TO
If no matches check wildcarded AT and sent to best match.
P Message without SentPtoMultiple or Directed B messages:
Check TO then Implied AT then AT then HA then Wildcarded AT. Send to first found.
B messages (not Directed)
Send to All systems that match TO AT or HA. If none found send to first Wildcarded AT found.
Probably as clear as mud, but hopefully will help people understand how it is supposed to work.
73,
John
On 27/09/2024 14:04, Chuck Gelm wrote:
On 9/27/24 08:53, Mark Taylor wrote:
I would be curious to see the forwarding record of one that matched USA on the AT field.
