Wireshark mailing list archives
Re: Conversations - addresses/ports, more general endpoints, and "circuits" with their own IDs
From: Luke Mewburn <luke () mewburn net>
Date: Sun, 6 Jan 2019 11:01:04 +1100
On 17-10-28 20:12, Guy Harris wrote: | Michael Mann is looking at generalizing conversations to handle | arbitrary endpoints, presumably not necessarily in the form of an | AT_ address plus a PT_ numeric port ID. Hi Guy, Was there any further development on this topic? (I did try & send a reply to this thread on 2017-11-21 but it didn't get through). cheers, Luke. ___________________________________________________________________________ Sent via: Wireshark-dev mailing list <wireshark-dev () wireshark org> Archives: https://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-request () wireshark org?subject=unsubscribe
Current thread:
- Re: Conversations - addresses/ports, more general endpoints, and "circuits" with their own IDs Luke Mewburn (Jan 05)
- <Possible follow-ups>
- Re: Conversations - addresses/ports, more general endpoints, and "circuits" with their own IDs Luke Mewburn (Jan 05)
- Re: Conversations - addresses/ports, more general endpoints, and "circuits" with their own IDs Roland Knall (Jan 06)
- Re: Conversations - addresses/ports, more general endpoints, and "circuits" with their own IDs Jaap Keuter (Jan 06)
- Re: Conversations - addresses/ports, more general endpoints, and "circuits" with their own IDs Guy Harris (Jan 06)
- Re: Conversations - addresses/ports, more general endpoints, and "circuits" with their own IDs Jaap Keuter (Jan 07)
- Re: Conversations - addresses/ports, more general endpoints, and "circuits" with their own IDs Guy Harris (Jan 07)
- Re: Conversations - addresses/ports, more general endpoints, and "circuits" with their own IDs Roland Knall (Jan 06)