Problem solved. I ended up amending the rewrite file to deal with the culprit messages.<div>Don -ve3zda<br><br>On Monday, 18 April 2016, Don Moore <<a href="mailto:ve3zda@gmail.com">ve3zda@gmail.com</a>> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">FYI: I've had similar problems since yesterday but have not upgraded to the latest Jnos.<div>I'll get a request from a station to forward to me and Jnos responds giving the go ahead.</div><div>Almost right after that, and it's the last item in the log, all users are locked out including the sysop. I can see that Jnos is still running because of the activity on tun0.</div><div>The only way out is to reboot the Pi. After fighting with it I decided to have Jnos restart automatically every 15 minutes.</div><div>If there is a fix for this or someone knows what is causing this, I'd sure like to know!</div><div>Is it possible the other end upgraded and now we can't communicate properly?</div><div>Is it possible that the other end is not 'hearing' me and my end sits and waits, locking everyone out?</div><div><br></div><div>Cheers, Don - ve3zda<br><br>On Monday, 18 April 2016, Michael Fox - N6MEF <<a href="javascript:_e(%7B%7D,'cvml','n6mef@mefox.org');" target="_blank">n6mef@mefox.org</a>> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Maiko,<br>
<br>
One error (I think) and one improvement request regarding FBB error<br>
handling:<br>
<br>
<br>
1) End of line termination error?<br>
<br>
In the example below, N6MEF is jnos 2.0j.7v with "bleeding edge" fixes.<br>
AG6QO is a BPQ station.<br>
Look at the last two packets. Notice that the "*** Protocole" (sp?) line<br>
sent by JNOS ends with only a line feed (\x0a) and the "FQ" line ends with<br>
only a carriage return (\x0d). Both should end with CRLF (\x0d\x0a), right?<br>
<br>
Date/Time Src Dst Telnet Data<br>
<br>
Apr 18, 2016 03:48:35.016291000 N6MEF ag6qo \x0d\x0a,JNOS<br>
(<a href="http://n6mef.ampr.org" target="_blank">n6mef.ampr.org</a>)\x0d\x0a,\x0d\x0a,login:<br>
Apr 18, 2016 03:48:35.093917000 ag6qo N6MEF<br>
.AG6QO\x0d\x0a,********\x0d\x0a<br>
Apr 18, 2016 03:48:35.094427000 N6MEF ag6qo Password:<br>
Apr 18, 2016 03:48:35.133692000 N6MEF ag6qo<br>
\x0d[JNOS-2.0j.7v.XSC32.3-BFHIM$]\x0d>\x0d<br>
Apr 18, 2016 03:48:35.519054000 ag6qo N6MEF<br>
[BPQ-6.0.12.25-BFIHJM$]\x0dFA B G8MNY WW TECH 1766_GB7CIP 3361\x0dFA B G8MNY<br>
WW TECH 1767_GB7CIP 4976\x0dF> 04\x0d<br>
Apr 18, 2016 03:48:35.523969000 N6MEF ag6qo FS ++\x0d<br>
Apr 18, 2016 03:48:36.071589000 ag6qo N6MEF \x01!Ferrite Ring Demo<br>
circuit<br>
Apr 18, 2016 03:48:36.105448000 ag6qo N6MEF N\xd5\x12\x96[.binary data<br>
clipped for brevity.]<br>
Apr 18, 2016 03:48:36.107784000 N6MEF ag6qo *** Protocole Error (3)\x0a<br>
Apr 18, 2016 03:48:36.133338000 N6MEF ag6qo FQ\x0d<br>
<br>
<br>
2) Nos.log improvement request: please preface errors with connection info<br>
<br>
This is the JNOS log of the above telnet session. The "fbb protocol error"<br>
line doesn't say which connection it belongs to at all. The "lzhuf" and<br>
"FBBFWD" lines don't include the "MBOX(ag6qo)" info. When multiple<br>
connections are happening at the same time, the entries in nos.log can be<br>
interspersed. It would be helpful to know which connection the error<br>
belongs to. So, at a minimum, the "<ip-addr>:<port>" (or "<callsign> on<br>
port <port>") info is needed. If the "MBOX (<callsign>) info were also<br>
present it would make it easier to find all log lines with "grep 'MBOX<br>
(<callsign>)'".<br>
<br>
Mon Apr 18 03:48:35 2016 <a href="http://76.14.186.245:44915" target="_blank">76.14.186.245:44915</a> - possible airmail telnet<br>
client ...<br>
Mon Apr 18 03:48:35 2016 <a href="http://76.14.186.245:44915" target="_blank">76.14.186.245:44915</a> - MBOX (ag6qo) login<br>
Mon Apr 18 03:48:35 2016 <a href="http://76.14.186.245:44915" target="_blank">76.14.186.245:44915</a> - MBOX (ag6qo) open<br>
Mon Apr 18 03:48:35 2016 <a href="http://76.14.186.245:44915" target="_blank">76.14.186.245:44915</a> - MBOX (ag6qo) forwarding<br>
Mon Apr 18 03:48:35 2016 <a href="http://76.14.186.245:44915" target="_blank">76.14.186.245:44915</a> - MBOX (ag6qo) incoming<br>
proposal FA B G8MNY WW TECH 1766_GB7CIP 3361<br>
Mon Apr 18 03:48:35 2016 <a href="http://76.14.186.245:44915" target="_blank">76.14.186.245:44915</a> - MBOX (ag6qo) incoming<br>
proposal FA B G8MNY WW TECH 1767_GB7CIP 4976<br>
Mon Apr 18 03:48:35 2016 <a href="http://76.14.186.245:44915" target="_blank">76.14.186.245:44915</a> - MBOX (ag6qo) our response FS<br>
++<br>
Mon Apr 18 03:48:36 2016 - fbb protocol error, expecting STX or EOT<br>
Mon Apr 18 03:48:36 2016 <a href="http://76.14.186.245:44915" target="_blank">76.14.186.245:44915</a> - lzhuf: detected FBB protocol<br>
error 3<br>
Mon Apr 18 03:48:36 2016 <a href="http://76.14.186.245:44915" target="_blank">76.14.186.245:44915</a> - FBBFWD: recv_yapp() error.<br>
Mon Apr 18 03:48:36 2016 <a href="http://76.14.186.245:44915" target="_blank">76.14.186.245:44915</a> - MBOX (ag6qo) FBB error, last<br>
read : F> 04<br>
Mon Apr 18 03:48:36 2016 <a href="http://76.14.186.245:44915" target="_blank">76.14.186.245:44915</a> - MBOX (ag6qo) exit<br>
<br>
Michael<br>
N6MEF<br>
<br>
_______________________________________________ <br>
nos-bbs mailing list<br>
<a>nos-bbs@tapr.org</a><br>
<a href="http://www.tapr.org/mailman/listinfo/nos-bbs" target="_blank">http://www.tapr.org/mailman/listinfo/nos-bbs</a><br>
</blockquote></div>
</blockquote></div>