Should be all buttoned up now @Mac84 . Thanks for the feedback.
GlobalTalk - Global AppleTalk network for MARCHintosh 2024 (and beyond!)
- Thread starter eric
- Start date
-
- Tags
- #marchintosh globaltalk
So looking at these guides - even as someone who does networking as part of his job - seemed like this is crazy to have to setup this much just to pass a one port to a VM. So I read the QEMU networking docs and I believe for the normal use case of just having a VM access GlobalTalk (and nothing else) you don't need to setup any advanced networking. Just use the default user network adapter.
note the -nic switch with the added port forwarding. (user is default if -nic is not specified, but we need the ports exposed on the host)
Since the image uses mactcp which doesnt support dhcp the details are:
router: 10.0.2.2
ip: 10.0.2.15 (or higher)
subnet: 255.255.255.0
DNS: you choose or 1.1.1.1
Note you'll need root/admin privileges (of course) to listen on any port under 1024
I was able to get networking working fine but didn't have time to go through the entire AIR setup.
-
Also I am not using AIR this year as jrouter is so easy to setup and I don't need a QEMU host or retro computer running 24/7. My "BlueSCSI HQ" network is jrouter + Netatalk - all modern software. I can fire up my Q700 to jump on and poke around other people's shares/printers/etc.
Code:
qemu-system-m68k -M q800 -m 128 -g 1152x870x8 -display sdl -bios Q800.ROM \
-drive file=pram.img,format=raw,if=mtd -device scsi-hd,scsi-id=0,drive=hd0 -drive format=raw,media=disk,if=none,id=hd0,file=GlobalTalk_HD.img \
-nic user,hostfwd=udp::387-:387note the -nic switch with the added port forwarding. (user is default if -nic is not specified, but we need the ports exposed on the host)
Since the image uses mactcp which doesnt support dhcp the details are:
router: 10.0.2.2
ip: 10.0.2.15 (or higher)
subnet: 255.255.255.0
DNS: you choose or 1.1.1.1
Note you'll need root/admin privileges (of course) to listen on any port under 1024
I was able to get networking working fine but didn't have time to go through the entire AIR setup.
-
Also I am not using AIR this year as jrouter is so easy to setup and I don't need a QEMU host or retro computer running 24/7. My "BlueSCSI HQ" network is jrouter + Netatalk - all modern software. I can fire up my Q700 to jump on and poke around other people's shares/printers/etc.
Worth a shot. In this configuration, you'd port forward to the computer hosting the qemu guest. If someone wants to test it and report back, that's great! The disadvantage of this configuration is that your guest might not see other computers on its own network. For example, I am using FTP to a Raspberry Pi on my local network. I don't think that would work in this configuration. And you probably wouldn't see LocalTalk Macs on your network either is my guess.
Last edited:
100% sure they wont, which is why I mentioned that in my post. I see a ton of people wanting to get on GlobalTalk that may not even have a Vintage Mac to run AIR that have 0 network experience - this is for them. Others should choose the more complex bridge setup.
Nice! vmnet-bridged doesn't seem to exist on the linux build - unsure about windows.
Also to clarify (as I've been asked a few times) - the network details I provided are for the internal Qemu user network - so you must use those exact ones in MacTCP. The network looks like:
|Internet| -> |Home Router (eg: 192.168.1.x)| -> |PC Host(192.168.1.123)| -> |Qemu user network(10.0.2.x)| -> |Qemu Guest(10.0.2.15)|
Haha, you sure did! My reading comprehension is apparently not great as of late. Apologies.
Super late to the party, but has anyone experienced "devcon failed" when installing the TAP driver? This is a fresh Win10 install.
Peculiar. A couple of options here:
- Try to install OpenVPN, and select the TAP driver as a part of the install
- Try User mode per @eric's suggestion
Last night I released several GlobalTalk-related resources - see Apple Internet Router Administrator’s Guide—Addendum and GlobalTalk Setup Files v1.0.4 released for MARCHintosh 2025!
I haven’t yet reviewed this whole thread, but the OCI command file in my QEMU GlobalTalk Setup Files package uses just such a -nic definition to just forward UDP port 387 using slirp.
The reason I go to the trouble of setting up the bridge interface on Ubuntu when I can (as detailed in #MARCHintosh Wrap Up, GlobalTalk News) is easier use of any port to/from the guest OS (the guest OS is a full “citizen” of the Ethernet network), and the ability to avoid evoking QEMU as root.
Also, vmnet-bridged is macOS-only and is great! (It’s a feature of the OS, not QEMU.)
Going to trawl back now, but AMA about GlobalTalk and I’ll likely have an opinion on it...
Oh, and speaking of opinions about GlobalTalk...
If you’re setting up a GlobalTalk node (or already have with a network range spanning 2+ numbers) - you’ll almost certainly need only one network number for your EtherTalk port (so enter the range as, for example, 12345-12345).
See my docs for rationale - but basically that will support 253 AppleTalk devices on that EtherTalk port.
You may need more numbers if you have multiple networks/segments, and LocalTalk networks need their own number/s (outside of that range and unique across GlobalTalk).
Be kind…only one network number assigned!*
europlus
*kind because it increases the odds other admins can choose their own “special” number.
I haven’t yet reviewed this whole thread, but the OCI command file in my QEMU GlobalTalk Setup Files package uses just such a -nic definition to just forward UDP port 387 using slirp.
The reason I go to the trouble of setting up the bridge interface on Ubuntu when I can (as detailed in #MARCHintosh Wrap Up, GlobalTalk News) is easier use of any port to/from the guest OS (the guest OS is a full “citizen” of the Ethernet network), and the ability to avoid evoking QEMU as root.
Also, vmnet-bridged is macOS-only and is great! (It’s a feature of the OS, not QEMU.)
Going to trawl back now, but AMA about GlobalTalk and I’ll likely have an opinion on it...
Oh, and speaking of opinions about GlobalTalk...
If you’re setting up a GlobalTalk node (or already have with a network range spanning 2+ numbers) - you’ll almost certainly need only one network number for your EtherTalk port (so enter the range as, for example, 12345-12345).
See my docs for rationale - but basically that will support 253 AppleTalk devices on that EtherTalk port.
You may need more numbers if you have multiple networks/segments, and LocalTalk networks need their own number/s (outside of that range and unique across GlobalTalk).
Be kind…only one network number assigned!*
europlus
*kind because it increases the odds other admins can choose their own “special” number.
Please use the **NEW** link to my resources, which will always have the latest GlobalTalk Setup Files packages: WOzFest HQ GlobalTalk Files
Also, just put a fullstops/period/dot in the Domain field for your default DNS server – this ensures MacTCP uses that DNS server for all searches. The “Domain” field is not the hostname of the DNS server, it is the Search Domain that DNS server handles DNS for.
Short summary, a search domain allows you to enter a one-word hostname and the search domain gets appended to it for a search on that DNS server.
So, for example, if tinkerdifferent.com had subdomains mail.tinkerdifferent.com, forums.tinkerdifferent.com, appleshare.tinkerdifferent.com, and a DNS server at 192.168.0.1 which handles requests for tinkerdifferent.com domains and subdomains, you could set the first Domain as “tinkerdifferent.com." (note the trailing dot! it’s important!) and the IP address as 192.168.0.1, then enter a second DNS server for all other requests with the “dot only” domain (i.e. a search domain of the whole internet) and IP address of “8.8.8.8”, and then when connecting to one of those tinkerdifferent.com subdomains in a client app, you could just specify a hostname of “mail”, “forums”, or “appleshare” and the DNS server at 192.168.0.1 will return the appropriate IP addresses for those “tinkerdifferent.com” hosts.
It was meant as a time saver when many client devices would be on the same network as the servers they were connecting, and entering server addresses was a new thing (or done often enough to want to save the time, for example, at the command line).
It’s still possible to set search domains up in modern OSes, but it’s rarely relevant in day-to-day Internet use.
I return you to your regular programming...
europlus
Hello everyone,
I'd like to share my new A-Z GlobalTalk guide, this has been in the works since last year and is finally ready. You can check it out here:
The Ultimate GlobalTalk Network Guide
It is designed for vintage Macintosh users of all backgrounds, those just getting started and those Mac heads who may want a refresher. It covers topics ranging from understanding LocalTalk and AppleTalk, preparing your network, handling network printers and of course a full step-by-step section (with images) of how to configure the Apple Internet Router for GlobalTalk.
I hope this resource becomes a handy tool in getting newcomers online to our AppleTalk fun zone!
I'd like to share my new A-Z GlobalTalk guide, this has been in the works since last year and is finally ready. You can check it out here:
The Ultimate GlobalTalk Network Guide
It is designed for vintage Macintosh users of all backgrounds, those just getting started and those Mac heads who may want a refresher. It covers topics ranging from understanding LocalTalk and AppleTalk, preparing your network, handling network printers and of course a full step-by-step section (with images) of how to configure the Apple Internet Router for GlobalTalk.
I hope this resource becomes a handy tool in getting newcomers online to our AppleTalk fun zone!
Thanks for the feedback! I added the new link (kept the old one, made it clear with version numbers), I modified the screenshots for the DNS server inside the MacTCP stepts.