Hi Peter, if you remember, i wrote you some time ago for a question about using cyclades-serial-client in conjuction with sercd. Thanx again for your help at that time. Now my company bought a CISCO AS5350, and that device will be used in my project. To be more precise, we want to use it from the linux client by means of the cyclades-serial-client. As i said, everythings worked for me until we used the sercd as server, and we were confident to be compliant also with the Cisco AS as long as they both use RFC2217. But the first when i tried to connect the cyclades-ser-cli to the CISCO AS i discovered that the solution doesn't work anymore. I tried to look in the log, the code and around the web (reaching mostly content from you) and now i think that there are some difference on the RFC2217 implementation. First of all, speed : the Cisco (as also i read in a newsgroup thread) report speed not as it receives it. Other differences: command-notification sequence: the cyclades-ser-cli blocks waiting for a response from the server, but in the case of SET_MODEMSTATE_MASK and SET_LINESTATE_MASK the Cisco doesn't send any notifycation back. I modified the code ignoring the speed sent back by the Cisco and making the two commands not blocking, but still it doesnt'work. Have you ever tried a CISCO AS as a server form cyclades-serial-client? Do you now what are the big differences between it and sercd? Con you help me in some manner to make cyclades-serial-client work also with CISCO AS? Best Regards and thanx a lot in advance Francesco Ciacca
Now my company bought a CISCO AS5350, and that device will be used in my project. To be more precise, we want to use it from the linux client by means of the cyclades-serial-client. As i said, everythings worked for me until we used the sercd as server, and we were confident to be compliant also with the Cisco AS as long as they both use RFC2217. But the first when i tried to connect the cyclades-ser-cli to the CISCO AS i discovered that the solution doesn't work anymore. I tried to look in the log, the code and around the web (reaching mostly content from you) and now i think that there are some difference on the RFC2217 implementation.
Yes, I've heard that Cisco is not really 2217-compliant. Take a look at http://www.mail-archive.com/ltsp-discuss@lists.sourceforge.net/msg16322.html:
"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."
First of all, speed : the Cisco (as also i read in a newsgroup thread) report speed not as it receives it.
Probably, it accepts both formats as input, but always reports it's canonical form back to the client. Is it the enumeration-form that gets returned?
cyclades-serial-client doesn't support the enumeration-form, as far as I know. It shouldn't be very hard to add such support, though.
Other differences: command-notification sequence: the cyclades-ser-cli blocks waiting for a response from the server, but in the case of SET_MODEMSTATE_MASK and SET_LINESTATE_MASK the Cisco doesn't send any notifycation back. I modified the code ignoring the speed sent back by the Cisco and making the two commands not blocking, but still it doesnt'work.
Never heard of this problem.
Have you ever tried a CISCO AS as a server form cyclades-serial-client? Do you now what are the big differences between it and sercd? Con you help me in some manner to make cyclades-serial-client work also with CISCO AS?
I have no experience with Cisco AS, and haven't access to any Cisco hardware. So, I probably can't help. I'll be glad to accept patches, however, if you find a solution.
Hi Peter, i made some minor modification to your software to make it works in conjuction of a CISCO AS server, which is , as you said before, not really RFC2217-compliant. Beside the enumeration-instead-of-speed issue there were some protocol mismatch that i fix with some workaround. In any case now it works quite smoothly with the CISCO AS, and for example (which actually was my main target) now i can use it to setup a ppp link over the emulated serial. So now i want to know if u are interested in my modifications (that I have to publish because the license, i suppose...) , because my modifications may breaks the actual sercd or Cyclades compatibility... Let me know... On Sunday 05 September 2004 21:41, you wrote:
Now my company bought a CISCO AS5350, and that device will be used in my project. To be more precise, we want to use it from the linux client by means of the cyclades-serial-client. As i said, everythings worked for me until we used the sercd as server, and we were confident to be compliant also with the Cisco AS as long as they both use RFC2217. But the first when i tried to connect the cyclades-ser-cli to the CISCO AS i discovered that the solution doesn't work anymore. I tried to look in the log, the code and around the web (reaching mostly content from you) and now i think that there are some difference on the RFC2217 implementation.
Yes, I've heard that Cisco is not really 2217-compliant. Take a look at http://www.mail-archive.com/ltsp-discuss@lists.sourceforge.net/msg16322.htm l:
"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."
First of all, speed : the Cisco (as also i read in a newsgroup thread) report speed not as it receives it.
Probably, it accepts both formats as input, but always reports it's canonical form back to the client. Is it the enumeration-form that gets returned?
cyclades-serial-client doesn't support the enumeration-form, as far as I know. It shouldn't be very hard to add such support, though.
Other differences: command-notification sequence: the cyclades-ser-cli blocks waiting for a response from the server, but in the case of SET_MODEMSTATE_MASK and SET_LINESTATE_MASK the Cisco doesn't send any notifycation back. I modified the code ignoring the speed sent back by the Cisco and making the two commands not blocking, but still it doesnt'work.
Never heard of this problem.
Have you ever tried a CISCO AS as a server form cyclades-serial-client? Do you now what are the big differences between it and sercd? Con you help me in some manner to make cyclades-serial-client work also with CISCO AS?
I have no experience with Cisco AS, and haven't access to any Cisco hardware. So, I probably can't help. I'll be glad to accept patches, however, if you find a solution.
Hi Peter, i made some minor modification to your software to make it works in conjuction of a CISCO AS server, which is , as you said before, not really RFC2217-compliant. Beside the enumeration-instead-of-speed issue there were some protocol mismatch that i fix with some workaround. In any case now it works quite smoothly with the CISCO AS, and for example (which actually was my main target) now i can use it to setup a ppp link over the emulated serial. So now i want to know if u are interested in my modifications (that I have to publish because the license, i suppose...) , because my modifications may
Yes, this sounds very interesting. Send the modifications either directly to the list, or directly to me.
-
Francesco Ciacca (Consultant) -
Peter Astrand -
Peter Åstrand