OPL (or other homebrew software) network featured won't work.
I believe the issue is due to smap emulation issues in the plugin, however I haven't been able to figure out the cause of the issue, and finding documentation about dev9 hardware has not been easy.
@cerceuse
Your issue is not related to IP options.
Can you confirm you DNS is set correctly for outbreak?
Oh, well that is disappointing as I'd gotten the slims to handle OPL all nicely, and was kinda hoping I could get PCSX2 in on the same system.
If it's not stupid (accessible pads and 100MHz or less), I may be able to hook up my logic analyser to sniff the link to the adaptor if you want.
Hi it's me again,
I tried to play online using WiFi in my campus but it couldn't connect. I'm still using the plugin you've given me unfortunately it only works in my home WiFi.
here is the log, hope you can help it.
I tried the new one and I think it gave me the same result as @yogzgm. Attached is the log.
By the way, thank you so much for your help. Maybe the plugin is doing OK, I think it's my ISP connection.
Hello, I'm trying to play Re: Outbreak and I've followed all the instructions, and everything is checked and rechecked to be configured allright but when I'm stuck in now loading and the login screen does not appear.
I got this error: CLR_DEV9:UDPSession Error: 11301 : UDP Got Data
I've noticed a strange case among some users. In my PC, the log says "opening dest port TCP 443" before loading the data.
But in some users' PC I've witnessed through Team-Viewer, this never shows up on their logs and the game remains on the "Now Loading" loading screen when connecting until it times out.
Could you check on that?
TCP Port 443 is HTTPS (opening dest means it's connecting to that port)
Of the logs I've seen posted on here which fail to reach that step.
One had the DNS return ServerError, despite being set correctly.
The rest seem to not have the DNS respond at all.
The 1st one seems like ISP filtering.
The rest I'm not sure, could be ISP filtering, could be the plug-in failing to bind to the correct adapter, could be firewall issues.