Re: ACK char issue

2020-08-20 Thread Dro Ghazarian
I forgot to mention that as an example if we turnoff the bell sound by setting vbell in screenrc, my incoming packet would not receive the bell character anymore, which means that the screen terminal is not printing out the bell character. if vbell is removed , then I can see the bell character in

Re: ACK char issue

2020-08-20 Thread Dro Ghazarian
Hi David, screenlog.0 contains the ack characters, which if I cat -v the log file I'll see ^FX^F^M. I know that if I pipe the output of printf to cat -v or redirect it a file it will have the ack character, but the incoming packet being logged by putty or any other ssh tool would not have the ack

Re: ACK char issue

2020-08-20 Thread david kerns
if you do this: screen -L printf "\x6X\x6\n" exit then look at the screenlog.0 file, does it contain your ACK ? On Tue, Aug 18, 2020 at 11:47 PM Dro Ghazarian wrote: > Hi David, > Thank you for your quick reply. I believe I did not explain the > problem correctly. I do not want to see th

Re: ACK char issue

2020-08-18 Thread Dro Ghazarian
Hi David, Thank you for your quick reply. I believe I did not explain the problem correctly. I do not want to see the actual ACK character on the screen but rather being able to get the packet information that contains the ACK character. To demonstrate the issue, it can be done as the followi

Re: ACK char issue

2020-08-14 Thread david kerns
ACK is a non-printable char ... if you run your app in a non screen window, I'd be surprised if you saw them. Try running your app like this: app | cat -v should print "^F" for every ACK ... independent of screen On Fri, Aug 14, 2020 at 12:59 PM Dro Ghazarian wrote: > Hi, > I have been trying