| |
AL0Y > SYSOP 20.12.20 23:01l 150 Lines 5551 Bytes #999 (0) @ WW
BID : 585_AL0Y
Read: GUEST
Subj: Let's talk routing and forwarding :)
Path: IW8PGT<IZ3LSV<IK5FKA<IK5FKA<LU9HGS<LU3DVN<LU4DRH<W4GON<W9GM<KK4DIV<
AL0Y
Sent: 201220/2056Z @:AL0Y.#NNJ.NJ.USA.NOAM #:585 [WAYNE] $:585_AL0Y
From: AL0Y@AL0Y.#NNJ.NJ.USA.NOAM
To : SYSOP@WW
Let's talk routing...
Hello, SYSOPs...
Let's have a small chi-chat about routing messages through the network.
I believe all SYSOPs should allocate sometime (at least once a month) to dicuss with their forwarding
partners, how to route messages across the network.
They should put together a table of where to send which messages. Doing so, will guarantee much more confidence
that when you send a message, it will achieve its destiantion, and with minimal points of failure as possible.
This also makes sure that we don't waste valueable resources like airwaves by jamming them with repeated messages,
or unneccessary messages because the routing is incorrect.
I know for fact, I personally have lost a number of messages (both incoming and outgoing) because they incorrectly
reached a station that didn't know what to do with them. And I guess we all have been there at least once before.
It doesn't matter how you configure forwarding; whether you use BPQ, *NOS, FBB, or any other BBS system...
as long as the configuraion is correct, and you are not sending messages to a station that doesn't know what
to do with those messages, you should be fine.
Have a talk with your forwarding partners. I did with all my 14 partners I forward to.
I collected from each one of them what HRoutes they accpet messages to, and I came up with the following
mini-map of routing:
WW:
|
|- NOAM:
| |- USA:
| | |- AR: (via N5MDT)
| | |- CA: (via N2NOV)
| | |- CO: (via W0ARP)
| | | |- #SECO (via K5DAT, W0ARP)
| | |
| | |- FL: (via KD8FMR)
| | | |- #NWFL (via KD8FMR)
| | | |- #SRQ (via KK4DIV, KD8FMR)
| | |
| | |- ID: (via N5MDT)
| | |- IL: (via KK4DIV, N2NOV)
| | |- IN: (via N5MDT)
| | |- MD: (via N5MDT)
| | |- KY: (via K5DAT)
| | |- MI: (via K5DAT)
| | |- MN: (via N5MDT)
| | |- NJ: (via AL0Y, KY2D, W2LI)
| | |- NY: (via N2KGC, N2NOV)
| | | |- KD2MDV (via KD2MDV)
| | |
| | |- OH: (via KD8FMR)
| | |- OR: (via K5DAT)
| | |- PA:
| | | |- #SEPA (via N5MDT)
| | | |- #EPA (via KK4DIV)
| | |
| | |- TX: (via N5MDT)
| | |- WI: (via K5DAT)
| | |- #CWI (via K5DAT)
| | |- #SWWI (via KK4DIV)
| |
| |- CAN: (via VE2PKT)
| | |- BC (via VE2PKT, PE1RRR)
| | |- MB (via VE2PKT)
| | |- ON (via VE2PKT)
| | |- QC (via VE2PKT, PE1RRR)
| |
| |- MEX: (via N5MDT)
|
|- CEAM: (via N5MDT)
|
|- SOAM:
| |- BRA: (via PY2BIL)
| | |- #SPA (via PY2BIL)
| |- ARG: (via LU4EGV)
| |- BA (via LU4EGV)
|
|- EURO:
| |- BEL: (via VE2PKT)
| |- DEU: (Via GM7YEW, PE1RRR)
| |- FRA:
| | |- FRHA (via PE1RRR)
| | |- FAQI (via VE2PKT)
| |
| |- FIN:
| | |- KOU (via PE1RRR)
| |
| |- GBR: (via GM7YEW)
| | |- #29 (via PE1RRR)
| | |- #32 (via PE1RRR)
| | |- #38 (via PE1RRR)
| | |- #44 (via PE1RRR)
| | |- #48 (via PE1RRR)
| | |- #79 (Via GM7YEW)
| |
| |- ITA: (via IZ5FSA, PE1RRR)
| | |- I0OJJ (via VE2PKT)
| | |- IUMB (via VE2PKT)
| | |- IFVG (via PE1RRR)
| |
| |- IRL:
| | |- DGL (via PE1RRR)
| |
| |- NLD: (via PE1RRR)
| | |- #FRL (via PE1RRR)
| | |- #NBW (via PE1RRR)
| | |- #ZH (via PE1RRR)
| | |- #ZH1 (via PE1RRR)
| |
| |- PRT: (via PR1RRR)
| |- RUS: (via VE2PKT)
| |- SWE: (via N5MDT)
| |- UKR:
| |- KHE (via PE1RRR)
| |- POL (via PE1RRR)
|
|- AUNZ: (via N5MDT, VE2PKT)
| |- AUS: (via N5MDT, VE2PKT)
| |- NSW (via N5MDT, VE2PKT, PE1RRR)
|
|- SAFR:
| |- ZAF: (via via GM7YEW)
Now, each of my forwarding partners know where I can forward to.
If any of them need to forward to some of the locations in my previous mini-map, and they don't have a direct
outlet to send to, they can set that HRoute to be forwarded to my BBS, and I will move it on based on its
destination to another station that I know can handle that route.
I wouold like to ask all SYSOPs, to do th same. To get the conversation started. To build a better and a stronger
communication network. A network we can rely on whether for personal communication, or EmComms. A network that will be there when everything else fails.
If you are afraid that the Internet and emails will kill BBS and this great facet of the great ham radio hobby,
let's do it. let's build it together.
If you need help with setting up your BBS system, or want to make sure you are doing it the way it should be done, then
let's all talk. post your questions to SYSOP@WW, or send a message to your forwarding partners, or even send me a message
and I am sure we will get you there.
Feel too lazy to do any configuration on your BBS? at least tell your partners who you already have links with...
so they can send messages your way for forwarding...
But whatever you do, please do not let the message get lost in your system...
73 and happy holidays .. de AL0Y
Read previous mail | Read next mail
| |
