OpenBCM V1.07b12 (Linux)

Packet Radio Mailbox

DB0FFL

[Box DB0FFL]

 Login: GAST





  
N2NOV  > SYSOP    28.03.24 05:32l 38 Lines 1397 Bytes #999 (0) @ WW
BID : 9DT5_N2NOV
Read: GAST
Subj: B2F or not B2F? Use B1F in BPQ if Unsure
Path: DB0FFL<OE5XBL<OE2XZR<OE6XPE<DB0ERF<DB0RES<SR4BBX<SR1BSZ<IW0QNL<JH4XSY<
      N3HYM<N2NOV
Sent: 240328/0121z @:N2NOV.#RICH.NY.USA.NOAM $:9DT5_N2NOV

Unless your forwarding partner is WL2K or BPQ, do not automatically set
their system as accepting B2F. All modern systems can do B1F, but not
all can do B2F as this is reserved for encryption and file attachments.

When a non-B2F system like JNOS encounters a BPQ system that has either B2F or
B2F+B1F set, then the JNOS system has "FBBFWD: remote disconnected early."
in the logs and the connection drops. You would see something similar in
the FBB systems as they do not do B2F either. B2F was invented by WL2K.

>From KA1VSC recently:
> To prevent unwanted B2 forwarding, BPQ BBS Sysops need to configure 
> their NON BPQ forwarding partners this way:
> 
> 1- User account is NOT flagged as a RMS Express User.
> (example:)
> 
>       Update User N2NOV
> X     BBS                             Permit Email
>       PMS                             RMS Express User
>       SYSOP                           Poll RMS
> X     Expert                          For SSID's
>       Excluded                        Hold Messages
>       Include SYSOP msgs in LM        Don't add @ winlink.org
> X     Allow Sending Bulls             NTS MPS
>       Redirect to RMS
>       Send APRS Mail For to SSID
> 
> 2- Forwarding Record has Allow Binary & Use B1 Protocol checked (if you
> want binary)
> (example:)
> Allow Binary  Use B1 Protocol

--
73 de N2NOV
n2nov@n2nov.ampr.org
n2nov@n2nov.#rich.ny.usa.noam



Lese vorherige Mail | Lese naechste Mail


 21.11.2024 13:33:23lZurueck Nach oben