[Ltsp-discuss] Re: Serial port redirection
Jeffrey Altman wrote: Its not a Kermit bug; If you pass the socket file descriptor to an external program the external program must understand telnet protocol. Otherwise, it can't send the correct data format. No, it *is* a kermit bug. When kermit sends an 0xff character, it needs to escape it per the standard telnet protocol. It's obviously not doing this. -Corey Peter Astrand wrote: Hi. I'm trying to find a generic serial port redirection solution for a Linux terminal server environment. I'd like a solution based on RFC2217. I'm particularly interested in syncing Palm Pilot PDAs. ... ser2net/sredird + Kermit Kermit has built-in RFC2217 support, but it doesn't work for me: --- C-Kermitset host localhost:4911 DNS Lookup... Trying 127.0.0.1... Reverse DNS Lookup... (OK) localhost.localdomain connected on port 4911 C-Kermitset speed 2400 localhost.localdomain:4911, 2400 bps C-Kermitconnect Connecting to host localhost.localdomain:4911 Escape character: Ctrl-\ (ASCII 28, FS): enabled Type the escape character followed by C to get back, or followed by ? to see other options. , Communications disconnect --- Well, this was my fault: I didn't understand how Kermit worked. When using set carrier-watch off, things worked much better. * BUT: When using Kermit as a RFC2217 client for transferring files with ZMODEM, I get Bad CRC pretty much all the time. This happens *both* with the sredird, ser2net and Tactical Softwares Dialout/Server for Windows. The problem seems to go away if I transfer files without 0xff bytes(!) This looks like a Kermit bug to me. I'll guess I have to talk to the Kermit folks about this. * ser2net is totally incompatible with cyclades-serial-client. This is because ser2net interprets RFC2217 a bit differently. sredird sends command 101 as ack for command 1, while ser2net sends 1. RFC2217 is not very explicit about which way is most correct. The ser2net approach looks better to me, but the sredird one is probably more widely used (since Cyclades terminal server uses it, for example.) Probably, RFC2217 software needs to handle both cases. Some more test cases: * minicom + cyclades-serial-client + sredird: Works * pilot-link + cyclades-serial-client + sredird: Does not work (see my previous mail) * pilot-link + cyclades-serial-client + Dialout/Server: Works perfectly. * photopc + cyclades-serial-client + sredird: Does not work. I get excessive retries. * photopc + cyclades-serial-client + Dialout/Server: Works perfectly. So, the combination of sredird + cyclades-serial-client does not work correctly. Also, I tried running Contract I.T. Communications Analyzer on a Windows machine. One physical port was connected to a Linux machine via a null modem cable. This machine ran sredird. One virtual port was created with Tactical Softwares Dialout software, connecting to sredird. Communications Analyzer indicated 90% Byte Error Rate! Since cyclades-serial-client was not involved in this test, I would say that it looks like sredird is doing something wrong. If *anyone* has any ideas of how to solve these problem, please let me know. I'm starting to run out of time and patience... (Which mailing list is best for this topic?) --- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278alloc_id=3371op=click _ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net
[Ltsp-discuss] Re: Serial port redirection
Corey Minyard wrote: Jeffrey Altman wrote: Its not a Kermit bug; If you pass the socket file descriptor to an external program the external program must understand telnet protocol. Otherwise, it can't send the correct data format. No, it *is* a kermit bug. When kermit sends an 0xff character, it needs to escape it per the standard telnet protocol. It's obviously not doing this. -Corey I agree, the IAC must be quoted. The problem is that when an external protocol handler is executed as a child process, Kermit is suspended and the child process has complete control over the socket file descriptor. Kermit is not sitting between the external protocol and the host. Some versions of sz have a command line flag to handle this situation such that IAC (0xff) are not sent but are instead escaped within the zmodem protocol. Jeffrey Altman smime.p7s Description: S/MIME Cryptographic Signature
[Ltsp-discuss] Re: Serial port redirection
Jeffrey Altman wrote: Peter Astrand wrote: * ser2net is totally incompatible with cyclades-serial-client. This is because ser2net interprets RFC2217 a bit differently. sredird sends command 101 as ack for command 1, while ser2net sends 1. RFC2217 is not very explicit about which way is most correct. The ser2net approach looks better to me, but the sredird one is probably more widely used (since Cyclades terminal server uses it, for example.) Probably, RFC2217 software needs to handle both cases. ser2net is wrong Umm, no. Cyclades and sredird are wrong. And it's pretty clear. From RFC2217: Client to Access Server Access Server to Client SIGNATUREtext text SET-BAUDRATE1 101 SET-DATASIZE2 102 SET-PARITY 3 103 SET-STOPSIZE4 104 SET-CONTROL 5 105 NOTIFY-LINESTATE6 106 NOTIFY-MODEMSTATE 7 107 FLOWCONTROL-SUSPEND 8 108 FLOWCONTROL-RESUME 9 109 SET-LINESTATE-MASK 10 110 SET-MODEMSTATE-MASK11 111 PURGE-DATA 12 112 Discussion: As initially proposed, com port configuration commands are only sent from the client to the access server. There is no current vision that the access server would initiate the use of a com port configuration command, only the notify commands. However, to allow for access server initiated com port configurations different command values have been established. That last sentence of the discussion says it. The 1xx commands are there to allow the access server to *initiate* com port configuration changes. Not to ack the changes. Unless you can point me to something in the manual to say that I am wrong. I am willing to change this in the spirit of keeping things consistent, though. -Corey --- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278alloc_id=3371op=click _ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net
[Ltsp-discuss] Re: Serial port redirection
Ah, I missed that. Ideally, something (i would think kermit) should sit between the program and the socket to make it transparent. But yes, I see what you are saying. Thanks, -Corey Jeffrey Altman wrote: Corey Minyard wrote: Jeffrey Altman wrote: Its not a Kermit bug; If you pass the socket file descriptor to an external program the external program must understand telnet protocol. Otherwise, it can't send the correct data format. No, it *is* a kermit bug. When kermit sends an 0xff character, it needs to escape it per the standard telnet protocol. It's obviously not doing this. -Corey I agree, the IAC must be quoted. The problem is that when an external protocol handler is executed as a child process, Kermit is suspended and the child process has complete control over the socket file descriptor. Kermit is not sitting between the external protocol and the host. Some versions of sz have a command line flag to handle this situation such that IAC (0xff) are not sent but are instead escaped within the zmodem protocol. Jeffrey Altman --- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278alloc_id=3371op=click _ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net
[Ltsp-discuss] Re: Serial port redirection
I've attached a ser2net patch for this. Could you try it out? -Corey Peter Astrand wrote: * ser2net is totally incompatible with cyclades-serial-client. This is because ser2net interprets RFC2217 a bit differently. sredird sends command 101 as ack for command 1, while ser2net sends 1. RFC2217 is not very explicit about which way is most correct. The ser2net approach looks better to me, but the sredird one is probably more widely used (since Cyclades terminal server uses it, for example.) Probably, RFC2217 software needs to handle both cases. ? .libs ? Makefile ? Makefile.in ? aclocal.m4 ? config.cache ? config.log ? config.status ? configure ? libtool ? ser2net ? .deps/controller.P ? .deps/dataxfer.P ? .deps/devcfg.P ? .deps/readconfig.P ? .deps/selector.P ? .deps/ser2net.P ? .deps/telnet.P ? .deps/utils.P Index: ChangeLog === RCS file: /cvsroot/ser2net/ser2net/ChangeLog,v retrieving revision 1.36 diff -u -r1.36 ChangeLog --- ChangeLog 14 Oct 2003 20:52:13 - 1.36 +++ ChangeLog 4 Dec 2003 17:31:04 - @@ -1,4 +1,11 @@ +2003-12-04 Corey Minyard [EMAIL PROTECTED] + + * dataxfer.c: Have the telnet option responses use the 1xx + responses to the com port control options. I believe this is + wrong, but it is consistent with other products already in the + field. + 2003-10-14 Corey Minyard [EMAIL PROTECTED] * configure.in: Moved to version 2.0. Index: dataxfer.c === RCS file: /cvsroot/ser2net/ser2net/dataxfer.c,v retrieving revision 1.28 diff -u -r1.28 dataxfer.c --- dataxfer.c 14 Oct 2003 20:52:13 - 1.28 +++ dataxfer.c 4 Dec 2003 17:31:04 - @@ -2000,7 +2000,7 @@ } get_rate_from_baud_rate(val, val); outopt[0] = 44; - outopt[1] = 1; + outopt[1] = 101; *((uint32_t *) (outopt+2)) = htonl(val); telnet_send_option(port-tn_data, outopt, 6); break; @@ -2030,7 +2030,7 @@ } } outopt[0] = 44; - outopt[1] = 2; + outopt[1] = 102; outopt[2] = val; telnet_send_option(port-tn_data, outopt, 3); break; @@ -2061,7 +2061,7 @@ val = 1; /* NONE */ } outopt[0] = 44; - outopt[1] = 3; + outopt[1] = 103; outopt[2] = val; telnet_send_option(port-tn_data, outopt, 3); break; @@ -2088,7 +2088,7 @@ val = 1; /* 1 stop bit. */ } outopt[0] = 44; - outopt[1] = 4; + outopt[1] = 104; outopt[2] = val; telnet_send_option(port-tn_data, outopt, 3); break; @@ -2210,7 +2210,7 @@ } outopt[0] = 44; - outopt[1] = 5; + outopt[1] = 105; outopt[2] = val; telnet_send_option(port-tn_data, outopt, 3); break;
[Ltsp-discuss] Re: Serial port redirection
The reality is RFC is experimental and not authoritative. The only thing that really counts is what Cisco actually shipped in their IOS implementation. Lucky me I actually have a terminal server that implements it. If you look at the C-Kermit sources you will see that the client is written to accept both values from the server. You will also find that Cisco does not send the baudrates as specified in the RFC but instead uses an enumeration. With regards to the comment about the use of separate codes to indicate direction, this was written without a good understanding of the Telnet Option negotiation. The reality is that there is no need for a telnet protocol option to have separate commands for each direction as the option itself must be negotiated separately in each direction. Therefore, there is no possibility of confusion. Jeffrey Altman Corey Minyard wrote: Jeffrey Altman wrote: Peter Astrand wrote: * ser2net is totally incompatible with cyclades-serial-client. This is because ser2net interprets RFC2217 a bit differently. sredird sends command 101 as ack for command 1, while ser2net sends 1. RFC2217 is not very explicit about which way is most correct. The ser2net approach looks better to me, but the sredird one is probably more widely used (since Cyclades terminal server uses it, for example.) Probably, RFC2217 software needs to handle both cases. ser2net is wrong Umm, no. Cyclades and sredird are wrong. And it's pretty clear. From RFC2217: Client to Access Server Access Server to Client SIGNATUREtext text SET-BAUDRATE1 101 SET-DATASIZE2 102 SET-PARITY 3 103 SET-STOPSIZE4 104 SET-CONTROL 5 105 NOTIFY-LINESTATE6 106 NOTIFY-MODEMSTATE 7 107 FLOWCONTROL-SUSPEND 8 108 FLOWCONTROL-RESUME 9 109 SET-LINESTATE-MASK 10 110 SET-MODEMSTATE-MASK11 111 PURGE-DATA 12 112 Discussion: As initially proposed, com port configuration commands are only sent from the client to the access server. There is no current vision that the access server would initiate the use of a com port configuration command, only the notify commands. However, to allow for access server initiated com port configurations different command values have been established. That last sentence of the discussion says it. The 1xx commands are there to allow the access server to *initiate* com port configuration changes. Not to ack the changes. Unless you can point me to something in the manual to say that I am wrong. I am willing to change this in the spirit of keeping things consistent, though. -Corey smime.p7s Description: S/MIME Cryptographic Signature
[Ltsp-discuss] Re: Serial port redirection
Ideally that would be true. However, the mechanisms for doing so are not portable to all platforms on which C-Kermit still compiles. Please remember that C-Kermit works on platforms that existed before select() was invented. Jeffrey Altman Corey Minyard wrote: Ah, I missed that. Ideally, something (i would think kermit) should sit between the program and the socket to make it transparent. But yes, I see what you are saying. Thanks, -Corey smime.p7s Description: S/MIME Cryptographic Signature
[Ltsp-discuss] Re: Serial port redirection
Jeffrey Altman wrote: The reality is RFC is experimental and not authoritative. The only thing that really counts is what Cisco actually shipped in their IOS implementation. Lucky me I actually have a terminal server that implements it. If you look at the C-Kermit sources you will see that the client is written to accept both values from the server. You will also find that Cisco does not send the baudrates as specified in the RFC but instead uses an enumeration. True. But if I had been lucky and had a terminal server, I would not have written ser2net :). So Cisco uses a enumeration? Do you think it is possible to make them compatible and do both in ser2net, or is it a non-issue? With regards to the comment about the use of separate codes to indicate direction, this was written without a good understanding of the Telnet Option negotiation. The reality is that there is no need for a telnet protocol option to have separate commands for each direction as the option itself must be negotiated separately in each direction. Therefore, there is no possibility of confusion. Also true. It seemed silly to have it this way. -Corey --- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278alloc_id=3371op=click _ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net
[Ltsp-discuss] Re: Serial port redirection
It would be fairly trivial to write such a program, though. You could pass it the actual program you want, and it could make the protocol transparent. -Corey Jeffrey Altman wrote: Ideally that would be true. However, the mechanisms for doing so are not portable to all platforms on which C-Kermit still compiles. Please remember that C-Kermit works on platforms that existed before select() was invented. Jeffrey Altman Corey Minyard wrote: Ah, I missed that. Ideally, something (i would think kermit) should sit between the program and the socket to make it transparent. But yes, I see what you are saying. Thanks, -Corey --- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278alloc_id=3371op=click _ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net
[Ltsp-discuss] Re: Serial port redirection
Corey Minyard wrote: Jeffrey Altman wrote: The reality is RFC is experimental and not authoritative. The only thing that really counts is what Cisco actually shipped in their IOS implementation. Lucky me I actually have a terminal server that implements it. If you look at the C-Kermit sources you will see that the client is written to accept both values from the server. You will also find that Cisco does not send the baudrates as specified in the RFC but instead uses an enumeration. True. But if I had been lucky and had a terminal server, I would not have written ser2net :). So Cisco uses a enumeration? Do you think it is possible to make them compatible and do both in ser2net, or is it a non-issue? Clients can use heuristics to determine which should be used. Servers must choose one; but I would make a configurable option. (The clock is off by one day 4 hours and 12 minutes. This causes your e-mail to get lost way down in my queue.) smime.p7s Description: S/MIME Cryptographic Signature
[Ltsp-discuss] Re: Serial port redirection
That would not help you. Its not simply a question of mapping escaping the IAC. You must be prepared to process and respond to telnet option negotiations during the file transfer. This is especially true with the Remote Com Port option since the host is likely to be sending flow control and signal status messages to the client. This change really does need to be added to C-Kermit. Unfortunately, as I am no longer employed by Columbia to work on Kermit this is very very very low on my stack. Jeffrey Altman Corey Minyard wrote: It would be fairly trivial to write such a program, though. You could pass it the actual program you want, and it could make the protocol transparent. -Corey smime.p7s Description: S/MIME Cryptographic Signature
[Ltsp-discuss] Re: Serial port redirection
Hi. I'm trying to find a generic serial port redirection solution for a Linux terminal server environment. I'd like a solution based on RFC2217. I'm particularly interested in syncing Palm Pilot PDAs. ... ser2net/sredird + Kermit Kermit has built-in RFC2217 support, but it doesn't work for me: --- C-Kermitset host localhost:4911 DNS Lookup... Trying 127.0.0.1... Reverse DNS Lookup... (OK) localhost.localdomain connected on port 4911 C-Kermitset speed 2400 localhost.localdomain:4911, 2400 bps C-Kermitconnect Connecting to host localhost.localdomain:4911 Escape character: Ctrl-\ (ASCII 28, FS): enabled Type the escape character followed by C to get back, or followed by ? to see other options. , Communications disconnect --- Well, this was my fault: I didn't understand how Kermit worked. When using set carrier-watch off, things worked much better. * BUT: When using Kermit as a RFC2217 client for transferring files with ZMODEM, I get Bad CRC pretty much all the time. This happens *both* with the sredird, ser2net and Tactical Softwares Dialout/Server for Windows. The problem seems to go away if I transfer files without 0xff bytes(!) This looks like a Kermit bug to me. I'll guess I have to talk to the Kermit folks about this. * ser2net is totally incompatible with cyclades-serial-client. This is because ser2net interprets RFC2217 a bit differently. sredird sends command 101 as ack for command 1, while ser2net sends 1. RFC2217 is not very explicit about which way is most correct. The ser2net approach looks better to me, but the sredird one is probably more widely used (since Cyclades terminal server uses it, for example.) Probably, RFC2217 software needs to handle both cases. Some more test cases: * minicom + cyclades-serial-client + sredird: Works * pilot-link + cyclades-serial-client + sredird: Does not work (see my previous mail) * pilot-link + cyclades-serial-client + Dialout/Server: Works perfectly. * photopc + cyclades-serial-client + sredird: Does not work. I get excessive retries. * photopc + cyclades-serial-client + Dialout/Server: Works perfectly. So, the combination of sredird + cyclades-serial-client does not work correctly. Also, I tried running Contract I.T. Communications Analyzer on a Windows machine. One physical port was connected to a Linux machine via a null modem cable. This machine ran sredird. One virtual port was created with Tactical Softwares Dialout software, connecting to sredird. Communications Analyzer indicated 90% Byte Error Rate! Since cyclades-serial-client was not involved in this test, I would say that it looks like sredird is doing something wrong. If *anyone* has any ideas of how to solve these problem, please let me know. I'm starting to run out of time and patience... (Which mailing list is best for this topic?) -- Peter Åstrand www.thinlinc.com Cendio www.cendio.se Teknikringen 3 Phone: +46-13-21 46 00 583 30 Linköping --- This SF.net email is sponsored by OSDN's Audience Survey. Help shape OSDN's sites and tell us what you think. Take this five minute survey and you could win a $250 Gift Certificate. http://www.wrgsurveys.com/2003/osdntech03.php?site=8 _ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net
[Ltsp-discuss] Re: Serial port redirection
Its not a Kermit bug; If you pass the socket file descriptor to an external program the external program must understand telnet protocol. Otherwise, it can't send the correct data format. Peter Astrand wrote: Hi. I'm trying to find a generic serial port redirection solution for a Linux terminal server environment. I'd like a solution based on RFC2217. I'm particularly interested in syncing Palm Pilot PDAs. ... ser2net/sredird + Kermit Kermit has built-in RFC2217 support, but it doesn't work for me: --- C-Kermitset host localhost:4911 DNS Lookup... Trying 127.0.0.1... Reverse DNS Lookup... (OK) localhost.localdomain connected on port 4911 C-Kermitset speed 2400 localhost.localdomain:4911, 2400 bps C-Kermitconnect Connecting to host localhost.localdomain:4911 Escape character: Ctrl-\ (ASCII 28, FS): enabled Type the escape character followed by C to get back, or followed by ? to see other options. , Communications disconnect --- Well, this was my fault: I didn't understand how Kermit worked. When using set carrier-watch off, things worked much better. * BUT: When using Kermit as a RFC2217 client for transferring files with ZMODEM, I get Bad CRC pretty much all the time. This happens *both* with the sredird, ser2net and Tactical Softwares Dialout/Server for Windows. The problem seems to go away if I transfer files without 0xff bytes(!) This looks like a Kermit bug to me. I'll guess I have to talk to the Kermit folks about this. * ser2net is totally incompatible with cyclades-serial-client. This is because ser2net interprets RFC2217 a bit differently. sredird sends command 101 as ack for command 1, while ser2net sends 1. RFC2217 is not very explicit about which way is most correct. The ser2net approach looks better to me, but the sredird one is probably more widely used (since Cyclades terminal server uses it, for example.) Probably, RFC2217 software needs to handle both cases. Some more test cases: * minicom + cyclades-serial-client + sredird: Works * pilot-link + cyclades-serial-client + sredird: Does not work (see my previous mail) * pilot-link + cyclades-serial-client + Dialout/Server: Works perfectly. * photopc + cyclades-serial-client + sredird: Does not work. I get excessive retries. * photopc + cyclades-serial-client + Dialout/Server: Works perfectly. So, the combination of sredird + cyclades-serial-client does not work correctly. Also, I tried running Contract I.T. Communications Analyzer on a Windows machine. One physical port was connected to a Linux machine via a null modem cable. This machine ran sredird. One virtual port was created with Tactical Softwares Dialout software, connecting to sredird. Communications Analyzer indicated 90% Byte Error Rate! Since cyclades-serial-client was not involved in this test, I would say that it looks like sredird is doing something wrong. If *anyone* has any ideas of how to solve these problem, please let me know. I'm starting to run out of time and patience... (Which mailing list is best for this topic?) smime.p7s Description: S/MIME Cryptographic Signature
[Ltsp-discuss] Re: Serial port redirection
Peter Astrand wrote: * ser2net is totally incompatible with cyclades-serial-client. This is because ser2net interprets RFC2217 a bit differently. sredird sends command 101 as ack for command 1, while ser2net sends 1. RFC2217 is not very explicit about which way is most correct. The ser2net approach looks better to me, but the sredird one is probably more widely used (since Cyclades terminal server uses it, for example.) Probably, RFC2217 software needs to handle both cases. ser2net is wrong smime.p7s Description: S/MIME Cryptographic Signature
Re: [Ltsp-discuss] Re: Serial port redirection
On Wed, 3 Dec 2003, alvin wrote: have you taken a look at comserv. I ran it up and did a few simple tests on my Xyplex terminal server. It did not do what I wanted and I put it aside for later use. http://www.bsdhome.com/comserv/ Also, there is a package called termpkg (http://www.linuxlots.com/~termpkg/). The problem with all these packages are that they only uses simple pseduo ttys. This means that ioctls/tcsetattr syscalls won't work (at least not with Linux 2.4; I've heard that 2.6 fixes this). To be able to interpret ioctl/tcsetattr correctly, one needs to use a LD_PRELOAD:ed library. It's not pretty, but this is the best solution I've found for current Linux distros. cyclades-serial-client is the only package I've found which uses this approach. -- Peter Åstrand www.thinlinc.com Cendio www.cendio.se Teknikringen 3 Phone: +46-13-21 46 00 583 30 Linköping --- This SF.net email is sponsored by OSDN's Audience Survey. Help shape OSDN's sites and tell us what you think. Take this five minute survey and you could win a $250 Gift Certificate. http://www.wrgsurveys.com/2003/osdntech03.php?site=8 _ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net
Re: [Ltsp-discuss] Re: Serial port redirection
Peter Astrand wrote: Hi. I'm trying to find a generic serial port redirection solution for a Linux terminal server environment. I'd like a solution based on RFC2217. I'm particularly interested in syncing Palm Pilot PDAs. ... ser2net/sredird + Kermit Kermit has built-in RFC2217 support, but it doesn't work for me: --- C-Kermitset host localhost:4911 DNS Lookup... Trying 127.0.0.1... Reverse DNS Lookup... (OK) localhost.localdomain connected on port 4911 C-Kermitset speed 2400 localhost.localdomain:4911, 2400 bps C-Kermitconnect Connecting to host localhost.localdomain:4911 Escape character: Ctrl-\ (ASCII 28, FS): enabled Type the escape character followed by C to get back, or followed by ? to see other options. , Communications disconnect --- Well, this was my fault: I didn't understand how Kermit worked. When using set carrier-watch off, things worked much better. * BUT: When using Kermit as a RFC2217 client for transferring files with ZMODEM, I get Bad CRC pretty much all the time. This happens *both* with the sredird, ser2net and Tactical Softwares Dialout/Server for Windows. The problem seems to go away if I transfer files without 0xff bytes(!) This looks like a Kermit bug to me. I'll guess I have to talk to the Kermit folks about this. * ser2net is totally incompatible with cyclades-serial-client. This is because ser2net interprets RFC2217 a bit differently. sredird sends command 101 as ack for command 1, while ser2net sends 1. RFC2217 is not very explicit about which way is most correct. The ser2net approach looks better to me, but the sredird one is probably more widely used (since Cyclades terminal server uses it, for example.) Probably, RFC2217 software needs to handle both cases. Some more test cases: * minicom + cyclades-serial-client + sredird: Works * pilot-link + cyclades-serial-client + sredird: Does not work (see my previous mail) * pilot-link + cyclades-serial-client + Dialout/Server: Works perfectly. * photopc + cyclades-serial-client + sredird: Does not work. I get excessive retries. * photopc + cyclades-serial-client + Dialout/Server: Works perfectly. So, the combination of sredird + cyclades-serial-client does not work correctly. Also, I tried running Contract I.T. Communications Analyzer on a Windows machine. One physical port was connected to a Linux machine via a null modem cable. This machine ran sredird. One virtual port was created with Tactical Softwares Dialout software, connecting to sredird. Communications Analyzer indicated 90% Byte Error Rate! Since cyclades-serial-client was not involved in this test, I would say that it looks like sredird is doing something wrong. If *anyone* has any ideas of how to solve these problem, please let me know. I'm starting to run out of time and patience... (Which mailing list is best for this topic?) have you taken a look at comserv. I ran it up and did a few simple tests on my Xyplex terminal server. It did not do what I wanted and I put it aside for later use. http://www.bsdhome.com/comserv/ --- This SF.net email is sponsored by OSDN's Audience Survey. Help shape OSDN's sites and tell us what you think. Take this five minute survey and you could win a $250 Gift Certificate. http://www.wrgsurveys.com/2003/osdntech03.php?site=8 _ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net
