https://osmocom.org/https://osmocom.org/favicon.ico?16647414092020-01-02T22:46:45ZOpen Source Mobile CommunicationsBBS-Revival - Feature #4341: setup for telnet access to legacy BBS software which doesn't have telnet/tcp supporthttps://osmocom.org/issues/4341?journal_id=169802020-01-02T22:46:45Zkeith
<ul></ul><p>laforge wrote:</p>
<blockquote>
<p>In case of a <em>telnet server</em>, that server then would also have to implement something like AT command emulation, so the DOS applications think they're talking to a modem with RING/ATA/CONNECT/...</p>
</blockquote>
<p>Is that what tcpser does?</p> BBS-Revival - Feature #4341: setup for telnet access to legacy BBS software which doesn't have telnet/tcp supporthttps://osmocom.org/issues/4341?journal_id=169812020-01-03T00:35:26Zkeith
<ul></ul><p>UPDATE: seems to have potential to work...</p>
<p>I'm running FRONT DOOR and X00 in dosemu with <br />$_com2 = "/dev/tnt0" in /etc/dosemu/dosemu.conf</p>
<p>Then tcpser -d /dev/tnt1</p>
<p>FD initialises the "modem" fine, and when I telnet to localhost 6400, I get RING, FD sends ATA, tcpser sends back CONNECT 38400, and FD says Carrier Detected. So far nothing else happens there. I think FD is waiting for a signal for a fido mailer to id itself, or for the dialling in user to press some key that I can't remember what it is, what's weird is I'm not seeing anything from FD on the com port after carrier detected and it doesn't seem to be receiving. <br />If I tell FD to hang up, the AT sequence works fine.</p>
<p>I can see all I type in tcpser's trace output. <br />Maybe something to do with the fossil, I'll play with locked baud rate..</p> BBS-Revival - Feature #4341: setup for telnet access to legacy BBS software which doesn't have telnet/tcp supporthttps://osmocom.org/issues/4341?journal_id=169842020-01-04T00:10:54Zkeith
<ul></ul><p>It seems that FrontDoor does not like the CONNECT 38400 coming "immediately" after DCD going high.</p>
<p>I added a sleep(1) and now it works.</p>
<p></code></pre></p>
<pre><code class="diff syntaxhl"><span class="gh">diff --git a/src/modem_core.c b/src/modem_core.c
index 222f58e..26c8135 100644
</span><span class="gd">--- a/src/modem_core.c
</span><span class="gi">+++ b/src/modem_core.c
</span><span class="p">@@ -243,6 +243,7 @@</span> int mdm_answer(modem_config *cfg)
cfg->conn_type = MDM_CONN_INCOMING;
mdm_off_hook(cfg);
mdm_set_control_lines(cfg);
<span class="gi">+ sleep(1);
</span> mdm_print_speed(cfg);
}
else if (cfg->conn_type == MDM_CONN_INCOMING) {
</code></pre>
<p>(this version): <a class="external" href="https://github.com/FozzTexx/tcpser">https://github.com/FozzTexx/tcpser</a></p>
<p>tcpser also works nicely the other way round so that one can use a terminal comms program to telnet to the BBS.</p>
<pre><code>tcpser -d /dev/tnt2 -n111=localhost:6400 -p 2323 -s 38400</code></pre>
<pre><code>minicom -D /dev/tnt3 -c on -b38400</code></pre> BBS-Revival - Feature #4341: setup for telnet access to legacy BBS software which doesn't have telnet/tcp supporthttps://osmocom.org/issues/4341?journal_id=249952022-10-03T12:09:44Zlaforge
<ul><li><strong>Subject</strong> changed from <i>setup for telnet access to legacy BBSs</i> to <i>setup for telnet access to legacy BBS software which doesn't have telnet/tcp support</i></li></ul>