• Updated 2023-07-12: Hello, Guest! Welcome back, and be sure to check out this follow-up post about our outage a week or so ago.

New version of MacIPgw virtual machine (v2.3) .... now with Netatalk file sharing

mactjaap

Well-known member
NEW VERSION OF MACIPGW VIRTUAL MACHINE



Version 2.3 is now the current version of MacIPgw virtual machine. I publish it as VirtualBox Appliance. The file is a Open Virtualization Format Archive

An easy and hassle free way of getting your old Macintosh on the Internet.
Just download the MacIPgw-v2.3.ova file.
( 430MB md5sum: be5bac2a3bdbb6757ed0ebb51238109c )
Or the zip file: macipgw-2.3.ova.zip.
( 424MB md5sum f577be97de521028d660947771a7c8c8 )

and import it in VirtualBox. This is done under File / import Appliance.
Be sure that the network device is on Network Bridge Adapter. Internet Explorer recognizes the file sometimes as a .tar. Be sure to save it as a .ova!

NEW in MacIPgw virtual machine version 2.3
A BIG NEW ONE!!!!…. Netatalk file sharing (2.2.5) added.



Now out of the box AppleShare file sharing. For old school Mac and new ones. If you open the Chooser you will find the MacIPgw File Server. On this server is a volume called: MacIPgw-DISK.

Login with the macipgw credentials:
username: macipgw
passwd: macipgw
You can upload your stuff here. I also put some old Internet goodies on the disk it for sharing…
User Guest can read this volume.
There is also a volume called Public Folder. This is for guest users. You can up and download here things without login in.

And more………

  • For debugging you can see the log at /var/log/afpd.log. This log is whipped every 12 hours so your disks stays clean.
  • Even more prevention of logs flooding
  • Instructions how to login in boot up messages
  • IP address is given in boot up messages for SSH connection or debug.

Improvements from older versions are in place:

Stopping the logfiles and cron from flooding the disk. My uptime is now 16 days and counting….
– A bigger disk, 1 GB in total. So more free disk space. So you can fill your home director with 100MB or more. Also and /extra directory with nearly 200 MB free space
– gw.macip.net and mac.macip.net are now resolved by DNS
– Installed nmap for testing
– Installed aecho for testing
– Installed Bash for more comfortable shell access
– Some more old services are starting up, besides telnetd and ftpd also tftpd, finger, daytime are started. Nice for testing old MacTCP applications. For ftp login with the macipgw account with password macipgw.
– Fixed typo in start up script which gave the impression that there was an 8 to much in macipgw DNS resolver.
– web server on port 80 so you can test a web browser. Point it to http://172.16.2.1and you will see a page telling you “It works!” Uses tthttpd in /etc/rc.local for startup.
– Lynx web browser. Login with telnet user: lynx and password: lynx and you will get the text only web browser so you can surf the web. No support for https however….
– Elinks web browser. Login with telnet user: elinks and password: elinks and you will get the text only web browser so you can surf the web. And yes… support for https!
– pkg added. Makes it simple to install binary packages to you macipgw virtual machine. Use as root. Look for packages with this command:
#pkg search package_name
or for more information
# pkg search –f package_name
# pkg search apache
Will give you al the possibilities for installing apache variants. Install with
#pkg install package_name
See for more information:
https://wiki.freebsd.org/PkgPrimer

SETUP INSTALL

To set up MACIPGW, follow these steps:
•  Download and install VirtualBox. https://www.virtualbox.org/wiki/Downloads
•  Download MacIPgw-v2.3.ova virtual machine. (md5sum 43e67ecbc4c09aa1a2cc644403955133 – file size 237 MB)
•  Open VirtualBox, and choose “Import Appliance…” from the File menu. Select the file you downloaded (MacIPgw-v2.3.ova).
•  Click Import.
•  When it’s done importing, click MacipGW v2.3, then click Settings, then click Network.
•  Ensure that “Attached To:” is set to “…Bridged Adapter”.
•  Click OK.
• Start him up! Select MacipGW v2.3 and click on green arrow…Start.

DOWNLOAD:
http://cdn.macip.net/MacIPgw-v2.3.ova

 

techknight

Well-known member
Did you ever fix it so I dont have to go into the router and screw around with its tables? That would be nice. 

 

mactjaap

Well-known member
No fix. But more fun on the virtual machine is added. Just start there. I will look into this in version 2.4.

 

mikes-macs

Well-known member
So, I have MacIPgw v2.3 running in VM on Mac OS X Server 10.6.8. It's working fine.

This particular setup (mine) involves an existing Mac OS X Server with proper dns and a domain name.

The VM bridges on the internal LAN using en0 which will then use a static IP from the Mac OS X Server 192.168.17.105. Firewall settings on the Mac OS X Server will allow Apple File Services and AppleTalk Protocols.

In the VM Network settings be sure to "Allow VMs" under the "Promiscuous Mode" menu.

To create a route in Mac OS X using Terminal enter

sudo route add 172.16.2.0/25 192.168.x.x

The 192.168.x.x = the IP you want the MacIPgw to use from Mac OS X Server.

en0 on the Mac OS X Server is connected to a gigabit hub in my case, which many other devices and Macs are connected and obtain an IP from Mac OS X Server. One of the 68k Macs I have is also connected to this hub. It is a Performa 400 with a Farallon ethernet card installed. 

This Macintosh (connected to the same hub that is putting out IPs in the range of 192.168.1.x range from the Mac OS X Server's DHCP server) will get an IP address from the MacIPgw running in the VM. Open Transport is installed on this Perfoma and the TCP/IP control panel is set to use MacIP Server to get and IP automatically from the MacIPgw in the form of 172.16.2.x range. The dns server is set to 8.8.8.8 automatically and this Mac's Appletalk control panel is set to use "Ethernet". This Mac also runs Apple's LocalTalk Bridge software and has a Farallon PhoneNet Adapter connected to printer port. This PhoneNet is connect to a Mac SE/30 and the Mac SE/30 is connected to a Mac SE and the Mac SE is connected to a Powerbook 520c, then the PhoneNet is terminated.

Also connected to the very same Hub thru ethernet is an Ibook G3 running Mac OS 9.2.2 and AppleShareIP v6 and is getting an IP from the same MacIPgw in the 172.16.2.x range. 

So in each of the the choosers on all the 68k Macs, each can see each other plus they see the MacIPGW share, and the ibook. They can all use the internet either using OpenTransport or MacTCP v 2.1. The ibook also has Shareware IP Pro which allows all LocalTalk enabled 68k Macs to be multi-homed over Appletalk thus allowing any Modern Mac to login into any 68 Mac on the PhoneNet network using the ibook's IP plus the corresponding port number which was setup in Shareware IP. ie. 172.16.2.3:18 would resolve to Mac SE/30. Using Mac OS X Connect to Server menu.

If I find an inexpensive PowerPC with LocalTalk ports and ethernet to replace the Perfoma400 task of being the LocalTalk to AppleTalk bridge, things would probably speed up and that same Mac can also run the Shareway IP software which requires a PPC. 

I loaded SheepShaver emulator and added it to the MacIPgw too and that can get the internet as well.

Thanks for the update on this Gateway, it's great!!

 

mikes-macs

Well-known member
I meant to mention that all the 68k Macs that are connected to this MacIPgw network thru PhoneNet that are running OpenTransport have their TCP/IP settings setup using:

Connect Via: AppleTalk(MacIP)

Configure: Using MacIP Server

The 68k Macs that are not using OpenTransport have their MacTCP v 2.1 settings setup manually

Give it an IP in the 172.16.2.x range from the MacIPgw

subnet mask = 255.255.255.0

router address = 172.16.2.1

Domain name Server Information:

Enter a period for the first space in Domain

Enter 172.16.2.1 for the IP Address

Restart Classic networked Macs to make changes and then on reboot it should be on the internet.

 

mactjaap

Well-known member
Thanks for your detailed setup. I will study on it and use your input for new versions. I'm still not happy that on some network situation you don't have direct internet connection. In yours it seems to work OK. I also like to add Samba windows file sharing.

 
Top