MTU size always reported as etd max at transfer start, even if etc is constrained to less?

[varenius]

oper@gyller:/mnt/raidz0/testtrans$ etc '/mnt/raidz0/vmux/b21084_oe/*' REMOTE#2641:/export/vlbi/data/etransfer_test/ --resume -m 3 --udt-mss 8000
2022-03-01 09:36:07.72: ETDServer starting, my uuid=lfx30uKwRYI6OcZh
[...]
2022-03-01 09:36:09.93: PUSH Resume /mnt/raidz0/vmux/b21084_oe/b21084_oe_084-1832b_all -> /export/vlbi/data/etransfer_test/b21084_oe_084-1832b_all
2022-03-01 09:36:10.44: sendFile/connected to <udt/REMOTE:2643/mss=9000,max-bw=-1>
finished; succesfully transferred 11 GiB (10,988,380,960 bytes) in 156.5 s [66.94 MBps]
2022-03-01 09:38:47.16: PUSH Resume /mnt/raidz0/vmux/b21084_oe/b21084_oe_084-1833_all -> /export/vlbi/data/etransfer_test/b21084_oe_084-1833_all
2022-03-01 09:38:47.67: sendFile/connected to <udt/REMOTE:2643/mss=9000,max-bw=-1>
^C2022-03-01 09:40:32.11: sigwaiterthread: Closing <udt/LOCAL:47458/mss=8000,max-bw=-1>
2022-03-01 09:40:32.11: sigwaiterthread: done.

See above; etc command specifies MTU 8000. (I have tested with other MTUs that this switch actually does work.) But, upon first connect, we get the message on screen as
2022-03-01 09:36:10.44: sendFile/connected to <udt/REMOTE:2643/mss=9000,max-bw=-1>
When we close (CTRL-C) we get
2022-03-01 09:40:32.11: sigwaiterthread: Closing <udt/LOCAL:47458/mss=8000,max-bw=-1>

This might make sense, but it would be nice to see the "actual connection MTU" reported instead of the server max perhaps? So, the etc output should report min(server,client)?

[haavee]

Hi Eskil, the actual mss that is chosen is currently reported at debug level 4 and above (as is the chosen bandwidth).
The code cannot update the values that the remote end has sent which is why they're currently displayed as they were received.