[nos-bbs] BPQ (inits connection) to JNOS and forwarding

[maiko at pcsinternet.ca]

Sorry, should have mentioned it first - Lee is correct

On 2024-12-30 12:39, maiko at pcsinternet.ca wrote:

> No ! At some point I had put in BBS validation, mixed feelings on
> it when Brian (N1URO) was still around, we bickered on that, but
> the bottom line is in /jnos/ftpusers :
> 
>   ve7ass passwordwhatever /root/jnos/rte/public 0x0605f
> 
> NOTE : the 0x06 vs the usual 0x04, the additional bit was
>   put in to tell JNOS it was okay to accept SID from that
>    user. Supposed to be a security feature.
> 
> IF YOU DON'T CARE FOR THAT :
> 
>  1) edit config.h and #define J2_DONT_ENFORCE_BBS_USER
> 
>  2) rm mboxmail.o ; make ; use new JNOS binary
> 
> Maiko / VE4KLM
> 
> On 2024-12-30 12:16, Lee D Bengston wrote:
>> On Mon, Dec 30, 2024 at 12:02 PM jerome schatten <romers at shaw.ca>
>> wrote:
>> 
>>> I wonder if the problem I’m having: 'bpq inits forwarding to jnos
>>> and fails’ is the same as what’s being discussed here? Below is
>>> what happens when BPQ initiates a forward cycle with jnos on my lan:
>>> 
>>> VE7ASS is BPQ & VE7POO is JNOS.
>>> -------------------
>>> 
>>> VE7ASS-1 to VE7POO-7 ttl 25 cct=0294 <CON REQ> w=4 VE7ASS-1 at
>>> VE7ASS-1 t/o 60
>>> 05:16:38R VE7POO-7>VE7ASS-7 Port=3 <RR R F R1>
>>> 05:16:40R VE7POO-7>VE7ASS-7 Port=3 <I C S0 R1> NET/ROM
>>> VE7POO-7 to VE7ASS-1 ttl 15 cct=0294  <CON ACK> w=0 my cct=0125
>>> 05:16:40R VE7POO-7>VE7ASS-7 Port=3 <I C S1 R1> NET/ROM
>>> VE7POO-7 to VE7ASS-1 ttl 15 cct=0294  <INFO S0 R0>:
>>> [JNOS-2.0p-B1FHIM$]
>>> You have 0 messages.
>>> YVRPOO:VE7POO-7 Area: ve7ass (#0) >
>>> 05:16:40T VE7ASS-7>VE7POO-7 Port=3 <I C P S1 R2> NET/ROM
>>> VE7ASS-1 to VE7POO-7 ttl 25 cct=0125  <INFO S0 R1>:
>>> [BPQ-6.0.24.1-IHJM$]
>>> 05:16:40R VE7POO-7>VE7ASS-7 Port=3 <RR R F R2>
>>> 05:16:44R VE7POO-7>VE7ASS-7 Port=3 <I C S2 R2> NET/ROM
>>> VE7POO-7 to VE7ASS-1 ttl 15 cct=0294  <INFO S1 R1>:
>>> *** User NOT configured for BBS operation
>>> Bad syntax.
>>> YVRPOO:VE7POO-7 Area: ve7ass (#0) >
>>> 05:16:44R VE7POO-7>VE7ASS-7 Port=3 <I C S3 R2> NET/ROM
>>> VE7POO-7 to VE7ASS-1 ttl 15 cct=0294  <INFO ACK R1>
>>> 05:16:44T VE7ASS-7>VE7POO-7 Port=3 <I C P S2 R4> NET/ROM
>>> VE7ASS-1 to VE7POO-7 ttl 25 cct=0125  <INFO S1 R2>:
>>> SP VE7POO @ VE7POO < VE7ASS $28585_VE7ASS
>>> 05:16:44R VE7POO-7>VE7ASS-7 Port=3 <RR R F R3>
>>> 05:16:47T VE7ASS-7>VE7YSF-10 Port=1 <RR C P R2>
>>> 05:16:48R VE7POO-7>VE7ASS-7 Port=3 <I C S4 R3> NET/ROM
>>> VE7POO-7 to VE7ASS-1 ttl 15 cct=0294  <INFO S2 R2>:
>>> To: allmail
>>> Subject:
>>> 05:16:48R VE7POO-7>VE7ASS-7 Port=3 <I C S5 R3> NET/ROM
>>> VE7POO-7 to VE7ASS-1 ttl 15 cct=0294  <INFO ACK R2>
>>> 05:16:48T VE7ASS-7>VE7POO-7 Port=3 <I C P S3 R6> NET/ROM
>>> VE7ASS-1 to VE7POO-7 ttl 25 cct=0125  <INFO S2 R3>:
>>> *** Error: Invalid Format
>>> 05:16:48R VE7POO-7>VE7ASS-7 Port=3 <RR R F R4>
>>> 05:16:49R VE7YSF-10>VE7ASS-7 Port=1 <RR R F R5>
>>> 05:16:52R VE7POO-7>VE7ASS-7 Port=3 <I C S6 R4> NET/ROM
>>> VE7POO-7 to VE7ASS-1 ttl 15 cct=0294  <INFO S3 R3>:
>>> Enter message.  End with /EX or ^Z in first column (^A aborts):
>>> 05:16:52R VE7POO-7>VE7ASS-7 Port=3 <I C S7 R4> NET/ROM
>>> VE7POO-7 to VE7ASS-1 ttl 15 cct=0294  <INFO ACK R3>
>>> ...
>>> -------------------------------
>>> 
>>> My take on this is that poo does not think ass is a bbs and treats
>>> the connection as if ass is simply sending a message on the bbs. Yet
>>> ass can connect and forward other jnos bbs’s, without a problem.
>>> So I have reason to think that the problem is on the jnos side. BPQ
>>> shows that the netrom link between the two stations is working fine.
>>> 
>>> 
>>> Jnos has only the lan connection to BPQ — BPQ has the internet
>>> connection.
>>> 
>>> So… is this the problem you were discussing in this thread or is
>>> this a different problem? In either case, I need some help with
>>> this.
>>> 
>>> Thanks, and a peaceful and healthy new year to you all!
>>> jerome - ve7ass & ve7poo
>> 
>> Hello Jerome,
>> 
>> Yes, it's been a while since I played with JNOS, but I do recall that
>> there is a way to configure the JNOS instance to understand that
>> VE7ASS is a BBS. It's the rough equivalent to "checking the BBS box"
>> in BPQ. I forget how to do it in JNOS, however. Unlike BPQ, once JNOS
>> understands VE7ASS is a BBS, it will not accept messages left manually
>> via a terminal from VE7ASS - will only accept them forwarded from the
>> BBS. That's how it used to work the last time I tried to manually
>> leave a message to a JNOS BBS that was accepting forwarded messages
>> from my BBS, but I'm not 100% sure if it still works that way.
>> 
>> 73,
>> Lee K5DAT
>> _______________________________________________
>> nos-bbs mailing list
>> nos-bbs at lists.tapr.org
>> http://lists.tapr.org/mailman/listinfo/nos-bbs_lists.tapr.org