snoww / loa-logs

LOA Logs - Modern DPS Meter for Lost Ark
GNU General Public License v3.0
124 stars 24 forks source link

Can not work with local pc port mapping, but loa details support it. #95

Open nvssoft123 opened 2 months ago

nvssoft123 commented 2 months ago

Such as 1.create a local tcp server listen on port 6040, if game connect to local pc 6040 port( we use WFP to let game connect to local pc's 6040 port) etc, it will port mapping to real game server's 6040 port and via socks5 proxy. 2.Loa details support this, it capture local pc's 6040 port packets with raw socket option. 3.If enable raw socket and 6040 port in loa logs, it can not capture anything. May be loa logs exclude local pc's 6040 port packets , only capture remote pc's 6040 port?

snoww commented 2 months ago

wfp is not supported unfortunately

nvssoft123 commented 2 months ago

Hello, You don't need support WFP, just support capture local pc's 6040 tcp packet, it's easy. We use wfp/hook to redirect game's packet to local pc 6040 port, it like a port mapping.

The game data -> local pc's 6040 port -> proxy server -> game server's 6040 port.

So just capture local pc's 6040 port packet with raw socket option or other.

It's because loa details can capture local IP address 6040, but loa logs don't capture local IP 6040 port packets, it just can capture remote IP 6040 port packets. so please remove this limit. such as lostark.exe connect to 2.4.5.6 6040 port ( loa logs and loa details works, game server is 2.4.5.6:6040 ) lostark.exe connect to 192.168.1.10 6040 port (loa log don't work, but loa details works, game server is 192.168.1.10:6040)

Snow @.***> 于2024年5月8日周三 16:23写道:

wfp is not supported unfortunately

— Reply to this email directly, view it on GitHub https://github.com/snoww/loa-logs/issues/95#issuecomment-2100023637, or unsubscribe https://github.com/notifications/unsubscribe-auth/BILD25KHFFYMUXOHO27MMQLZBHOHXAVCNFSM6AAAAABHMHVJ6WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMBQGAZDGNRTG4 . You are receiving this because you authored the thread.Message ID: @.***>

snoww commented 1 month ago

can you try manually adding the loopback ip to the settings.json file?