Hello,
My google-fu and searching has failed me. I am super new to the world of BBSs and have decided to try running my own. I am running version 318b via
a precompiled Windows build. After running through the wizard and doing a little network configuration I managed to get my BBS running! Yay! I am
able connect with PuTTY (telnet) and have a friend connecting to the
PETSCII ports via telnet on his C64. However, when I attempt to connect
with my Apple II, I get disconnected due to inactivity shortly after connecting.
Looking at the logs (pasted below) it appears that the terminal type my terminal emulator is reporting isn't recognized. I downloaded the source
and am starting to look through it now, but it'll take some time for me to reason through it.
Overall, I think what I'm reading is my terminal is reporting it's type as
a vt100, and since that isn't of type ANSI, PETSCII, or UTF-8 the login module sets my inactive timeout to 0 and I get kicked. I'm able to connect to other BBSs running versions of Synchronet, so I believe it's a configuration problem on my end. Any help would be appreciated.
Client machine: Apple IIe (on the same local network as my BBS server) Terminal Emulator: Telnet65, a part of the IP65 project
Client networking hardware: Uthernet II
Server OS: Windows 7 64-bit
Synchronet Version: 318b (based on download archive filename)
Debug log from Synchronet Control Panel:
7/3 07:33:00p 1528 Telnet connection accepted from: 192.168.1.174 port 51074
7/3 07:33:04p 1528 Telnet Hostname: <no name> [192.168.1.174]
7/3 07:33:04p Node 1 constructor using socket 1528 (settings=8212)
7/3 07:33:04p Node 1 temporary file directory: C:\sbbs\node1\temp\
7/3 07:33:04p Node 1 socket 1528 duplicated as 816
7/3 07:33:04p Node 1 socket 1528 attached to local interface 192.168.1.166 port 23
7/3 07:33:04p Node 1 passthru listen socket 988 opened
7/3 07:33:04p Node 1 passthru socket listening on port 61700
7/3 07:33:04p Node 1 passthru connect socket 784 opened
7/3 07:33:04p Node 1 JavaScript: Creating node runtime: 8388608 bytes
7/3 07:33:04p Node 1 JavaScript: Initializing node context (stack:
16384 bytes)
7/3 07:33:04p Node 1 07:33p Sat Jul 03 2021 Node 1
7/3 07:33:04p Node 1 Telnet <no name> [192.168.1.174]
7/3 07:33:04p Node 1 sending telnet cmd: WILL Echo
7/3 07:33:04p Node 1 sending telnet cmd: WILL Suppress Go Ahead
7/3 07:33:04p Node 1 sending telnet cmd: DO Terminal Type
7/3 07:33:04p Node 1 sending telnet cmd: DO Terminal Speed
7/3 07:33:04p Node 1 sending telnet cmd: DO Send Location
7/3 07:33:04p Node 1 sending telnet cmd: DO Negotiate About Window Size
7/3 07:33:04p Node 1 sending telnet cmd: DO New Environment Option
7/3 07:33:05p Node 1 received telnet cmd: DO Echo
7/3 07:33:05p Node 1 received telnet cmd: DO Suppress Go Ahead
7/3 07:33:05p Node 1 received telnet cmd: WILL Terminal Type
7/3 07:33:05p Node 1 requesting telnet terminal type
7/3 07:33:05p Node 1 received telnet cmd: WON'T Terminal Speed
7/3 07:33:05p Node 1 sending telnet cmd: DON'T Terminal Speed
7/3 07:33:05p Node 1 received telnet cmd: WON'T Send Location
7/3 07:33:05p Node 1 sending telnet cmd: DON'T Send Location
7/3 07:33:05p Node 1 received telnet cmd: WILL Negotiate About Window Size
7/3 07:33:05p Node 1 received telnet sub-negotiation command: Negotiate About Window Size (9 bytes)
7/3 07:33:05p Node 1 received telnet window size: 80x24
7/3 07:33:05p Node 1 received telnet cmd: WON'T New Environment Option
7/3 07:33:05p Node 1 received telnet cmd: WON'T Terminal Speed
7/3 07:33:05p Node 1 received telnet cmd: WON'T Send Location
7/3 07:33:05p Node 1 received telnet sub-negotiation command: Terminal Type (11 bytes)
7/3 07:33:05p Node 1 received telnet terminal type: vt100
7/3 07:33:10p Node 1 terminal type: 80x24 vt100
7/3 07:33:10p Node 1 terminal not detected, reducing inactivity hang-up timeout to 0 seconds
Re: Newbie Struggling to Get Apple II Connectedof
By: Sbushman to All on Sun Jul 04 2021 09:51 pm
Hello,
My google-fu and searching has failed me. I am super new to the world
318bBBSs and have decided to try running my own. I am running version
doing avia
a precompiled Windows build. After running through the wizard and
amlittle network configuration I managed to get my BBS running! Yay! I
connectable connect with PuTTY (telnet) and have a friend connecting to the PETSCII ports via telnet on his C64. However, when I attempt to
mywith my Apple II, I get disconnected due to inactivity shortly after connecting.
Looking at the logs (pasted below) it appears that the terminal type
sourceterminal emulator is reporting isn't recognized. I downloaded the
meand am starting to look through it now, but it'll take some time for
typeto reason through it.
Overall, I think what I'm reading is my terminal is reporting it's
loginas
a vt100, and since that isn't of type ANSI, PETSCII, or UTF-8 the
it's amodule sets my inactive timeout to 0 and I get kicked. I'm able to connect to other BBSs running versions of Synchronet, so I believe
server)configuration problem on my end. Any help would be appreciated.
Client machine: Apple IIe (on the same local network as my BBS
(settings=8212)Terminal Emulator: Telnet65, a part of the IP65 project
Client networking hardware: Uthernet II
Server OS: Windows 7 64-bit
Synchronet Version: 318b (based on download archive filename)
Debug log from Synchronet Control Panel:
7/3 07:33:00p 1528 Telnet connection accepted from: 192.168.1.174 port 51074
7/3 07:33:04p 1528 Telnet Hostname: <no name> [192.168.1.174]
7/3 07:33:04p Node 1 constructor using socket 1528
C:\sbbs\node1\temp\7/3 07:33:04p Node 1 temporary file directory:
bytes7/3 07:33:04p Node 1 socket 1528 duplicated as 816
7/3 07:33:04p Node 1 socket 1528 attached to local interface 192.168.1.166 port 23
7/3 07:33:04p Node 1 passthru listen socket 988 opened
7/3 07:33:04p Node 1 passthru socket listening on port 61700
7/3 07:33:04p Node 1 passthru connect socket 784 opened
7/3 07:33:04p Node 1 JavaScript: Creating node runtime: 8388608
(stack:7/3 07:33:04p Node 1 JavaScript: Initializing node context
Window16384 bytes)
7/3 07:33:04p Node 1 07:33p Sat Jul 03 2021 Node 1
7/3 07:33:04p Node 1 Telnet <no name> [192.168.1.174]
7/3 07:33:04p Node 1 sending telnet cmd: WILL Echo
7/3 07:33:04p Node 1 sending telnet cmd: WILL Suppress Go Ahead
7/3 07:33:04p Node 1 sending telnet cmd: DO Terminal Type
7/3 07:33:04p Node 1 sending telnet cmd: DO Terminal Speed
7/3 07:33:04p Node 1 sending telnet cmd: DO Send Location
7/3 07:33:04p Node 1 sending telnet cmd: DO Negotiate About
OptionSize
7/3 07:33:04p Node 1 sending telnet cmd: DO New Environment
Window7/3 07:33:05p Node 1 received telnet cmd: DO Echo
7/3 07:33:05p Node 1 received telnet cmd: DO Suppress Go Ahead
7/3 07:33:05p Node 1 received telnet cmd: WILL Terminal Type
7/3 07:33:05p Node 1 requesting telnet terminal type
7/3 07:33:05p Node 1 received telnet cmd: WON'T Terminal Speed
7/3 07:33:05p Node 1 sending telnet cmd: DON'T Terminal Speed
7/3 07:33:05p Node 1 received telnet cmd: WON'T Send Location
7/3 07:33:05p Node 1 sending telnet cmd: DON'T Send Location
7/3 07:33:05p Node 1 received telnet cmd: WILL Negotiate About
HankSize
7/3 07:33:05p Node 1 received telnet sub-negotiation command: Negotiate About Window Size (9 bytes)
7/3 07:33:05p Node 1 received telnet window size: 80x24
7/3 07:33:05p Node 1 received telnet cmd: WON'T New Environment Option
7/3 07:33:05p Node 1 received telnet cmd: WON'T Terminal Speed
7/3 07:33:05p Node 1 received telnet cmd: WON'T Send Location
7/3 07:33:05p Node 1 received telnet sub-negotiation command: Terminal Type (11 bytes)
7/3 07:33:05p Node 1 received telnet terminal type: vt100
7/3 07:33:10p Node 1 terminal type: 80x24 vt100
7/3 07:33:10p Node 1 terminal not detected, reducing inactivity hang-up timeout to 0 seconds
This problem was fixed back in March (in exec/login.js). A simple work-around is to just remove the comment (and the semicolon) from the inactive_hangup line in your ctrl/modopts.ini file.
--
digital man
Breaking Bad quote #11:
My apologies to the HR department: Grow tumescent with anticipation. -
Norco, CA WX: 62.6¨F, 87.0% humidity, 0 mph SE wind, 0.00 inchesrain/24hrs
Sysop: | Xerxes |
---|---|
Location: | Azle, Texas |
Users: | 131 |
Nodes: | 10 (0 / 10) |
Uptime: | 85:30:41 |
Calls: | 3,189 |
Calls today: | 0 |
Files: | 195 |
U/L today: |
0 files (0K bytes) |
D/L today: |
0 files (0K bytes) |
Messages: | 366,064 |
Posted today: | 0 |