Apple-2-Tools/ample
1
0
Fork 0
mirror of https://github.com/ksherlock/ample.git synced 2024-06-01 16:41:35 +00:00
Code Issues Projects Releases Wiki Activity

Updated Networking (markdown)

ksherlock 2023-05-01 18:17:22 -04:00
parent 1a0229ce71
commit f92410b62a
1 changed files with 3 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
Networking.md

@ -4,14 +4,15 @@ Ample uses the [vmnet.framework](https://developer.apple.com/documentation/vmnet
* DHCP is required. vmnet has packet filters in place to block most activity until a DHCP connection is established.
* On the MacOS side, vmnet is `bridge100` for wireshark, ifconfig, etc purposes.
* On the MacOS side, vmnet is `bridge100` for wireshark, ifconfig, etc purposes. (Wireshark likes to warn that the TCP CHECKSUM is INCORRECT on all incoming packets. This can be ignored or disable.)
* DHCP will assign an address in the 192.168.64.xx range, with 1921.68.64.1 as the gateway, DNS, DHCP server.
* DHCP will assign an address in the 192.168.64.xx range, with 192.168.64.1 as the gateway, DNS, DHCP server.
* Your macintosh can be accessed as 192.168.64.1. Other IP addresses usually work (eg, if your wifi is 192.168.1.234) but some software may not like that. VEDrive, for example, compares the UDP source IP Address so only 192.168.64.1 will work.
* vmnet re-uses parts of the Mac Internet Sharing (MIS). When both are in use, I have seen the DHCP server stop working for MIS. Turning MIS off and back on might resolve it.
* vmnet assigns a MAC address. Apple II NICs (Uthernet, Uthernet II, LANceGS) do not have an assigned MAC address (well, LANce has a MAC address stored in the non-volatile RAM) so it can't be communicated back into emulation. Ample MAME silently rewrites ethernet headers, DHCP messages, and ARP messages to swap MAC addresses. This should only be an issue if you're wondering why the MAC address is wrong in wireshark or if you're doing something really weird.