| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | Re: syncterm |
Hi Rob,
Rob Swindell wrote to Michiel Broek:
RS> > The one from a week to two weeks ago? Not a very recent one.
RS>
RS> From a few days ago. It must have gotten lost (?). Here's a re-post:
Indeed, this one I haven't seen.
RS>
RS>
-------------------------------------8<------------------------------------
RS> > Hi Rob,
RS> >
RS> > I got some things figured out. Your bbs puts the telnet connection in
RS> binary
RS> > mode. My bbs runs from inetd and doesn't put the telnet connection into
RS> > binary mode.
RS>
RS> Ah, that's a good clue. Synchronet puts both the send and receive channels
RS> into
RS> binary mode before a file transfer (and restores them after).
RS>
RS> And indeed, most Telnet clients will do the same.
RS>
RS> > Some terminal programs put the telnet connection in binary mode, but
RS> > syncterm does not.
RS>
RS> Yes, an oversight on Stephen and mine's part. Since we mostly test with
RS> Synchronet BBSes, it hasn't been an issue.
I can imagine that.
RS> > I experimented with minicom over modemu, and with some switches you can
RS> put
RS> > modemeu to force the telnet connection into binary mode or not. If I
RS> don't
RS> > set modemu binary then I get the same problems as syncterm has.
RS> >
RS> > I tried to put the connection into binary mode but that doesn't work
RS> because
RS> > in.telnetd sits between mbsebbs and the internet.
RS> >
RS> > My guess is that if syncterm sets binary mode most or all problems will
RS> be
RS> > fixed. Could you give me some ideas where I best could make the changes
RS> in
RS> > the syncterm source to try this?
RS>
RS> I went ahead and made those changes, so if you cvs update and rebuild (or
RS> get
RS> an updated binary from syncterm.bbsdev.net in a few days), you should be
RS> able
RS> to test it out. If you have telnet command logging enabled, you should see
RS> them
RS> in the SyncTerm log file output as well.
RS>
RS> > If that works then the next plan could be that I write my own telnetd,
RS> or
RS> > use some other way to answer the telnet connections.
RS>
RS> That may not be necessary if all Telnet clients (or at least the ones you
RS> plan
RS> to be compatible with) request binary mode (for both transmit and
RS> receive).
Most that are being used now do, so there is no rush for me anymore.
RS>
-------------------------------------8<------------------------------------
RS>
RS> > RS> > I also found that it doesn't harm that both the
server and the
RS> client
RS> > RS> put
RS> > RS> > the connection into binary mode.
RS> > RS>
RS> > RS> That's correct. And for clarification a Telnet
connection can have
RS> binar
RS> > RS> mode
RS> > RS> enabled in either (or both) directions.
RS> >
RS> > I think both directions must be set, but I mean setting it twice
RS> (server and
RS> > client side) doesn't harm.
RS>
RS> Yup, gotcha. Let me know how the SyncTerm update works for ya.
Perfect, and on the lan very fast transfers.
RS> > I think both directions must be set, but I mean setting it twice
Greetings, Michiel Broek
Email: mbse{at}mbse.dds.nl
Fidonet: Michiel Broek at 2:280/2802
... There's one in every car... You'll see.
--- MBSE BBS v0.83.16 (GNU/Linux-i386)
* Origin: MBSE Linux BBS. Made in the Netherlands (2:280/2802)SEEN-BY: 633/267 270 5030/786 @PATH: 280/2802 5003 2432/200 774/605 123/500 106/2000 633/267 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.