[nos-bbs] the 'noiac' or 'useiac' can of worms ...

['Gustavo Ponza']

Hi Michael,

now it's night here... and tests, if any, continue tomorrow.
OK for confirming some data about the BPQ ports... the
plain or the compress forwarding may derive from setups.

We are linked via BPQ node and XNET node and  not
via telnet.

However, just consider to leave definitively apart that
'mbox fbb 2' as that trouble the new native mode of
JNOS2 and so, your tests, that of Bob, of mine and
others become no correlated each other:)

73, gus


On 04/19/2016 05:37 PM, Michael Fox - N6MEF wrote:
> Hi Gus,
>
> I've seen the same thing with regard to the TCP ports when forwarding with a BPQ station here.  The "transparent" port doesn't answer with a SID.  The regular telnet port answers with the usual user/password prompts and then displays the SID.  So that's what I use.
>
> However, as you may have seen in an earlier message on this list, the telnet IAC fix in "2.0j.7v.bleeding" breaks inbound compressed FBB forwarding with BPQ.  And it looks like outbound compressed FBB forwarding with BPQ using "mbox fbb 2" also doesn't work.  I'll be sending a report on that shortly.  But the outbound problem may not be new.  It seems to exist in plain 2.0j.7v as well.  I'll gather my data and submit the report later today.
>
> I don't think I've seen the type of problem you're showing with plain MBL/RLI forwarding.  But I can also run that test later today.
>
> Michael
> N6MEF
>
>
>> -----Original Message-----
>> From: nos-bbs [mailto:nos-bbs-bounces at tapr.org] On Behalf Of 'Gustavo
>> Ponza'
>> Sent: Tuesday, April 19, 2016 7:48 AM
>> To: TAPR xNOS Mailing List <nos-bbs at tapr.org>
>> Subject: Re: [nos-bbs] the 'noiac' or 'useiac' can of worms ...
>>
>> All correct 100% Bob and naturally to Maiko again very TNX!
>>
>> As per general information I want to participate to all
>> of you that, since this early morning I completely shut
>> down the gorgeous obcm and the xdfbb and remain in
>> full production with this last JNOS2 improve together
>> with the new entry test set, namely the emerging LinBPQ.
>>
>> I'm puzzled of many data but can confirm that bpq at
>> VE3UIL is doing reverse forwarding in plain MBL/RLI style
>> toward the new I0OJJ-8 equipped by the 'bleed' JNOS2.
>>
>> However, something obscure happens...:
>>
>> 12:40:13  I0OJJ-3 on port xnet - MBOX (ve3uil) reverse forwarding mail
>> 12:40:13  I0OJJ-3 on port xnet - MBOX (ve3uil) proposal SB ALL @ WW <
>> UT1HZM
>> 12:40:17  I0OJJ-3 on port xnet - MBOX (ve3uil) sent $38970_ut1hzm
>> 12:40:17  I0OJJ-3 on port xnet - MBOX (ve3uil) proposal SB ALL @ EU <
>> I3XTY
>> 12:40:17  - about to send ['Re:' is no command
>> ]
>> 12:40:17  - looks like sent [=>
>> ]
>> 12:40:17  I0OJJ-3 on port xnet - MBOX (ve3uil) sent $28243v_i3xty
>> 12:40:17  I0OJJ-3 on port xnet - MBOX (ve3uil) proposal SB SATDIG @ WW <
>> CX2SA
>> 12:40:17  - about to send ['R:160417/1032z' is no command
>> ]
>> 12:40:17  - looks like sent [=>
>> ]
>> 12:40:17  I0OJJ-3 on port xnet - MBOX (ve3uil) sent $amsatbb11119
>> 12:40:18  I0OJJ-3 on port xnet - MBOX (ve3uil) proposal SB SATDIG @ WW <
>> CX2SA
>> 12:40:18  - about to send ['R:160417/1029z' is no command
>> ]
>> 12:40:18  - looks like sent [=>
>> ]
>> 12:40:18  I0OJJ-3 on port xnet - MBOX (ve3uil) sent $amsatbb11120
>> 12:40:18  I0OJJ-3 on port xnet - MBOX (ve3uil) proposal SB SATDIG @ WW <
>> CX2SA
>> 12:40:18  - about to send ['R:160417/1029z' is no command
>> ]
>> 12:40:18  - looks like sent [=>
>> ]
>> 12:40:18  I0OJJ-3 on port xnet - MBOX (ve3uil) sent $amsatbb11121
>> 12:40:18  I0OJJ-3 on port xnet - MBOX (ve3uil) proposal SB KEPS @ AMSAT
>> < CX2SA
>> 12:40:18  - about to send ['R:160417/1028z' is no command
>> ]
>> 12:40:18  I0OJJ-3 on port xnet - MBOX (ve3uil) fwd exit
>> -------------------------
>>
>>
>> For not forget the problem: I noted that the forwarding
>> time rate of JNOS2 is about half an hour or a little more
>> and so too high for a normal operation,  I'd like that
>> Maiko introduce a *cron job* style feature for this need
>> and useful for other production PBBS routines.
>> A minimal msg editor on the console should be needed too.
>>
>> For BPQ, if it functions, and as per my poor understanding,
>> the full compatibility with the JNOS2 should be reached
>> if the JNOS2 can fully use its TCPPORT which is claimed
>> as a real TCP connect... and NOT the so called FBBPORT
>> which was created by the author for the transparent TCP
>> connects, namely that used by the xdfbb forwarding :))
>> Then there is the dot (.) behind the caller... which is
>> understood only by the FBB systems, etc. ... but I just
>> speedy read ... and perhaps I can be confused :)
>>
>> However Bob et al you may try if you want.
>>
>> 73, gus
>>
>
> _______________________________________________
> nos-bbs mailing list
> nos-bbs at tapr.org
> http://www.tapr.org/mailman/listinfo/nos-bbs