https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=6854
--- Comment #4 from Michael Wojcik <michael.wojcik@xxxxxxxxxxxxxx> 2012-03-20 12:43:14 PDT ---
TN3270 is still used quite widely, but it's mostly used with legacy
applications that don't change very often, so I suspect that it's rare that
people run into problems and need to trace it. For the same reason, some
implementations have had known bugs for years; if they don't interfere with the
apps customers are running now, they're not likely to ever be a problem. IBM's
own Personal Communications TN3270 client violates RFC 2355 in at least one way
I know of: it sends non-zero sequence numbers even when the RESPONSES function
wasn't negotiated.
I've actually been using it while adding new features to one of our mainframe
emulation products, so I'm using TN3270 a bit more aggressively, trying to find
bugs in my TN3270 server implementation, and comparing what I'm generating with
flows from a real mainframe. The dissector's been very useful in that process -
so thanks for creating it!
The TN3270 clients I use for testing - mostly Rumba and x3270 - have trace
facilities, but none as thorough as Wireshark with the TN3270 dissector.
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
