[nos-bbs] Help with Telnet BBS connection

[Maiko Langelaar (Personal)]

OR more likely, your SID may not be 'correct' ?

Maiko / VE4KLM


On 8/26/25 11:45, Maiko Langelaar (Personal) wrote:
> I just tried this, and the first thing that came to mind is ...
>
> Are the permission for the logged in call set correctly, cause if I
> type in FF after login, I get the 'Huh ?', meaning I'm not setup.
>
> Maiko
>
> On 8/26/25 10:14, David Lounsbury wrote:
>
>>
>> My jnos 2.0q BBS is having a problem exchanging bulletins with the 
>> one system (the Q1ME Maine gateway.) The connection to Q1ME uses 
>> telnet over Hamgate. The problem report is below.
>>
>> I am hoping this is just a stupid config error on my end, so any help 
>> in diagnosing this would be much appreciated. I'd be happy to provide 
>> other information or run tests if needed..
>>
>> Regards,
>> Dave Lounsbury
>> KC1UIX
>>
>> *Symptoms*:
>>
>> When my node has a bulletin to transfer, it calls Q1ME, it 
>> successfully log in, but the FBB exchange seems to fail. The typical 
>> log entries on my node report:
>>
>> 09:46:04  44.118.0.2:2300 - MBOX (Q1ME) connected
>> 09:46:04  44.118.0.2:2300 - MBOX (Q1ME) forwarding
>> 09:46:04  44.118.0.2:2300 - MBOX (Q1ME) proposal FA B KF5JRV USA WX 
>> 12050_KF5JRV 5566
>> 09:46:04  44.118.0.2:2300 - MBOX (Q1ME) FBB error, expected FS, got Huh?
>> 09:46:04  44.118.0.2:2300 - MBOX (Q1ME) fwd exit
>>
>> N2NOV (the operator of Q1ME) reports similar error messages in the 
>> Q1ME logs.
>>
>>
>> When Q1ME calls my node, transfers are successful. I can manually 
>> telnet to Q1ME using the credentials from the spool/forward.bbsfile.
>>
>>
>> Exchanges with other nodes via netrom connections are successful - 
>> the problm seem limited to telnet.
>>
>> *Attempted remedies*:
>>
>> - Tried switching from compression to no compression in the Q1ME 
>> stanza in the spool/forward.bbs file - I believe we've tried this on 
>> both ends
>> - Reviewed the permissions in the ftpusers file, which are set to: 
>> q1me * /home/jnos/rte/public 24635
>>
>> None of these corrected the problem.
>>
>>
>> *Environment*:
>>
>> Linux: Linux workbench1 6.1.0-38-amd64 #1 SMP PREEMPT_DYNAMIC Debian 
>> 6.1.147-1 (2025-08-02) x86_64 GNU/Linux
>>
>> JNOS Info:
>> JNOS 2.0q (Linux), compiled Aug 25 2025 12:22:36 by GCC 12.2
>> for YORKCTY-ME, containing:
>>
>> TCP Servers: SMTP(filtered)(deny relay exception 
>> list)(translated)(refiled) FINGER FTP TCPGATE
>>              TELNET RSYSOP TRACE TTYLINK
>>              CALLBOOK (QRZ) CONVERS NNTP POP3 HTTP TIME
>> TCP Clients: SMTP FINGER FTP TELNET TTYLINK
>>              CALLBOOK (CD-ROM) CONVERS NNTP(stat)(2mail) POP3 TIME LOOK
>>     with LZW compression for TCP sockets
>>     with TCP/IP access controls
>> UDP Servers: DOMAIN-NAMESERVER REMOTE(with DYNIP)
>> UDP Clients: REMOTE
>> TIP Mailbox Server(with DYNIP)
>> Full Service BBS with:
>>      Message and BID expiry
>>      'Mail For' beaconing
>>      AX.25 mail forwarding
>>            with FBB Style Compressed Forwarding
>>            with B2F Style Forwarding for Winlink (RMS) Systems
>>      BBS 'R:-line' compatibility
>>      BBS 'Pseudo-White Pages'
>> Internet Services:  AX.25 Digipeating (48 ports)  IP Encapsulation
>> Hopcheck IP path tracing
>> RIP-2/-98 Routing Protocol
>> Radio Shortest Path First Protocol (RSPF)
>> Reverse Address Resolution Protocol (RARP)
>> MD5 Authentication
>> Generic termios interface driver
>> Async interface drivers:  AX.25  NET/ROM-TNC  VARA
>> NET/ROM network interface with (NRR) netrom route record support
>> Async IP drivers:  Point-to-Point (PPP)
>> Generic ethernet driver
>> Hardware interface packet tracing (minimal monitor-style trace 
>> available)
>> Linked with (n)curses version 6.4
>> AX.25 UI packet tx/rx
>> Ed ASCII text editor
>> trace file sync feature
>> APRS Services and Igate
>> AMPRnet RIP Updates (Early 2010)
>>
>> _______________________________________________
>> nos-bbs mailing list
>> nos-bbs at lists.tapr.org
>> http://lists.tapr.org/mailman/listinfo/nos-bbs_lists.tapr.org