Crash when using network adapter instead of SLIRP on Windows 10

[coldacid]

Windows 10 version 21H1 (19043.1288)
WinUAE 4.4.0

Normally I wouldn't be concerned about this (despite preferring having WinUAE as an actual "device" on my network) but as of this morning SLIRP stopped working properly (DNS resolution isn't working, although it's just fine on the host).

I've attached my config as well as the WinUAE log files for a crashed run. The selected network adapter is the one I also use for any Hyper-V VMs on my computer that I need connected to the internet. I should mention also that I'm using Roadshow 1.14 for the network stack.

[coldacid]

Figured out that I should run with -netlog, so here's an updated zip with fresh logs.

[coldacid]

I was able to get things working under SLIRP again by explicitly setting name servers for Roadshow to use (WinUAE was sending 10.0.2.3 as the suggested name server when it would only respond to DNS requests from 10.0.2.2). However, I'd still like to get working via proper network adapter instead of SLIRP.

I tried 4.9.0b39 but it would crash as soon as Roadshow would start initializing a connection with a 0xffffffff`ffffffff pointer in the JIT.

EDIT: 10.0.2.2 doesn't work for DNS either; I had also put in a nameserver line for another DNS resolver.

[Toni Wilen]

Switch off JIT and disable all unneeded expansions (including CSPPC). Does it still crash? If it does not, try to find out which expansion causes the problem.

If it still crashes, attach crash dump file.

[coldacid]

Without JIT, I can't even establish a network connection due to timeouts. Trying to reconnect (via Roadie) fails, and then quitting WinUAE with the emulation in this state causes a crash.

Switching from A2065 to X-Surf-100 with JIT off is able to establish the network connection, but then DNS requests time out instead despite other systems on my network being reachable, if very slowly. With JIT on, X-Surf-100 instead of A2065, and CSMk3 re-enabled with 128MB RAM, network speed is still slow but there are no crashes with UAESND Z3 disabled. However, the log is full of "NE2000: receive buffer full" and I continue to get timeouts for DNS and HTTP/S requests constantly. I have a suspicion that the full buffer is why the requests are all failing -- data is getting out to the network alright, but the response data is dying "on the wire" inside the emulation. My full configuration but with A2065 switched to X-Surf-100 doesn't fare any better.

[Toni Wilen]

Do you have separate NIC (that is not used by Windows) or share same NIC?

Sharing is not supported because it can cause all kinds of unexpected side-effects.

[coldacid]

Two more A2065 quit-crashes although this time without trying to connect before quitting. This time with full config without JIT, and another without JIT or CSMk3.

The only way I can get non-quit crashes is with JIT enabled; so far it doesn't look like the presence or lack thereof of UAESND Z3 or CSMk3 make any difference.

[coldacid]

Looks like the reason the connections kept timing out before was because of the logging enabled from the command prompt. Running WinUAE with only standard winuaebootlog/winuaelog works with JIT turned off. Going to see if I can snag some proper crashes now.

[coldacid]

Here's an immediate crash with JIT turned off, no UAESND Z3, and no CS Mk III.

Windows and WinUAE have different virtual NICs connected to a virtual switch which uses the computer's physical NIC. It's the standard external virtual switch configuration from Hyper-V, which works not just for Hyper-V virtual machines but also for other virtual network devices on this computer.

[coldacid]

I think I figured out my error. Use of the virtual switch did not actually provide a new virtual NIC for WinUAE. I've now created a new virtual NIC and have WinUAE using that, so far so good. Hopefully I won't have any more crashes in WinUAE with my virtual network setup.

[Toni Wilen]

Quit crash should be fixed in next version. A2065 reset freed board's internal RAM from emulated memory map before closing winpcap and if winpcap sent new ethernet frames during this window (it runs in separate thread), it crashed because A2065 emulation was partially switched off..

Unfortunately this does not explain other problems.

[coldacid]

The other problem did turn out to be double-booking the NIC. With a new virtual NIC dedicated to WinUAE, I don't have any more network related crashes. Thanks for the A2065 quit crash though!

[Toni Wilen]

It still shouldn't cause crashes, unless some Amiga-side networking buffer overflowed. I don't think roadshow causes it, perhaps Amiga-side NIC driver gets confused if too much traffic appears almost immediately.

[coldacid]

That would explain the full buffer messages in the logs in the crashed sessions.