You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If I set the UseSocketFilter property of an FFXIVNetworkMonitor to true, the callback for MessageSent never triggers. I'm using raw sockets, not winpcap.
I've ensured that the app is allowed through the firewall and there are no errors in the trace log. At a deeper level, it looks like ProcessSentMessage is never called because no packets are ever returned for the sent side of the connection. Is this a limitation of UseSocketFilter or is there further configuration I need to do?
The text was updated successfully, but these errors were encountered:
If a foreign address is defined for the socket, it should correspond to the source address as specified in the IP header of the received datagram
For raw sockets, the received packets will have the expected remote ip as the source address. Unfortunately, packets originating from the game will have source address = local ip, and so this is the reason these packets are not available when this feature is turned on.
I will need to consider a larger change to Machina to resolve this - probably creating multiple raw sockets, one for each direction, when this flag is enabled.
If I set the
UseSocketFilter
property of anFFXIVNetworkMonitor
totrue
, the callback for MessageSent never triggers. I'm using raw sockets, not winpcap.I've ensured that the app is allowed through the firewall and there are no errors in the trace log. At a deeper level, it looks like
ProcessSentMessage
is never called because no packets are ever returned for the sent side of the connection. Is this a limitation ofUseSocketFilter
or is there further configuration I need to do?The text was updated successfully, but these errors were encountered: