Bug#903555: ser2net: replies with WONT COM_PORT on DO COM_PORT

2018-08-22 Thread Marc Haber
tags #903555 fixed-upstream confirmed pending thanks

Bug#903555: ser2net: replies with WONT COM_PORT on DO COM_PORT

2018-07-26 Thread Corey Minyard
On 07/11/2018 05:02 AM, Uwe Kleine-König wrote: Package: ser2net Version: 2.10.1-1 Severity: normal Hello, I'm currently working on improving rfc2217-support in microcom and think that ser2net behaves wrong in reply to microcom's improved behaviour. Actually, I realized yesterday working on

Bug#903555: ser2net: replies with WONT COM_PORT on DO COM_PORT

2018-07-11 Thread Marc Haber
tags #903555 confirmed thanks On Wed, Jul 11, 2018 at 01:18:48PM +0200, Uwe Kleine-König wrote: > Looking at the upstream repository this bug was fixed in commit > 59090a089484654e93ea753b87d66a1af37b41b9 two years ago. I will package the new upstream version in due time. Greetings Marc --

Bug#903555: ser2net: replies with WONT COM_PORT on DO COM_PORT

2018-07-11 Thread Uwe Kleine-König
Control: tag -1 + fixed-upstream On Wed, Jul 11, 2018 at 12:02:50PM +0200, Uwe Kleine-König wrote: > I'm currently working on improving rfc2217-support in microcom and think > that ser2net behaves wrong in reply to microcom's improved behaviour. > > When I connect to ser2net and then "say": > >

Bug#903555: ser2net: replies with WONT COM_PORT on DO COM_PORT

2018-07-11 Thread Uwe Kleine-König
Package: ser2net Version: 2.10.1-1 Severity: normal Hello, I'm currently working on improving rfc2217-support in microcom and think that ser2net behaves wrong in reply to microcom's improved behaviour. When I connect to ser2net and then "say": IAC DO COM_PORT (i.e. \xff \xfd \x2c)