OpenBCM V1.08-4-g0592 (Linux)

Login: GUEST @ JH4XSY.14.JNET1.JPN.AS [Tsuchiura]

Command:
home | newest check | boards | help index | log | ps | userlogin | send sysop | slog | status forward | bcm news | users | version | remove cookie
VE4KLM > JNOS     16.11.25 23:30l 24 Lines 731 Bytes #17 (0) @ WW
BID : C1HK8_VE4KLM
Read: JH4XSY GUEST
Subj: new forward.bbs fallback route (connection)
Path: JH4XSY<N3HYM<VE3CGR<VE4KLM
Sent: 251116/1427z @:VE4KLM.#WPG.MB.CAN.NOAM [Winnipeg] $:C1HK8_VE4KLM

Charles had asked about this, perhaps useful to some of you.

 15Nov2025, forward.c - fallback connection in case primary fails, note the
  new ALT directive in the example 'spool/forward.bbs' entry below. If JNOS
  fails to connect over the vhf port, then it will try to use a wormhole :

    ---------
    ve4pkt
    c vhf ve4pkt ALT c ax0 ve4pkt-1
    ve4pkt
    ww
    --------

Or looking at the BPQ example, it looked like the emphasis was if you can't
connect direct, then try using a digipeater instead, something like this ?

    c vhf ve4pkt ALT c vhf ve4pkt digi1 ... digiN

Just the one source file, in the development REPO, sorry I have not done
a great job with the house keeping and documentation.

Maiko / VE4KLM



前のメール | 次のメール