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
?
?
|
Re: Hierarchical routing not working
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:
toggle quoted message
Show quoted text
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
Eric, can we see the user record for KB3KOW?
?
?
|
Re: Hierarchical routing not working
On Thu, Sep 26, 2024 at 11:22 AM, Eric H. Christensen wrote:
Will the messages forward if you click the Start Forwarding button??
No, there aren't any @USA messages queued.
Eric, this makes me wonder.? 11 messages were queued (at that time) yet none of the forwarded when you tried to manually forward them.? The address of the messages are irrelevant. If they are queued then they should forward.
?
Do you still have messages queued to KB3KOW that are not sending regardless of the address of the messages?
?
?
?
|
Re: Hierarchical routing not working
On Fri, Sep 27, 2024 at 08:19 AM, Charles Hargrove wrote:
Yes. Also do not use a dotted @ field for bulletins.
I agree. In the AT Calls field there should be no multi segmented HR.
?
?
I'm wondering now if somehow the Times field has some unprintable character in it causing BPQ to not forward at all.? That should not prevent it from processing a route to it I would think...
?
?
|
Re: Hierarchical routing not working
Yes. Also do not use a dotted @ field for bulletins.
toggle quoted message
Show quoted text
On 9/27/2024 9:15 AM, Chuck Gelm wrote: On 9/26/24 20:20, Mark Taylor wrote:
You can try that or if someone else has a thought, or John adds something, that is where I am on this. I just noticed that I do not have 'Use 4 Char Continent Codes' enabled.
Should I enable this?
Personally, I prefer 4 character continent codes.
73, Chuck
--
Charles J. Hargrove - N2NOV
NYC-ARECS/RACES Citywide Radio Officer/Skywarn Coord.
NYC-ARECS/RACES Nets 441.100/136.5 PL
ARnewsline Broadcast Mon. @ 8:00PM
NYC-ARECS Weekly Net Mon. @ 8:30PM
NY-NBEMS Net Saturdays @ 10AM & USeast-NBEMS Net Wednesdays @ 7PM
on 7.036 Mhz USB (alt 3.536)/1500 hz waterfall spot; MFSK-16 or 32
"Information is the oxygen of the modern age. It seeps through the walls topped
by barbed wire, it wafts across the electrified borders." - Ronald Reagan
"The more corrupt the state, the more it legislates." - Tacitus
"Molann an obair an fear" - Irish Saying
(The work praises the man.)
"No matter how big and powerful government gets, and the many services it
provides, it can never take the place of volunteers." - Ronald Reagan
|
Re: Hierarchical routing not working
On 9/26/24 20:20, Mark Taylor wrote: You can try that or if someone else has a thought, or John adds something, that is where I am on this. I just noticed that I do not have 'Use 4 Char Continent Codes' enabled. Should I enable this? Personally, I prefer 4 character continent codes. 73, Chuck
|
Re: Hierarchical routing not working
Thanks Chuck. I was interpreting the line to read that the match was due to WX being in the AT field.? Maybe that is the reason I was still perplexed at why some messages forward the way that they do....
?
Maybe if Eric changes USA to USA.NOAM in his HR?? I'd be curious to see if things changed.
?
|
Re: Hierarchical routing not working
On 9/27/24 08:53, Mark Taylor wrote:
toggle quoted message
Show quoted text
I would be curious
to see the forwarding record of one that matched USA on the AT
field.
|
Re: Hierarchical routing not working
Thanks Chuck, that blows my theory, although it brings up a why your works at all.? WX is the TO part of the address, yet it matches on the AT part of the address.? I would be curious to see the forwarding record of one that matched USA on the AT field.
?
The only other difference that I see is that he is using USA where we are using USA.NOAM in the HR routing.
?
At this point I would have to browse around through his configuration looking for a subtle difference...hopefully John can see something.
?
?
?
?
|
Re: Hierarchical routing not working
On 9/26/24 20:20, Mark Taylor wrote:
You can try that or
if someone else has a thought, or John adds something, that is
where I am on this.
Since Eric and I have KA1VSC in our forwarding, here is an image of
my Mail/FWD screen:
|
Re: Hierarchical routing not working
On 9/26/24 20:20, Mark Taylor wrote:
On Thu, Sep 26, 2024 at 05:50 PM, Eric H. Christensen wrote:
240926 20:43:18 ?KA1VSC-4 Routing Trace USA Matches
AT KA1VSC
This may be a hint.? Do you have USA in the AT Calls of the
KA1VSC forwarding record?
?
Not sure but my belief is that since the TO Calls and AT
Calls are processed first, if any matches are found in those the
HR processing does not take place.? This shows that a match was
found in the AT Calls of the KA1VSC forwarding record.?
Processing halts at that point.
?
So, since you have a small installation it would be easy for
you to remove all heirarchical routing from the AT Calls and put
them in the HR field..., or remove all from the HR field and use
the AT Calls.? One or the other, but I don't think it will work
mixed.
?
You can try that or if someone else has a thought, or John
adds something, that is where I am on this.
?
Hi, Mark et alia:
Here is a segment from my log file which may indicate that both AT
and HR routing may be mixed.
240927 09:43:55 |W9GM-1??? Incoming Connect from W9GM
240927 09:43:55 >W9GM-1??? [BPQ-6.0.24.42-B1FWIHJM$]
240927 09:43:55 >W9GM-1??? Welcome expert user Ken W9GM
240927 09:43:55 >W9GM-1??? de NC8Q>
240927 09:43:57 <W9GM-1??? [BPQ-6.0.24.42-B1FIHJM$]
240927 09:43:57 <W9GM-1??? FA B KF5JRV USA WX 1711_KF5JRV 3582
240927 09:43:57 <W9GM-1??? F> 67
240927 09:43:57 >W9GM-1??? FS +
240927 09:43:59 |W9GM-1??? Uncompressing Message Comp Len 1583 Msg
Len 3582 CRC 8dd6
240927 09:43:59 ?W9GM-1??? Msg 27384 Routing Trace To WX Via USA
240927 09:43:59 ?W9GM-1??? Routing Trace Type B (Flood) TO WX VIA
USA Route On WW NA USA (null) (null)
240927 09:43:59 ?W9GM-1??? Routing Trace AT WX Matches BBS K5DAT
240927 09:43:59 ?W9GM-1??? Routing Trace HR WW NA USA (null) (null)
Matches BBS KA1VSC
240927 09:43:59 ?W9GM-1??? Routing Trace AT WX Matches BBS KB8PMY
240927 09:43:59 ?W9GM-1??? Routing Trace AT WX Matches BBS KB8UVN
240927 09:43:59 ?W9GM-1??? Routing Trace HR WW NA USA (null) (null)
Matches BBS KB9PVH
240927 09:43:59 ?W9GM-1??? Routing Trace AT WX Matches BBS KC8SLY
240927 09:43:59 ?W9GM-1??? Routing Trace HR WW NA USA (null) (null)
Matches BBS KE0GB
240927 09:43:59 ?W9GM-1??? Routing Trace AT WX Matches BBS KF8I
240927 09:43:59 ?W9GM-1??? Routing Trace AT WX Matches BBS N2LC
240927 09:43:59 ?W9GM-1??? Routing Trace AT WX Matches BBS N3FUD
240927 09:43:59 ?W9GM-1??? Routing Trace HR WW NA USA (null) (null)
Matches BBS N3MEL
240927 09:43:59 ?W9GM-1??? Routing Trace AT WX Matches BBS N5MDT
240927 09:43:59 ?W9GM-1??? Routing Trace HR WW NA USA (null) (null)
Matches BBS N9LYA
240927 09:43:59 ?W9GM-1??? Routing Trace AT WX Matches BBS N9SEO
240927 09:43:59 ?W9GM-1??? Routing Trace HR WW NA USA (null) (null)
Matches BBS W9GM
240927 09:43:59 ?W9GM-1??? Routing Trace HR WW NA USA (null) (null)
Matches BBS WB4WPF
240927 09:43:59 ?W9GM-1??? Routing Trace AT WX Matches BBS WW6Q
240927 09:43:59 ?W9GM-1??? Routing Trace - No Match
240927 09:43:59 >W9GM-1??? FF
73, Chuck
|
Re: Hierarchical routing not working
On Thu, Sep 26, 2024 at 05:50 PM, Eric H. Christensen wrote:
240926 20:43:18 ?KA1VSC-4 Routing Trace USA Matches AT KA1VSC
This may be a hint.? Do you have USA in the AT Calls of the KA1VSC forwarding record?
?
Not sure but my belief is that since the TO Calls and AT Calls are processed first, if any matches are found in those the HR processing does not take place.? This shows that a match was found in the AT Calls of the KA1VSC forwarding record.? Processing halts at that point.
?
So, since you have a small installation it would be easy for you to remove all heirarchical routing from the AT Calls and put them in the HR field..., or remove all from the HR field and use the AT Calls.? One or the other, but I don't think it will work mixed.
?
You can try that or if someone else has a thought, or John adds something, that is where I am on this.
?
?
?
|
Re: Hierarchical routing not working
240926 20:43:12 |KA1VSC-4 Incoming Connect from KA1VSC
240926 20:43:12 >KA1VSC-4 [BPQ-6.0.24.42-B1FWIHJM$]
240926 20:43:12 >KA1VSC-4
240926 20:43:12 >KA1VSC-4 de WG3K>
240926 20:43:13 <KA1VSC-4 [BPQ-6.0.24.38-B1FIHJM$]
240926 20:43:13 <KA1VSC-4 FA B N3MEL USA WX 49844_N3MEL 8998
240926 20:43:13 <KA1VSC-4 F> C6
240926 20:43:13 >KA1VSC-4 FS +
240926 20:43:18 |KA1VSC-4 Uncompressing Message Comp Len 4346 Msg Len 8998 CRC 28
240926 20:43:18 ?KA1VSC-4 Msg 8641 Routing Trace To WX Via USA
240926 20:43:18 ?KA1VSC-4 Routing Trace Type B TO WX VIA USA Route On WW NOAM USA (null) (null)
240926 20:43:18 ?KA1VSC-4 Routing Trace USA Matches AT KA1VSC
240926 20:43:18 >KA1VSC-4 FF
240926 20:43:19 <KA1VSC-4 FQ
240926 20:43:19 |KA1VSC-4 KA1VSC-4 Disconnected
|
Re: Hierarchical routing not working
On Thu, Sep 26, 2024 at 11:22 AM, Eric H. Christensen wrote:
Here is from the log:
240926 01:49:54 ?WG3K Msg 8624 Routing Trace To WX Via USA
240926 01:49:54 ?WG3K Routing Trace Type B TO WX VIA USA Route On WW NOAM USA (null) (null)
240926 01:49:54 ?WG3K Routing Trace USA Matches AT N3HYM
So, instead of seeing N3HYM and KA1VSC and KB3KOW, I'm just seeing N3HYM.
Can you provide the complete log entry?? For example... from the incoming connect all the way to the disconnect?
?
240926 09:34:36 |KA1VSC-4 ?Incoming Connect from KA1VSC
240926 09:34:36 >KA1VSC-4 ?[BPQ-6.0.24.42-B1FWIHJM$]
240926 09:34:36 >KA1VSC-4 ?Hello Matt. Latest Message is 52915, Last listed is 0
240926 09:34:36 >KA1VSC-4 ?de N5MDT>
240926 09:34:38 <KA1VSC-4 ?[BPQ-6.0.24.38-B1FIHJM$]
240926 09:34:38 <KA1VSC-4 ?FA B N3MEL USA WX 49819_N3MEL 9433
240926 09:34:38 <KA1VSC-4 ?F> D3
240926 09:34:38 >KA1VSC-4 ?FS +
240926 09:34:43 |KA1VSC-4 ?Uncompressing Message Comp Len 4368 Msg Len 9433 CRC dd53
240926 09:34:43 ?KA1VSC-4 ?Msg 52916 Routing Trace To WX Via USA
240926 09:34:43 ?KA1VSC-4 ?Routing Trace Type B (Flood) TO WX VIA USA Route On WW NOAM USA (null) (null)
240926 09:34:43 ?KA1VSC-4 ?Routing Trace HR WW NOAM USA (null) (null) Matches BBS K5DAT
240926 09:34:43 ?KA1VSC-4 ?Routing Trace HR WW NOAM USA (null) (null) Matches BBS K7EK
240926 09:34:43 ?KA1VSC-4 ?Routing Trace HR WW NOAM USA (null) (null) Matches BBS K9CTB
240926 09:34:43 ?KA1VSC-4 ?Routing Trace HR WW NOAM USA (null) (null) Matches BBS KA1VSC
240926 09:34:43 ?KA1VSC-4 ?Routing Trace HR WW NOAM USA (null) (null) Matches BBS KA5D
240926 09:34:43 ?KA1VSC-4 ?Routing Trace HR WW NOAM USA (null) (null) Matches BBS KC6UCN
240926 09:34:43 ?KA1VSC-4 ?Routing Trace HR WW NOAM USA (null) (null) Matches BBS KF5JRV
240926 09:34:43 ?KA1VSC-4 ?Routing Trace HR WW NOAM USA (null) (null) Matches BBS N2GWK
240926 09:34:43 ?KA1VSC-4 ?Routing Trace HR WW NOAM USA (null) (null) Matches BBS N2UEM
240926 09:34:43 ?KA1VSC-4 ?Routing Trace HR WW NOAM USA (null) (null) Matches BBS N3HYM
240926 09:34:43 ?KA1VSC-4 ?Routing Trace HR WW NOAM USA (null) (null) Matches BBS N4NVD
240926 09:34:43 ?KA1VSC-4 ?Routing Trace HR WW NOAM USA (null) (null) Matches BBS N4QMI
240926 09:34:43 ?KA1VSC-4 ?Routing Trace HR WW NOAM USA (null) (null) Matches BBS N6PNK
240926 09:34:43 ?KA1VSC-4 ?Routing Trace HR WW NOAM USA (null) (null) Matches BBS N9PNO
240926 09:34:43 ?KA1VSC-4 ?Routing Trace HR WW NOAM USA (null) (null) Matches BBS NC8Q
240926 09:34:43 ?KA1VSC-4 ?Routing Trace HR WW NOAM USA (null) (null) Matches BBS NJ3H
240926 09:34:43 ?KA1VSC-4 ?Routing Trace HR WW NOAM USA (null) (null) Matches BBS NM5PB
240926 09:34:43 ?KA1VSC-4 ?Routing Trace HR WW NOAM USA (null) (null) Matches BBS W0ARP
240926 09:34:43 ?KA1VSC-4 ?Routing Trace HR WW NOAM USA (null) (null) Matches BBS W5JEP
240926 09:34:43 ?KA1VSC-4 ?Routing Trace HR WW NOAM USA (null) (null) Matches BBS W9NPA
240926 09:34:43 ?KA1VSC-4 ?Routing Trace HR WW NOAM USA (null) (null) Matches BBS WA9JG
240926 09:34:43 ?KA1VSC-4 ?Routing Trace HR WW NOAM USA (null) (null) Matches BBS WB4MOZ
240926 09:34:43 ?KA1VSC-4 ?Routing Trace HR WW NOAM USA (null) (null) Matches BBS WG0A
240926 09:34:43 ?KA1VSC-4 ?Routing Trace HR WW NOAM USA (null) (null) Matches BBS WW2BSA
240926 09:34:43 ?KA1VSC-4 ?Routing Trace HR WW NOAM USA (null) (null) Matches BBS WY7EMT
240926 09:34:43 ?KA1VSC-4 ?Routing Trace - No Match
240926 09:34:43 >KA1VSC-4 ?FF
240926 09:34:44 <KA1VSC-4 ?FQ
240926 09:34:45 |KA1VSC-4 ?KA1VSC-4 Disconnected
|
Re: Hierarchical routing not working
On Thursday, September 26th, 2024 at 10:02, Mark Taylor <mtaylor@...> wrote: Ok, please confirm...
The 11 messages that are queued to him, none of them are addressed to @USA? Correct. Find a section of the BBS Log where you received a message addressed to @USA and show us the bps process of selecting which BBS to forward to... Here is from the log: 240926 01:49:54 ?WG3K Msg 8624 Routing Trace To WX Via USA 240926 01:49:54 ?WG3K Routing Trace Type B TO WX VIA USA Route On WW NOAM USA (null) (null) 240926 01:49:54 ?WG3K Routing Trace USA Matches AT N3HYM So, instead of seeing N3HYM and KA1VSC and KB3KOW, I'm just seeing N3HYM. In your Flood bulls you have WW,NOAM,USA.? All of those are not necessary.? WW will get everything. You can delete NOAM and USA. Okay, I've removed those. Will the messages forward if you click the Start Forwarding button?? No, there aren't any @USA messages queued. 73, Eric WG3K
|
Re: Hierarchical routing not working
Ok, please confirm...
?
The 11 messages that are queued to him, none of them are addressed to @USA?
Find a section of the BBS Log where you received a message addressed to @USA and show us the bps process of selecting which BBS to forward to...
?
In your Flood bulls you have WW,NOAM,USA.? All of those are not necessary.? WW will get everything. You can delete NOAM and USA.
?
Will the messages forward if you click the Start Forwarding button??
?
The connect script shown is an RF VHF path.
Find the section of the BBS Log where an attempt is made to send those messages.
?
?
Since you have shown the forwarding record with 11 message queued I'm really trying to determine if it is a connection issue or a forwarding issue...
?
?
?
?
|
Re: Hierarchical routing not working
Attached is a screenshot of my settings.
73,
Eric WG3K
FM18rp
Packet: WG3K@WG3K.#SMD.MD.USA.NOAM
E-Mail: wg3k@...
toggle quoted message
Show quoted text
On Monday, September 23rd, 2024 at 23:38, Mark Taylor <mtaylor@...> wrote: Post some images of the routing for a BBS you think should get USA bulletins.
Looks like you have 2 AXIP connections.? It will not send back to the station that you received it from... lets see the routing for the other station.
And the User as well....
Sometimes all it takes is a typo... in this case it might be something from the changelog going to .42
|
