<div dir="ltr"><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">On Mon, Dec 30, 2024 at 12:02 PM jerome schatten <<a href="mailto:romers@shaw.ca">romers@shaw.ca</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">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:<br>
<br>
VE7ASS is BPQ & VE7POO is JNOS. <br>
-------------------<br>
<br>
VE7ASS-1 to VE7POO-7 ttl 25 cct=0294 <CON REQ> w=4 VE7ASS-1 at VE7ASS-1 t/o 60<br>
05:16:38R VE7POO-7>VE7ASS-7 Port=3 <RR R F R1><br>
05:16:40R VE7POO-7>VE7ASS-7 Port=3 <I C S0 R1> NET/ROM<br>
VE7POO-7 to VE7ASS-1 ttl 15 cct=0294 <CON ACK> w=0 my cct=0125<br>
05:16:40R VE7POO-7>VE7ASS-7 Port=3 <I C S1 R1> NET/ROM<br>
VE7POO-7 to VE7ASS-1 ttl 15 cct=0294 <INFO S0 R0>:<br>
[JNOS-2.0p-B1FHIM$]<br>
You have 0 messages.<br>
YVRPOO:VE7POO-7 Area: ve7ass (#0) ><br>
05:16:40T VE7ASS-7>VE7POO-7 Port=3 <I C P S1 R2> NET/ROM<br>
VE7ASS-1 to VE7POO-7 ttl 25 cct=0125 <INFO S0 R1>:<br>
[BPQ-6.0.24.1-IHJM$]<br>
05:16:40R VE7POO-7>VE7ASS-7 Port=3 <RR R F R2><br>
05:16:44R VE7POO-7>VE7ASS-7 Port=3 <I C S2 R2> NET/ROM<br>
VE7POO-7 to VE7ASS-1 ttl 15 cct=0294 <INFO S1 R1>:<br>
*** User NOT configured for BBS operation<br>
Bad syntax.<br>
YVRPOO:VE7POO-7 Area: ve7ass (#0) ><br>
05:16:44R VE7POO-7>VE7ASS-7 Port=3 <I C S3 R2> NET/ROM<br>
VE7POO-7 to VE7ASS-1 ttl 15 cct=0294 <INFO ACK R1> <br>
05:16:44T VE7ASS-7>VE7POO-7 Port=3 <I C P S2 R4> NET/ROM<br>
VE7ASS-1 to VE7POO-7 ttl 25 cct=0125 <INFO S1 R2>:<br>
SP VE7POO @ VE7POO < VE7ASS $28585_VE7ASS<br>
05:16:44R VE7POO-7>VE7ASS-7 Port=3 <RR R F R3><br>
05:16:47T VE7ASS-7>VE7YSF-10 Port=1 <RR C P R2><br>
05:16:48R VE7POO-7>VE7ASS-7 Port=3 <I C S4 R3> NET/ROM<br>
VE7POO-7 to VE7ASS-1 ttl 15 cct=0294 <INFO S2 R2>:<br>
To: allmail<br>
Subject:<br>
05:16:48R VE7POO-7>VE7ASS-7 Port=3 <I C S5 R3> NET/ROM<br>
VE7POO-7 to VE7ASS-1 ttl 15 cct=0294 <INFO ACK R2> <br>
05:16:48T VE7ASS-7>VE7POO-7 Port=3 <I C P S3 R6> NET/ROM<br>
VE7ASS-1 to VE7POO-7 ttl 25 cct=0125 <INFO S2 R3>:<br>
*** Error: Invalid Format<br>
05:16:48R VE7POO-7>VE7ASS-7 Port=3 <RR R F R4><br>
05:16:49R VE7YSF-10>VE7ASS-7 Port=1 <RR R F R5><br>
05:16:52R VE7POO-7>VE7ASS-7 Port=3 <I C S6 R4> NET/ROM<br>
VE7POO-7 to VE7ASS-1 ttl 15 cct=0294 <INFO S3 R3>:<br>
Enter message. End with /EX or ^Z in first column (^A aborts):<br>
05:16:52R VE7POO-7>VE7ASS-7 Port=3 <I C S7 R4> NET/ROM<br>
VE7POO-7 to VE7ASS-1 ttl 15 cct=0294 <INFO ACK R3><br>
...<br>
-------------------------------<br>
<br>
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. <br>
<br>
Jnos has only the lan connection to BPQ — BPQ has the internet connection.<br>
<br>
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.<br>
<br>
Thanks, and a peaceful and healthy new year to you all!<br>
jerome - ve7ass & ve7poo<br>
<br></blockquote><div> </div><div>
<div>Hello Jerome,</div><div><br></div><div>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.<br></div><div><br></div><div>73,</div><div>Lee K5DAT<br></div> <br></div></div></div>