sedbgmux/sedbgmux
Vadim Yanitskiy 0c15e0baac DbgMuxConnHandler: accumulate DataBlockCount
Looking at samples/k800_tems.pcapng.gz I noticed that the client
side (TEMS Investigation) is accumulating the FlowControl credits.
Below is an extract from it, showing the client sending three
data blocks in one go:

Record #0031 @ 1674591313.020628 Tx 42421000070e6f00940900022c0104690103a2bd
  DebugMux Tx frame (Ns=007, Nr=014, fcs=0xbda2) ConnData 00940900022c0104690103
  Container:
    ConnRef = 0x9400
    Data = hexundump("""
    0000   09 00 02 2C 01 04 69 01 03                        ...,..i..
    """)

Record #0032 @ 1674591313.020628 Tx 42421000080e6f00940900022c0105da0103db5b
  DebugMux Tx frame (Ns=008, Nr=014, fcs=0x5bdb) ConnData 00940900022c0105da0103
  Container:
    ConnRef = 0x9400
    Data = hexundump("""
    0000   09 00 02 2C 01 05 DA 01 03                        ...,.....
    """)

Record #0033 @ 1674591313.036228 Tx 42421000090e6f00940900022c01069300034c83
  DebugMux Tx frame (Ns=009, Nr=014, fcs=0x834c) ConnData 00940900022c0106930003
  Container:
    ConnRef = 0x9400
    Data = hexundump("""
    0000   09 00 02 2C 01 06 93 00 03                        ...,.....
    """)
2024-05-02 01:47:45 +02:00
..
ch DbgMuxConnHandler: accumulate DataBlockCount 2024-05-02 01:47:45 +02:00
io sedbgmux: remove Python shebang and executable flags 2024-04-22 19:35:56 +07:00
__init__.py DbgMuxClient: client role implementation 2023-01-22 23:20:02 +06:00
client.py DbgMux{Frame,ConnHandler}: DataBlockLimit != DataBlockCount 2024-05-02 01:42:03 +02:00
peer.py Rework logging: use module-level loggers 2023-04-29 15:58:15 +07:00
ping_pong.py sedbgmux: remove Python shebang and executable flags 2024-04-22 19:35:56 +07:00
proto.py DbgMux{Frame,ConnHandler}: DataBlockLimit != DataBlockCount 2024-05-02 01:42:03 +02:00