Timeline for Running WarpCopy64 on an emulator
Current License: CC BY-SA 4.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 24, 2021 at 16:44 | comment | added | Brian H | Yep. Sounds a routing problem. The Vice emulation is dead simple and performs no NAT functions. | |
| Jan 24, 2021 at 16:42 | comment | added | cyberixae | Actually, it seems that I can send commands from another computer and WarpCopy server will process them just fine. I can see the responses with WireShark on the computer running the server but I can not see them on WireShark on the computer that is waiting for the response. The server responses get lost somehow on their way back. | |
| Jan 24, 2021 at 16:37 | comment | added | Brian H | I was afraid of that. The VICE Ethernet cart emulation uses libpcap and libnet to "sniff" the packets passing through the host for any addressed to Vice. Getting that working correctly has a lot to do with your network and host security setup. | |
| Jan 24, 2021 at 16:31 | comment | added | cyberixae | I'm still unable to reach the server from another Windows computer on the same LAN. Not sure why. The IP address 192.168.0.64 doesn't seem to mean anything outside the computer that is running VICE. | |
| Jan 24, 2021 at 16:22 | comment | added | Brian H | If I follow correctly, then the only issue was a Windows networking setting that prevented correct IP packets being formed for a locally rouetable destination IP. So, it would have worked fine if using separate Windows machines for VICE and for the WarpCopy client, right? | |
| Jan 24, 2021 at 16:15 | history | edited | cyberixae | CC BY-SA 4.0 | added 317 characters in body |
| Jan 24, 2021 at 15:57 | history | edited | cyberixae | CC BY-SA 4.0 | added 178 characters in body |
| Jan 24, 2021 at 15:49 | history | answered | cyberixae | CC BY-SA 4.0 |