Re: Node Taking Application Callsigns
Never mind - I figured it out.? SIMPLE already included the NODE and HIDENODES settings and my configuration reversed them.? I guess HIDENODES hides the subject node as well :)
?
Thanks for the suggestion.
?
73 - Murray? VE3KNO
?
|
Re: Node Taking Application Callsigns
|
Re: Node Taking Application Callsigns
Thanks Mark.? The NODECALL and NODEALIAS are right at the top of the config file:
?
SIMPLE
?
LOCATOR=43.397939, -79.976857
NODECALL=VA3AMJ-7
NODEALIAS=CARLYL
?
CTEXT:
...and so on.? Further down I have:
?
BBS=1
NODE=0
HIDENODES=1
?
...and then the Port definitions.? Everything seems to work okay except for the node callsign.
?
?
|
Re: Node Taking Application Callsigns
Be sure your NODECALL and NOALIAS is not contained within a multiline comment.
?
?
|
Node Taking Application Callsigns
I'm working through the configuration of a LinBPQ node.? Using the terminal on the html page, I see that the node is taking the SSID and ALIAS of either the chat server or the BBS (depending upon which are enabled) instead of the NODECALL and NODEALIAS defined in bpq32.cfg.? This is also showing up on the nodemap.? If no applications are enabled there is no callsign - it just says "BPQ32 Node" and there is nothing appearing on the nodemap.? I'm running L6.0.23.8.? Has anyone encountered this?
?
Thanks for any ideas.
?
Murray? VE3KNO
?
|
Re: Missing calls in MH ?
I'm sure I was looking at your -8 then...
|
Re: Missing calls in MH ?
Mark,
?
Port 2 is the SCS Tracker running the bpq hostmode driver.
?
RFTMG:K7TMG-7} Ports
? 1 Loopback ? ? ? ? ? ? ? ? ? ? ?
? 2 SCS Tracker (hostmode) ? ? ? ?
? 3 Telnet ? ? ? ?
?
?There is no tcp/udp port on this instance of BPQ. This is on a Windows 11 machine incidentally.
?
73
|
Re: Hierarchical routing not working
Another possibility Eric is that you give someone admin access over the web to your node to double check your settings.? At this point it wouldn't hurt.
?
I'll be glad to if you want.. email on my node pages.
?
?
Mark
?
?
?
|
Re: Hierarchical routing not working
Yes, they are being treated as directed. I guess it would be useful to display your HA as part of the routing trace, but it seems it doesn't think you are in USA or NOAM!
73,
John
toggle quoted message
Show quoted text
On 29/09/2024 16:32, Eric H. Christensen via groups.io wrote: On Saturday, September 28th, 2024 at 15:33, John G8BPQ <john.wiseman@...> wrote:
Please include the routing trace from the BBS log with any reports of
routing not working as expected so I can investigate. Here are the logs from the recent @USA and @NA messages:
240929 07:50:51 |KA1VSC-4 Incoming Connect from KA1VSC
240929 07:50:51 >KA1VSC-4 [BPQ-6.0.24.42-B1FWIHJM$]
240929 07:50:51 >KA1VSC-4
240929 07:50:51 >KA1VSC-4 de WG3K>
240929 07:50:52 <KA1VSC-4 [BPQ-6.0.24.38-B1FIHJM$]
240929 07:50:52 <KA1VSC-4 FA B KF5JRV USA WX 1779_KF5JRV 3107
240929 07:50:52 <KA1VSC-4 F> 60
240929 07:50:52 >KA1VSC-4 FS +
240929 07:50:54 |KA1VSC-4 Uncompressing Message Comp Len 1370 Msg Len 3107 CRC b492
240929 07:50:54 ?KA1VSC-4 Msg 8735 Routing Trace To WX Via USA
240929 07:50:54 ?KA1VSC-4 Routing Trace Type B TO WX VIA USA Route On WW NOAM USA (null) (null)
240929 07:50:54 ?KA1VSC-4 Routing Trace HR Matches BBS KA1VSC Depth 3
240929 07:50:54 ?KA1VSC-4 Routing Trace HR Matches BBS N3HYM Depth 3
240929 07:50:54 ?KA1VSC-4 Routing Trace HR Best Match is KA1VSC
240929 07:50:54 >KA1VSC-4 FF
240929 07:50:55 <KA1VSC-4 FQ
240929 07:50:55 |KA1VSC-4 KA1VSC-4 Disconnected
240929 08:08:17 |KA1VSC-4 Incoming Connect from KA1VSC
240929 08:08:17 >KA1VSC-4 [BPQ-6.0.24.42-B1FWIHJM$]
240929 08:08:17 >KA1VSC-4
240929 08:08:17 >KA1VSC-4 de WG3K>
240929 08:08:19 <KA1VSC-4 [BPQ-6.0.24.38-B1FIHJM$]
240929 08:08:19 <KA1VSC-4 FA B KF5JRV NA WX 1780_KF5JRV 8357
240929 08:08:19 <KA1VSC-4 F> B6
240929 08:08:19 >KA1VSC-4 FS +
240929 08:08:23 |KA1VSC-4 Uncompressing Message Comp Len 3552 Msg Len 8357 CRC 90a7
240929 08:08:23 ?KA1VSC-4 Msg 8736 Routing Trace To WX Via NA
240929 08:08:23 ?KA1VSC-4 Routing Trace Alias Substitution NA > NOAM
240929 08:08:23 ?KA1VSC-4 Routing Trace Type B TO WX VIA NA Route On WW NOAM (null) (null) (null)
240929 08:08:23 ?KA1VSC-4 Routing Trace HR Matches BBS KA1VSC Depth 2
240929 08:08:23 ?KA1VSC-4 Routing Trace HR Matches BBS N3HYM Depth 2
240929 08:08:23 ?KA1VSC-4 Routing Trace HR Best Match is KA1VSC
240929 08:08:23 >KA1VSC-4 FF
240929 08:08:24 <KA1VSC-4 FQ
240929 08:08:24 |KA1VSC-4 KA1VSC-4 Disconnected
From here, it appears that these messages aren't being routed as flood bulletins.
73,
Eric WG3K
FM18rp
Packet: WG3K@WG3K.#SMD.MD.USA.NOAM
E-Mail: wg3k@...
|
Re: Hierarchical routing not working
On Saturday, September 28th, 2024 at 15:33, John G8BPQ <john.wiseman@...> wrote: Please include the routing trace from the BBS log with any reports of
routing not working as expected so I can investigate. Here are the logs from the recent @USA and @NA messages: 240929 07:50:51 |KA1VSC-4 Incoming Connect from KA1VSC 240929 07:50:51 >KA1VSC-4 [BPQ-6.0.24.42-B1FWIHJM$] 240929 07:50:51 >KA1VSC-4 240929 07:50:51 >KA1VSC-4 de WG3K> 240929 07:50:52 <KA1VSC-4 [BPQ-6.0.24.38-B1FIHJM$] 240929 07:50:52 <KA1VSC-4 FA B KF5JRV USA WX 1779_KF5JRV 3107 240929 07:50:52 <KA1VSC-4 F> 60 240929 07:50:52 >KA1VSC-4 FS + 240929 07:50:54 |KA1VSC-4 Uncompressing Message Comp Len 1370 Msg Len 3107 CRC b492 240929 07:50:54 ?KA1VSC-4 Msg 8735 Routing Trace To WX Via USA 240929 07:50:54 ?KA1VSC-4 Routing Trace Type B TO WX VIA USA Route On WW NOAM USA (null) (null) 240929 07:50:54 ?KA1VSC-4 Routing Trace HR Matches BBS KA1VSC Depth 3 240929 07:50:54 ?KA1VSC-4 Routing Trace HR Matches BBS N3HYM Depth 3 240929 07:50:54 ?KA1VSC-4 Routing Trace HR Best Match is KA1VSC 240929 07:50:54 >KA1VSC-4 FF 240929 07:50:55 <KA1VSC-4 FQ 240929 07:50:55 |KA1VSC-4 KA1VSC-4 Disconnected 240929 08:08:17 |KA1VSC-4 Incoming Connect from KA1VSC 240929 08:08:17 >KA1VSC-4 [BPQ-6.0.24.42-B1FWIHJM$] 240929 08:08:17 >KA1VSC-4 240929 08:08:17 >KA1VSC-4 de WG3K> 240929 08:08:19 <KA1VSC-4 [BPQ-6.0.24.38-B1FIHJM$] 240929 08:08:19 <KA1VSC-4 FA B KF5JRV NA WX 1780_KF5JRV 8357 240929 08:08:19 <KA1VSC-4 F> B6 240929 08:08:19 >KA1VSC-4 FS + 240929 08:08:23 |KA1VSC-4 Uncompressing Message Comp Len 3552 Msg Len 8357 CRC 90a7 240929 08:08:23 ?KA1VSC-4 Msg 8736 Routing Trace To WX Via NA 240929 08:08:23 ?KA1VSC-4 Routing Trace Alias Substitution NA > NOAM 240929 08:08:23 ?KA1VSC-4 Routing Trace Type B TO WX VIA NA Route On WW NOAM (null) (null) (null) 240929 08:08:23 ?KA1VSC-4 Routing Trace HR Matches BBS KA1VSC Depth 2 240929 08:08:23 ?KA1VSC-4 Routing Trace HR Matches BBS N3HYM Depth 2 240929 08:08:23 ?KA1VSC-4 Routing Trace HR Best Match is KA1VSC 240929 08:08:23 >KA1VSC-4 FF 240929 08:08:24 <KA1VSC-4 FQ 240929 08:08:24 |KA1VSC-4 KA1VSC-4 Disconnected From here, it appears that these messages aren't being routed as flood bulletins. 73, Eric WG3K FM18rp Packet: WG3K@WG3K.#SMD.MD.USA.NOAM E-Mail: wg3k@...
|
Re: Missing calls in MH ?
Port 2 is your AXIP port.
?
On windows my AXIP Port MHeard List only shows direct connections to my node.? Not pass through connections.? Could it be the same on linux?
?
?
|
Re: Hierarchical routing not working
On Sat, Sep 28, 2024 at 01:52 PM, Eric H. Christensen wrote:
H Route is set to "#SMD.MD.USA.NOAM" although I wonder if that should be "WG3K.#SMD.MD.USA.NOAM".
I don't think so. ?WG3K.#SMD.MD.USA.NOAM is the H Address. ?#SMD.MD.USA.NOAM is the H Route.
?
The only things I can imagine at this point is, are those copy/paste or typed in.? I sometimes will correct my errors if I type it in, where cut/paste or an image will show my errors...
?
And I'd check the box "Use 4 character continent codes" and get in the habit of writing out the NOAM and EURO, etc.? Mine forward @NA with that checked..
?
Still, your BBS thinks it is somewhere it is not....? If it cannot be found it could be something corrupted in the update you did, since it seemed to happen when you updated.
?
?
?
|
Re: Hierarchical routing not working
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.
|
Re: Hierarchical routing not working
H Route is set to "#SMD.MD.USA.NOAM" although I wonder if that should be "WG3K.#SMD.MD.USA.NOAM".
73,
Eric WG3K
FM18rp
Packet: WG3K@WG3K.#SMD.MD.USA.NOAM
E-Mail: wg3k@...
toggle quoted message
Show quoted text
On Saturday, September 28th, 2024 at 13:31, Mark Taylor <mtaylor@...> wrote: On your main BBS Configuration page what is the BBS H Route?
|
Re: Hierarchical routing not working
On your main BBS Configuration page what is the BBS H Route?
?
?
?
?
|
Re: Hierarchical routing not working
Routing is also not occurring for messages sent to @NA.
73,
Eric WG3K
FM18rp
Packet: WG3K@WG3K.#SMD.MD.USA.NOAM
E-Mail: wg3k@...
toggle quoted message
Show quoted text
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.
|
Re: Hierarchical routing not working
WG3K.#SMD.MD.USA.NOAM
73,
Eric WG3K
FM18rp
Packet: WG3K@WG3K.#SMD.MD.USA.NOAM
E-Mail: wg3k@...
Sent from Proton Mail Android
toggle quoted message
Show quoted text
-------- 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.
>>>
>>
>>
>
>
>
>
|
Re: Hierarchical routing not working
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.
toggle quoted message
Show quoted text
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.
|
Re: Hierarchical routing not working
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@...
toggle quoted message
Show quoted text
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.
|
?
Maybe it's just me but I think there might be an issue with MH not showing all heard calls?
?
My MH just now:
?
RFTMG:K7TMG-7} Version 6.0.24.42
mh 2
RFTMG:K7TMG-7} Heard List for Port 2
K7TMG. ? ? 00:00:05:28 ? ?
KB9PVH-5 ? 00:00:10:51 ? ?
K7TMG ? ? ?00:00:13:34 ? ?
KB5YZB-1 ? 00:00:17:45 ? ?
W8MSD-7 ? ?00:00:18:29 ? ?
N0HI-7 ? ? 00:00:18:37 ? ?
KB8UVN-1 ? 00:00:19:09 ? ?
N0HI-7 ? ? 00:00:20:35 ? ?
KB9PVH ? ? 00:00:21:46 ? ?
KB9PVH+ ? ?00:00:21:46 ? ?
?
A recent extract from my monitor window:
?
16:28:19R WH6ANH>W8MSD-7 Port=2 <RR C P R3>
16:28:44R WH6ANH>W8MSD-7 Port=2 <RR C P R3>
16:28:56R WH6ANH>W8MSD-7 Port=2 <I C P S7 R3>:
HURT A THING ?LOTS TO LEARN
16:29:11R WH6ANH>W8MSD-7 Port=2 <RR C P R3>
16:29:15R WH6ANH>W8MSD-7 Port=2 <I C P S7 R3>:
HURT A THING ?LOTS TO LEARN
16:29:30R WH6ANH>W8MSD-7 Port=2 <RR C P R3>
?
Why is WH6ANH not in the MH list? I'm at a loss to explain it.
?
73
?
?
|
