| |
WG3K > SYSOP 25.04.24 13:04l 27 Lines 1551 Bytes #999 (0) @ WW
BID : 3568_WG3K
Read: GAST
Subj: Sending WP updates
Path: DB0FFL<OE2XZR<DB0FHN<DB0RKB<DK0WUE<DB0ZAV<LU4ECL<VK2RZ<KC9UHI<KA1VSC<
WG3K
Sent: 240425/0519Z 3568@WG3K.#SMD.MD.USA.NOAM LinBPQ6.0.24
Based on a conversation that occurred on the BPQ32 email list, I'm passing along this information regarding the sending of WP updates.
== Sending WP updates
If you are sending WP updates, and you should be, make sure they are being sent as (P)ersonal messages and not (B)ulletins. Also, they should be addressed only to the BBSs that you directly connect to for forwarding. Further, it would be helpful if all BBSs rejected WP Bulletins.
In BPQ, the settings can be found on the Main Configuration page, WP Params. Select "Send WPUpdates" and "Reject WP Bulls". Select "Type P" and then under "WP Destinations" add each of your forwarding partners in this way:
WP@<BBS 1 CALLSIGN>
WP@<BBS 2 CALLSIGN>
etc.
There is no need to use the full H-route here and by not doing so you can prevent WP messages from being routed across the network instead of just one hop to your neighbor.
-----
== How WP updates work.
When a user on your BBS updates their information (name, location, home BBS, etc) your system updates its WP database. During the next housekeeping maintenance time, a WP update message will be created and sent out to your neighbors informing them of this change. This will lead to their WP databases being updated and the change that came from your BBS to be propagated out to their neighbors, and so on and so forth. Eventually, everyone on the globe will have the update that originated from your BBS.
-----
Original discussion regarding WP updates is available at https://groups.io/g/bpq32/message/41214.
73,
Eric WG3K
Lese vorherige Mail | Lese naechste Mail
| |
