This smells strongly of a double NAT or improper routing configuration where the iBook is isolated behind the AirPort's internal 10.0.1.x network and packets aren’t properly NAT’d back to your router's 192.168.50.x LAN.

I have an original Airport Base Station (not Extreme) and can't seem to get it to provide internet to my OS 9.2 iBook. Everything seems to be working except the iBook can't access the internet (or local network) through the Base Station.

The Airport Base Station is connected to my router (Asus ZenWifi Pro ET12) through an Ethernet cable. The iBook can connect and configure the Base Station via Airport. I've tried to configure the Base Station all different ways (including enabling "Airport to Ethernet bridging"), but the iBook can't connect to the internet via Airport.

The iBook connects to the internet fine through Ethernet (using DHCP), which is how I'm posting this comment (thanks Classilla!).

What works:
+ The iBook can connect to the Base Station via Airport and set it up with the Airport Admin Utility.
+ The Base Station can get its TCP/IP info via DHCP from my router (192.168.50.x subnet).
+ The Base Station can provide DHCP to the iBook on the 10.0.1.x subnet.
+ The "status" field in the Airport application says "Connected to the Internet via Ethernet", and the signal strength is steady at about 90%.

What doesn't work:
- iBook can't access the internet or LAN using Airport connected to the Base Station (this website is the test since it works fine through Ethernet).

I'm wracking my brain trying to think of what the missing piece is. I haven't been able to see with any network scanning software the iBook when it is connected with Airport. It may be that the network protocols of the Base Station are too old to route network traffic correctly.

Any help is appreciated!

Thanks @Architecture, that is just the kind of links I was looking for. I tend to gravitate to live and acoustical in music, but back in the day I got sort of hooked on SIDs on my Commodore. I see what appears to be an old Commodore monitor in your setup I went ahead and subscribed to your channel. I never turn on notifications, so please post links when you have something new up.

Here’s one of my “Tiny Desk” sessions with my smaller MIX TDM setup.

https://youtu.be/IjdbGAC1UT4?si=0-jsKQ-q_5A5Tzc6

this thread is showing its age already... my findings.

if one is stubborn enough to dual boot a mini from one, non-partitioned disk, you can, but it's not fun and not ideal. a couple of weeks ago I partitioned the drive and installed the OSes on their own partitions. That works better, but you still can't use startup disk in OS X to select an older system, whether on a different partition, or not. have to hold down ALT at startup and use the OF startup screen to select OS 9.

In any case, the entire point of this exercise, for me, is nostalgia and tinkering. i have no production uses for my macs, it'ts just for fun and experimentation. I am enjoying all of it, even if i have to wipe a drive and start over. it's all in fun.

enjoy

I've stayed out of this discussion because I don't own a Mini. I DO however have a dual-boot G4 MDD. Few subjects have received as extensive, circular and frustrating discourse on this Forum as have all of the trials and tribulations of dual-booting OS9 and OSX-whatever on one Mac model or another not originally built to allow this.

If there is one constant that constantly reappears as that major part of the solution, it is the one you are clearly aware of and you yourself quoted in your original post:

Hey guys,
Per everything I have read the disk has to be partitioned and 9.2.2 installed on one, and 10.4 or whatever on the other...

Please understand that a LOT of people have spent a LOT of time trial-and-erroring and otherwise testing every possible alternative they could think of to find the solution to allow two essentially incompatible OS'es and their really incompatible filesystems to coexist and operate where they were never intended to by Apple.

This is just one more of many, many issues that have occurred in this situation.
The solution that you are evidently to stubborn to embrace is the one you're well aware of:

Initialize the disk and install OS9 drivers, then:
Partition the disk and reinstall the OS'es then:
Enjoy your now dual-booting-without-issues Mini.

It's like a NIKE thing…… Just Do It

seems to dual boot ok using the OF startup (option at as startup). am i missing something?

if you are brave enough for OF (i am not), OF is surely an option.

but if you have an old firewire case around (and an available SSD/HD) this might be the more convenient option for the future.

(the already existing OS9 folder on your mini can simply be copied to the external drive in that case... opening the system folder once usually should bless it.)

if you go on youtube and search for electronic music from around 1993 - 2003, you can safely assume that 40-50% of those are made using classic MacOS in the one or other way.

but a /music folder for the works of the members of this board in the download server (which is what i understand you're mainly asking for) would also about time - we´re discussing that since quite a while.

seems to dual boot ok using the OF startup (option at as startup). am i missing something?

Take the external OS9 drive, boot from it, run the DiskWarrior or Norton Disk Doctor maintenance utilities and see for yourself