14:51 <rixed> Hey there! With only the TCPV4.flow that a TCP server is given, is it possible to retrieve the peer IP address/port ?

14:56 <yomimono> TCPV4.get_dest, I believe, will give you both.

14:56 <yomimono> (if you're using the current set of development packages that will become 3.0, the function's been renamed)

14:57 <yomimono> rixed: more generally, to find out what you can do with TCPV4, see https://github.com/mirage/mirage/blob/master/types/V1.mli#L631

14:58 <yomimono> (that's current master, https://github.com/mirage/mirage/blob/v2.9.1/types/V1.mli#L596 for version 2.9.1 which is the latest release)

14:58 <rixed> yomimono: yes! thank you.

14:58 <rixed> I used to grep in my opam build dir when it comes to mirageos :)

14:59 <yomimono> :)

15:08 <rixed> s it possible to Stack.listen first, then attach (several) tcpv4 callbacks with listen_tcpv4 on the same stack we have started a listener earlier?

15:08 <rixed> (sorry haven't read code nor doc, trying to hack a mirageos version of some service in a hurry :))

15:12 <yomimono> yes, it should work -- the set of listeners in stackv4 is mutable

15:12 <yomimono> when a packet comes in, stack.listen consults the current hashtable

15:12 <yomimono> so changes that you make should be reflected

15:13 <yomimono> (but note that it's a hashtable replacement, so you can't set multiple listeners per port)

15:16 <rixed> yomimono: yep this I was expecting. Thank you again.

15:19 <yomimono> rixed: no problem! :) let us know if what you're lashing up is public. always want to see more running out there.

15:23 <rixed> yomimono: will do. it will be public if it works.