Need some assistance with connection/file sharing issues

[celebi23]

So, I've got MacOS 9.2.2 set up in "Qemu-system-ppc-screamer-macOS-universal-05-01-2025". I want to set up a Hotline Server inside of Qemu. I'm kinda at a loss as to why MacOS 9.2.2 will not connect to the internet at all with the "vmnet-bridged" option. Here's my starting point with the commands to launch Qemu:

Code: Select all

./qemu-system-ppc \
-L pc-bios \
-cpu G4 \
-M mac99,via=pmu \
-m 990 \
-boot c \
-g 1440x1050x32 \
-display cocoa \
-device VGA,edid=on,vgamem_mb=64 \
-netdev user,id=network01 \
-device sungem,netdev=network01 \
-drive file=MacintoshHD.img,format=raw,media=disk \
-drive file=Hotline.img,format=raw,media=disk \
-drive file=Files.img,format=raw,media=disk \
-rtc base=localtime \
-name "Hotline"

After fiddling around with various options, and trying to forward ports 5500 & 5501, this is where I ended up:

Code: Select all

sudo ./qemu-system-ppc \
-L pc-bios \
-cpu G4 \
-M mac99,via=pmu \
-m 990 \
-boot c \
-g 1440x1050x32 \
-display cocoa \
-device VGA,edid=on,vgamem_mb=64 \
-netdev vmnet-bridged,id=network01,ifname=en0 \
-device sungem,netdev=network01 \
-drive file=MacintoshHD.img,format=raw,media=disk \
-drive file=Hotline.img,format=raw,media=disk \
-drive file=Files.img,format=raw,media=disk \
-name "Hotline"

If you're setting up a hotline server, I'd recommend using QEMU, as SheepShaver is known to lock up after running for a while.

Hotline Server will need ports 5500 and 5501 connectable. Since you're going the bridging route, your guest OS should be assigned its own unique IP on your LAN, and have those ports available.

You've changed your QEMU config to vmnet-bridged. But what are you bridging it TO? With what you listed, it's bridging to en0. Is en0 the name of your active WiFi device in the host?

As far as WiFi vs Ethernet goes -- DDP (AppleTalk networking) isn't supported by WiFi routers unless it is encapsulated in some other protocol such as UDP. WiFi supports TCP, UDP and ICMP (and a few other protocols that don't have to do with moving application data). Since the stuff you're trying to do is on TCP, it should work fine over WiFi.

Once you've verified that all of that is working from another device on your LAN, you'll need to port forward 5500 and 5501 on your router in order for them to be visible on the Internet. You'll want to forward to the IP address that your guest OS shows up as on your LAN.

I've got that same configuration set up, and it works for me.

When you say "I still cannot connect to the Internet", how are you measuring this? Remember that even running Classilla is unlikely to work with most websites these days, but you should be able to ping google.com or connect to a known Hotline server IP address.

Gotcha, will go with Qemu then. Yeah, I've confirmed that it is en0.

Sorry, let me be clearer. I can't connect to the internet from with Mac OS 9, in Qemu if I have the bridge set up via the command line option. If I try and connect via Hotline Connect, for instance, it errors out when trying to load a tracker:


And I know my internet connection for the host MacBook Pro is working as I can connect to the same tracker via the Hotline app.

If I try to connect to a specific server, by entering the server address manually, I see this:


It does look like it's trying to bridge the connection because I see this in IE:

It's the correct host's IP address.

But, IE errors out when even trying to connect to Google:


In the TCP/IP control panel, it does list a different IP address, the correct Subnet Mask and Router Address:
.

I've tried setting up the port forwarding with my Xfinity router but, I still have not internet connection within the MacOS 9.2.2 guest os. I feel like I'm missing something super obvious but, I'm not sure what is causing this

I'm running these commands to launch Qemu:

Code: Select all

sudo ./qemu-system-ppc \
-L pc-bios \
-cpu G4 \
-M mac99,via=pmu \
-m 940 \
-boot c \
-device VGA,edid=on,vgamem_mb=64 \
-netdev vmnet-bridged,id=network01,ifname=en0 \
-device sungem,netdev=network01 \
-drive file=MacintoshHD.img,format=raw,media=disk \
-drive file=Hotline.img,format=raw,media=disk \
-drive file=Files.img,format=raw,media=disk \
-g 1440x1050x32 \
-display cocoa \
-name "Hotline"

am I missing something here?

I also cannot get Qemu to recognize the Shared/Qemushare options at all. I've tried these variations and the Shared folder does not appear in Mac OS 9.2.2 at all:

Code: Select all

-device virtio-tablet-pci \
-device virtio-9p-pci,fsdev=shareddir,mount_tag="Shared" \
-fsdev local,id=shareddir,security_model=none,path=/Users/celebi23/qemushare/ \

-device virtio-9p-pci,fsdev=qemushare,mount_tag="Shared" \
-fsdev local,id=qemushare,security_model=none,path=/Users/celebi23/qemushare \

-device virtio-9p-pci,fsdev=shareddir,mount_tag="Shared" \
-fsdev local,id=shareddir,security_model=none,path=/Users/celebi23/qemushare \

-device virtio-9p-pci,fsdev=SHARED,mount_tag="Shared" \
-fsdev local,id=SHARED,security_model=none,path=/Users/celebi23/qemushare \

-virtfs local,security_model=none,mount_tag=qemushare,path="/Users/celebi23/qemushare/" 

Any help would be incredibly appreciated

[Cat_7]

I'm not sure which qemu builds you are using for what?
Are your questions related to the screamer build?

Edit: you do not show your complete command file when trying to add the shared folder. It now looks like you are missing the lines to load the loader file and to run it. Without it, the shared folder will not be available. Make sure to add these lines before the device lines for tablet and virtio-9p devices. Regarding networking: are you sure you cannot connect to any sites? The old browsers available for Mac OS 9 do not support https. Check whether you can connect to e.g. http://macintoshgarden.org. If so, you are good to go.
There is also no need to black out any 192.168.x.x ip address lines as these are on an internal ip address range that cannot be accessed from the outside world
This works over here (including vmnet network):

sudo ./qemu-system-ppc \
-L pc-bios \
-M mac99,via=pmu \
-display cocoa \
-m 512 \
-device sungem,netdev=network01 \
-netdev vmnet-bridged,id=network01,ifname=en0 \
-boot c \
-drive file=/Users/hsp/mac-disks/9.2.img,format=raw,media=disk \
-device loader,addr=0x4000000,file=./ndrvloader \
-prom-env "boot-command=init-program go" \
-device virtio-tablet-pci \
-device virtio-9p-pci,fsdev=UNIQUENAME,mount_tag="Macintosh HD" \
-fsdev local,id=UNIQUENAME,security_model=none,path=/Users/hsp/qemushare


Best,
Cat_7

[celebi23]

posting.php?mode=quote&p=80474

I'm not sure which qemu builds you are using for what?
Are your questions related to the screamer build?

Edit: you do not show your complete command file when trying to add the shared folder. It now looks like you are missing the lines to load the loader file and to run it. Without it, the shared folder will not be available. Make sure to add these lines before the device lines for tablet and virtio-9p devices. Regarding networking: are you sure you cannot connect to any sites? The old browsers available for Mac OS 9 do not support https. Check whether you can connect to e.g. http://macintoshgarden.org. If so, you are good to go.
There is also no need to black out any 192.168.x.x ip address lines as these are on an internal ip address range that cannot be accessed from the outside world
This works over here (including vmnet network):

sudo ./qemu-system-ppc \
-L pc-bios \
-M mac99,via=pmu \
-display cocoa \
-m 512 \
-device sungem,netdev=network01 \
-netdev vmnet-bridged,id=network01,ifname=en0 \
-boot c \
-drive file=/Users/hsp/mac-disks/9.2.img,format=raw,media=disk \
-device loader,addr=0x4000000,file=./ndrvloader \
-prom-env "boot-command=init-program go" \
-device virtio-tablet-pci \
-device virtio-9p-pci,fsdev=UNIQUENAME,mount_tag="Macintosh HD" \
-fsdev local,id=UNIQUENAME,security_model=none,path=/Users/hsp/qemushare


Best,
Cat_7

Sorry, yeah, I'm using "Qemu-system-ppc-screamer-macOS-universal-05-01-2025". Ah, right. I forgot about that with IP addresses. It's been years since my computer/technology classes at college I'm unfortunately still having those connection issues. When I don't have the vmnet-bridged command line options (and have the default -device sungem,netdev=network01 netdev user,id=network01 options), I can connect the internet without issue in Mac OS 9.2.2, with Classilla & Hotline:



When I have the vmnet-bridged command line options, however, everything still errors out:






I do though, see the Shared drive/folder on the Mac OS 9.2.2 desktop though so, I count that as a win in my book Do I need to do anything on the host's side, besides the qemu launch commands, to achieve what I'm trying to do here? Theses are the commands I've been using (I made an app launcher for this, this executable sits in the "Contents/MacOS/" directory of the app launcher):

Code: Select all

#!/bin/bash
cd "$(dirname "$0")"
cd "$mypath"
sudo ./qemu-system-ppc \
-L pc-bios \
-M mac99,via=pmu \
-display cocoa \
-g 1440x1050x32 \
-device VGA,edid=on,vgamem_mb=64 \
-m 980 \
-cpu G4 \
-device sungem,netdev=network01 \
-netdev vmnet-bridged,id=network01,ifname=en0 \
-boot c \
-drive file=MacintoshHD.img,format=raw,media=disk \
-drive file=Files.img,format=raw,media=disk \
-device loader,addr=0x4000000,file=./ndrvloader \
-prom-env "boot-command=init-program go" \
-device virtio-tablet-pci \
-device virtio-9p-pci,fsdev=shareddir,mount_tag="Shared" \
-fsdev local,id=shareddir,security_model=none,path=/Applications/Qemu/Shared \
-rtc base=localtime \
-name "Hotline"

I really can't think of what's still causing this connection issue. If I upload my MacintoshHD.img file to say, mega/Google Drive, could you take a look to see if I'm missing something there as well?

Thanks so much for the assistance with this

[Cat_7]

Sure, I'll pm you with my email address.

Best,
Cat_7

[celebi23]

Sure, I'll pm you with my email address.

Best,
Cat_7

Just sent the link, thanks so much!

[Cat_7]

There is nothing wrong with the image or network settings. I receive an ip address etc. from my router and can connect to websites, run the hotline client and see servers.

I have no idea whether your app laucher has anything to do with it.
You are not running two qemu instances at the same time?
Are you sure en0 is the correct name for you wired ethernet connection?

Perhaps you can try with a clean Mac OS 9.2 installation running straight from the command line?

Best,
Cat_7

[celebi23]

There is nothing wrong with the image or network settings. I receive an ip address etc. from my router and can connect to websites, run the hotline client and see servers.

I have no idea whether your app laucher has anything to do with it.
You are not running two qemu instances at the same time?
Are you sure en0 is the correct name for you wired ethernet connection?

Perhaps you can try with a clean Mac OS 9.2 installation running straight from the command line?

Best,
Cat_7

Hmm, interesting
My app launcher is just this (a way to keep Qemu instances organized)


I don't have 2 Qemu instances open at once and I'm pretty sure en0 is my internet connection. Do I need a wired ethernet connection for this to work? Or, can it be done via WiFi? I tried running "ipconfig getiflist" and got this result:
en4 en5 en6 en0 bridge0

If I have anything else except en0, I see this message:
qemu-system-ppc: -netdev vmnet-bridged,id=network01,ifname=en6: unsupported ifname 'en6', expected one of [ en0 ]

I tried to run the commands straight in Terminal, rather than my launcher script, and still having the connection issues. I'll try doing a fresh install of Mac OS 9 next.

Thank you for looking at it for me, I really do appreciate it . Seems to rule out an issue with Qemu itself and probably something to do with my MacBook Pro

[Cat_7]

To be sure of your network connection names open a system report and check at the network entry.

Best,
Cat_7

[celebi23]

Did a fresh install of 9.2.1 and still having the same weird connection issues in Mac OS 9. Confirmed that "en0" is the only thing listed under "Interfaces:" in the "Wi-Fi" section, under "Network". Do I need to be connected via Ethernet for this to work properly, or were you able to get around the issue while connected to WiFi?

Thanks so much

[Cat_7]

I can't remember whether I ever tried with wireless. However, you might experiment with turning IPv6 support on or off on the wireless connection.

Best,
Cat_7

[adespoton]

I've used that configuration both with IPv6 enabled and disabled with no issues. Still drawing a blank as to why bridged vmnet wouldn't handle outbound connections in this configuration.

[Cat_7]

Your image has no connection when bridging to wireless when using the screamer build. It will connect over wireless with our "normal" build.

So my suggestion would be to drop the sound-enabled build.

Best,
Cat_7

[celebi23]

Your image has no connection when bridging to wireless when using the screamer build. It will connect over wireless with our "normal" build.

So my suggestion would be to drop the sound-enabled build.

Best,
Cat_7

Yep, that did it Thank you so much! Final question, I promise

So, I see the IP address is still a 192.168.86.250. How do I configure Mac OS 9 to show a normal external IP address for people to use to connect to the Hotline Server? I've tired websites like https://www.ipchicken.com and using that IP address but, I can't connect to the server with that IP address, say with the Hotline app .

Thanks again

[Cat_7]

Ah, you want to make your hotline server reachable from the internet That requires some steps:

1. Make sure Qemu always gets the same IP address.
2. Setup port forwarding rules in your router

1) You have some router connecting you to the internet. All machines inside your home connected to that router get an ip address from that router in the internal 192.168.x.x range. That is what DHCP does for you: It assigns an IP address based on the MAC address of the network card in the device that connects to your router. In your current Qemu setup the emulated Qemu network card uses the MAC address 52:54:00:12:34:56

IP addresses assigned through DHCP have a lease time. This means that your Qemu might not always get the same IP address when it starts. However, this is required to always successfully complete step 2 below. To prevent this, find the DHCP settings in your router and set a rule to reserve a certain IP address when a device with MAC address 52:54:00:12:34:56 requests an IP address. This results in Qemu always getting the same IP address, and other devices never getting this IP address.

2) The TCP/IP protocol uses port numbers to differentiate between various types of network traffic. You need to find which ports numbers your hotline server is set to use. In your router you then need to create one or more port forwarding rules to these ports. These create a path for the hotline network traffic from and to the outside world (internet) to your internal Qemu IP address. How this works in your router is dependent on its software. It might be you can create one rule to forward multiple ports at once, or you might have to create as much rules as the hotline server uses ports.

Hotline users can then access your Qemu hotline server by using the public external IP address of your router, but should also be able to use the tracker when you advertise your server.

Good luck!

Best,
Cat_7

[adespoton]

As I mentioned above (well, in the other thread, quoted above):

Once you've verified that all of that is working from another device on your LAN, you'll need to port forward 5500 and 5501 on your router in order for them to be visible on the Internet. You'll want to forward to the IP address that your guest OS shows up as on your LAN.